RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '910438-2072178', '/home/buildd/filecache-default/d2274dc817bfb38268428dd7a696094ae85a7255'] Synching the system clock with the buildd NTP service... 18 Mar 23:46:48 ntpdate[6087]: adjust time server 10.211.37.1 offset -0.000059 sec Unpacking chroot for build 910438-2072178 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '910438-2072178'] Mounting chroot for build 910438-2072178 RUN: /usr/share/launchpad-buildd/slavebin/apply-ogre-model ['apply-ogre-model', '910438-2072178', 'universe'] Attempting OGRE for universe in build-910438-2072178 RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '910438-2072178', 'deb http://ftpmaster.internal/ubuntu jaunty main universe'] Overriding sources.list in build-910438-2072178 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '910438-2072178'] Updating debian chroot for build 910438-2072178 Get:1 http://ftpmaster.internal jaunty Release.gpg [189B] Get:2 http://ftpmaster.internal jaunty Release [74.6kB] Get:3 http://ftpmaster.internal jaunty/main Packages [1238kB] Get:4 http://ftpmaster.internal jaunty/universe Packages [4632kB] Fetched 5945kB in 3s (1772kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: libgmp3c2 libmpfr1ldbl The following packages will be upgraded: base-passwd cpp-4.3 g++-4.3 gcc-4.3 gcc-4.3-base initscripts libgcc1 libgomp1 libpam-foreground libsepol1 libstdc++6 libstdc++6-4.3-dev linux-libc-dev login passwd pkgbinarymangler python2.6-minimal sysv-rc sysvinit-utils tzdata zlib1g 21 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 870kB/16.5MB of archives. After this operation, 41.7MB disk space will be freed. WARNING: The following packages cannot be authenticated! login base-passwd libsepol1 sysvinit-utils libgomp1 gcc-4.3-base libstdc++6 libgmp3c2 libmpfr1ldbl cpp-4.3 gcc-4.3 g++-4.3 libstdc++6-4.3-dev libgcc1 passwd zlib1g python2.6-minimal tzdata initscripts sysv-rc libpam-foreground linux-libc-dev pkgbinarymangler Authentication warning overridden. Get:1 http://ftpmaster.internal jaunty/main libsepol1 2.0.30-2ubuntu1 [113kB] Get:2 http://ftpmaster.internal jaunty/main linux-libc-dev 2.6.28-11.35 [756kB] Preconfiguring packages ... Fetched 870kB in 0s (28.6MB/s) dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace login 1:4.1.1-6ubuntu2 (using .../login_1%3a4.1.1-6ubuntu3_lpia.deb) ... Unpacking replacement login ... Setting up login (1:4.1.1-6ubuntu3) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace base-passwd 3.5.19 (using .../base-passwd_3.5.21_lpia.deb) ... Unpacking replacement base-passwd ... Setting up base-passwd (3.5.21) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace libsepol1 2.0.30-2 (using .../libsepol1_2.0.30-2ubuntu1_lpia.deb) ... Unpacking replacement libsepol1 ... Setting up libsepol1 (2.0.30-2ubuntu1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace sysvinit-utils 2.86.ds1-61ubuntu8 (using .../sysvinit-utils_2.86.ds1-61ubuntu9_lpia.deb) ... Unpacking replacement sysvinit-utils ... Setting up sysvinit-utils (2.86.ds1-61ubuntu9) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace libgomp1 4.3.3-5ubuntu3 (using .../libgomp1_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement libgomp1 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace gcc-4.3-base 4.3.3-5ubuntu3 (using .../gcc-4.3-base_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement gcc-4.3-base ... Setting up gcc-4.3-base (4.3.3-5ubuntu4) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9141 files and directories currently installed.) Preparing to replace libstdc++6 4.3.3-5ubuntu3 (using .../libstdc++6_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement libstdc++6 ... Setting up libstdc++6 (4.3.3-5ubuntu4) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgmp3c2. (Reading database ... 9141 files and directories currently installed.) Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.2.4+dfsg-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmpfr1ldbl. Unpacking libmpfr1ldbl (from .../libmpfr1ldbl_2.4.0-1ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace cpp-4.3 4.3.3-5ubuntu3 (using .../cpp-4.3_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement cpp-4.3 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace gcc-4.3 4.3.3-5ubuntu3 (using .../gcc-4.3_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement gcc-4.3 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace g++-4.3 4.3.3-5ubuntu3 (using .../g++-4.3_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement g++-4.3 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libstdc++6-4.3-dev 4.3.3-5ubuntu3 (using .../libstdc++6-4.3-dev_4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement libstdc++6-4.3-dev ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libgcc1 1:4.3.3-5ubuntu3 (using .../libgcc1_1%3a4.3.3-5ubuntu4_lpia.deb) ... Unpacking replacement libgcc1 ... Setting up libgcc1 (1:4.3.3-5ubuntu4) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9164 files and directories currently installed.) Preparing to replace passwd 1:4.1.1-6ubuntu2 (using .../passwd_1%3a4.1.1-6ubuntu3_lpia.deb) ... Unpacking replacement passwd ... Setting up passwd (1:4.1.1-6ubuntu3) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9164 files and directories currently installed.) Preparing to replace zlib1g 1:1.2.3.3.dfsg-12ubuntu1 (using .../zlib1g_1%3a1.2.3.3.dfsg-12ubuntu2_lpia.deb) ... Unpacking replacement zlib1g ... Setting up zlib1g (1:1.2.3.3.dfsg-12ubuntu2) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9164 files and directories currently installed.) Preparing to replace python2.6-minimal 2.6.1-1ubuntu1 (using .../python2.6-minimal_2.6.1-1ubuntu3_lpia.deb) ... Unpacking replacement python2.6-minimal ... Setting up python2.6-minimal (2.6.1-1ubuntu3) ... Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] (Reading database ... 9164 files and directories currently installed.) Preparing to replace tzdata 2009b-1 (using .../tzdata_2009c-1_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2009c-1) ... Current default timezone: 'Etc/UTC' Local time is now: Wed Mar 18 23:47:18 UTC 2009. Universal Time is now: Wed Mar 18 23:47:18 UTC 2009. Run 'dpkg-reconfigure tzdata' if you wish to change it. dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9164 files and directories currently installed.) Preparing to replace initscripts 2.86.ds1-61ubuntu8 (using .../initscripts_2.86.ds1-61ubuntu9_lpia.deb) ... Unpacking replacement initscripts ... Preparing to replace sysv-rc 2.86.ds1-61ubuntu8 (using .../sysv-rc_2.86.ds1-61ubuntu9_all.deb) ... Unpacking replacement sysv-rc ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libpam-foreground 0.4-1 (using .../libpam-foreground_0.5_lpia.deb) ... Unpacking replacement libpam-foreground ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace linux-libc-dev 2.6.28-10.32 (using .../linux-libc-dev_2.6.28-11.35_lpia.deb) ... Unpacking replacement linux-libc-dev ... Preparing to replace pkgbinarymangler 53 (using .../pkgbinarymangler_55_all.deb) ... Unpacking replacement pkgbinarymangler ... Setting up libgomp1 (4.3.3-5ubuntu4) ... Setting up libgmp3c2 (2:4.2.4+dfsg-2ubuntu1) ... Setting up libmpfr1ldbl (2.4.0-1ubuntu3) ... Setting up cpp-4.3 (4.3.3-5ubuntu4) ... Setting up gcc-4.3 (4.3.3-5ubuntu4) ... Setting up initscripts (2.86.ds1-61ubuntu9) ... Setting up sysv-rc (2.86.ds1-61ubuntu9) ... Setting up libpam-foreground (0.5) ... Setting up linux-libc-dev (2.6.28-11.35) ... Setting up pkgbinarymangler (55) ... Setting up libstdc++6-4.3-dev (4.3.3-5ubuntu4) ... Setting up g++-4.3 (4.3.3-5ubuntu4) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', '910438-2072178', '--nolog', '--batch', '--archive=ubuntu', '--purpose=PRIMARY', '--dist=jaunty', '--comp=universe', 'cheese_2.26.0-0ubuntu1.dsc'] Initiating build Automatic build of cheese_2.26.0-0ubuntu1 on molybdenum by sbuild/lpia 1.170.5 Build started at 20090318-2347 ****************************************************************************** cheese_2.26.0-0ubuntu1.dsc exists in cwd ** Using build dependencies supplied by package: Build-Depends: cdbs (>= 0.4.41), debhelper (>= 5), gnome-pkg-tools (>= 0.10), libglib2.0-dev (>= 2.16.0), libpango1.0-dev (>= 1.18.0), librsvg2-dev (>= 2.18.0), libgtk2.0-dev (>= 2.14.0), libgnome-desktop-dev (>= 2.25.1), libgconf2-4 (>= 2.16.0), libgstreamer0.10-dev (>= 0.10.20), libgstreamer-plugins-base0.10-dev, libcairo2-dev (>= 1.4.0), libebook1.2-dev (>= 1.12.0), libdbus-1-dev (>= 1.0), libhal-dev (>= 0.5.9), libdbus-glib-1-dev (>= 0.7), libhildon-1-dev, libxml-parser-perl, scrollkeeper, gnome-doc-utils Checking for already installed source dependencies... cdbs: missing debhelper: missing gnome-pkg-tools: missing libglib2.0-dev: missing libpango1.0-dev: missing librsvg2-dev: missing libgtk2.0-dev: missing libgnome-desktop-dev: missing libgconf2-4: missing libgstreamer0.10-dev: missing libgstreamer-plugins-base0.10-dev: missing libcairo2-dev: missing libebook1.2-dev: missing libdbus-1-dev: missing libhal-dev: missing libdbus-glib-1-dev: missing libhildon-1-dev: missing libxml-parser-perl: missing scrollkeeper: missing gnome-doc-utils: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install cdbs debhelper gnome-pkg-tools libglib2.0-dev libpango1.0-dev librsvg2-dev libgtk2.0-dev libgnome-desktop-dev libgconf2-4 libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libcairo2-dev libebook1.2-dev libdbus-1-dev libhal-dev libdbus-glib-1-dev libhildon-1-dev libxml-parser-perl scrollkeeper gnome-doc-utils Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: adduser autoconf automake autotools-dev bsdmainutils check consolekit dbus defoma docbook-xml esound-common fdupes file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-mime-data groff-base html2text intltool intltool-debian libasound2 libatk1.0-0 libatk1.0-dev libaudiofile-dev libaudiofile0 libavahi-client-dev libavahi-client3 libavahi-common-data libavahi-common-dev libavahi-common3 libavahi-glib-dev libavahi-glib1 libbonobo2-0 libbonobo2-common libbonobo2-dev libcairo2 libcamel1.2-14 libcroco3 libdatrie0 libdbus-1-3 libdbus-glib-1-2 libdirectfb-1.0-0 libdirectfb-dev libdirectfb-extra libebook1.2-9 libedataserver1.2-11 libedataserver1.2-dev libesd-alsa0 libesd0-dev libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgamin0 libgconf2-dev libgcrypt11 libgcrypt11-dev libglib2.0-0 libgnome-desktop-2-11 libgnome2-0 libgnome2-common libgnome2-dev libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-dev libgnutls-dev libgnutls26 libgpg-error-dev libgpg-error0 libgsf-1-114 libgsf-1-common libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libgtk2.0-0 libgtk2.0-common libhal-storage1 libhal1 libhildon-1-0 libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjpeg62 libjpeg62-dev libkeyutils1 libkrb53 libmagic1 libncursesw5 libnewt0.52 libnspr4-0d libnspr4-dev libnss3-1d liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-dbus2 libpolkit2 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libreadline5 librsvg2-2 libscrollkeeper0 libselinux1-dev libsepol1-dev libsm-dev libsm6 libsmbios2 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libssl0.9.8 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libtasn1-3 libtasn1-3-dev libthai-data libthai0 libts-0.0-0 liburi-perl libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxslt1.1 m4 man-db mime-support netbase pkg-config po-debconf psmisc python python-libxml2 python-support python2.6 readline-common sgml-base sgml-data shared-mime-info ttf-dejavu ttf-dejavu-core ttf-dejavu-extra ucf whiptail x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xml-core xsltproc xtrans-dev zlib1g-dev Suggested packages: liblocale-gettext-perl ecryptfs-utils autoconf2.13 autobook autoconf-archive gnu-standards autoconf-doc libtool wamerican wordlist whois vacation devscripts doc-base dh-make defoma-doc psfontmgr x-ttcidfont-conf dfontmgr libft-perl docbook docbook-dsssl docbook-xsl docbook-defguide cvs gettext-doc svn-buildpackage groff libasound2-plugins libbonobo2-bin libcairo2-doc esound rng-tools libgcrypt11-doc libglib2.0-doc desktop-base libgnome2-doc libgnomevfs2-bin gnutls-doc gnutls-bin guile-gnutls libvisual-0.4-plugins gstreamer-codec-install gnome-codec-install gstreamer0.10-tools gstreamer0.10-plugins gstreamer0.10-doc librsvg2-common libgtk2.0-doc hal-doc libdata-dump-perl krb5-doc krb5-user ttf-japanese-gothic ttf-japanese-mincho ttf-thryomanes ttf-baekmuk ttf-arphic-gbsn00lp ttf-arphic-bsmi00lp ttf-arphic-gkai00mp ttf-arphic-bkai00mp libpango1.0-doc imagemagick librsvg2-bin libsmbios-doc libsoup2.4-doc libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python-libxml2-dbg python2.6-doc python2.6-profiler logrotate sgml-base-doc perlsgml doc-html-w3 opensp Recommended packages: libpam-ck-connector dbus-x11 curl wget lynx libatk1.0-data esound-clients libglib2.0-data gvfs libgnomevfs2-extra gnome-mount hicolor-icon-theme libgtk2.0-bin libgpm2 libfribidi0 orbit2 libmailtools-perl libhtml-format-perl libcompress-zlib-perl ifupdown libmail-sendmail-perl The following NEW packages will be installed: adduser autoconf automake autotools-dev bsdmainutils cdbs check consolekit dbus debhelper defoma docbook-xml esound-common fdupes file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-doc-utils gnome-mime-data gnome-pkg-tools groff-base html2text intltool intltool-debian libasound2 libatk1.0-0 libatk1.0-dev libaudiofile-dev libaudiofile0 libavahi-client-dev libavahi-client3 libavahi-common-data libavahi-common-dev libavahi-common3 libavahi-glib-dev libavahi-glib1 libbonobo2-0 libbonobo2-common libbonobo2-dev libcairo2 libcairo2-dev libcamel1.2-14 libcroco3 libdatrie0 libdbus-1-3 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdirectfb-1.0-0 libdirectfb-dev libdirectfb-extra libebook1.2-9 libebook1.2-dev libedataserver1.2-11 libedataserver1.2-dev libesd-alsa0 libesd0-dev libexpat1 libexpat1-dev libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgamin0 libgconf2-4 libgconf2-dev libgcrypt11 libgcrypt11-dev libglib2.0-0 libglib2.0-dev libgnome-desktop-2-11 libgnome-desktop-dev libgnome2-0 libgnome2-common libgnome2-dev libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-dev libgnutls-dev libgnutls26 libgpg-error-dev libgpg-error0 libgsf-1-114 libgsf-1-common libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base0.10-dev libgstreamer0.10-0 libgstreamer0.10-dev libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libhal-dev libhal-storage1 libhal1 libhildon-1-0 libhildon-1-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libjpeg62 libjpeg62-dev libkeyutils1 libkrb53 libmagic1 libncursesw5 libnewt0.52 libnspr4-0d libnspr4-dev libnss3-1d liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-dbus2 libpolkit2 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libreadline5 librsvg2-2 librsvg2-dev libscrollkeeper0 libselinux1-dev libsepol1-dev libsm-dev libsm6 libsmbios2 libsoup2.4-1 libsoup2.4-dev libsqlite3-0 libssl0.9.8 libstartup-notification0 libstartup-notification0-dev libsysfs-dev libsysfs2 libtasn1-3 libtasn1-3-dev libthai-data libthai0 libts-0.0-0 liburi-perl libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxcb-render-util0 libxcb-render-util0-dev libxcb-render0 libxcb-render0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxslt1.1 m4 man-db mime-support netbase pkg-config po-debconf psmisc python python-libxml2 python-support python2.6 readline-common scrollkeeper sgml-base sgml-data shared-mime-info ttf-dejavu ttf-dejavu-core ttf-dejavu-extra ucf whiptail x11-common x11proto-composite-dev x11proto-core-dev x11proto-damage-dev x11proto-fixes-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev x11proto-render-dev x11proto-xext-dev x11proto-xinerama-dev xml-core xsltproc xtrans-dev zlib1g-dev 0 upgraded, 231 newly installed, 0 to remove and 0 not upgraded. Need to get 1956kB/63.4MB of archives. After this operation, 249MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! x11-common sgml-base xml-core sgml-data docbook-xml libice6 x11proto-core-dev libice-dev libsm6 libsm-dev libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev libxext6 libxfixes3 libxcomposite1 x11proto-xext-dev x11proto-fixes-dev libxfixes-dev x11proto-composite-dev libxext-dev libxcomposite-dev libxrender1 libxcursor1 x11proto-render-dev libxrender-dev libxcursor-dev libxdamage1 x11proto-damage-dev libxdamage-dev libexpat1 libfreetype6 ucf libnewt0.52 libpopt0 whiptail libmagic1 file defoma ttf-dejavu-core ttf-dejavu-extra ttf-dejavu fontconfig-config libfontconfig1 libxft2 libexpat1-dev zlib1g-dev libfreetype6-dev libglib2.0-0 pkg-config libfontconfig1-dev libxft-dev libxi6 libxi-dev libxinerama1 x11proto-xinerama-dev libxinerama-dev libxrandr2 x11proto-randr-dev libxrandr-dev adduser libgpg-error0 libgcrypt11 libtasn1-3 libgnutls26 libkeyutils1 libkrb53 libncursesw5 readline-common libreadline5 libsqlite3-0 libssl0.9.8 mime-support netbase python2.6 python bsdmainutils gettext-base groff-base libhtml-tagset-perl liburi-perl libhtml-parser-perl libhtml-tree-perl libwww-perl libxml-parser-perl libxml2 man-db psmisc python-support m4 autoconf autotools-dev automake html2text libcroco3 gettext intltool-debian po-debconf debhelper fdupes intltool cdbs check libdbus-1-3 dbus consolekit esound-common fontconfig libgamin0 gamin libdbus-glib-1-2 libidl0 liborbit2 libpolkit2 libpolkit-dbus2 gconf2-common libgconf2-4 gconf2 python-libxml2 libxml2-utils libxslt1.1 xsltproc gnome-doc-utils gnome-mime-data gnome-pkg-tools libasound2 libatk1.0-0 libglib2.0-dev libatk1.0-dev libaudiofile0 libaudiofile-dev libavahi-common-data libavahi-common3 libavahi-client3 libavahi-common-dev libdbus-1-dev libavahi-client-dev libavahi-glib1 libavahi-glib-dev libbonobo2-common libbonobo2-0 libidl-dev liborbit2-dev libpopt-dev libbonobo2-dev libsysfs2 libts-0.0-0 libdirectfb-1.0-0 libpixman-1-0 libpng12-0 libxcb-render0 libxcb-render-util0 libcairo2 libpng12-dev libjpeg62 libdirectfb-extra libjpeg62-dev libsysfs-dev libdirectfb-dev libpixman-1-dev libxcb-render0-dev libxcb-render-util0-dev libcairo2-dev libnspr4-0d libsoup2.4-1 libedataserver1.2-11 libnss3-1d libcamel1.2-14 libdatrie0 libdbus-glib-1-dev libebook1.2-9 libesd-alsa0 libsmbios2 libhal1 libhal-storage1 shared-mime-info libgnomevfs2-common libgnomevfs2-0 libgnome2-common libgnome2-0 libgconf2-dev libgpg-error-dev libgcrypt11-dev libtasn1-3-dev libgnutls-dev libxml2-dev libsepol1-dev libselinux1-dev libgnomevfs2-dev libesd0-dev libgnome2-dev libnspr4-dev libsoup2.4-dev libedataserver1.2-dev libebook1.2-dev libgtk2.0-common libgtk2.0-0 libstartup-notification0 libgnome-desktop-2-11 libpango1.0-common libthai-data libthai0 libpango1.0-0 libpango1.0-dev libgtk2.0-dev libstartup-notification0-dev libgnome-desktop-dev libgsf-1-common libgsf-1-114 libgstreamer0.10-0 libgstreamer-plugins-base0.10-0 libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev libhal-dev libhildon-1-0 libhildon-1-dev librsvg2-2 librsvg2-dev libscrollkeeper0 scrollkeeper Authentication warning overridden. Get:1 http://ftpmaster.internal jaunty/main fontconfig-config 2.6.0-1ubuntu11 [51.5kB] Get:2 http://ftpmaster.internal jaunty/main libfontconfig1 2.6.0-1ubuntu11 [117kB] Get:3 http://ftpmaster.internal jaunty/main libfontconfig1-dev 2.6.0-1ubuntu11 [575kB] Get:4 http://ftpmaster.internal jaunty/main fontconfig 2.6.0-1ubuntu11 [137kB] Get:5 http://ftpmaster.internal jaunty/main libgnome2-common 2.26.0-0ubuntu1 [39.4kB] Get:6 http://ftpmaster.internal jaunty/main libgnome2-0 2.26.0-0ubuntu1 [66.4kB] Get:7 http://ftpmaster.internal jaunty/main libsepol1-dev 2.0.30-2ubuntu1 [522kB] Get:8 http://ftpmaster.internal jaunty/main libgnome2-dev 2.26.0-0ubuntu1 [50.9kB] Get:9 http://ftpmaster.internal jaunty/main libhildon-1-0 2.0.1-1ubuntu7 [142kB] Get:10 http://ftpmaster.internal jaunty/main libhildon-1-dev 2.0.1-1ubuntu7 [23.1kB] Get:11 http://ftpmaster.internal jaunty/main librsvg2-2 2.26.0-0ubuntu1 [105kB] Get:12 http://ftpmaster.internal jaunty/main librsvg2-dev 2.26.0-0ubuntu1 [127kB] dpkg-preconfigure: unable to re-open stdin: Fetched 1956kB in 0s (25.7MB/s) Selecting previously deselected package x11-common. (Reading database ... 9167 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.4~5ubuntu16_all.deb) ... Selecting previously deselected package sgml-base. Unpacking sgml-base (from .../sgml-base_1.26_all.deb) ... Selecting previously deselected package xml-core. Unpacking xml-core (from .../archives/xml-core_0.12_all.deb) ... Selecting previously deselected package sgml-data. Unpacking sgml-data (from .../sgml-data_2.0.3_all.deb) ... Setting up sgml-base (1.26) ... Setting up xml-core (0.12) ... Selecting previously deselected package docbook-xml. (Reading database ... 9481 files and directories currently installed.) Unpacking docbook-xml (from .../docbook-xml_4.5-6_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.4-1_lpia.deb) ... Setting up x11-common (1:7.4~5ubuntu16) ... Selecting previously deselected package x11proto-core-dev. (Reading database ... 9642 files and directories currently installed.) Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.14-2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libice-dev. Unpacking libice-dev (from .../libice-dev_2%3a1.0.4-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.1.0-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.1.0-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.4-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.2-3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.1.93-0ubuntu3_lpia.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.1.99.2-1ubuntu2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.1.99.2-1ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.4-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.0.2-3_lpia.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_1.5.0-1ubuntu1_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.3-3ubuntu1_all.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.3-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.1-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.1-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.1.93-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.1.99.2-1ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.0.99.1-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.3-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.0-3_lpia.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.0.4-1_all.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.0-3_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.3-2_lpia.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4-2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.0.99.1-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.0-3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.4-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.9-1_lpia.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.9.3-2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.4-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.9-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.1-4_lpia.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.1.0-2build1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.1-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.9-4_lpia.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0014_all.deb) ... Moving old data out of the way dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnewt0.52. Unpacking libnewt0.52 (from .../libnewt0.52_0.52.2-11.3ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.14-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package whiptail. Unpacking whiptail (from .../whiptail_0.52.2-11.3ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_4.26-2ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package file. Unpacking file (from .../file_4.26-2ubuntu3_lpia.deb) ... Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.10-0.2ubuntu1_all.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.28-1_all.deb) ... Selecting previously deselected package ttf-dejavu-extra. Unpacking ttf-dejavu-extra (from .../ttf-dejavu-extra_2.28-1_all.deb) ... Selecting previously deselected package ttf-dejavu. Unpacking ttf-dejavu (from .../ttf-dejavu_2.28-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.6.0-1ubuntu11_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.6.0-1ubuntu11_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.1.13-3ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.3.dfsg-12ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.3.9-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.20.0-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.22-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.6.0-1ubuntu11_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.1.13-3ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.2.0-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.2.0-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.0.3-2_lpia.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.1.2-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.0.3-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.0-1_lpia.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.3.0-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.0-1_lpia.deb) ... Selecting previously deselected package adduser. Unpacking adduser (from .../adduser_3.110ubuntu2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgpg-error0. Unpacking libgpg-error0 (from .../libgpg-error0_1.4-2ubuntu7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgcrypt11. Unpacking libgcrypt11 (from .../libgcrypt11_1.4.1-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtasn1-3. Unpacking libtasn1-3 (from .../libtasn1-3_1.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnutls26. Unpacking libgnutls26 (from .../libgnutls26_2.4.2-6_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libkeyutils1. Unpacking libkeyutils1 (from .../libkeyutils1_1.2-9_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libkrb53. Unpacking libkrb53 (from .../libkrb53_1.6.dfsg.4~beta1-5ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libncursesw5. Unpacking libncursesw5 (from .../libncursesw5_5.7+20090207-1ubuntu1_lpia.deb) ... Selecting previously deselected package readline-common. Unpacking readline-common (from .../readline-common_5.2-4_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libreadline5. Unpacking libreadline5 (from .../libreadline5_5.2-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.10-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libssl0.9.8. Unpacking libssl0.9.8 (from .../libssl0.9.8_0.9.8g-15ubuntu1_lpia.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.44-1_all.deb) ... Selecting previously deselected package netbase. Unpacking netbase (from .../netbase_4.34ubuntu2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package python2.6. Unpacking python2.6 (from .../python2.6_2.6.1-1ubuntu3_lpia.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.1-0ubuntu3_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_6.1.10ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.17-6ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.18.1.1-22_lpia.deb) ... Selecting previously deselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.37+dfsg-1ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.59-1ubuntu1_lpia.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_3.23-1_all.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.820-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.6.32.dfsg-5ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.6-1_lpia.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_0.8.7ubuntu2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.11-1_lpia.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.63-2ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20080123.2_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.10.2-0ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.1-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.17-6ubuntu2_lpia.deb) ... Selecting previously deselected package intltool-debian. Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710.1_all.deb) ... Selecting previously deselected package po-debconf. Unpacking po-debconf (from .../po-debconf_1.0.15ubuntu1_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_7.0.17ubuntu4_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package fdupes. Unpacking fdupes (from .../fdupes_1.50-PR2-1_lpia.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.40.6-1_all.deb) ... Selecting previously deselected package cdbs. Unpacking cdbs (from .../cdbs_0.4.52ubuntu17_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package check. Unpacking check (from .../check_0.9.5-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdbus-1-3. Unpacking libdbus-1-3 (from .../libdbus-1-3_1.2.12-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package dbus. Unpacking dbus (from .../dbus_1.2.12-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package consolekit. Unpacking consolekit (from .../consolekit_0.3.0-2ubuntu1_lpia.deb) ... Selecting previously deselected package esound-common. Unpacking esound-common (from .../esound-common_0.2.40-0ubuntu3_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.6.0-1ubuntu11_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgamin0. Unpacking libgamin0 (from .../libgamin0_0.1.9-2ubuntu4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gamin. Unpacking gamin (from .../gamin_0.1.9-2ubuntu4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.80-3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.11-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.17-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpolkit2. Unpacking libpolkit2 (from .../libpolkit2_0.9-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpolkit-dbus2. Unpacking libpolkit-dbus2 (from .../libpolkit-dbus2_0.9-2ubuntu1_lpia.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.26.0-0ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package python-libxml2. Unpacking python-libxml2 (from .../python-libxml2_2.6.32.dfsg-5ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.6.32.dfsg-5ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.24-2ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package xsltproc. Unpacking xsltproc (from .../xsltproc_1.1.24-2ubuntu2_lpia.deb) ... Selecting previously deselected package gnome-doc-utils. Unpacking gnome-doc-utils (from .../gnome-doc-utils_0.16.0-0ubuntu1_all.deb) ... Selecting previously deselected package gnome-mime-data. Unpacking gnome-mime-data (from .../gnome-mime-data_2.18.0-1_all.deb) ... Selecting previously deselected package gnome-pkg-tools. Unpacking gnome-pkg-tools (from .../gnome-pkg-tools_0.14ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libasound2. Unpacking libasound2 (from .../libasound2_1.0.18-1ubuntu7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.26.0-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.20.0-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.26.0-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libaudiofile0. Unpacking libaudiofile0 (from .../libaudiofile0_0.2.6-7ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libaudiofile-dev. Unpacking libaudiofile-dev (from .../libaudiofile-dev_0.2.6-7ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-common-dev. Unpacking libavahi-common-dev (from .../libavahi-common-dev_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.2.12-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-client-dev. Unpacking libavahi-client-dev (from .../libavahi-client-dev_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-glib1. Unpacking libavahi-glib1 (from .../libavahi-glib1_0.6.23-4ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavahi-glib-dev. Unpacking libavahi-glib-dev (from .../libavahi-glib-dev_0.6.23-4ubuntu3_lpia.deb) ... Selecting previously deselected package libbonobo2-common. Unpacking libbonobo2-common (from .../libbonobo2-common_2.24.1-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libbonobo2-0. Unpacking libbonobo2-0 (from .../libbonobo2-0_2.24.1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.11-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.17-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpopt-dev. Unpacking libpopt-dev (from .../libpopt-dev_1.14-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libbonobo2-dev. Unpacking libbonobo2-dev (from .../libbonobo2-dev_2.24.1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsysfs2. Unpacking libsysfs2 (from .../libsysfs2_2.1.0-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libts-0.0-0. Unpacking libts-0.0-0 (from .../libts-0.0-0_1.0-4ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdirectfb-1.0-0. Unpacking libdirectfb-1.0-0 (from .../libdirectfb-1.0-0_1.0.1-11ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.13.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpng12-0. Unpacking libpng12-0 (from .../libpng12-0_1.2.27-2ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.1.93-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb-render-util0. Unpacking libxcb-render-util0 (from .../libxcb-render-util0_0.2.1+git1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.8.6-1ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.27-2ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b-14_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdirectfb-extra. Unpacking libdirectfb-extra (from .../libdirectfb-extra_1.0.1-11ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libjpeg62-dev. Unpacking libjpeg62-dev (from .../libjpeg62-dev_6b-14_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsysfs-dev. Unpacking libsysfs-dev (from .../libsysfs-dev_2.1.0-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdirectfb-dev. Unpacking libdirectfb-dev (from .../libdirectfb-dev_1.0.1-11ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.13.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.1.93-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxcb-render-util0-dev. Unpacking libxcb-render-util0-dev (from .../libxcb-render-util0-dev_0.2.1+git1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.8.6-1ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnspr4-0d. Unpacking libnspr4-0d (from .../libnspr4-0d_4.7.3-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsoup2.4-1. Unpacking libsoup2.4-1 (from .../libsoup2.4-1_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libedataserver1.2-11. Unpacking libedataserver1.2-11 (from .../libedataserver1.2-11_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnss3-1d. Unpacking libnss3-1d (from .../libnss3-1d_3.12.2~rc1-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcamel1.2-14. Unpacking libcamel1.2-14 (from .../libcamel1.2-14_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdatrie0. Unpacking libdatrie0 (from .../libdatrie0_0.1.3-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.80-3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libebook1.2-9. Unpacking libebook1.2-9 (from .../libebook1.2-9_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libesd-alsa0. Unpacking libesd-alsa0 (from .../libesd-alsa0_0.2.40-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsmbios2. Unpacking libsmbios2 (from .../libsmbios2_2.2.13-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhal1. Unpacking libhal1 (from .../libhal1_0.5.12~rc1+git20090204-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhal-storage1. Unpacking libhal-storage1 (from .../libhal-storage1_0.5.12~rc1+git20090204-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.60-1_lpia.deb) ... Selecting previously deselected package libgnomevfs2-common. Unpacking libgnomevfs2-common (from .../libgnomevfs2-common_1%3a2.24.1-0ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnomevfs2-0. Unpacking libgnomevfs2-0 (from .../libgnomevfs2-0_1%3a2.24.0-1ubuntu3_lpia.deb) ... Selecting previously deselected package libgnome2-common. Unpacking libgnome2-common (from .../libgnome2-common_2.26.0-0ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnome2-0. Unpacking libgnome2-0 (from .../libgnome2-0_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgpg-error-dev. Unpacking libgpg-error-dev (from .../libgpg-error-dev_1.4-2ubuntu7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgcrypt11-dev. Unpacking libgcrypt11-dev (from .../libgcrypt11-dev_1.4.1-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtasn1-3-dev. Unpacking libtasn1-3-dev (from .../libtasn1-3-dev_1.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnutls-dev. Unpacking libgnutls-dev (from .../libgnutls-dev_2.4.2-6_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxml2-dev. Unpacking libxml2-dev (from .../libxml2-dev_2.6.32.dfsg-5ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsepol1-dev. Unpacking libsepol1-dev (from .../libsepol1-dev_2.0.30-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libselinux1-dev. Unpacking libselinux1-dev (from .../libselinux1-dev_2.0.65-5build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnomevfs2-dev. Unpacking libgnomevfs2-dev (from .../libgnomevfs2-dev_1%3a2.24.0-1ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libesd0-dev. Unpacking libesd0-dev (from .../libesd0-dev_0.2.40-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnome2-dev. Unpacking libgnome2-dev (from .../libgnome2-dev_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnspr4-dev. Unpacking libnspr4-dev (from .../libnspr4-dev_4.7.3-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsoup2.4-dev. Unpacking libsoup2.4-dev (from .../libsoup2.4-dev_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libedataserver1.2-dev. Unpacking libedataserver1.2-dev (from .../libedataserver1.2-dev_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libebook1.2-dev. Unpacking libebook1.2-dev (from .../libebook1.2-dev_2.26.0-0ubuntu1_lpia.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.16.0-1ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.16.0-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.9-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnome-desktop-2-11. Unpacking libgnome-desktop-2-11 (from .../libgnome-desktop-2-11_1%3a2.26.0-0ubuntu1_lpia.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.22.4-1_all.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.9-4_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.9-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.22.4-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.22.4-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.16.0-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libstartup-notification0-dev. Unpacking libstartup-notification0-dev (from .../libstartup-notification0-dev_0.9-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnome-desktop-dev. Unpacking libgnome-desktop-dev (from .../libgnome-desktop-dev_1%3a2.26.0-0ubuntu1_lpia.deb) ... Selecting previously deselected package libgsf-1-common. Unpacking libgsf-1-common (from .../libgsf-1-common_1.14.11-2ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgsf-1-114. Unpacking libgsf-1-114 (from .../libgsf-1-114_1.14.11-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgstreamer0.10-0. Unpacking libgstreamer0.10-0 (from .../libgstreamer0.10-0_0.10.22-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgstreamer-plugins-base0.10-0. Unpacking libgstreamer-plugins-base0.10-0 (from .../libgstreamer-plugins-base0.10-0_0.10.22-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgstreamer0.10-dev. Unpacking libgstreamer0.10-dev (from .../libgstreamer0.10-dev_0.10.22-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgstreamer-plugins-base0.10-dev. Unpacking libgstreamer-plugins-base0.10-dev (from .../libgstreamer-plugins-base0.10-dev_0.10.22-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhal-dev. Unpacking libhal-dev (from .../libhal-dev_0.5.12~rc1+git20090204-0ubuntu3_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhildon-1-0. Unpacking libhildon-1-0 (from .../libhildon-1-0_2.0.1-1ubuntu7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libhildon-1-dev. Unpacking libhildon-1-dev (from .../libhildon-1-dev_2.0.1-1ubuntu7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package librsvg2-2. Unpacking librsvg2-2 (from .../librsvg2-2_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package librsvg2-dev. Unpacking librsvg2-dev (from .../librsvg2-dev_2.26.0-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libscrollkeeper0. Unpacking libscrollkeeper0 (from .../libscrollkeeper0_0.3.14-16ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package scrollkeeper. Unpacking scrollkeeper (from .../scrollkeeper_0.3.14-16ubuntu1_lpia.deb) ... Setting up sgml-data (2.0.3) ... Setting up docbook-xml (4.5-6) ... Setting up libice6 (2:1.0.4-1) ... Setting up x11proto-core-dev (7.0.14-2) ... Setting up libice-dev (2:1.0.4-1) ... Setting up libsm6 (2:1.1.0-1) ... Setting up libsm-dev (2:1.1.0-1) ... Setting up libxau6 (1:1.0.4-1) ... Setting up libxdmcp6 (1:1.0.2-3) ... Setting up libxcb1 (1.1.93-0ubuntu3) ... Setting up libx11-data (2:1.1.99.2-1ubuntu2) ... Setting up libx11-6 (2:1.1.99.2-1ubuntu2) ... Setting up libxau-dev (1:1.0.4-1) ... Setting up libxdmcp-dev (1:1.0.2-3) ... Setting up x11proto-input-dev (1.5.0-1ubuntu1) ... Setting up x11proto-kb-dev (1.0.3-3ubuntu1) ... Setting up xtrans-dev (1.2.3-1) ... Setting up libpthread-stubs0 (0.1-2) ... Setting up libpthread-stubs0-dev (0.1-2) ... Setting up libxcb1-dev (1.1.93-0ubuntu3) ... Setting up libx11-dev (2:1.1.99.2-1ubuntu2) ... Setting up libxext6 (2:1.0.99.1-0ubuntu2) ... Setting up libxfixes3 (1:4.0.3-2) ... Setting up libxcomposite1 (1:0.4.0-3) ... Setting up x11proto-xext-dev (7.0.4-1) ... Setting up x11proto-fixes-dev (1:4.0-3) ... Setting up libxfixes-dev (1:4.0.3-2) ... Setting up x11proto-composite-dev (1:0.4-2) ... Setting up libxext-dev (2:1.0.99.1-0ubuntu2) ... Setting up libxcomposite-dev (1:0.4.0-3) ... Setting up libxrender1 (1:0.9.4-2) ... Setting up libxcursor1 (1:1.1.9-1) ... Setting up x11proto-render-dev (2:0.9.3-2) ... Setting up libxrender-dev (1:0.9.4-2) ... Setting up libxcursor-dev (1:1.1.9-1) ... Setting up libxdamage1 (1:1.1.1-4) ... Setting up x11proto-damage-dev (1:1.1.0-2build1) ... Setting up libxdamage-dev (1:1.1.1-4) ... Setting up libexpat1 (2.0.1-4) ... Setting up libfreetype6 (2.3.9-4) ... Setting up ucf (3.0014) ... Setting up libnewt0.52 (0.52.2-11.3ubuntu2) ... Setting up libpopt0 (1.14-4) ... Setting up whiptail (0.52.2-11.3ubuntu2) ... Setting up libmagic1 (4.26-2ubuntu3) ... Setting up file (4.26-2ubuntu3) ... Setting up defoma (0.11.10-0.2ubuntu1) ... Setting up ttf-dejavu-core (2.28-1) ... Setting up ttf-dejavu-extra (2.28-1) ... Setting up ttf-dejavu (2.28-1) ... Setting up fontconfig-config (2.6.0-1ubuntu11) ... Setting up libfontconfig1 (2.6.0-1ubuntu11) ... Setting up libxft2 (2.1.13-3ubuntu1) ... Setting up libexpat1-dev (2.0.1-4) ... Setting up zlib1g-dev (1:1.2.3.3.dfsg-12ubuntu2) ... Setting up libfreetype6-dev (2.3.9-4) ... Setting up libglib2.0-0 (2.20.0-1) ... Setting up pkg-config (0.22-1) ... Setting up libfontconfig1-dev (2.6.0-1ubuntu11) ... Setting up libxft-dev (2.1.13-3ubuntu1) ... Setting up libxi6 (2:1.2.0-1ubuntu1) ... Setting up libxi-dev (2:1.2.0-1ubuntu1) ... Setting up libxinerama1 (2:1.0.3-2) ... Setting up x11proto-xinerama-dev (1.1.2-5ubuntu1) ... Setting up libxinerama-dev (2:1.0.3-2) ... Setting up libxrandr2 (2:1.3.0-1) ... Setting up x11proto-randr-dev (1.3.0-1) ... Setting up libxrandr-dev (2:1.3.0-1) ... Setting up adduser (3.110ubuntu2) ... Setting up libgpg-error0 (1.4-2ubuntu7) ... Setting up libgcrypt11 (1.4.1-2ubuntu1) ... Setting up libtasn1-3 (1.5-1) ... Setting up libgnutls26 (2.4.2-6) ... Setting up libkeyutils1 (1.2-9) ... Setting up libkrb53 (1.6.dfsg.4~beta1-5ubuntu1) ... Setting up libncursesw5 (5.7+20090207-1ubuntu1) ... Setting up readline-common (5.2-4) ... Setting up libreadline5 (5.2-4) ... Setting up libsqlite3-0 (3.6.10-1) ... Setting up libssl0.9.8 (0.9.8g-15ubuntu1) ... Setting up mime-support (3.44-1) ... Setting up netbase (4.34ubuntu2) ... Setting up python2.6 (2.6.1-1ubuntu3) ... Setting up python (2.6.1-0ubuntu3) ... Setting up bsdmainutils (6.1.10ubuntu3) ... Setting up gettext-base (0.17-6ubuntu2) ... Setting up groff-base (1.18.1.1-22) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up liburi-perl (1.37+dfsg-1ubuntu1) ... Setting up libhtml-parser-perl (3.59-1ubuntu1) ... Setting up libhtml-tree-perl (3.23-1) ... Setting up libwww-perl (5.820-1) ... Setting up libxml-parser-perl (2.36-1.1build2) ... Setting up libxml2 (2.6.32.dfsg-5ubuntu3) ... Setting up man-db (2.5.5-1) ... Building database of manual pages ... ... skipping, since this is a buildd Setting up psmisc (22.6-1) ... Setting up python-support (0.8.7ubuntu2) ... Setting up m4 (1.4.11-1) ... Setting up autoconf (2.63-2ubuntu1) ... Setting up autotools-dev (20080123.2) ... Setting up automake (1:1.10.2-0ubuntu1) ... Setting up html2text (1.3.2a-5) ... Setting up libcroco3 (0.6.1-2) ... Setting up gettext (0.17-6ubuntu2) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.15ubuntu1) ... Setting up debhelper (7.0.17ubuntu4) ... Setting up fdupes (1.50-PR2-1) ... Setting up intltool (0.40.6-1) ... Setting up cdbs (0.4.52ubuntu17) ... Setting up check (0.9.5-4) ... Setting up libdbus-1-3 (1.2.12-0ubuntu2) ... Setting up esound-common (0.2.40-0ubuntu3) ... Setting up fontconfig (2.6.0-1ubuntu11) ... Updating font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating category type1.. Updating category truetype.. Updating category cid.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-dejavu Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libdbus-glib-1-2 (0.80-3) ... Setting up libidl0 (0.8.11-0.1) ... Setting up liborbit2 (1:2.14.17-0.1) ... Setting up libpolkit2 (0.9-2ubuntu1) ... Setting up libpolkit-dbus2 (0.9-2ubuntu1) ... Setting up gconf2-common (2.26.0-0ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.26.0-0ubuntu1) ... Setting up gconf2 (2.26.0-0ubuntu1) ... Setting up python-libxml2 (2.6.32.dfsg-5ubuntu3) ... Setting up libxml2-utils (2.6.32.dfsg-5ubuntu3) ... Setting up libxslt1.1 (1.1.24-2ubuntu2) ... Setting up xsltproc (1.1.24-2ubuntu2) ... Setting up gnome-doc-utils (0.16.0-0ubuntu1) ... Setting up gnome-mime-data (2.18.0-1) ... Setting up gnome-pkg-tools (0.14ubuntu1) ... Setting up libasound2 (1.0.18-1ubuntu7) ... Setting up libatk1.0-0 (1.26.0-0ubuntu2) ... Setting up libglib2.0-dev (2.20.0-1) ... Setting up libatk1.0-dev (1.26.0-0ubuntu2) ... Setting up libaudiofile0 (0.2.6-7ubuntu1) ... Setting up libaudiofile-dev (0.2.6-7ubuntu1) ... Setting up libavahi-common-data (0.6.23-4ubuntu3) ... Setting up libavahi-common3 (0.6.23-4ubuntu3) ... Setting up libavahi-client3 (0.6.23-4ubuntu3) ... Setting up libavahi-common-dev (0.6.23-4ubuntu3) ... Setting up libdbus-1-dev (1.2.12-0ubuntu2) ... Setting up libavahi-client-dev (0.6.23-4ubuntu3) ... Setting up libavahi-glib1 (0.6.23-4ubuntu3) ... Setting up libavahi-glib-dev (0.6.23-4ubuntu3) ... Setting up libbonobo2-common (2.24.1-1) ... Setting up libbonobo2-0 (2.24.1-1) ... Setting up libidl-dev (0.8.11-0.1) ... Setting up liborbit2-dev (1:2.14.17-0.1) ... Setting up libpopt-dev (1.14-4) ... Setting up libbonobo2-dev (2.24.1-1) ... Setting up libsysfs2 (2.1.0-5) ... Setting up libts-0.0-0 (1.0-4ubuntu2) ... Setting up libdirectfb-1.0-0 (1.0.1-11ubuntu1) ... Setting up libpixman-1-0 (0.13.2-1) ... Setting up libpng12-0 (1.2.27-2ubuntu2) ... Setting up libxcb-render0 (1.1.93-0ubuntu3) ... Setting up libxcb-render-util0 (0.2.1+git1-1) ... Setting up libcairo2 (1.8.6-1ubuntu2) ... Setting up libpng12-dev (1.2.27-2ubuntu2) ... Setting up libjpeg62 (6b-14) ... Setting up libdirectfb-extra (1.0.1-11ubuntu1) ... Setting up libjpeg62-dev (6b-14) ... Setting up libsysfs-dev (2.1.0-5) ... Setting up libdirectfb-dev (1.0.1-11ubuntu1) ... Setting up libpixman-1-dev (0.13.2-1) ... Setting up libxcb-render0-dev (1.1.93-0ubuntu3) ... Setting up libxcb-render-util0-dev (0.2.1+git1-1) ... Setting up libcairo2-dev (1.8.6-1ubuntu2) ... Setting up libnspr4-0d (4.7.3-0ubuntu2) ... Setting up libsoup2.4-1 (2.26.0-0ubuntu1) ... Setting up libedataserver1.2-11 (2.26.0-0ubuntu1) ... Setting up libnss3-1d (3.12.2~rc1-0ubuntu2) ... Setting up libcamel1.2-14 (2.26.0-0ubuntu1) ... Setting up libdatrie0 (0.1.3-2) ... Setting up libdbus-glib-1-dev (0.80-3) ... Setting up libebook1.2-9 (2.26.0-0ubuntu1) ... Setting up libesd-alsa0 (0.2.40-0ubuntu3) ... Setting up libsmbios2 (2.2.13-0ubuntu2) ... Setting up libhal1 (0.5.12~rc1+git20090204-0ubuntu3) ... Setting up libhal-storage1 (0.5.12~rc1+git20090204-0ubuntu3) ... Setting up shared-mime-info (0.60-1) ... Setting up libgnomevfs2-common (1:2.24.1-0ubuntu1) ... Setting up libgnome2-common (2.26.0-0ubuntu1) ... Setting up libgconf2-dev (2.26.0-0ubuntu1) ... Setting up libgpg-error-dev (1.4-2ubuntu7) ... Setting up libgcrypt11-dev (1.4.1-2ubuntu1) ... Setting up libtasn1-3-dev (1.5-1) ... Setting up libgnutls-dev (2.4.2-6) ... Setting up libxml2-dev (2.6.32.dfsg-5ubuntu3) ... Setting up libsepol1-dev (2.0.30-2ubuntu1) ... Setting up libselinux1-dev (2.0.65-5build1) ... Setting up libesd0-dev (0.2.40-0ubuntu3) ... Setting up libnspr4-dev (4.7.3-0ubuntu2) ... Setting up libsoup2.4-dev (2.26.0-0ubuntu1) ... Setting up libedataserver1.2-dev (2.26.0-0ubuntu1) ... Setting up libgtk2.0-common (2.16.0-1ubuntu1) ... Setting up libgtk2.0-0 (2.16.0-1ubuntu1) ... Setting up libstartup-notification0 (0.9-1) ... Setting up libgnome-desktop-2-11 (1:2.26.0-0ubuntu1) ... Setting up libpango1.0-common (1.22.4-1) ... Cleaning up font configuration of pango... Updating font configuration of pango... Cleaning up category xfont.. Updating category xfont.. *** You don't have any defomized font packages. *** So we are trying to force to generate pangox.aliases... Setting up libthai-data (0.1.9-4) ... Setting up libthai0 (0.1.9-4) ... Setting up libpango1.0-0 (1.22.4-1) ... Setting up libpango1.0-dev (1.22.4-1) ... Setting up libgtk2.0-dev (2.16.0-1ubuntu1) ... Setting up libstartup-notification0-dev (0.9-1) ... Setting up libgnome-desktop-dev (1:2.26.0-0ubuntu1) ... Setting up libgsf-1-common (1.14.11-2ubuntu1) ... Setting up libgsf-1-114 (1.14.11-2ubuntu1) ... Setting up libgstreamer0.10-0 (0.10.22-1) ... Setting up libgstreamer-plugins-base0.10-0 (0.10.22-4) ... Setting up libgstreamer0.10-dev (0.10.22-1) ... Setting up libgstreamer-plugins-base0.10-dev (0.10.22-4) ... Setting up libhal-dev (0.5.12~rc1+git20090204-0ubuntu3) ... Setting up libhildon-1-0 (2.0.1-1ubuntu7) ... Setting up libhildon-1-dev (2.0.1-1ubuntu7) ... Setting up librsvg2-2 (2.26.0-0ubuntu1) ... Setting up librsvg2-dev (2.26.0-0ubuntu1) ... Setting up libscrollkeeper0 (0.3.14-16ubuntu1) ... Setting up scrollkeeper (0.3.14-16ubuntu1) ... Rebuilding the database. This may take some time. Setting up consolekit (0.3.0-2ubuntu1) ... Setting up dbus (1.2.12-0ubuntu2) ... Adding system user `messagebus' (UID 101) ... Adding new group `messagebus' (GID 102) ... Adding new user `messagebus' (UID 101) with group `messagebus' ... Not creating home directory `/var/run/dbus'. * Starting system message bus dbus ...done. Setting up gamin (0.1.9-2ubuntu4) ... Setting up libgamin0 (0.1.9-2ubuntu4) ... Setting up libgnomevfs2-0 (1:2.24.0-1ubuntu3) ... Setting up libgnome2-0 (2.26.0-0ubuntu1) ... Setting up libgnomevfs2-dev (1:2.24.0-1ubuntu3) ... Setting up libgnome2-dev (2.26.0-0ubuntu1) ... Setting up libebook1.2-dev (2.26.0-0ubuntu1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place Processing triggers for python-support ... Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.9-4ubuntu2 make_3.81-5 dpkg-dev_1.14.24ubuntu1 g++-4.3_4.3.3-5ubuntu4 gcc-4.3_4.3.3-5ubuntu4 binutils_2.19.1-0ubuntu3 libstdc++6_4.3.3-5ubuntu4 libstdc++6-4.3-dev_4.3.3-5ubuntu4 ------------------------------------------------------------------------------ sh: gcc: not found dpkg-source: warning: Couldn't determine gcc system type, falling back to default (native compilation) gpg: Signature made Wed Mar 18 23:40:10 2009 GMT using DSA key ID A2D7D292 gpg: Can't check signature: public key not found dpkg-source: extracting cheese in cheese-2.26.0 dpkg-source: unpacking cheese_2.26.0.orig.tar.gz dpkg-source: applying /home/buildd/build-910438-2072178/cheese_2.26.0-0ubuntu1.diff.gz dpkg-buildpackage: set CFLAGS to default value: -g -O2 dpkg-buildpackage: set CPPFLAGS to default value: dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions dpkg-buildpackage: set FFLAGS to default value: -g -O2 dpkg-buildpackage: set CXXFLAGS to default value: -g -O2 dpkg-buildpackage: source package cheese dpkg-buildpackage: source version 2.26.0-0ubuntu1 dpkg-buildpackage: host architecture lpia /usr/bin/fakeroot debian/rules clean test -x debian/rules dh_testroot rmdir debian/build rmdir: failed to remove `debian/build': Directory not empty make: [cleanbuilddir] Error 1 (ignored) for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done dh_clean rm -f debian/cdbs-install-list debian/cdbs-package-list GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 /usr/bin/make -C debian/build -k distclean make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[1]: *** No rule to make target `distclean'. make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make: [makefile-clean] Error 2 (ignored) rm -f debian/stamp-makefile-build rm -f debian/stamp-autotools-files test -d debian/build && cd debian/build && \ rm -f intltool-extract intltool-merge intltool-update po/.intltool-merge-cache; \ if test -d doc; then find doc -name '*.omf.out' -exec rm -f \{\} \; ; fi; \ if test -d help; then find help -name '*.omf.out' -exec rm -f \{\} \; ; fi /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/build/buildd/cheese-2.26.0' for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done make[1]: Leaving directory `/build/buildd/cheese-2.26.0' if [ "reverse-patches" = "reverse-patches" ]; then rm -f debian/stamp-patched; fi patches: debian/patches/30_fix-desktop-file.patch Patch debian/patches/30_fix-desktop-file.patch is not applied. if [ "reverse-patches" != "reverse-patches" ]; then touch debian/stamp-patched; fi if [ "reverse-patches" != "reverse-patches" ] ; then \ /usr/bin/make -f debian/rules update-config ; \ fi for dir in debian/patches ; do \ rm -f $dir/*.log ; \ done rm -rf /build/buildd/cheese-2.26.0/debian/build-hildon debian/rules build test -x debian/rules mkdir -p "debian/build" /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/build/buildd/cheese-2.26.0' for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done make[1]: Leaving directory `/build/buildd/cheese-2.26.0' if [ "debian/stamp-patched" = "reverse-patches" ]; then rm -f debian/stamp-patched; fi patches: debian/patches/30_fix-desktop-file.patch Trying patch debian/patches/30_fix-desktop-file.patch at level 1 ... success. if [ "debian/stamp-patched" != "reverse-patches" ]; then touch debian/stamp-patched; fi if [ "debian/stamp-patched" != "reverse-patches" ] ; then \ /usr/bin/make -f debian/rules update-config ; \ fi make[1]: Entering directory `/build/buildd/cheese-2.26.0' if test -e /usr/share/misc/config.guess ; then \ for i in ./config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi make[1]: Leaving directory `/build/buildd/cheese-2.26.0' if test -e /usr/share/misc/config.guess ; then \ for i in ./config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi touch debian/stamp-autotools-files chmod a+x /build/buildd/cheese-2.26.0/./configure cd debian/build && CC="cc" CXX="g++" CFLAGS="-g -O2 -g -Wall -O2" CXXFLAGS="-g -O2 -g -Wall -O2" CPPFLAGS="" LDFLAGS="-Wl,-Bsymbolic-functions" /build/buildd/cheese-2.26.0/./configure --build=i686-linux-gnulp --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/cheese" --disable-maintainer-mode --disable-dependency-tracking --disable-scrollkeeper --enable-hildon 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... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... none checking for library containing strerror... none required checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) none checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) none checking how to run the C preprocessor... cc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnulp checking host system type... i686-pc-linux-gnulp checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by cc... /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 cc object... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC -DPIC checking if cc PIC flag -fPIC -DPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.o... (cached) yes checking whether the cc 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 what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes checking what language compliance flags to pass to the C compiler... checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.40.6 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.0 checking for XML::Parser... ok checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for CHEESE... yes checking for HILDON... 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 data/Makefile config.status: creating data/cheese.desktop.in config.status: creating data/effects/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating data/icons/16x16/actions/Makefile config.status: creating data/icons/22x22/actions/Makefile config.status: creating data/icons/24x24/actions/Makefile config.status: creating data/icons/32x32/actions/Makefile config.status: creating data/icons/48x48/actions/Makefile config.status: creating data/icons/scalable/actions/Makefile config.status: creating data/pixmaps/Makefile config.status: creating data/sounds/Makefile config.status: creating help/Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating cheese-config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands rm -rf /build/buildd/cheese-2.26.0/debian/build-hildon mkdir /build/buildd/cheese-2.26.0/debian/build-hildon cd /build/buildd/cheese-2.26.0/debian/build-hildon && \ /build/buildd/cheese-2.26.0/./configure \ --build=i686-linux-gnulp --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/cheese" --disable-maintainer-mode --disable-dependency-tracking \ \ --disable-scrollkeeper --enable-hildon \ \ --enable-hildon 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 for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnulp checking host system type... i686-pc-linux-gnulp checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes checking what language compliance flags to pass to the C compiler... checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.40.6 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.0 checking for XML::Parser... ok checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for CHEESE... yes checking for HILDON... 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 data/Makefile config.status: creating data/cheese.desktop.in config.status: creating data/effects/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating data/icons/16x16/actions/Makefile config.status: creating data/icons/22x22/actions/Makefile config.status: creating data/icons/24x24/actions/Makefile config.status: creating data/icons/32x32/actions/Makefile config.status: creating data/icons/48x48/actions/Makefile config.status: creating data/icons/scalable/actions/Makefile config.status: creating data/pixmaps/Makefile config.status: creating data/sounds/Makefile config.status: creating help/Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating cheese-config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 /usr/bin/make -C debian/build make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' /usr/bin/make all-recursive make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' Making all in src make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' /usr/bin/make all-am make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-countdown.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-dbus.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-effect-chooser.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_video_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:48: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_photo_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:65: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_log_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:88: warning: unused variable 'priv' cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-gconf.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-thumb-view.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-webcam.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-window.c /build/buildd/cheese-2.26.0/./src/cheese-window.c: In function 'cheese_window_create_window': /build/buildd/cheese-2.26.0/./src/cheese-window.c:1794: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type /build/buildd/cheese-2.26.0/./src/cheese-window.c:1800: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumbnail.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumb-nav.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/ephy-spinner.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gst-audio-play.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gedit-message-area.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-no-camera.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-widget.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog-widgets.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-resolution-combo.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-flash.c cc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-webcam-combo.c /bin/bash ../libtool --tag=CC --mode=link cc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lgtk-x11-2.0 -lstartup-notification-1 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lfreetype -lfontconfig -lgstreamer-0.10 -lebook-1.2 -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lbonobo-2 -lgio-2.0 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lrt -ldbus-glib-1 -lhal -ldbus-1 -lpangocairo-1.0 -lpango-1.0 -lrsvg-2 -lgdk_pixbuf-2.0 -lm -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lgstinterfaces-0.10 -lhildon-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 libtool: link: cc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lstartup-notification-1 /usr/lib/libgstreamer-0.10.so -ldl -lebook-1.2 -ledataserver-1.2 /usr/lib/libxml2.so /usr/lib/libgconf-2.so -lsoup-2.4 /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBit-2.so /usr/lib/libgthread-2.0.so -lrt -ldbus-glib-1 -lhal -ldbus-1 -lrsvg-2 -lgstinterfaces-0.10 -lhildon-1 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so -lz -lfontconfig /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libglib-2.0.so -pthread make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' Making all in po make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ar.po file=`echo as | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/as.po file=`echo be@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/be@latin.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bg.po file=`echo bn_IN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bn_IN.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/dz.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/el.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/et.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/eu.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fr.po file=`echo ga | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ga.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gl.po file=`echo gu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gu.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hi.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hu.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ja.po file=`echo kn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/kn.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ko.po file=`echo ku | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ku.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lt.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lv.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ml.po file=`echo mr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mr.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nl.po file=`echo nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nn.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/oc.po file=`echo or | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/or.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pl.po file=`echo ps | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ps.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt_BR.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ru.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sl.po file=`echo sq | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sq.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr.po file=`echo sr@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr@latin.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sv.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ta.po file=`echo te | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/te.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/th.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_TW.po make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/po' Making all in data make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' Making all in icons make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making all in 16x16 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making all in 22x22 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making all in 24x24 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making all in 32x32 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making all in 48x48 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making all in scalable make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making all in effects make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' Making all in pixmaps make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' Making all in sounds make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po cheese.desktop.in cheese.desktop Generating and caching the translation database Merging translations into cheese.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po /build/buildd/cheese-2.26.0/./data/cheese.schemas.in cheese.schemas Found cached translation database Merging translations into cheese.schemas. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' Making all in help make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' xsltproc -o cheese-C.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/C/cheese.xml || { rm -f "cheese-C.omf"; exit 1; } xsltproc -o cheese-ca.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ca --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ca/cheese.xml || { rm -f "cheese-ca.omf"; exit 1; } xsltproc -o cheese-de.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang de --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/de/cheese.xml || { rm -f "cheese-de.omf"; exit 1; } xsltproc -o cheese-el.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang el --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/el/cheese.xml || { rm -f "cheese-el.omf"; exit 1; } xsltproc -o cheese-en_GB.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang en_GB --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml || { rm -f "cheese-en_GB.omf"; exit 1; } xsltproc -o cheese-es.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang es --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/es/cheese.xml || { rm -f "cheese-es.omf"; exit 1; } xsltproc -o cheese-fr.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang fr --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/fr/cheese.xml || { rm -f "cheese-fr.omf"; exit 1; } xsltproc -o cheese-nl.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang nl --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/nl/cheese.xml || { rm -f "cheese-nl.omf"; exit 1; } xsltproc -o cheese-oc.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang oc --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/oc/cheese.xml || { rm -f "cheese-oc.omf"; exit 1; } xsltproc -o cheese-pt_BR.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang pt_BR --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml || { rm -f "cheese-pt_BR.omf"; exit 1; } xsltproc -o cheese-ru.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ru --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ru/cheese.xml || { rm -f "cheese-ru.omf"; exit 1; } xsltproc -o cheese-sv.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang sv --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/sv/cheese.xml || { rm -f "cheese-sv.omf"; exit 1; } xsltproc -o cheese-th.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang th --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/th/cheese.xml || { rm -f "cheese-th.omf"; exit 1; } make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' touch debian/stamp-makefile-build DEB_MAKE_CHECK_TARGET unset, not running checks /usr/bin/make -C /build/buildd/cheese-2.26.0/debian/build-hildon make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' /usr/bin/make all-recursive make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' Making all in src make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' /usr/bin/make all-am make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-countdown.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-dbus.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-effect-chooser.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_video_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:48: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_photo_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:65: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_log_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:88: warning: unused variable 'priv' gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-gconf.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-thumb-view.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-webcam.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-window.c /build/buildd/cheese-2.26.0/./src/cheese-window.c: In function 'cheese_window_create_window': /build/buildd/cheese-2.26.0/./src/cheese-window.c:1794: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type /build/buildd/cheese-2.26.0/./src/cheese-window.c:1800: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumbnail.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumb-nav.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/ephy-spinner.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gst-audio-play.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gedit-message-area.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-no-camera.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-widget.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog-widgets.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-resolution-combo.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-flash.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-webcam-combo.c /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lgtk-x11-2.0 -lstartup-notification-1 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lfreetype -lfontconfig -lgstreamer-0.10 -lebook-1.2 -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lbonobo-2 -lgio-2.0 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lrt -ldbus-glib-1 -lhal -ldbus-1 -lpangocairo-1.0 -lpango-1.0 -lrsvg-2 -lgdk_pixbuf-2.0 -lm -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lgstinterfaces-0.10 -lhildon-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 libtool: link: gcc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lstartup-notification-1 /usr/lib/libgstreamer-0.10.so -ldl -lebook-1.2 -ledataserver-1.2 /usr/lib/libxml2.so /usr/lib/libgconf-2.so -lsoup-2.4 /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBit-2.so /usr/lib/libgthread-2.0.so -lrt -ldbus-glib-1 -lhal -ldbus-1 -lrsvg-2 -lgstinterfaces-0.10 -lhildon-1 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so -lz -lfontconfig /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libglib-2.0.so -pthread make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' Making all in po make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ar.po file=`echo as | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/as.po file=`echo be@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/be@latin.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bg.po file=`echo bn_IN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bn_IN.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/dz.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/el.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/et.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/eu.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fr.po file=`echo ga | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ga.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gl.po file=`echo gu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gu.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hi.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hu.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ja.po file=`echo kn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/kn.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ko.po file=`echo ku | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ku.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lt.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lv.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ml.po file=`echo mr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mr.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nl.po file=`echo nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nn.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/oc.po file=`echo or | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/or.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pl.po file=`echo ps | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ps.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt_BR.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ru.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sl.po file=`echo sq | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sq.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr.po file=`echo sr@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr@latin.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sv.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ta.po file=`echo te | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/te.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/th.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_TW.po make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' Making all in data make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making all in icons make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making all in 16x16 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making all in 22x22 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making all in 24x24 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making all in 32x32 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making all in 48x48 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making all in scalable make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making all in effects make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' Making all in pixmaps make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' Making all in sounds make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po cheese.desktop.in cheese.desktop Generating and caching the translation database Merging translations into cheese.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po /build/buildd/cheese-2.26.0/./data/cheese.schemas.in cheese.schemas Found cached translation database Merging translations into cheese.schemas. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making all in help make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' xsltproc -o cheese-C.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/C/cheese.xml || { rm -f "cheese-C.omf"; exit 1; } xsltproc -o cheese-ca.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ca --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ca/cheese.xml || { rm -f "cheese-ca.omf"; exit 1; } xsltproc -o cheese-de.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang de --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/de/cheese.xml || { rm -f "cheese-de.omf"; exit 1; } xsltproc -o cheese-el.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang el --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/el/cheese.xml || { rm -f "cheese-el.omf"; exit 1; } xsltproc -o cheese-en_GB.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang en_GB --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml || { rm -f "cheese-en_GB.omf"; exit 1; } xsltproc -o cheese-es.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang es --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/es/cheese.xml || { rm -f "cheese-es.omf"; exit 1; } xsltproc -o cheese-fr.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang fr --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/fr/cheese.xml || { rm -f "cheese-fr.omf"; exit 1; } xsltproc -o cheese-nl.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang nl --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/nl/cheese.xml || { rm -f "cheese-nl.omf"; exit 1; } xsltproc -o cheese-oc.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang oc --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/oc/cheese.xml || { rm -f "cheese-oc.omf"; exit 1; } xsltproc -o cheese-pt_BR.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang pt_BR --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml || { rm -f "cheese-pt_BR.omf"; exit 1; } xsltproc -o cheese-ru.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ru --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ru/cheese.xml || { rm -f "cheese-ru.omf"; exit 1; } xsltproc -o cheese-sv.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang sv --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/sv/cheese.xml || { rm -f "cheese-sv.omf"; exit 1; } xsltproc -o cheese-th.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang th --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/th/cheese.xml || { rm -f "cheese-th.omf"; exit 1; } make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' /usr/bin/fakeroot debian/rules binary-arch test -x debian/rules dh_testroot dh_clean -k dh_installdirs -A mkdir -p "debian/build" if test -e /usr/share/misc/config.guess ; then \ for i in ./config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.sub $i ; \ fi ; \ done ; \ fi chmod a+x /build/buildd/cheese-2.26.0/./configure cd debian/build && CC="cc" CXX="g++" CFLAGS="-g -O2 -g -Wall -O2" CXXFLAGS="-g -O2 -g -Wall -O2" CPPFLAGS="" LDFLAGS="-Wl,-Bsymbolic-functions" /build/buildd/cheese-2.26.0/./configure --build=i686-linux-gnulp --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/cheese" --disable-maintainer-mode --disable-dependency-tracking --disable-scrollkeeper --enable-hildon 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... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking dependency style of cc... none checking for library containing strerror... none required checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) none checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking dependency style of cc... (cached) none checking how to run the C preprocessor... cc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnulp checking host system type... i686-pc-linux-gnulp checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by cc... /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 cc object... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if cc supports -fno-rtti -fno-exceptions... no checking for cc option to produce PIC... -fPIC -DPIC checking if cc PIC flag -fPIC -DPIC works... yes checking if cc static flag -static works... yes checking if cc supports -c -o file.o... yes checking if cc supports -c -o file.o... (cached) yes checking whether the cc 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 what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes checking what language compliance flags to pass to the C compiler... checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.40.6 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.0 checking for XML::Parser... ok checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for CHEESE... yes checking for HILDON... 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 data/Makefile config.status: creating data/cheese.desktop.in config.status: creating data/effects/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating data/icons/16x16/actions/Makefile config.status: creating data/icons/22x22/actions/Makefile config.status: creating data/icons/24x24/actions/Makefile config.status: creating data/icons/32x32/actions/Makefile config.status: creating data/icons/48x48/actions/Makefile config.status: creating data/icons/scalable/actions/Makefile config.status: creating data/pixmaps/Makefile config.status: creating data/sounds/Makefile config.status: creating help/Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating cheese-config.h config.status: cheese-config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands rm -rf /build/buildd/cheese-2.26.0/debian/build-hildon mkdir /build/buildd/cheese-2.26.0/debian/build-hildon cd /build/buildd/cheese-2.26.0/debian/build-hildon && \ /build/buildd/cheese-2.26.0/./configure \ --build=i686-linux-gnulp --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/cheese" --disable-maintainer-mode --disable-dependency-tracking \ \ --disable-scrollkeeper --enable-hildon \ \ --enable-hildon 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 for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... none checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) none checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnulp checking host system type... i686-pc-linux-gnulp checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes checking what language compliance flags to pass to the C compiler... checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.40.6 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.0 checking for XML::Parser... ok checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for CHEESE... yes checking for HILDON... 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 data/Makefile config.status: creating data/cheese.desktop.in config.status: creating data/effects/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating data/icons/16x16/actions/Makefile config.status: creating data/icons/22x22/actions/Makefile config.status: creating data/icons/24x24/actions/Makefile config.status: creating data/icons/32x32/actions/Makefile config.status: creating data/icons/48x48/actions/Makefile config.status: creating data/icons/scalable/actions/Makefile config.status: creating data/pixmaps/Makefile config.status: creating data/sounds/Makefile config.status: creating help/Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating cheese-config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands DEB_MAKE_CHECK_TARGET unset, not running checks /usr/bin/make -C /build/buildd/cheese-2.26.0/debian/build-hildon make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' /usr/bin/make all-recursive make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' Making all in src make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' /usr/bin/make all-am make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-countdown.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-dbus.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-effect-chooser.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_video_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:48: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_photo_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:65: warning: unused variable 'priv' /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c: In function 'cheese_fileutil_get_log_path': /build/buildd/cheese-2.26.0/./src/cheese-fileutil.c:88: warning: unused variable 'priv' gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-gconf.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-thumb-view.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-webcam.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-window.c /build/buildd/cheese-2.26.0/./src/cheese-window.c: In function 'cheese_window_create_window': /build/buildd/cheese-2.26.0/./src/cheese-window.c:1794: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type /build/buildd/cheese-2.26.0/./src/cheese-window.c:1800: warning: passing argument 1 of 'gtk_menu_shell_append' from incompatible pointer type gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumbnail.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/eog-thumb-nav.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/ephy-spinner.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gst-audio-play.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/gedit-message-area.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-no-camera.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-widget.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog-widgets.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-resolution-combo.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-dialog.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-flash.c gcc -DHAVE_CONFIG_H -I. -I/build/buildd/cheese-2.26.0/./src -I.. -DBINDIR=\"/usr/bin\" -DDATADIR=\"/usr/share\" -DPREFIX=\""/usr"\" -DSYSCONFDIR=\""/etc"\" -DLIBDIR=\""/usr/lib"\" -DPACKAGE_DATADIR=\""/usr/share/cheese"\" -DPACKAGE_LOCALEDIR=\""/usr/share/locale"\" -DAPPNAME_DATA_DIR=\"/usr/share/cheese\" -DGNOME_DESKTOP_USE_UNSTABLE_API=1 -D_REENTRANT -DORBIT2=1 -pthread -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/gnome-desktop-2.0 -I/usr/include/startup-notification-1.0 -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/gstreamer-0.10 -I/usr/include/libxml2 -I/usr/include/evolution-data-server-2.26 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libsoup-2.4 -I/usr/include/hal -I/usr/include/librsvg-2 -D_REENTRANT -I/usr/include/hildon-1 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DHILDON -g -O2 -g -Wall -O2 -Wall -c /build/buildd/cheese-2.26.0/./src/cheese-prefs-webcam-combo.c /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lgtk-x11-2.0 -lstartup-notification-1 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lfreetype -lfontconfig -lgstreamer-0.10 -lebook-1.2 -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lbonobo-2 -lgio-2.0 -lbonobo-activation -lORBit-2 -lgthread-2.0 -lrt -ldbus-glib-1 -lhal -ldbus-1 -lpangocairo-1.0 -lpango-1.0 -lrsvg-2 -lgdk_pixbuf-2.0 -lm -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lgstinterfaces-0.10 -lhildon-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 libtool: link: gcc -g -O2 -g -Wall -O2 -Wall -Wl,-Bsymbolic-functions -o cheese cheese.o cheese-countdown.o cheese-dbus.o cheese-effect-chooser.o cheese-fileutil.o cheese-gconf.o cheese-thumb-view.o cheese-webcam.o cheese-window.o eog-thumbnail.o eog-thumb-nav.o ephy-spinner.o gst-audio-play.o gedit-message-area.o cheese-no-camera.o cheese-prefs-widget.o cheese-prefs-dialog-widgets.o cheese-prefs-resolution-combo.o cheese-prefs-dialog.o cheese-flash.o cheese-prefs-webcam-combo.o -pthread -L//lib -lgnome-desktop-2 -lstartup-notification-1 /usr/lib/libgstreamer-0.10.so -ldl -lebook-1.2 -ledataserver-1.2 /usr/lib/libxml2.so /usr/lib/libgconf-2.so -lsoup-2.4 /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBit-2.so /usr/lib/libgthread-2.0.so -lrt -ldbus-glib-1 -lhal -ldbus-1 -lrsvg-2 -lgstinterfaces-0.10 -lhildon-1 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so -lz -lfontconfig /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libglib-2.0.so -pthread make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' Making all in po make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ar.po file=`echo as | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/as.po file=`echo be@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/be@latin.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bg.po file=`echo bn_IN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/bn_IN.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/de.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/dz.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/el.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/et.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/eu.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/fr.po file=`echo ga | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ga.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gl.po file=`echo gu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/gu.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/he.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hi.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/hu.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ja.po file=`echo kn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/kn.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ko.po file=`echo ku | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ku.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lt.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/lv.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mk.po file=`echo ml | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ml.po file=`echo mr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/mr.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nb.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nl.po file=`echo nn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/nn.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/oc.po file=`echo or | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/or.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pl.po file=`echo ps | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ps.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/pt_BR.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ru.po file=`echo sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sl.po file=`echo sq | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sq.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr.po file=`echo sr@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sr@latin.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/sv.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/ta.po file=`echo te | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/te.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/th.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file /build/buildd/cheese-2.26.0/./po/zh_TW.po make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' Making all in data make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making all in icons make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making all in 16x16 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making all in 22x22 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making all in 24x24 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making all in 32x32 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making all in 48x48 make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making all in scalable make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' Making all in actions make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making all in effects make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' Making all in pixmaps make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' Making all in sounds make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po cheese.desktop.in cheese.desktop Generating and caching the translation database Merging translations into cheese.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po /build/buildd/cheese-2.26.0/./data/cheese.schemas.in cheese.schemas Found cached translation database Merging translations into cheese.schemas. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making all in help make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' xsltproc -o cheese-C.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/C/cheese.xml || { rm -f "cheese-C.omf"; exit 1; } xsltproc -o cheese-ca.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ca --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ca/cheese.xml || { rm -f "cheese-ca.omf"; exit 1; } xsltproc -o cheese-de.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang de --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/de/cheese.xml || { rm -f "cheese-de.omf"; exit 1; } xsltproc -o cheese-el.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang el --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/el/cheese.xml || { rm -f "cheese-el.omf"; exit 1; } xsltproc -o cheese-en_GB.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang en_GB --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml || { rm -f "cheese-en_GB.omf"; exit 1; } xsltproc -o cheese-es.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang es --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/es/cheese.xml || { rm -f "cheese-es.omf"; exit 1; } xsltproc -o cheese-fr.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang fr --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/fr/cheese.xml || { rm -f "cheese-fr.omf"; exit 1; } xsltproc -o cheese-nl.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang nl --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/nl/cheese.xml || { rm -f "cheese-nl.omf"; exit 1; } xsltproc -o cheese-oc.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang oc --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/oc/cheese.xml || { rm -f "cheese-oc.omf"; exit 1; } xsltproc -o cheese-pt_BR.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang pt_BR --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml || { rm -f "cheese-pt_BR.omf"; exit 1; } xsltproc -o cheese-ru.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ru --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/ru/cheese.xml || { rm -f "cheese-ru.omf"; exit 1; } xsltproc -o cheese-sv.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang sv --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/sv/cheese.xml || { rm -f "cheese-sv.omf"; exit 1; } xsltproc -o cheese-th.omf --stringparam db2omf.basename cheese --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang th --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/cheese-2.26.0/./help/cheese.omf.in" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` /build/buildd/cheese-2.26.0/./help/th/cheese.xml || { rm -f "cheese-th.omf"; exit 1; } make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' if [ -d debian/build/po ]; then \ if grep -q intltool debian/build/po/Makefile*; then \ if [ -x /usr/bin/intltool-update ]; then \ cd debian/build/po; /usr/bin/intltool-update -p --verbose || true; \ elif [ -x debian/build/intltool-update ]; then \ cd debian/build/po; env XGETTEXT=/usr/bin/xgettext ../intltool-update -p --verbose || true; \ else \ echo 'langpack.mk: po/Makefile* mentions intltool, but intltool-update is not available'; \ exit 1; \ fi; \ elif [ -e debian/build/po/Makefile ]; then \ DOMAIN=$(grep --max-count 1 '^GETTEXT_PACKAGE[[:space:]]*=' debian/build/po/Makefile | sed 's/^.*=[[:space:]]\([^[:space:]]\)/\1/'); \ if [ "$DOMAIN" ]; then \ echo "langpack.mk: Generating $DOMAIN.pot..."; \ make -C debian/build/po "$DOMAIN.pot" || true; \ fi; \ fi; \ fi Unsuccessful open on filename containing newline at /usr/bin/intltool-update line 1071. intltool-update: POTFILES.in not found. if [ -d debian/build/help ]; then \ cd debian/build/help; make pot || true; \ fi make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' make[1]: Nothing to be done for `pot'. make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL=1 /usr/bin/make -C debian/build install DESTDIR=/build/buildd/cheese-2.26.0/debian/tmp/ make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' Making install in src make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' /usr/bin/make install-am make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/bin" /bin/bash ../libtool --mode=install /usr/bin/install -c 'cheese' '/build/buildd/cheese-2.26.0/debian/tmp//usr/bin/cheese' libtool: install: /usr/bin/install -c cheese /build/buildd/cheese-2.26.0/debian/tmp//usr/bin/cheese make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' Making install in po make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/po' linguas="ar as be@latin bg bn_IN ca cs da de dz el en_GB es et eu fi fr ga gl gu he hi hr hu it ja kn ko ku lt lv mk ml mr nb nl nn oc or pa pl ps pt pt_BR ro ru sl sq sr sr@latin sv ta te th tr uk vi zh_CN zh_HK zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/cheese-2.26.0/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/cheese.mo; \ echo "installing $lang.gmo as $dir/cheese.mo"; \ else \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo $dir/cheese.mo; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo as" \ "$dir/cheese.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/cheese.mo.m; \ echo "installing $lang.gmo.m as $dir/cheese.mo.m"; \ else \ if test -r /build/buildd/cheese-2.26.0/./po/$lang.gmo.m ; then \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo.m \ $dir/cheese.mo.m; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo.m as" \ "$dir/cheese.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ar/LC_MESSAGES/cheese.mo installing as.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/as/LC_MESSAGES/cheese.mo installing be@latin.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/be@latin/LC_MESSAGES/cheese.mo installing bg.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/bg/LC_MESSAGES/cheese.mo installing bn_IN.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/bn_IN/LC_MESSAGES/cheese.mo installing ca.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ca/LC_MESSAGES/cheese.mo installing cs.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/cs/LC_MESSAGES/cheese.mo installing da.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/da/LC_MESSAGES/cheese.mo installing de.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/de/LC_MESSAGES/cheese.mo installing dz.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/dz/LC_MESSAGES/cheese.mo installing el.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/el/LC_MESSAGES/cheese.mo installing en_GB.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/en_GB/LC_MESSAGES/cheese.mo installing es.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/es/LC_MESSAGES/cheese.mo installing et.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/et/LC_MESSAGES/cheese.mo installing eu.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/eu/LC_MESSAGES/cheese.mo installing fi.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/fi/LC_MESSAGES/cheese.mo installing fr.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/fr/LC_MESSAGES/cheese.mo installing ga.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ga/LC_MESSAGES/cheese.mo installing gl.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/gl/LC_MESSAGES/cheese.mo installing gu.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/gu/LC_MESSAGES/cheese.mo installing he.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/he/LC_MESSAGES/cheese.mo installing hi.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/hi/LC_MESSAGES/cheese.mo installing hr.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/hr/LC_MESSAGES/cheese.mo installing hu.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/hu/LC_MESSAGES/cheese.mo installing it.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/it/LC_MESSAGES/cheese.mo installing ja.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ja/LC_MESSAGES/cheese.mo installing kn.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/kn/LC_MESSAGES/cheese.mo installing ko.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ko/LC_MESSAGES/cheese.mo installing ku.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ku/LC_MESSAGES/cheese.mo installing lt.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/lt/LC_MESSAGES/cheese.mo installing lv.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/lv/LC_MESSAGES/cheese.mo installing mk.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/mk/LC_MESSAGES/cheese.mo installing ml.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ml/LC_MESSAGES/cheese.mo installing mr.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/mr/LC_MESSAGES/cheese.mo installing nb.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/nb/LC_MESSAGES/cheese.mo installing nl.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/nl/LC_MESSAGES/cheese.mo installing nn.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/nn/LC_MESSAGES/cheese.mo installing oc.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/oc/LC_MESSAGES/cheese.mo installing or.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/or/LC_MESSAGES/cheese.mo installing pa.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/pa/LC_MESSAGES/cheese.mo installing pl.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/pl/LC_MESSAGES/cheese.mo installing ps.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ps/LC_MESSAGES/cheese.mo installing pt.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/pt/LC_MESSAGES/cheese.mo installing pt_BR.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/pt_BR/LC_MESSAGES/cheese.mo installing ro.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ro/LC_MESSAGES/cheese.mo installing ru.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ru/LC_MESSAGES/cheese.mo installing sl.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/sl/LC_MESSAGES/cheese.mo installing sq.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/sq/LC_MESSAGES/cheese.mo installing sr.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/sr/LC_MESSAGES/cheese.mo installing sr@latin.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/sr@latin/LC_MESSAGES/cheese.mo installing sv.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/sv/LC_MESSAGES/cheese.mo installing ta.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/ta/LC_MESSAGES/cheese.mo installing te.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/te/LC_MESSAGES/cheese.mo installing th.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/th/LC_MESSAGES/cheese.mo installing tr.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/tr/LC_MESSAGES/cheese.mo installing uk.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/uk/LC_MESSAGES/cheese.mo installing vi.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/vi/LC_MESSAGES/cheese.mo installing zh_CN.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/zh_CN/LC_MESSAGES/cheese.mo installing zh_HK.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/zh_HK/LC_MESSAGES/cheese.mo installing zh_TW.gmo as /build/buildd/cheese-2.26.0/debian/tmp//usr/share/locale/zh_TW/LC_MESSAGES/cheese.mo make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/po' Making install in data make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' Making install in icons make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making install in 16x16 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/16x16/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/16x16/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/16x16/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/16x16/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/cheese.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/16x16/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making install in 22x22 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/22x22/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/22x22/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/22x22/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/22x22/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/cheese.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/22x22/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making install in 24x24 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/24x24/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/24x24/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/24x24/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/24x24/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/cheese.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/24x24/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making install in 32x32 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/32x32/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/32x32/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/32x32/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/32x32/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/cheese.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/32x32/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making install in 48x48 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/48x48/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/48x48/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/48x48/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/48x48/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/cheese.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/48x48/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making install in scalable make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/scalable/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/scalable/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/actions/browse-webcam-effects.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/icons/hicolor/scalable/actions/browse-webcam-effects.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/scalable/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/scalable/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/cheese.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/icons/hicolor/scalable/apps/cheese.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Nothing to be done for `install-exec-am'. /usr/bin/make install-data-hook make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making install in effects make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/effects" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/dicetv.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/dicetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/edgetv.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/edgetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Hulk.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/Hulk.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/identity.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/identity.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Mauve.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/Mauve.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/NoirBlanc.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/NoirBlanc.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Saturation.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/Saturation.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/shagadelictv.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/shagadelictv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/vertigotv.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/vertigotv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_h.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/videoflip_h.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_v.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/videoflip_v.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/warptv.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/effects/warptv.png' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' Making install in pixmaps make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/pixmaps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/thumbnail-frame.png' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps/thumbnail-frame.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/camera-icon.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps/camera-icon.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-1.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps/cheese-1.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-2.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps/cheese-2.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-3.svg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/pixmaps/cheese-3.svg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' Making install in sounds make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/sounds" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter0.ogg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds/shutter0.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter1.ogg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds/shutter1.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter2.ogg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds/shutter2.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter3.ogg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds/shutter3.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter4.ogg' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/sounds/shutter4.ogg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache /build/buildd/cheese-2.26.0/./po cheese.desktop.in cheese.desktop Found cached translation database Merging translations into cheese.desktop. make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/cheese/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/lib/cheese/cheese" /usr/bin/install -c '/build/buildd/cheese-2.26.0/./data/cheese-bugreport.sh' '/build/buildd/cheese-2.26.0/debian/tmp//usr/lib/cheese/cheese/cheese-bugreport.sh' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule cheese.schemas GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL is set, not installing schemas (gconftool-2:23452): GConf-WARNING **: Failed to load source "xml:readwrite:/root/.gconf": Failed: Could not make directory `/root/.gconf': Permission denied (gconftool-2:23452): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible test -z "/usr/share/applications" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/applications" /usr/bin/install -c -m 644 'cheese.desktop' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/applications/cheese.desktop' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/gtkrc' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/gtkrc' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese.ui' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/cheese.ui' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-ui.xml' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/cheese-ui.xml' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-prefs.ui' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/cheese/cheese-prefs.ui' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//etc/gconf/schemas" /usr/bin/install -c -m 644 'cheese.schemas' '/build/buildd/cheese-2.26.0/debian/tmp//etc/gconf/schemas/cheese.schemas' test -z "/usr/share/dbus-1/services" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/tmp//usr/share/dbus-1/services" /usr/bin/install -c -m 644 'org.gnome.Cheese.service' '/build/buildd/cheese-2.26.0/debian/tmp//usr/share/dbus-1/services/org.gnome.Cheese.service' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' Making install in help make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' make[3]: Nothing to be done for `install-exec-am'. /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/legal.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/legal.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/de/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/el/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/oc/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ru/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/cheese.xml /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th/cheese.xml /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de/figures/ cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el/figures/ cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB/figures/ cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc/figures/ cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru/figures/ cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th/figures/cheese-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/C/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ca/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/es/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/fr/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/nl/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/pt_BR/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/sv/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/tmp//usr/share/gnome/help/cheese/th/figures/cheese-effects-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese mkdir -p -- /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese /usr/bin/install -c -m 644 cheese-C.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-C.omf /usr/bin/install -c -m 644 cheese-ca.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-ca.omf /usr/bin/install -c -m 644 cheese-de.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-de.omf /usr/bin/install -c -m 644 cheese-el.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-el.omf /usr/bin/install -c -m 644 cheese-en_GB.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-en_GB.omf /usr/bin/install -c -m 644 cheese-es.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-es.omf /usr/bin/install -c -m 644 cheese-fr.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-fr.omf /usr/bin/install -c -m 644 cheese-nl.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-nl.omf /usr/bin/install -c -m 644 cheese-oc.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-oc.omf /usr/bin/install -c -m 644 cheese-pt_BR.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-pt_BR.omf /usr/bin/install -c -m 644 cheese-ru.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-ru.omf /usr/bin/install -c -m 644 cheese-sv.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-sv.omf /usr/bin/install -c -m 644 cheese-th.omf /build/buildd/cheese-2.26.0/debian/tmp//usr/share/omf/cheese/cheese-th.omf make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' dh_installdirs -pcheese /usr/bin/make -C /build/buildd/cheese-2.26.0/debian/build DESTDIR=/build/buildd/cheese-2.26.0/debian/cheese install make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' Making install in src make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' /usr/bin/make install-am make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/bin" /bin/bash ../libtool --mode=install /usr/bin/install -c 'cheese' '/build/buildd/cheese-2.26.0/debian/cheese/usr/bin/cheese' libtool: install: /usr/bin/install -c cheese /build/buildd/cheese-2.26.0/debian/cheese/usr/bin/cheese make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/src' Making install in po make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/po' linguas="ar as be@latin bg bn_IN ca cs da de dz el en_GB es et eu fi fr ga gl gu he hi hr hu it ja kn ko ku lt lv mk ml mr nb nl nn oc or pa pl ps pt pt_BR ro ru sl sq sr sr@latin sv ta te th tr uk vi zh_CN zh_HK zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/cheese-2.26.0/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/cheese.mo; \ echo "installing $lang.gmo as $dir/cheese.mo"; \ else \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo $dir/cheese.mo; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo as" \ "$dir/cheese.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/cheese.mo.m; \ echo "installing $lang.gmo.m as $dir/cheese.mo.m"; \ else \ if test -r /build/buildd/cheese-2.26.0/./po/$lang.gmo.m ; then \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo.m \ $dir/cheese.mo.m; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo.m as" \ "$dir/cheese.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ar/LC_MESSAGES/cheese.mo installing as.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/as/LC_MESSAGES/cheese.mo installing be@latin.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/be@latin/LC_MESSAGES/cheese.mo installing bg.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/bg/LC_MESSAGES/cheese.mo installing bn_IN.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/bn_IN/LC_MESSAGES/cheese.mo installing ca.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ca/LC_MESSAGES/cheese.mo installing cs.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/cs/LC_MESSAGES/cheese.mo installing da.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/da/LC_MESSAGES/cheese.mo installing de.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/de/LC_MESSAGES/cheese.mo installing dz.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/dz/LC_MESSAGES/cheese.mo installing el.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/el/LC_MESSAGES/cheese.mo installing en_GB.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/en_GB/LC_MESSAGES/cheese.mo installing es.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/es/LC_MESSAGES/cheese.mo installing et.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/et/LC_MESSAGES/cheese.mo installing eu.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/eu/LC_MESSAGES/cheese.mo installing fi.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/fi/LC_MESSAGES/cheese.mo installing fr.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/fr/LC_MESSAGES/cheese.mo installing ga.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ga/LC_MESSAGES/cheese.mo installing gl.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/gl/LC_MESSAGES/cheese.mo installing gu.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/gu/LC_MESSAGES/cheese.mo installing he.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/he/LC_MESSAGES/cheese.mo installing hi.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/hi/LC_MESSAGES/cheese.mo installing hr.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/hr/LC_MESSAGES/cheese.mo installing hu.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/hu/LC_MESSAGES/cheese.mo installing it.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/it/LC_MESSAGES/cheese.mo installing ja.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ja/LC_MESSAGES/cheese.mo installing kn.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/kn/LC_MESSAGES/cheese.mo installing ko.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ko/LC_MESSAGES/cheese.mo installing ku.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ku/LC_MESSAGES/cheese.mo installing lt.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/lt/LC_MESSAGES/cheese.mo installing lv.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/lv/LC_MESSAGES/cheese.mo installing mk.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/mk/LC_MESSAGES/cheese.mo installing ml.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ml/LC_MESSAGES/cheese.mo installing mr.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/mr/LC_MESSAGES/cheese.mo installing nb.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/nb/LC_MESSAGES/cheese.mo installing nl.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/nl/LC_MESSAGES/cheese.mo installing nn.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/nn/LC_MESSAGES/cheese.mo installing oc.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/oc/LC_MESSAGES/cheese.mo installing or.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/or/LC_MESSAGES/cheese.mo installing pa.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/pa/LC_MESSAGES/cheese.mo installing pl.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/pl/LC_MESSAGES/cheese.mo installing ps.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ps/LC_MESSAGES/cheese.mo installing pt.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/pt/LC_MESSAGES/cheese.mo installing pt_BR.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/pt_BR/LC_MESSAGES/cheese.mo installing ro.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ro/LC_MESSAGES/cheese.mo installing ru.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ru/LC_MESSAGES/cheese.mo installing sl.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/sl/LC_MESSAGES/cheese.mo installing sq.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/sq/LC_MESSAGES/cheese.mo installing sr.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/sr/LC_MESSAGES/cheese.mo installing sr@latin.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/sr@latin/LC_MESSAGES/cheese.mo installing sv.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/sv/LC_MESSAGES/cheese.mo installing ta.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/ta/LC_MESSAGES/cheese.mo installing te.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/te/LC_MESSAGES/cheese.mo installing th.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/th/LC_MESSAGES/cheese.mo installing tr.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/tr/LC_MESSAGES/cheese.mo installing uk.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/uk/LC_MESSAGES/cheese.mo installing vi.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/vi/LC_MESSAGES/cheese.mo installing zh_CN.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/zh_CN/LC_MESSAGES/cheese.mo installing zh_HK.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/zh_HK/LC_MESSAGES/cheese.mo installing zh_TW.gmo as /build/buildd/cheese-2.26.0/debian/cheese/usr/share/locale/zh_TW/LC_MESSAGES/cheese.mo make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/po' Making install in data make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' Making install in icons make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making install in 16x16 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/16x16/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/16x16/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/16x16/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/16x16/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/16x16/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/16x16' Making install in 22x22 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/22x22/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/22x22/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/22x22/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/22x22/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/22x22/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/22x22' Making install in 24x24 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/24x24/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/24x24/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/24x24/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/24x24/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/24x24/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/24x24' Making install in 32x32 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/32x32/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/32x32/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/32x32/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/32x32/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/32x32/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/32x32' Making install in 48x48 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/48x48/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/48x48/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/48x48/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/48x48/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/48x48/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/48x48' Making install in scalable make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/scalable/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/scalable/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/actions/browse-webcam-effects.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/icons/hicolor/scalable/actions/browse-webcam-effects.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/scalable/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/scalable/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/cheese.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/icons/hicolor/scalable/apps/cheese.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons/scalable' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Nothing to be done for `install-exec-am'. /usr/bin/make install-data-hook make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/icons' Making install in effects make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/effects" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/dicetv.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/dicetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/edgetv.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/edgetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Hulk.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/Hulk.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/identity.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/identity.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Mauve.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/Mauve.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/NoirBlanc.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/NoirBlanc.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Saturation.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/Saturation.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/shagadelictv.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/shagadelictv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/vertigotv.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/vertigotv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_h.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/videoflip_h.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_v.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/videoflip_v.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/warptv.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/effects/warptv.png' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/effects' Making install in pixmaps make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/pixmaps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/thumbnail-frame.png' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps/thumbnail-frame.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/camera-icon.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps/camera-icon.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-1.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps/cheese-1.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-2.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps/cheese-2.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-3.svg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/pixmaps/cheese-3.svg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/pixmaps' Making install in sounds make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/sounds" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter0.ogg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds/shutter0.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter1.ogg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds/shutter1.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter2.ogg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds/shutter2.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter3.ogg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds/shutter3.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter4.ogg' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/sounds/shutter4.ogg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data/sounds' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/cheese/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/lib/cheese/cheese" /usr/bin/install -c '/build/buildd/cheese-2.26.0/./data/cheese-bugreport.sh' '/build/buildd/cheese-2.26.0/debian/cheese/usr/lib/cheese/cheese/cheese-bugreport.sh' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule cheese.schemas (gconftool-2:24722): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/cheese/countdown' to key `/apps/cheese/countdown' WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `tr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `oc': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `C': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `el': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `gl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `mk': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ml': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `kn': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ko': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ar': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `as': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `cs': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `it': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `et': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `eu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `es': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `or': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sq': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `gu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sv': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `da': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `mr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `uk': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ja': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `de': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `bg': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `he': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nb': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ta': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `fi': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pa': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `te': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `fr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nn': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `vi': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ro': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `hu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `lt': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ps': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `lv': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ru': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `dz': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ca': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pt': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ga': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `th': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/webcam' to key `/apps/cheese/webcam' WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `tr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `oc': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `C': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `el': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `gl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `mk': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ml': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `kn': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ko': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ar': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `as': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `cs': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `mr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `et': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `eu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `it': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `or': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sq': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `gu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `es': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `da': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sv': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `uk': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ja': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `de': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `bg': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `he': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nb': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ta': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `fi': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pa': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `te': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `fr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nn': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `vi': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ro': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `hu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `lt': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ps': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `lv': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ru': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `dz': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ca': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pt': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `th': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/selected_effects' to key `/apps/cheese/selected_effects' WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `tr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `oc': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `C': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `el': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `gl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `mk': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ml': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `kn': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ko': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ar': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `as': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `cs': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `it': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `et': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `eu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `es': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `or': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sq': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `gu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sv': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `da': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `mr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `uk': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ja': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `de': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `bg': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `he': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nb': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ta': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `fi': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pa': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `te': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `fr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nn': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `vi': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ro': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `hu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `lt': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ps': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `lv': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ru': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `dz': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ca': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pt': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ga': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `th': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/x_resolution' to key `/apps/cheese/x_resolution' WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `uk': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `C': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `el': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `gl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `mk': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ml': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `kn': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `as': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ar': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `et': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `cs': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `mr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `it': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `eu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `es': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `or': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sq': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ko': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sv': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `da': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `gu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ja': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `de': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `bg': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `nb': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `he': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ta': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `fi': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pa': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `te': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `nl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `fr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `vi': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ro': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `hu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `lt': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `lv': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ru': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pt': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ca': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `tr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ga': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `th': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/y_resolution' to key `/apps/cheese/y_resolution' WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `uk': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `C': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `el': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `gl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `mk': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ml': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `kn': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `as': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ar': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `et': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `cs': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `mr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `it': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `eu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `es': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `or': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sq': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ko': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sv': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `da': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `gu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ja': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `de': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `bg': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `nb': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `he': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ta': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `fi': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pa': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `te': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `nl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `fr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `vi': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ro': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `hu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `lt': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `lv': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ru': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pt': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ca': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `tr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ga': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `th': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/video_path' to key `/apps/cheese/video_path' WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `oc': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `C': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `el': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `gl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `mk': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ml': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `kn': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ko': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ar': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `as': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `cs': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `mr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `et': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `eu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `it': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `or': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sq': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `gu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `es': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `da': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sv': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `uk': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ja': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `de': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `bg': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `he': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `nb': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ta': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `fi': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pa': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `te': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `nl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `fr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `vi': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ro': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `hu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `lt': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ps': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `lv': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ru': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pt': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ca': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `tr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ga': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `th': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/photo_path' to key `/apps/cheese/photo_path' WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `oc': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `C': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `el': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `gl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `mk': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ml': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `kn': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ko': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ar': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `as': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `cs': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `mr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `et': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `eu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `it': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `or': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sq': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `gu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `es': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `da': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sv': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `uk': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ja': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `de': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `bg': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `he': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `nb': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ta': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `fi': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pa': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `te': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `nl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `fr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `vi': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ro': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `hu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `lt': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ps': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `lv': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ru': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pt': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ca': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `tr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ga': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `th': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/enable_delete' to key `/apps/cheese/enable_delete' WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `uk': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `C': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `el': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `gl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `mk': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ml': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `kn': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ko': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ar': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `as': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `cs': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `mr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `et': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `eu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `es': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `or': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sq': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `it': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sv': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `da': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `gu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ja': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `de': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `bg': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `nb': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `he': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ta': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `fi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `hi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pa': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `te': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `nl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `fr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `vi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ro': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `hu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `lt': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `lv': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ru': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pt': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ca': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `tr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `th': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/applications" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/applications" /usr/bin/install -c -m 644 'cheese.desktop' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/applications/cheese.desktop' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/gtkrc' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/gtkrc' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese.ui' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/cheese.ui' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-ui.xml' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/cheese-ui.xml' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-prefs.ui' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/cheese/cheese-prefs.ui' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/etc/gconf/schemas" /usr/bin/install -c -m 644 'cheese.schemas' '/build/buildd/cheese-2.26.0/debian/cheese/etc/gconf/schemas/cheese.schemas' test -z "/usr/share/dbus-1/services" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese/usr/share/dbus-1/services" /usr/bin/install -c -m 644 'org.gnome.Cheese.service' '/build/buildd/cheese-2.26.0/debian/cheese/usr/share/dbus-1/services/org.gnome.Cheese.service' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/data' Making install in help make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build/help' make[3]: Nothing to be done for `install-exec-am'. /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/legal.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/legal.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/de/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/el/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/oc/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ru/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th/cheese.xml /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th/figures/cheese-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/C/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ca/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/es/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/fr/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/nl/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/pt_BR/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/sv/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese/usr/share/gnome/help/cheese/th/figures/cheese-effects-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese /usr/bin/install -c -m 644 cheese-C.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-C.omf /usr/bin/install -c -m 644 cheese-ca.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-ca.omf /usr/bin/install -c -m 644 cheese-de.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-de.omf /usr/bin/install -c -m 644 cheese-el.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-el.omf /usr/bin/install -c -m 644 cheese-en_GB.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-en_GB.omf /usr/bin/install -c -m 644 cheese-es.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-es.omf /usr/bin/install -c -m 644 cheese-fr.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-fr.omf /usr/bin/install -c -m 644 cheese-nl.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-nl.omf /usr/bin/install -c -m 644 cheese-oc.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-oc.omf /usr/bin/install -c -m 644 cheese-pt_BR.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-pt_BR.omf /usr/bin/install -c -m 644 cheese-ru.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-ru.omf /usr/bin/install -c -m 644 cheese-sv.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-sv.omf /usr/bin/install -c -m 644 cheese-th.omf /build/buildd/cheese-2.26.0/debian/cheese/usr/share/omf/cheese/cheese-th.omf make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build/help' make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build' dh_installdirs -pcheese-hildon /usr/bin/make -C /build/buildd/cheese-2.26.0/debian/build-hildon DESTDIR=/build/buildd/cheese-2.26.0/debian/cheese-hildon install make[1]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' Making install in src make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' /usr/bin/make install-am make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/bin" /bin/bash ../libtool --mode=install /usr/bin/install -c 'cheese' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/bin/cheese' libtool: install: /usr/bin/install -c cheese /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/bin/cheese make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/src' Making install in po make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' linguas="ar as be@latin bg bn_IN ca cs da de dz el en_GB es et eu fi fr ga gl gu he hi hr hu it ja kn ko ku lt lv mk ml mr nb nl nn oc or pa pl ps pt pt_BR ro ru sl sq sr sr@latin sv ta te th tr uk vi zh_CN zh_HK zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/cheese-2.26.0/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/cheese.mo; \ echo "installing $lang.gmo as $dir/cheese.mo"; \ else \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo $dir/cheese.mo; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo as" \ "$dir/cheese.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/cheese.mo.m; \ echo "installing $lang.gmo.m as $dir/cheese.mo.m"; \ else \ if test -r /build/buildd/cheese-2.26.0/./po/$lang.gmo.m ; then \ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./po/$lang.gmo.m \ $dir/cheese.mo.m; \ echo "installing /build/buildd/cheese-2.26.0/./po/$lang.gmo.m as" \ "$dir/cheese.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ar/LC_MESSAGES/cheese.mo installing as.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/as/LC_MESSAGES/cheese.mo installing be@latin.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/be@latin/LC_MESSAGES/cheese.mo installing bg.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/bg/LC_MESSAGES/cheese.mo installing bn_IN.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/bn_IN/LC_MESSAGES/cheese.mo installing ca.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ca/LC_MESSAGES/cheese.mo installing cs.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/cs/LC_MESSAGES/cheese.mo installing da.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/da/LC_MESSAGES/cheese.mo installing de.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/de/LC_MESSAGES/cheese.mo installing dz.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/dz/LC_MESSAGES/cheese.mo installing el.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/el/LC_MESSAGES/cheese.mo installing en_GB.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/en_GB/LC_MESSAGES/cheese.mo installing es.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/es/LC_MESSAGES/cheese.mo installing et.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/et/LC_MESSAGES/cheese.mo installing eu.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/eu/LC_MESSAGES/cheese.mo installing fi.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/fi/LC_MESSAGES/cheese.mo installing fr.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/fr/LC_MESSAGES/cheese.mo installing ga.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ga/LC_MESSAGES/cheese.mo installing gl.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/gl/LC_MESSAGES/cheese.mo installing gu.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/gu/LC_MESSAGES/cheese.mo installing he.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/he/LC_MESSAGES/cheese.mo installing hi.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/hi/LC_MESSAGES/cheese.mo installing hr.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/hr/LC_MESSAGES/cheese.mo installing hu.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/hu/LC_MESSAGES/cheese.mo installing it.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/it/LC_MESSAGES/cheese.mo installing ja.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ja/LC_MESSAGES/cheese.mo installing kn.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/kn/LC_MESSAGES/cheese.mo installing ko.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ko/LC_MESSAGES/cheese.mo installing ku.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ku/LC_MESSAGES/cheese.mo installing lt.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/lt/LC_MESSAGES/cheese.mo installing lv.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/lv/LC_MESSAGES/cheese.mo installing mk.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/mk/LC_MESSAGES/cheese.mo installing ml.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ml/LC_MESSAGES/cheese.mo installing mr.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/mr/LC_MESSAGES/cheese.mo installing nb.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/nb/LC_MESSAGES/cheese.mo installing nl.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/nl/LC_MESSAGES/cheese.mo installing nn.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/nn/LC_MESSAGES/cheese.mo installing oc.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/oc/LC_MESSAGES/cheese.mo installing or.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/or/LC_MESSAGES/cheese.mo installing pa.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/pa/LC_MESSAGES/cheese.mo installing pl.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/pl/LC_MESSAGES/cheese.mo installing ps.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ps/LC_MESSAGES/cheese.mo installing pt.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/pt/LC_MESSAGES/cheese.mo installing pt_BR.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/pt_BR/LC_MESSAGES/cheese.mo installing ro.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ro/LC_MESSAGES/cheese.mo installing ru.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ru/LC_MESSAGES/cheese.mo installing sl.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/sl/LC_MESSAGES/cheese.mo installing sq.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/sq/LC_MESSAGES/cheese.mo installing sr.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/sr/LC_MESSAGES/cheese.mo installing sr@latin.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/sr@latin/LC_MESSAGES/cheese.mo installing sv.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/sv/LC_MESSAGES/cheese.mo installing ta.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/ta/LC_MESSAGES/cheese.mo installing te.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/te/LC_MESSAGES/cheese.mo installing th.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/th/LC_MESSAGES/cheese.mo installing tr.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/tr/LC_MESSAGES/cheese.mo installing uk.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/uk/LC_MESSAGES/cheese.mo installing vi.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/vi/LC_MESSAGES/cheese.mo installing zh_CN.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/zh_CN/LC_MESSAGES/cheese.mo installing zh_HK.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/zh_HK/LC_MESSAGES/cheese.mo installing zh_TW.gmo as /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/locale/zh_TW/LC_MESSAGES/cheese.mo make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/po' Making install in data make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making install in icons make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making install in 16x16 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/16x16/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/16x16/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/16x16/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/16x16/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/16x16/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/16x16/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/16x16' Making install in 22x22 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/22x22/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/22x22/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/22x22/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/22x22/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/22x22/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/22x22/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/22x22' Making install in 24x24 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/24x24/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/24x24/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/24x24/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/24x24/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/24x24/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/24x24/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/24x24' Making install in 32x32 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/32x32/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/32x32/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/32x32/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/32x32/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/32x32/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/32x32/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/32x32' Making install in 48x48 make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/48x48/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/48x48/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/actions/browse-webcam-effects.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/48x48/actions/browse-webcam-effects.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/48x48/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/48x48/cheese.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/48x48/apps/cheese.png' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/48x48' Making install in scalable make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' Making install in actions make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/icons/hicolor/scalable/actions" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/scalable/actions" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/actions/browse-webcam-effects.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/icons/hicolor/scalable/actions/browse-webcam-effects.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable/actions' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[6]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/scalable/apps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/scalable/apps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/icons/scalable/cheese.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/icons/hicolor/scalable/apps/cheese.svg' make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons/scalable' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[5]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[5]: Nothing to be done for `install-exec-am'. /usr/bin/make install-data-hook make[6]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[6]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[5]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/icons' Making install in effects make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/effects" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/dicetv.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/dicetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/edgetv.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/edgetv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Hulk.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/Hulk.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/identity.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/identity.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Mauve.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/Mauve.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/NoirBlanc.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/NoirBlanc.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/Saturation.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/Saturation.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/shagadelictv.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/shagadelictv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/vertigotv.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/vertigotv.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_h.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/videoflip_h.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/videoflip_v.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/videoflip_v.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/effects/warptv.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/effects/warptv.png' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/effects' Making install in pixmaps make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/pixmaps" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/thumbnail-frame.png' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps/thumbnail-frame.png' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/camera-icon.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps/camera-icon.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-1.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps/cheese-1.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-2.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps/cheese-2.svg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/pixmaps/cheese-3.svg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/pixmaps/cheese-3.svg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/pixmaps' Making install in sounds make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/cheese/sounds" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter0.ogg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds/shutter0.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter1.ogg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds/shutter1.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter2.ogg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds/shutter2.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter3.ogg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds/shutter3.ogg' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/sounds/shutter4.ogg' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/sounds/shutter4.ogg' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data/sounds' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[4]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/cheese/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/lib/cheese/cheese" /usr/bin/install -c '/build/buildd/cheese-2.26.0/./data/cheese-bugreport.sh' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/lib/cheese/cheese/cheese-bugreport.sh' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule cheese.schemas (gconftool-2:25992): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/cheese/countdown' to key `/apps/cheese/countdown' WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `tr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `oc': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `C': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `el': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `gl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `mk': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ml': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `kn': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ko': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ar': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `as': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `cs': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `it': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `et': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `eu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `es': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `or': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sq': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `gu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sv': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `da': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `mr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `uk': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ja': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `de': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `bg': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `he': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nb': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ta': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `fi': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pa': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `te': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `fr': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `nn': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `vi': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ro': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `hu': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `lt': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ps': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `lv': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ru': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `dz': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ca': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `pt': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `ga': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `sl': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `th': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/countdown', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/countdown', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/webcam' to key `/apps/cheese/webcam' WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `tr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `oc': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `C': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `el': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `gl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `mk': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ml': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `kn': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ko': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ar': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `as': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `cs': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `mr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `et': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `eu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `it': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `or': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sq': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `gu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `es': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `da': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sv': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `uk': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ja': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `de': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `bg': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `he': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nb': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ta': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `fi': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pa': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `te': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `fr': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `nn': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `vi': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ro': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `hu': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `lt': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ps': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `lv': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ru': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `dz': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `ca': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `pt': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `sl': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `th': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/webcam', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/webcam', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/selected_effects' to key `/apps/cheese/selected_effects' WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `tr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `oc': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `C': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `el': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `gl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `mk': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ml': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `kn': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ko': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ar': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `as': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `cs': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `it': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `et': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `eu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `es': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `or': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sq': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `gu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sv': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `da': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `mr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `uk': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ja': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `de': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `bg': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `he': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nb': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ta': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `fi': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pa': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `te': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `fr': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `nn': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `vi': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ro': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `hu': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `lt': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ps': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `lv': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ru': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `dz': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ca': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `pt': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `ga': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `sl': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `th': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/selected_effects', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/selected_effects', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/x_resolution' to key `/apps/cheese/x_resolution' WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `uk': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `C': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `el': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `gl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `mk': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ml': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `kn': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `as': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ar': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `et': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `cs': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `mr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `it': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `eu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `es': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `or': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sq': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ko': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sv': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `da': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `gu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ja': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `de': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `bg': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `nb': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `he': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ta': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `fi': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pa': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `te': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `nl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `fr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `vi': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ro': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `hu': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `lt': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sl': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `lv': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ru': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `pt': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ca': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `tr': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `ga': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/x_resolution', locale `th': Unable to store a value at key '/schemas/apps/cheese/x_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/y_resolution' to key `/apps/cheese/y_resolution' WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `uk': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `C': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `el': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `gl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `mk': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ml': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `kn': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `as': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ar': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `et': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `cs': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `mr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `it': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `eu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `es': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `or': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sq': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ko': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sv': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `da': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `gu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ja': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `de': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `bg': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `nb': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `he': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ta': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `fi': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pa': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `te': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `nl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `fr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `vi': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ro': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `hu': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `lt': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sl': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `lv': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ru': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `pt': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ca': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `tr': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `ga': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/y_resolution', locale `th': Unable to store a value at key '/schemas/apps/cheese/y_resolution', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/video_path' to key `/apps/cheese/video_path' WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `oc': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `C': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `el': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `gl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `mk': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ml': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `kn': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ko': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ar': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `as': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `cs': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `mr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `et': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `eu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `it': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `or': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sq': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `gu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `es': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `da': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sv': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `uk': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ja': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `de': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `bg': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `he': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `nb': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ta': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `fi': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pa': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `te': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `nl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `fr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `vi': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ro': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `hu': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `lt': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ps': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `lv': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ru': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `pt': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ca': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `tr': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `ga': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `sl': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `th': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/video_path', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/video_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/photo_path' to key `/apps/cheese/photo_path' WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `oc': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `C': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `el': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `gl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `mk': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ml': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `kn': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ko': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ar': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `as': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `cs': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `mr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `et': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `eu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `it': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `or': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sq': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `gu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `es': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `da': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sv': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `uk': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ja': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `de': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `bg': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `he': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `nb': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ta': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `fi': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pa': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `te': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `nl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `fr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `vi': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ro': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `hu': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `lt': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ps': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `lv': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ru': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `pt': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ca': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `tr': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `ga': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `sl': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `be@latin': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `th': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/photo_path', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/photo_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/cheese/enable_delete' to key `/apps/cheese/enable_delete' WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `uk': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `C': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `el': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `gl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `mk': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ml': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `kn': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ko': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ar': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `as': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `cs': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `mr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `et': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `eu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `es': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `or': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sq': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `it': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pt_BR': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sv': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `da': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `gu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ja': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `de': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `bg': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `nb': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `he': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ta': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `fi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `hi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pa': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `te': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_CN': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `nl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `fr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_HK': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `vi': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ro': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `hu': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `lt': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sl': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `en_GB': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `lv': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ru': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `pt': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `ca': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `tr': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `sr@latin': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `bn_IN': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `zh_TW': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/cheese/enable_delete', locale `th': Unable to store a value at key '/schemas/apps/cheese/enable_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/applications" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/applications" /usr/bin/install -c -m 644 'cheese.desktop' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/applications/cheese.desktop' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/gtkrc' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/gtkrc' test -z "/usr/share/cheese" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese" /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese.ui' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/cheese.ui' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-ui.xml' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/cheese-ui.xml' /usr/bin/install -c -m 644 '/build/buildd/cheese-2.26.0/./data/cheese-prefs.ui' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/cheese/cheese-prefs.ui' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/etc/gconf/schemas" /usr/bin/install -c -m 644 'cheese.schemas' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/etc/gconf/schemas/cheese.schemas' test -z "/usr/share/dbus-1/services" || /bin/mkdir -p "/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/dbus-1/services" /usr/bin/install -c -m 644 'org.gnome.Cheese.service' '/build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/dbus-1/services/org.gnome.Cheese.service' make[4]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/data' Making install in help make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[3]: Nothing to be done for `install-exec-am'. /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/legal.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/legal.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/de/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/el/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/en_GB/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/oc/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ru/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv/cheese.xml /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/cheese.xml /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th/cheese.xml /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/fr/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru/figures/ cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-screenshot.jpg cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv/figures/cheese-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th/figures/ mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th/figures/ /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th/figures/cheese-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/C/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/C/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/ca/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ca/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/de/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/el/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/en_GB/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/es/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/es/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/fr/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/nl/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/nl/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/oc/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/pt_BR/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/pt_BR/figures/cheese-effects-screenshot.jpg cd /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/ru/figures/ && ln -s -f ../../C/figures/cheese-effects-screenshot.jpg cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/sv/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/sv/figures/cheese-effects-screenshot.jpg /usr/bin/install -c -m 644 /build/buildd/cheese-2.26.0/./help/th/figures/cheese-effects-screenshot.jpg /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/gnome/help/cheese/th/figures/cheese-effects-screenshot.jpg /bin/bash /build/buildd/cheese-2.26.0/./mkinstalldirs /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese mkdir -p -- /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese /usr/bin/install -c -m 644 cheese-C.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-C.omf /usr/bin/install -c -m 644 cheese-ca.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-ca.omf /usr/bin/install -c -m 644 cheese-de.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-de.omf /usr/bin/install -c -m 644 cheese-el.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-el.omf /usr/bin/install -c -m 644 cheese-en_GB.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-en_GB.omf /usr/bin/install -c -m 644 cheese-es.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-es.omf /usr/bin/install -c -m 644 cheese-fr.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-fr.omf /usr/bin/install -c -m 644 cheese-nl.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-nl.omf /usr/bin/install -c -m 644 cheese-oc.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-oc.omf /usr/bin/install -c -m 644 cheese-pt_BR.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-pt_BR.omf /usr/bin/install -c -m 644 cheese-ru.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-ru.omf /usr/bin/install -c -m 644 cheese-sv.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-sv.omf /usr/bin/install -c -m 644 cheese-th.omf /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/omf/cheese/cheese-th.omf make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon/help' make[2]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[3]: Entering directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[2]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' make[1]: Leaving directory `/build/buildd/cheese-2.26.0/debian/build-hildon' mkdir -p /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/man/man1 cp /build/buildd/cheese-2.26.0/debian/cheese.1 /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/man/man1 gzip /build/buildd/cheese-2.26.0/debian/cheese-hildon/usr/share/man/man1/cheese.1 dh_installdocs -pcheese ./README ./NEWS ./AUTHORS dh_installexamples -pcheese dh_installman -pcheese dh_installinfo -pcheese dh_installmenu -pcheese dh_installcron -pcheese dh_installinit -pcheese dh_installdebconf -pcheese dh_installemacsen -pcheese dh_installcatalogs -pcheese dh_installpam -pcheese dh_installlogrotate -pcheese dh_installlogcheck -pcheese dh_installchangelogs -pcheese dh_installudev -pcheese dh_lintian -pcheese dh_install -pcheese dh_link -pcheese dh_installmime -pcheese dh_scrollkeeper -pcheese dh_gconf -pcheese dh_desktop -pcheese dh_icons -pcheese dh_installdocs -pcheese-hildon ./README ./NEWS ./AUTHORS dh_installexamples -pcheese-hildon dh_installman -pcheese-hildon dh_installinfo -pcheese-hildon dh_installmenu -pcheese-hildon dh_installcron -pcheese-hildon dh_installinit -pcheese-hildon dh_installdebconf -pcheese-hildon dh_installemacsen -pcheese-hildon dh_installcatalogs -pcheese-hildon dh_installpam -pcheese-hildon dh_installlogrotate -pcheese-hildon dh_installlogcheck -pcheese-hildon dh_installchangelogs -pcheese-hildon dh_installudev -pcheese-hildon dh_lintian -pcheese-hildon dh_install -pcheese-hildon dh_link -pcheese-hildon dh_installmime -pcheese-hildon dh_scrollkeeper -pcheese-hildon dh_gconf -pcheese-hildon dh_desktop -pcheese-hildon dh_icons -pcheese-hildon dh_strip -pcheese dh_strip debug symbol extraction: all non-arch-all packages for this build platform lpia: cheese cheese-hildon dh_strip debug symbol extraction: packages to act on: cheese dh_strip debug symbol extraction: ignored packages: pkgstriptranslations: processing control file: ./debian/cheese-dbgsym/DEBIAN/control, package cheese-dbgsym, directory ./debian/cheese-dbgsym pkgstriptranslations: cheese-dbgsym does not contain translations, skipping pkgstriptranslations: preparing translation tarball cheese_2.26.0-0ubuntu1_lpia_translations.tar.gz...done (73 files) pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: building package `cheese-dbgsym' in `../cheese-dbgsym_2.26.0-0ubuntu1_lpia.ddeb'. dh_compress -pcheese dh_fixperms -pcheese dh_makeshlibs -pcheese dh_strip -pcheese-hildon dh_strip debug symbol extraction: all non-arch-all packages for this build platform lpia: cheese cheese-hildon dh_strip debug symbol extraction: packages to act on: cheese-hildon dh_strip debug symbol extraction: ignored packages: pkgstriptranslations: processing control file: ./debian/cheese-hildon-dbgsym/DEBIAN/control, package cheese-hildon-dbgsym, directory ./debian/cheese-hildon-dbgsym pkgstriptranslations: cheese-hildon-dbgsym does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: building package `cheese-hildon-dbgsym' in `../cheese-hildon-dbgsym_2.26.0-0ubuntu1_lpia.ddeb'. dh_compress -pcheese-hildon dh_fixperms -pcheese-hildon dh_makeshlibs -pcheese-hildon dh_installdeb -pcheese dh_perl -pcheese dh_shlibdeps -pcheese dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libstartup-notification-1.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libbonobo-activation.so.4 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfontconfig.so.1 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libatk-1.0.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxml2.so.2 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdl.so.2 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libedataserver-1.2.so.11 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfreetype.so.6 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libORBit-2.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libm.so.6 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgmodule-2.0.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libbonobo-2.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libsoup-2.4.so.1 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangoft2-1.0.so.0 could be avoided if "debian/cheese/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). echo "langpack.mk: add translation domain to cheese"; \ if [ -e debian/build/po/Makefile ]; then \ DOMAIN=$(grep --max-count 1 '^GETTEXT_PACKAGE[[:space:]]*=' debian/build/po/Makefile | sed 's/^.*=[[:space:]]*\([^[:space:]]\)/\1/'); \ if [ "$DOMAIN" ]; then \ for d in $(find debian/cheese -type f \( -name "*.desktop" -o -name "*.directory" \) ); do \ echo "langpack.mk: Replacing translations with domain $DOMAIN in $d..."; \ sed -ri '/^(Name|GenericName|Comment)\[/d' $d; \ echo "X-Ubuntu-Gettext-Domain=$DOMAIN" >> $d; \ done; \ for d in $(find debian/cheese -type f -name "*.server" ); do \ echo "langpack.mk: Adding translation domain $DOMAIN to $d..."; \ sed -i "s//)/\1$DOMAIN<\/gettext_domain>\n\1\2/; /^[[:space:]]*[[:space:]]*\$/ d; /^$/d; s/<\/schema>$/&\n/" $d; \ done; \ fi; \ fi langpack.mk: add translation domain to cheese langpack.mk: Replacing translations with domain cheese in debian/cheese/usr/share/applications/cheese.desktop... langpack.mk: Replacing translations with domain cheese in debian/cheese/usr/share/gconf/schemas/cheese.schemas... dh_installdeb -pcheese-hildon dh_perl -pcheese-hildon dh_shlibdeps -pcheese-hildon dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libstartup-notification-1.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libbonobo-activation.so.4 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfontconfig.so.1 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libatk-1.0.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libxml2.so.2 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libdl.so.2 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libedataserver-1.2.so.11 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libfreetype.so.6 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libORBit-2.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libm.so.6 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgmodule-2.0.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libbonobo-2.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libsoup-2.4.so.1 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangoft2-1.0.so.0 could be avoided if "debian/cheese-hildon/usr/bin/cheese" were not uselessly linked against it (they use none of its symbols). echo "langpack.mk: add translation domain to cheese-hildon"; \ if [ -e debian/build/po/Makefile ]; then \ DOMAIN=$(grep --max-count 1 '^GETTEXT_PACKAGE[[:space:]]*=' debian/build/po/Makefile | sed 's/^.*=[[:space:]]*\([^[:space:]]\)/\1/'); \ if [ "$DOMAIN" ]; then \ for d in $(find debian/cheese-hildon -type f \( -name "*.desktop" -o -name "*.directory" \) ); do \ echo "langpack.mk: Replacing translations with domain $DOMAIN in $d..."; \ sed -ri '/^(Name|GenericName|Comment)\[/d' $d; \ echo "X-Ubuntu-Gettext-Domain=$DOMAIN" >> $d; \ done; \ for d in $(find debian/cheese-hildon -type f -name "*.server" ); do \ echo "langpack.mk: Adding translation domain $DOMAIN to $d..."; \ sed -i "s//)/\1$DOMAIN<\/gettext_domain>\n\1\2/; /^[[:space:]]*[[:space:]]*\$/ d; /^$/d; s/<\/schema>$/&\n/" $d; \ done; \ fi; \ fi langpack.mk: add translation domain to cheese-hildon langpack.mk: Replacing translations with domain cheese in debian/cheese-hildon/usr/share/applications/cheese.desktop... langpack.mk: Replacing translations with domain cheese in debian/cheese-hildon/usr/share/gconf/schemas/cheese.schemas... dh_gencontrol -pcheese # symlink identical documentation to depending packages [ -n "$CDBS_NO_DOC_SYMLINKING" ] || \ [ -h debian/cheese/usr/share/doc ] || \ [ ! -d debian/cheese/usr/share/doc ] || \ for dep in `perl -ne 'if (/^(Pre-)?Depends:/) {s/^\w+://; foreach (split /,/) { split; print($_[0], "\n"); } }' debian/cheese/DEBIAN/control`; do \ if [ -d debian/$dep/usr/share/doc ]; then \ echo "Searching for duplicated docs in dependency $dep..."; \ rootdir=`pwd`; \ (cd debian/cheese/usr/share/doc/cheese; find -type f ! -name copyright | while read f; do \ thisfile="$rootdir/debian/cheese/usr/share/doc/cheese/$f"; \ depfile="$rootdir/debian/$dep/usr/share/doc/$dep/$f"; \ if [ -f $depfile -o -L $depfile ] && zcmp $thisfile $depfile >/dev/null; then \ echo " symlinking $f in cheese to file in $dep"; \ rm $thisfile; ln -s /usr/share/doc/$dep/$f $thisfile; \ fi; \ done ); \ fi; \ done # symlink identical Gnome help files within packages if [ -z "$CDBS_NO_GNOME_HELP_SYMLINKING" ] && [ -d debian/cheese/usr/share/gnome/help ]; then \ cd debian/cheese && LC_ALL=C fdupes -r1nq usr/share/gnome/help | while read s; do \ set -- $(echo $s | tr ' ' '\n' | sort); \ f=$1; shift; \ for d; do \ echo "symlinking duplicate Gnome help file $d to $f"; \ rm $d; ln -s /$f $d; \ done; \ done; \ fi dh_link -p cheese dh_md5sums -pcheese dh_builddeb -pcheese pkgstriptranslations: processing control file: ./debian/cheese/DEBIAN/control, package cheese, directory ./debian/cheese pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: building package `cheese' in `../cheese_2.26.0-0ubuntu1_lpia.deb'. dh_gencontrol -pcheese-hildon # symlink identical documentation to depending packages [ -n "$CDBS_NO_DOC_SYMLINKING" ] || \ [ -h debian/cheese-hildon/usr/share/doc ] || \ [ ! -d debian/cheese-hildon/usr/share/doc ] || \ for dep in `perl -ne 'if (/^(Pre-)?Depends:/) {s/^\w+://; foreach (split /,/) { split; print($_[0], "\n"); } }' debian/cheese-hildon/DEBIAN/control`; do \ if [ -d debian/$dep/usr/share/doc ]; then \ echo "Searching for duplicated docs in dependency $dep..."; \ rootdir=`pwd`; \ (cd debian/cheese-hildon/usr/share/doc/cheese-hildon; find -type f ! -name copyright | while read f; do \ thisfile="$rootdir/debian/cheese-hildon/usr/share/doc/cheese-hildon/$f"; \ depfile="$rootdir/debian/$dep/usr/share/doc/$dep/$f"; \ if [ -f $depfile -o -L $depfile ] && zcmp $thisfile $depfile >/dev/null; then \ echo " symlinking $f in cheese-hildon to file in $dep"; \ rm $thisfile; ln -s /usr/share/doc/$dep/$f $thisfile; \ fi; \ done ); \ fi; \ done # symlink identical Gnome help files within packages if [ -z "$CDBS_NO_GNOME_HELP_SYMLINKING" ] && [ -d debian/cheese-hildon/usr/share/gnome/help ]; then \ cd debian/cheese-hildon && LC_ALL=C fdupes -r1nq usr/share/gnome/help | while read s; do \ set -- $(echo $s | tr ' ' '\n' | sort); \ f=$1; shift; \ for d; do \ echo "symlinking duplicate Gnome help file $d to $f"; \ rm $d; ln -s /$f $d; \ done; \ done; \ fi dh_link -p cheese-hildon dh_md5sums -pcheese-hildon dh_builddeb -pcheese-hildon pkgstriptranslations: processing control file: ./debian/cheese/DEBIAN/control, package cheese, directory ./debian/cheese pkgstriptranslations: processing control file: ./debian/cheese-hildon/DEBIAN/control, package cheese-hildon, directory ./debian/cheese-hildon pkgstriptranslations: tarball already exists pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com dpkg-deb: building package `cheese-hildon' in `../cheese-hildon_2.26.0-0ubuntu1_lpia.deb'. dpkg-genchanges -B -mUbuntu/lpia Build Daemon >../cheese_2.26.0-0ubuntu1_lpia.changes dpkg-genchanges: arch-specific upload - not including arch-independent packages dpkg-genchanges: binary-only upload - not including any source code Use of uninitialized value within %f2p in hash element at /usr/bin/dpkg-genchanges line 496. Use of uninitialized value within @_ in list assignment at /usr/share/perl5/Dpkg/Arch.pm line 300. Use of uninitialized value $b in string eq at /usr/share/perl5/Dpkg/Arch.pm line 302. Use of uninitialized value $_ in pattern match (m//) at /usr/share/perl5/Dpkg/Arch.pm line 251. Use of uninitialized value $arch in hash element at /usr/share/perl5/Dpkg/Arch.pm line 258. dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20090318-2349 Publishing chroot-autobuild/build/buildd/cheese_2.26.0-0ubuntu1_lpia_translations.tar.gz for rosetta. Publishing debug debs. chroot-autobuild/build/buildd/cheese_2.26.0-0ubuntu1_lpia.deb: new debian package, version 2.0. size 2808742 bytes: control archive= 5484 bytes. 1348 bytes, 16 lines control 11748 bytes, 151 lines md5sums 508 bytes, 17 lines * postinst #!/bin/sh 661 bytes, 24 lines * postrm #!/bin/sh 181 bytes, 7 lines * prerm #!/bin/sh Package: cheese Version: 2.26.0-0ubuntu1 Architecture: lpia Maintainer: Ubuntu Desktop Team Installed-Size: 5072 Depends: libatk1.0-0 (>= 1.20.0), libbonobo2-0 (>= 2.15.0), libc6 (>= 2.9), libcairo2 (>= 1.4.0), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libebook1.2-9 (>= 2.26.0), libedataserver1.2-11 (>= 2.26.0), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.16.0), libgnome-desktop-2-11 (>= 1:2.25.90), libgstreamer-plugins-base0.10-0 (>= 0.10.0), libgstreamer0.10-0 (>= 0.10.20), libgtk2.0-0 (>= 2.16.0), libhal1 (>= 0.5.8.1), libhildon-1-0 (>= 2.0.1), liborbit2 (>= 1:2.14.10), libpango1.0-0 (>= 1.22.0), librsvg2-2 (>= 2.22.3), libsoup2.4-1 (>= 2.25.4), libstartup-notification0 (>= 0.8-1), libxml2 (>= 2.6.27), zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), gstreamer0.10-plugins-base (>= 0.10.20), gstreamer0.10-plugins-good (>= 0.10.8), gstreamer0.10-x (>= 0.10.20) Suggests: nautilus-sendto Conflicts: cheese-hildon Replaces: cheese-hildon Section: gnome Priority: optional Homepage: http://www.gnome.org/projects/cheese/ Description: A tool to take pictures and videos from your webcam Cheese is a cheesy program to take pictures and videos from your web cam. It also provides some graphical effects in order to please the users play instinct. chroot-autobuild/build/buildd/cheese-hildon_2.26.0-0ubuntu1_lpia.deb: new debian package, version 2.0. size 2808892 bytes: control archive= 5612 bytes. 1550 bytes, 21 lines control 11783 bytes, 151 lines md5sums 508 bytes, 17 lines * postinst #!/bin/sh 661 bytes, 24 lines * postrm #!/bin/sh 181 bytes, 7 lines * prerm #!/bin/sh Package: cheese-hildon Source: cheese Version: 2.26.0-0ubuntu1 Architecture: lpia Maintainer: Ubuntu Desktop Team Installed-Size: 5072 Depends: libatk1.0-0 (>= 1.20.0), libbonobo2-0 (>= 2.15.0), libc6 (>= 2.9), libcairo2 (>= 1.4.0), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), libebook1.2-9 (>= 2.26.0), libedataserver1.2-11 (>= 2.26.0), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.16.0), libgnome-desktop-2-11 (>= 1:2.25.90), libgstreamer-plugins-base0.10-0 (>= 0.10.0), libgstreamer0.10-0 (>= 0.10.20), libgtk2.0-0 (>= 2.16.0), libhal1 (>= 0.5.8.1), libhildon-1-0 (>= 2.0.1), liborbit2 (>= 1:2.14.10), libpango1.0-0 (>= 1.22.0), librsvg2-2 (>= 2.22.3), libsoup2.4-1 (>= 2.25.4), libstartup-notification0 (>= 0.8-1), libxml2 (>= 2.6.27), zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), gstreamer0.10-plugins-base (>= 0.10.20), gstreamer0.10-plugins-good (>= 0.10.8), gstreamer0.10-x (>= 0.10.20) Suggests: nautilus-sendto Conflicts: cheese Replaces: cheese Section: gnome Priority: optional Homepage: http://www.gnome.org/projects/cheese/ Description: A tool to take pictures and videos for Hildon enviornments Cheese is a cheesy program to take pictures and videos from your web cam. It also provides some graphical effects in order to please the users play instinct. . This package is specifically configured and designed for Hildon based systems such as Ubuntu Mobile Internet Edition. Please do not try to install this package on a normal desktop. chroot-autobuild/build/buildd/cheese_2.26.0-0ubuntu1_lpia.deb: drwxr-xr-x root/root 0 2009-03-18 23:49 ./ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/bin/ -rwxr-xr-x root/root 130676 2009-03-18 23:49 ./usr/bin/cheese drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 9709 2009-03-18 23:49 ./usr/share/locale/ar/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/as/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/as/LC_MESSAGES/ -rw-r--r-- root/root 13622 2009-03-18 23:49 ./usr/share/locale/as/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/be@latin/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/be@latin/LC_MESSAGES/ -rw-r--r-- root/root 8057 2009-03-18 23:49 ./usr/share/locale/be@latin/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 12581 2009-03-18 23:49 ./usr/share/locale/bg/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bn_IN/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bn_IN/LC_MESSAGES/ -rw-r--r-- root/root 15307 2009-03-18 23:49 ./usr/share/locale/bn_IN/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 9799 2009-03-18 23:49 ./usr/share/locale/ca/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 9781 2009-03-18 23:49 ./usr/share/locale/cs/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 9381 2009-03-18 23:49 ./usr/share/locale/da/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 10111 2009-03-18 23:49 ./usr/share/locale/de/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/dz/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/dz/LC_MESSAGES/ -rw-r--r-- root/root 10032 2009-03-18 23:49 ./usr/share/locale/dz/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 12992 2009-03-18 23:49 ./usr/share/locale/el/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 9087 2009-03-18 23:49 ./usr/share/locale/en_GB/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 9974 2009-03-18 23:49 ./usr/share/locale/es/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 9516 2009-03-18 23:49 ./usr/share/locale/et/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/eu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/eu/LC_MESSAGES/ -rw-r--r-- root/root 9721 2009-03-18 23:49 ./usr/share/locale/eu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 9354 2009-03-18 23:49 ./usr/share/locale/fi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 10332 2009-03-18 23:49 ./usr/share/locale/fr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ga/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ga/LC_MESSAGES/ -rw-r--r-- root/root 5965 2009-03-18 23:49 ./usr/share/locale/ga/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 9649 2009-03-18 23:49 ./usr/share/locale/gl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gu/LC_MESSAGES/ -rw-r--r-- root/root 13224 2009-03-18 23:49 ./usr/share/locale/gu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 9808 2009-03-18 23:49 ./usr/share/locale/he/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 4346 2009-03-18 23:49 ./usr/share/locale/hi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hr/LC_MESSAGES/ -rw-r--r-- root/root 656 2009-03-18 23:49 ./usr/share/locale/hr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 9838 2009-03-18 23:49 ./usr/share/locale/hu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 9532 2009-03-18 23:49 ./usr/share/locale/it/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 10647 2009-03-18 23:49 ./usr/share/locale/ja/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/kn/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/kn/LC_MESSAGES/ -rw-r--r-- root/root 14321 2009-03-18 23:49 ./usr/share/locale/kn/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 9773 2009-03-18 23:49 ./usr/share/locale/ko/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ku/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ku/LC_MESSAGES/ -rw-r--r-- root/root 1061 2009-03-18 23:49 ./usr/share/locale/ku/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 9515 2009-03-18 23:49 ./usr/share/locale/lt/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lv/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lv/LC_MESSAGES/ -rw-r--r-- root/root 9776 2009-03-18 23:49 ./usr/share/locale/lv/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mk/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mk/LC_MESSAGES/ -rw-r--r-- root/root 11850 2009-03-18 23:49 ./usr/share/locale/mk/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ml/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ml/LC_MESSAGES/ -rw-r--r-- root/root 17752 2009-03-18 23:49 ./usr/share/locale/ml/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mr/LC_MESSAGES/ -rw-r--r-- root/root 13817 2009-03-18 23:49 ./usr/share/locale/mr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 9176 2009-03-18 23:49 ./usr/share/locale/nb/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 9527 2009-03-18 23:49 ./usr/share/locale/nl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 6619 2009-03-18 23:49 ./usr/share/locale/nn/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/oc/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/oc/LC_MESSAGES/ -rw-r--r-- root/root 7557 2009-03-18 23:49 ./usr/share/locale/oc/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/or/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/or/LC_MESSAGES/ -rw-r--r-- root/root 15549 2009-03-18 23:49 ./usr/share/locale/or/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pa/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pa/LC_MESSAGES/ -rw-r--r-- root/root 13345 2009-03-18 23:49 ./usr/share/locale/pa/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 9792 2009-03-18 23:49 ./usr/share/locale/pl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ps/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ps/LC_MESSAGES/ -rw-r--r-- root/root 7259 2009-03-18 23:49 ./usr/share/locale/ps/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 9743 2009-03-18 23:49 ./usr/share/locale/pt/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 9976 2009-03-18 23:49 ./usr/share/locale/pt_BR/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 10022 2009-03-18 23:49 ./usr/share/locale/ro/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 13137 2009-03-18 23:49 ./usr/share/locale/ru/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sl/LC_MESSAGES/ -rw-r--r-- root/root 9496 2009-03-18 23:49 ./usr/share/locale/sl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sq/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sq/LC_MESSAGES/ -rw-r--r-- root/root 9780 2009-03-18 23:49 ./usr/share/locale/sq/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 12310 2009-03-18 23:49 ./usr/share/locale/sr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr@latin/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr@latin/LC_MESSAGES/ -rw-r--r-- root/root 9775 2009-03-18 23:49 ./usr/share/locale/sr@latin/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 9638 2009-03-18 23:49 ./usr/share/locale/sv/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ta/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ta/LC_MESSAGES/ -rw-r--r-- root/root 17126 2009-03-18 23:49 ./usr/share/locale/ta/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/te/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/te/LC_MESSAGES/ -rw-r--r-- root/root 14950 2009-03-18 23:49 ./usr/share/locale/te/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 13801 2009-03-18 23:49 ./usr/share/locale/th/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 9404 2009-03-18 23:49 ./usr/share/locale/tr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 12818 2009-03-18 23:49 ./usr/share/locale/uk/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 10162 2009-03-18 23:49 ./usr/share/locale/vi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 8974 2009-03-18 23:49 ./usr/share/locale/zh_CN/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_HK/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_HK/LC_MESSAGES/ -rw-r--r-- root/root 9174 2009-03-18 23:49 ./usr/share/locale/zh_HK/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 9177 2009-03-18 23:49 ./usr/share/locale/zh_TW/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/actions/ -rw-r--r-- root/root 745 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/actions/ -rw-r--r-- root/root 866 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/actions/ -rw-r--r-- root/root 896 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/actions/ -rw-r--r-- root/root 1556 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/actions/ -rw-r--r-- root/root 2722 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/actions/ -rw-r--r-- root/root 23659 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/actions/browse-webcam-effects.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/effects/ -rw-r--r-- root/root 27289 2009-03-18 23:49 ./usr/share/cheese/effects/dicetv.png -rw-r--r-- root/root 32141 2009-03-18 23:49 ./usr/share/cheese/effects/edgetv.png -rw-r--r-- root/root 21118 2009-03-18 23:49 ./usr/share/cheese/effects/Hulk.png -rw-r--r-- root/root 19816 2009-03-18 23:49 ./usr/share/cheese/effects/identity.png -rw-r--r-- root/root 20317 2009-03-18 23:49 ./usr/share/cheese/effects/Mauve.png -rw-r--r-- root/root 12765 2009-03-18 23:49 ./usr/share/cheese/effects/NoirBlanc.png -rw-r--r-- root/root 12482 2009-03-18 23:49 ./usr/share/cheese/effects/Saturation.png -rw-r--r-- root/root 27488 2009-03-18 23:49 ./usr/share/cheese/effects/shagadelictv.png -rw-r--r-- root/root 26408 2009-03-18 23:49 ./usr/share/cheese/effects/vertigotv.png -rw-r--r-- root/root 19652 2009-03-18 23:49 ./usr/share/cheese/effects/videoflip_h.png -rw-r--r-- root/root 19558 2009-03-18 23:49 ./usr/share/cheese/effects/videoflip_v.png -rw-r--r-- root/root 20932 2009-03-18 23:49 ./usr/share/cheese/effects/warptv.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/pixmaps/ -rw-r--r-- root/root 908 2009-03-18 23:49 ./usr/share/cheese/pixmaps/thumbnail-frame.png -rw-r--r-- root/root 5108 2009-03-18 23:49 ./usr/share/cheese/pixmaps/camera-icon.svg -rw-r--r-- root/root 43694 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-1.svg -rw-r--r-- root/root 16970 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-2.svg -rw-r--r-- root/root 23023 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-3.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/sounds/ -rw-r--r-- root/root 9420 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter0.ogg -rw-r--r-- root/root 30289 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter1.ogg -rw-r--r-- root/root 17024 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter2.ogg -rw-r--r-- root/root 26650 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter3.ogg -rw-r--r-- root/root 22302 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter4.ogg -rw-r--r-- root/root 376 2009-03-18 23:49 ./usr/share/cheese/gtkrc -rw-r--r-- root/root 39308 2009-03-18 23:49 ./usr/share/cheese/cheese.ui -rw-r--r-- root/root 1301 2009-03-18 23:49 ./usr/share/cheese/cheese-ui.xml -rw-r--r-- root/root 5837 2009-03-18 23:49 ./usr/share/cheese/cheese-prefs.ui drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 645 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 935 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 915 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2107 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 3198 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 23050 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/apps/cheese.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/applications/ -rw-r--r-- root/root 451 2009-03-18 23:49 ./usr/share/applications/cheese.desktop drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/dbus-1/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/dbus-1/services/ -rw-r--r-- root/root 59 2009-03-18 23:49 ./usr/share/dbus-1/services/org.gnome.Cheese.service drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/ -rw-r--r-- root/root 3672 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/legal.xml -rw-r--r-- root/root 21109 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/ -rw-r--r-- root/root 297091 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/cheese-screenshot.jpg -rw-r--r-- root/root 288651 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/ -rw-r--r-- root/root 24297 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/ -rw-r--r-- root/root 138960 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/cheese-screenshot.jpg -rw-r--r-- root/root 151412 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/ -rw-r--r-- root/root 25562 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/ -rw-r--r-- root/root 34483 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/ -rw-r--r-- root/root 22911 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/ -rw-r--r-- root/root 24315 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/ -rw-r--r-- root/root 302843 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/cheese-screenshot.jpg -rw-r--r-- root/root 296437 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/ -rw-r--r-- root/root 25298 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/ -rw-r--r-- root/root 80368 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/cheese-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/ -rw-r--r-- root/root 25089 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/ -rw-r--r-- root/root 72763 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/cheese-screenshot.jpg -rw-r--r-- root/root 70249 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/ -rw-r--r-- root/root 25054 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/ -rw-r--r-- root/root 24679 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/ -rw-r--r-- root/root 83154 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/cheese-screenshot.jpg -rw-r--r-- root/root 96957 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/ -rw-r--r-- root/root 27633 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/ -rw-r--r-- root/root 23970 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/ -rw-r--r-- root/root 68567 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/cheese-screenshot.jpg -rw-r--r-- root/root 94971 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/ -rw-r--r-- root/root 38446 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/ -rw-r--r-- root/root 87479 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/cheese-screenshot.jpg -rw-r--r-- root/root 100823 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/omf/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/omf/cheese/ -rw-r--r-- root/root 978 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-C.omf -rw-r--r-- root/root 981 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-ca.omf -rw-r--r-- root/root 1010 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-de.omf -rw-r--r-- root/root 987 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-el.omf -rw-r--r-- root/root 962 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-en_GB.omf -rw-r--r-- root/root 994 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-es.omf -rw-r--r-- root/root 1020 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-fr.omf -rw-r--r-- root/root 1000 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-nl.omf -rw-r--r-- root/root 983 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-oc.omf -rw-r--r-- root/root 989 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-pt_BR.omf -rw-r--r-- root/root 996 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-ru.omf -rw-r--r-- root/root 978 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-sv.omf -rw-r--r-- root/root 1143 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-th.omf drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/doc/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/doc/cheese/ -rw-r--r-- root/root 1025 2009-03-16 17:46 ./usr/share/doc/cheese/README -rw-r--r-- root/root 1333 2009-03-16 17:46 ./usr/share/doc/cheese/AUTHORS -rw-r--r-- root/root 2812 2009-03-18 23:48 ./usr/share/doc/cheese/copyright -rw-r--r-- root/root 9569 2009-03-16 17:49 ./usr/share/doc/cheese/NEWS.gz -rw-r--r-- root/root 4321 2009-03-18 23:48 ./usr/share/doc/cheese/changelog.Debian.gz drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/man/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/man/man1/ -rw-r--r-- root/root 297 2009-03-18 23:49 ./usr/share/man/man1/cheese.1.gz drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gconf/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 3611 2009-03-18 23:49 ./usr/share/gconf/schemas/cheese.schemas drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/cheese/cheese/ -rwxr-xr-x root/root 63 2009-03-18 23:49 ./usr/lib/cheese/cheese/cheese-bugreport.sh lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg chroot-autobuild/build/buildd/cheese-hildon_2.26.0-0ubuntu1_lpia.deb: drwxr-xr-x root/root 0 2009-03-18 23:49 ./ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/bin/ -rwxr-xr-x root/root 130676 2009-03-18 23:49 ./usr/bin/cheese drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 9709 2009-03-18 23:49 ./usr/share/locale/ar/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/as/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/as/LC_MESSAGES/ -rw-r--r-- root/root 13622 2009-03-18 23:49 ./usr/share/locale/as/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/be@latin/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/be@latin/LC_MESSAGES/ -rw-r--r-- root/root 8057 2009-03-18 23:49 ./usr/share/locale/be@latin/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 12581 2009-03-18 23:49 ./usr/share/locale/bg/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bn_IN/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/bn_IN/LC_MESSAGES/ -rw-r--r-- root/root 15307 2009-03-18 23:49 ./usr/share/locale/bn_IN/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 9799 2009-03-18 23:49 ./usr/share/locale/ca/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 9781 2009-03-18 23:49 ./usr/share/locale/cs/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 9381 2009-03-18 23:49 ./usr/share/locale/da/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 10111 2009-03-18 23:49 ./usr/share/locale/de/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/dz/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/dz/LC_MESSAGES/ -rw-r--r-- root/root 10032 2009-03-18 23:49 ./usr/share/locale/dz/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 12992 2009-03-18 23:49 ./usr/share/locale/el/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 9087 2009-03-18 23:49 ./usr/share/locale/en_GB/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 9974 2009-03-18 23:49 ./usr/share/locale/es/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 9516 2009-03-18 23:49 ./usr/share/locale/et/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/eu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/eu/LC_MESSAGES/ -rw-r--r-- root/root 9721 2009-03-18 23:49 ./usr/share/locale/eu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 9354 2009-03-18 23:49 ./usr/share/locale/fi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 10332 2009-03-18 23:49 ./usr/share/locale/fr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ga/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ga/LC_MESSAGES/ -rw-r--r-- root/root 5965 2009-03-18 23:49 ./usr/share/locale/ga/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 9649 2009-03-18 23:49 ./usr/share/locale/gl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/gu/LC_MESSAGES/ -rw-r--r-- root/root 13224 2009-03-18 23:49 ./usr/share/locale/gu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 9808 2009-03-18 23:49 ./usr/share/locale/he/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hi/LC_MESSAGES/ -rw-r--r-- root/root 4346 2009-03-18 23:49 ./usr/share/locale/hi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hr/LC_MESSAGES/ -rw-r--r-- root/root 656 2009-03-18 23:49 ./usr/share/locale/hr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 9838 2009-03-18 23:49 ./usr/share/locale/hu/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 9532 2009-03-18 23:49 ./usr/share/locale/it/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 10647 2009-03-18 23:49 ./usr/share/locale/ja/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/kn/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/kn/LC_MESSAGES/ -rw-r--r-- root/root 14321 2009-03-18 23:49 ./usr/share/locale/kn/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 9773 2009-03-18 23:49 ./usr/share/locale/ko/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ku/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ku/LC_MESSAGES/ -rw-r--r-- root/root 1061 2009-03-18 23:49 ./usr/share/locale/ku/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 9515 2009-03-18 23:49 ./usr/share/locale/lt/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lv/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/lv/LC_MESSAGES/ -rw-r--r-- root/root 9776 2009-03-18 23:49 ./usr/share/locale/lv/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mk/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mk/LC_MESSAGES/ -rw-r--r-- root/root 11850 2009-03-18 23:49 ./usr/share/locale/mk/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ml/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ml/LC_MESSAGES/ -rw-r--r-- root/root 17752 2009-03-18 23:49 ./usr/share/locale/ml/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/mr/LC_MESSAGES/ -rw-r--r-- root/root 13817 2009-03-18 23:49 ./usr/share/locale/mr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 9176 2009-03-18 23:49 ./usr/share/locale/nb/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 9527 2009-03-18 23:49 ./usr/share/locale/nl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nn/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/nn/LC_MESSAGES/ -rw-r--r-- root/root 6619 2009-03-18 23:49 ./usr/share/locale/nn/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/oc/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/oc/LC_MESSAGES/ -rw-r--r-- root/root 7557 2009-03-18 23:49 ./usr/share/locale/oc/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/or/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/or/LC_MESSAGES/ -rw-r--r-- root/root 15549 2009-03-18 23:49 ./usr/share/locale/or/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pa/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pa/LC_MESSAGES/ -rw-r--r-- root/root 13345 2009-03-18 23:49 ./usr/share/locale/pa/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 9792 2009-03-18 23:49 ./usr/share/locale/pl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ps/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ps/LC_MESSAGES/ -rw-r--r-- root/root 7259 2009-03-18 23:49 ./usr/share/locale/ps/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 9743 2009-03-18 23:49 ./usr/share/locale/pt/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 9976 2009-03-18 23:49 ./usr/share/locale/pt_BR/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 10022 2009-03-18 23:49 ./usr/share/locale/ro/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 13137 2009-03-18 23:49 ./usr/share/locale/ru/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sl/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sl/LC_MESSAGES/ -rw-r--r-- root/root 9496 2009-03-18 23:49 ./usr/share/locale/sl/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sq/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sq/LC_MESSAGES/ -rw-r--r-- root/root 9780 2009-03-18 23:49 ./usr/share/locale/sq/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 12310 2009-03-18 23:49 ./usr/share/locale/sr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr@latin/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sr@latin/LC_MESSAGES/ -rw-r--r-- root/root 9775 2009-03-18 23:49 ./usr/share/locale/sr@latin/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 9638 2009-03-18 23:49 ./usr/share/locale/sv/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ta/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/ta/LC_MESSAGES/ -rw-r--r-- root/root 17126 2009-03-18 23:49 ./usr/share/locale/ta/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/te/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/te/LC_MESSAGES/ -rw-r--r-- root/root 14950 2009-03-18 23:49 ./usr/share/locale/te/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 13801 2009-03-18 23:49 ./usr/share/locale/th/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 9404 2009-03-18 23:49 ./usr/share/locale/tr/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 12818 2009-03-18 23:49 ./usr/share/locale/uk/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 10162 2009-03-18 23:49 ./usr/share/locale/vi/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 8974 2009-03-18 23:49 ./usr/share/locale/zh_CN/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_HK/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_HK/LC_MESSAGES/ -rw-r--r-- root/root 9174 2009-03-18 23:49 ./usr/share/locale/zh_HK/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 9177 2009-03-18 23:49 ./usr/share/locale/zh_TW/LC_MESSAGES/cheese.mo drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/actions/ -rw-r--r-- root/root 745 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/16x16/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/actions/ -rw-r--r-- root/root 866 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/22x22/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/actions/ -rw-r--r-- root/root 896 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/24x24/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/actions/ -rw-r--r-- root/root 1556 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/32x32/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/actions/ -rw-r--r-- root/root 2722 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/48x48/actions/browse-webcam-effects.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/actions/ -rw-r--r-- root/root 23659 2009-03-18 23:49 ./usr/share/cheese/icons/hicolor/scalable/actions/browse-webcam-effects.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/effects/ -rw-r--r-- root/root 27289 2009-03-18 23:49 ./usr/share/cheese/effects/dicetv.png -rw-r--r-- root/root 32141 2009-03-18 23:49 ./usr/share/cheese/effects/edgetv.png -rw-r--r-- root/root 21118 2009-03-18 23:49 ./usr/share/cheese/effects/Hulk.png -rw-r--r-- root/root 19816 2009-03-18 23:49 ./usr/share/cheese/effects/identity.png -rw-r--r-- root/root 20317 2009-03-18 23:49 ./usr/share/cheese/effects/Mauve.png -rw-r--r-- root/root 12765 2009-03-18 23:49 ./usr/share/cheese/effects/NoirBlanc.png -rw-r--r-- root/root 12482 2009-03-18 23:49 ./usr/share/cheese/effects/Saturation.png -rw-r--r-- root/root 27488 2009-03-18 23:49 ./usr/share/cheese/effects/shagadelictv.png -rw-r--r-- root/root 26408 2009-03-18 23:49 ./usr/share/cheese/effects/vertigotv.png -rw-r--r-- root/root 19652 2009-03-18 23:49 ./usr/share/cheese/effects/videoflip_h.png -rw-r--r-- root/root 19558 2009-03-18 23:49 ./usr/share/cheese/effects/videoflip_v.png -rw-r--r-- root/root 20932 2009-03-18 23:49 ./usr/share/cheese/effects/warptv.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/pixmaps/ -rw-r--r-- root/root 908 2009-03-18 23:49 ./usr/share/cheese/pixmaps/thumbnail-frame.png -rw-r--r-- root/root 5108 2009-03-18 23:49 ./usr/share/cheese/pixmaps/camera-icon.svg -rw-r--r-- root/root 43694 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-1.svg -rw-r--r-- root/root 16970 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-2.svg -rw-r--r-- root/root 23023 2009-03-18 23:49 ./usr/share/cheese/pixmaps/cheese-3.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/cheese/sounds/ -rw-r--r-- root/root 9420 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter0.ogg -rw-r--r-- root/root 30289 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter1.ogg -rw-r--r-- root/root 17024 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter2.ogg -rw-r--r-- root/root 26650 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter3.ogg -rw-r--r-- root/root 22302 2009-03-18 23:49 ./usr/share/cheese/sounds/shutter4.ogg -rw-r--r-- root/root 376 2009-03-18 23:49 ./usr/share/cheese/gtkrc -rw-r--r-- root/root 39308 2009-03-18 23:49 ./usr/share/cheese/cheese.ui -rw-r--r-- root/root 1301 2009-03-18 23:49 ./usr/share/cheese/cheese-ui.xml -rw-r--r-- root/root 5837 2009-03-18 23:49 ./usr/share/cheese/cheese-prefs.ui drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 645 2009-03-18 23:49 ./usr/share/icons/hicolor/16x16/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 935 2009-03-18 23:49 ./usr/share/icons/hicolor/22x22/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 915 2009-03-18 23:49 ./usr/share/icons/hicolor/24x24/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2107 2009-03-18 23:49 ./usr/share/icons/hicolor/32x32/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 3198 2009-03-18 23:49 ./usr/share/icons/hicolor/48x48/apps/cheese.png drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 23050 2009-03-18 23:49 ./usr/share/icons/hicolor/scalable/apps/cheese.svg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/applications/ -rw-r--r-- root/root 451 2009-03-18 23:49 ./usr/share/applications/cheese.desktop drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/dbus-1/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/dbus-1/services/ -rw-r--r-- root/root 59 2009-03-18 23:49 ./usr/share/dbus-1/services/org.gnome.Cheese.service drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/ -rw-r--r-- root/root 3672 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/legal.xml -rw-r--r-- root/root 21109 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/ -rw-r--r-- root/root 297091 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/cheese-screenshot.jpg -rw-r--r-- root/root 288651 2009-03-18 23:49 ./usr/share/gnome/help/cheese/C/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/ -rw-r--r-- root/root 24297 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/ -rw-r--r-- root/root 138960 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/cheese-screenshot.jpg -rw-r--r-- root/root 151412 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ca/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/ -rw-r--r-- root/root 25562 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/ -rw-r--r-- root/root 34483 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/ -rw-r--r-- root/root 22911 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/ -rw-r--r-- root/root 24315 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/ -rw-r--r-- root/root 302843 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/cheese-screenshot.jpg -rw-r--r-- root/root 296437 2009-03-18 23:49 ./usr/share/gnome/help/cheese/es/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/ -rw-r--r-- root/root 25298 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/ -rw-r--r-- root/root 80368 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/cheese-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/ -rw-r--r-- root/root 25089 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/ -rw-r--r-- root/root 72763 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/cheese-screenshot.jpg -rw-r--r-- root/root 70249 2009-03-18 23:49 ./usr/share/gnome/help/cheese/nl/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/ -rw-r--r-- root/root 25054 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/ -rw-r--r-- root/root 24679 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/ -rw-r--r-- root/root 83154 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/cheese-screenshot.jpg -rw-r--r-- root/root 96957 2009-03-18 23:49 ./usr/share/gnome/help/cheese/pt_BR/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/ -rw-r--r-- root/root 27633 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/ -rw-r--r-- root/root 23970 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/ -rw-r--r-- root/root 68567 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/cheese-screenshot.jpg -rw-r--r-- root/root 94971 2009-03-18 23:49 ./usr/share/gnome/help/cheese/sv/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/ -rw-r--r-- root/root 38446 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/cheese.xml drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/ -rw-r--r-- root/root 87479 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/cheese-screenshot.jpg -rw-r--r-- root/root 100823 2009-03-18 23:49 ./usr/share/gnome/help/cheese/th/figures/cheese-effects-screenshot.jpg drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/omf/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/omf/cheese/ -rw-r--r-- root/root 978 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-C.omf -rw-r--r-- root/root 981 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-ca.omf -rw-r--r-- root/root 1010 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-de.omf -rw-r--r-- root/root 987 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-el.omf -rw-r--r-- root/root 962 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-en_GB.omf -rw-r--r-- root/root 994 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-es.omf -rw-r--r-- root/root 1020 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-fr.omf -rw-r--r-- root/root 1000 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-nl.omf -rw-r--r-- root/root 983 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-oc.omf -rw-r--r-- root/root 989 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-pt_BR.omf -rw-r--r-- root/root 996 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-ru.omf -rw-r--r-- root/root 978 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-sv.omf -rw-r--r-- root/root 1143 2009-03-18 23:49 ./usr/share/omf/cheese/cheese-th.omf drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/man/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/man/man1/ -rw-r--r-- root/root 297 2009-03-18 23:49 ./usr/share/man/man1/cheese.1.gz drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/doc/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/doc/cheese-hildon/ -rw-r--r-- root/root 1025 2009-03-16 17:46 ./usr/share/doc/cheese-hildon/README -rw-r--r-- root/root 1333 2009-03-16 17:46 ./usr/share/doc/cheese-hildon/AUTHORS -rw-r--r-- root/root 2812 2009-03-18 23:48 ./usr/share/doc/cheese-hildon/copyright -rw-r--r-- root/root 9569 2009-03-16 17:49 ./usr/share/doc/cheese-hildon/NEWS.gz -rw-r--r-- root/root 4321 2009-03-18 23:48 ./usr/share/doc/cheese-hildon/changelog.Debian.gz drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gconf/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 3611 2009-03-18 23:49 ./usr/share/gconf/schemas/cheese.schemas drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/cheese/ drwxr-xr-x root/root 0 2009-03-18 23:49 ./usr/lib/cheese/cheese/ -rwxr-xr-x root/root 63 2009-03-18 23:49 ./usr/lib/cheese/cheese/cheese-bugreport.sh lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/de/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/el/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/en_GB/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/fr/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/oc/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/cheese-screenshot.jpg -> ../../C/figures/cheese-screenshot.jpg lrwxrwxrwx root/root 0 2009-03-18 23:49 ./usr/share/gnome/help/cheese/ru/figures/cheese-effects-screenshot.jpg -> ../../C/figures/cheese-effects-screenshot.jpg cheese_2.26.0-0ubuntu1_lpia.changes: Format: 1.8 Date: Thu, 19 Mar 2009 00:24:22 +0100 Source: cheese Binary: cheese cheese-hildon Architecture: lpia_translations lpia Version: 2.26.0-0ubuntu1 Distribution: jaunty Urgency: low Maintainer: Ubuntu/lpia Build Daemon Changed-By: Andreas Moog Description: cheese - A tool to take pictures and videos from your webcam cheese-hildon - A tool to take pictures and videos for Hildon enviornments Launchpad-Bugs-Fixed: 345143 Changes: cheese (2.26.0-0ubuntu1) jaunty; urgency=low . * New upstream release (LP: #345143) - Lock gdk mutex in photo-saved and video-saved callbacks Those signals are emitted within a gstreamer callback so outside the mainloop, hence the need for locking. This fixes the flash locking issue and also the one about the grey thumbview right after the flash. - updated translations Checksums-Sha1: 68a29b35498041c06d0ecb6e45949eb9e0af8318 283555 cheese_2.26.0-0ubuntu1_lpia_translations.tar.gz b20ed1a6a8db4ece998b74e2cde4873cdf8cbc16 2808742 cheese_2.26.0-0ubuntu1_lpia.deb 9ad6907637864c4934df789ce23bbb237b3752bc 2808892 cheese-hildon_2.26.0-0ubuntu1_lpia.deb Checksums-Sha256: aed83a2648b3ab7358985993c5c6eed2b028c2a1c83a39c737bf97e2759308d0 283555 cheese_2.26.0-0ubuntu1_lpia_translations.tar.gz 231bd4128ddde9b828b938a2586345e386235b2cd6535fb567f0c0081ff3eb7c 2808742 cheese_2.26.0-0ubuntu1_lpia.deb 5cd572bb04fde14763585092b8e5d0e95e24cc2fc0737c3336078772dddbd38c 2808892 cheese-hildon_2.26.0-0ubuntu1_lpia.deb Files: de6320e43561d58c37dd73067d70389c 283555 raw-translations - cheese_2.26.0-0ubuntu1_lpia_translations.tar.gz f5408d2163f9be0b8a5fb72951137366 2808742 gnome optional cheese_2.26.0-0ubuntu1_lpia.deb 5622b970793f18694cbd9d012262be6b 2808892 gnome optional cheese-hildon_2.26.0-0ubuntu1_lpia.deb ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/cheese-2.26.0 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --root=/home/buildd/build-910438-2072178/chroot-autobuild --purge groff-base libavahi-common3 libxfixes-dev libx11-data libgnome2-0 esound-common m4 libgconf2-dev fontconfig-config libstartup-notification0-dev gettext file zlib1g-dev libhtml-parser-perl libselinux1-dev ttf-dejavu libbonobo2-dev libcairo2 x11-common libidl-dev python2.6 libx11-dev libhildon-1-0 libxi6 automake libjpeg62 libbonobo2-common libxcursor1 libgstreamer0.10-0 libavahi-glib-dev x11proto-input-dev libexpat1-dev libpixman-1-dev libjpeg62-dev libxcomposite-dev libnspr4-dev libfontconfig1 libnspr4-0d sgml-base libgnutls26 libdbus-glib-1-2 docbook-xml libgstreamer-plugins-base0.10-0 libgstreamer0.10-dev xsltproc libsysfs-dev libx11-6 libkrb53 xtrans-dev x11proto-randr-dev psmisc libhal-storage1 gnome-doc-utils libglib2.0-0 libnewt0.52 libxinerama-dev libpango1.0-common libhal1 libxdamage1 libaudiofile0 libedataserver1.2-dev libtasn1-3 sgml-data libxml2-utils libdbus-1-dev libhtml-tree-perl libglib2.0-dev libxcb-render-util0 gconf2 libgpg-error-dev libdirectfb-dev libhtml-tagset-perl libxml2 dbus x11proto-xext-dev pkg-config python-libxml2 libthai-data libice6 intltool-debian libavahi-client3 libxrender1 liborbit2-dev libfontconfig1-dev libxml2-dev xml-core libtasn1-3-dev libxrandr-dev libxext-dev libaudiofile-dev libdirectfb-extra libxau-dev libgpg-error0 libgnomevfs2-dev libxcb-render-util0-dev check libxrender-dev ttf-dejavu-extra librsvg2-dev libpng12-dev libavahi-common-data libxft2 libreadline5 libpopt-dev consolekit x11proto-render-dev libxext6 libsysfs2 libasound2 libsqlite3-0 libxinerama1 libbonobo2-0 libesd0-dev libdbus-glib-1-dev libxdamage-dev libsm-dev libncursesw5 libgsf-1-common gconf2-common libxdmcp-dev defoma libgnomevfs2-common ttf-dejavu-core readline-common librsvg2-2 libebook1.2-9 libscrollkeeper0 libcairo2-dev libxcb-render0-dev fontconfig liburi-perl libcamel1.2-14 libavahi-client-dev libgcrypt11-dev libstartup-notification0 autotools-dev libavahi-common-dev libcroco3 liborbit2 libgamin0 python-support libpopt0 libfreetype6 libsepol1-dev libice-dev libssl0.9.8 libatk1.0-0 libdbus-1-3 libgnome-desktop-2-11 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 x11proto-damage-dev libidl0 libxcb1 libebook1.2-dev libnss3-1d html2text libgcrypt11 libgsf-1-114 libxrandr2 libsoup2.4-dev libpthread-stubs0 debhelper libkeyutils1 libthai0 python libxslt1.1 libmagic1 libgnutls-dev gnome-pkg-tools gnome-mime-data libexpat1 bsdmainutils libdirectfb-1.0-0 libxau6 fdupes libpango1.0-dev libxcursor-dev libxcomposite1 x11proto-composite-dev adduser libgconf2-4 mime-support x11proto-core-dev whiptail intltool libts-0.0-0 libxcb1-dev libxi-dev gamin libwww-perl libgnome2-common libgstreamer-plugins-base0.10-dev shared-mime-info libxfixes3 libxdmcp6 libgtk2.0-dev po-debconf libavahi-glib1 libatk1.0-dev libxml-parser-perl libxft-dev libhal-dev netbase libpng12-0 man-db libsoup2.4-1 scrollkeeper x11proto-kb-dev libsmbios2 libpixman-1-0 libpolkit-dbus2 x11proto-xinerama-dev libdatrie0 libpthread-stubs0-dev libgnome-desktop-dev libpango1.0-0 ucf cdbs libgtk2.0-common gettext-base libedataserver1.2-11 libhildon-1-dev libgnome2-dev libsm6 libgnomevfs2-0 libesd-alsa0 libxcb-render0 libpolkit2 autoconf (Reading database ... 18841 files and directories currently installed.) Removing gnome-doc-utils ... Removing python-libxml2 ... Removing librsvg2-dev ... Removing libdbus-glib-1-dev ... Removing librsvg2-2 ... Purging configuration files for librsvg2-2 ... Removing python-support ... Purging configuration files for python-support ... dpkg - warning: while removing python-support, directory `/usr/lib/python-support/private' not empty so not removed. dpkg - warning: while removing python-support, directory `/usr/lib/python-support' not empty so not removed. dpkg - warning: while removing python-support, directory `/usr/share/python/runtime.d' not empty so not removed. dpkg - warning: while removing python-support, directory `/usr/share/doc/python-support' not empty so not removed. dpkg - warning: while removing python-support, directory `/usr/share/python-support' not empty so not removed. Removing libebook1.2-dev ... Removing libgsf-1-114 ... Purging configuration files for libgsf-1-114 ... Removing gnome-pkg-tools ... Removing libgstreamer-plugins-base0.10-dev ... Removing libhal-dev ... Removing scrollkeeper ... Purging configuration files for scrollkeeper ... Removing libgnome-desktop-dev ... Removing cdbs ... Removing libhildon-1-dev ... Removing libgnome2-dev ... Removing libgnome2-0 ... Purging configuration files for libgnome2-0 ... Removing libstartup-notification0-dev ... Removing libhildon-1-0 ... Purging configuration files for libhildon-1-0 ... Removing docbook-xml ... Purging configuration files for docbook-xml ... dpkg - warning: while removing docbook-xml, directory `/usr/share/sgml/docbook' not empty so not removed. Removing libgstreamer-plugins-base0.10-0 ... Purging configuration files for libgstreamer-plugins-base0.10-0 ... Removing libgstreamer0.10-dev ... Removing xsltproc ... Removing libedataserver1.2-dev ... Removing sgml-data ... Purging configuration files for sgml-data ... Removing xml-core ... Purging configuration files for xml-core ... dpkg - warning: while removing xml-core, directory `/etc/sgml' not empty so not removed. Removing libgnomevfs2-dev ... Removing check ... Removing libesd0-dev ... Removing libgsf-1-common ... Removing libebook1.2-9 ... Purging configuration files for libebook1.2-9 ... Removing libscrollkeeper0 ... Purging configuration files for libscrollkeeper0 ... Removing libcamel1.2-14 ... Purging configuration files for libcamel1.2-14 ... Removing libavahi-client-dev ... Removing libgnome-desktop-2-11 ... Purging configuration files for libgnome-desktop-2-11 ... Removing libnss3-1d ... Purging configuration files for libnss3-1d ... Removing libsoup2.4-dev ... Removing debhelper ... Removing libxslt1.1 ... Purging configuration files for libxslt1.1 ... Removing libgnutls-dev ... Removing fdupes ... Removing intltool ... Removing libgnome2-common ... Purging configuration files for libgnome2-common ... Removing libgtk2.0-dev ... Removing po-debconf ... Removing libatk1.0-dev ... Removing libxml-parser-perl ... Removing man-db ... Purging configuration files for man-db ... Removing catpages as well as /var/cache/man hierarchy. dpkg - warning: while removing man-db, directory `/usr/share/doc/man-db/examples' not empty so not removed. dpkg - warning: while removing man-db, directory `/usr/share/doc/man-db' not empty so not removed. dpkg - warning: while removing man-db, directory `/usr/share/man-db' not empty so not removed. dpkg - warning: while removing man-db, directory `/usr/share/bug/man-db' not empty so not removed. dpkg - warning: while removing man-db, directory `/usr/lib/man-db' not empty so not removed. Removing libedataserver1.2-11 ... Purging configuration files for libedataserver1.2-11 ... Removing libgnomevfs2-0 ... Purging configuration files for libgnomevfs2-0 ... Removing libesd-alsa0 ... Purging configuration files for libesd-alsa0 ... Removing groff-base ... Purging configuration files for groff-base ... Removing esound-common ... Purging configuration files for esound-common ... Removing libgconf2-dev ... Removing libselinux1-dev ... Removing libbonobo2-dev ... Removing automake ... Removing libgstreamer0.10-0 ... Purging configuration files for libgstreamer0.10-0 ... Removing libavahi-glib-dev ... Removing libxcomposite-dev ... Removing libnspr4-dev ... Removing libnspr4-0d ... Purging configuration files for libnspr4-0d ... Removing sgml-base ... Purging configuration files for sgml-base ... Removing libgnutls26 ... Purging configuration files for libgnutls26 ... Removing libkrb53 ... Purging configuration files for libkrb53 ... Removing libhal-storage1 ... Purging configuration files for libhal-storage1 ... Removing libxinerama-dev ... Removing libhal1 ... Purging configuration files for libhal1 ... Removing libxml2-utils ... Removing libdbus-1-dev ... Removing intltool-debian ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing liborbit2-dev ... dpkg - warning: while removing liborbit2-dev, directory `/usr/share/gtk-doc/html' not empty so not removed. dpkg - warning: while removing liborbit2-dev, directory `/usr/share/gtk-doc' not empty so not removed. Removing libxml2-dev ... Removing libtasn1-3-dev ... Removing libxrandr-dev ... Removing libaudiofile-dev ... Removing libpopt-dev ... Removing libasound2 ... Purging configuration files for libasound2 ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libbonobo2-0 ... Purging configuration files for libbonobo2-0 ... Removing libxdamage-dev ... Removing libgnomevfs2-common ... Purging configuration files for libgnomevfs2-common ... Removing libgcrypt11-dev ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing autotools-dev ... Removing libavahi-common-dev ... Removing libsepol1-dev ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... Removing x11proto-damage-dev ... Removing html2text ... Purging configuration files for html2text ... Removing libgcrypt11 ... Purging configuration files for libgcrypt11 ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing libkeyutils1 ... Purging configuration files for libkeyutils1 ... Removing gnome-mime-data ... Purging configuration files for gnome-mime-data ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libpango1.0-dev ... Removing libxcursor-dev ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing x11proto-composite-dev ... Removing libxi-dev ... Removing libwww-perl ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... dpkg - warning: while removing shared-mime-info, directory `/usr/share/mime' not empty so not removed. Removing libavahi-glib1 ... Purging configuration files for libavahi-glib1 ... Removing libxft-dev ... Removing netbase ... Purging configuration files for netbase ... Removing libsoup2.4-1 ... Purging configuration files for libsoup2.4-1 ... Removing libsmbios2 ... Purging configuration files for libsmbios2 ... Removing x11proto-xinerama-dev ... Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libgtk2.0-common ... Removing autoconf ... Purging configuration files for autoconf ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing libxfixes-dev ... Removing m4 ... Removing gettext ... Removing libidl-dev ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing libbonobo2-common ... Purging configuration files for libbonobo2-common ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing x11proto-randr-dev ... Removing libpango1.0-common ... Purging font configuration of pango... Purging category xfont.. Purging configuration files for libpango1.0-common ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing libaudiofile0 ... Purging configuration files for libaudiofile0 ... Removing libtasn1-3 ... Purging configuration files for libtasn1-3 ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libgpg-error-dev ... Removing libgpg-error0 ... Purging configuration files for libgpg-error0 ... Removing libavahi-common-data ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing libcairo2-dev ... Removing fontconfig ... Purging font configuration of fontconfig... Purging category cid.. Purging category truetype.. Purging category type1.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-dejavu Purging configuration files for fontconfig ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing x11proto-fixes-dev ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing python ... Purging configuration files for python ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libpolkit-dbus2 ... Purging configuration files for libpolkit-dbus2 ... Removing libdatrie0 ... Purging configuration files for libdatrie0 ... Removing gettext-base ... Removing libpolkit2 ... Purging configuration files for libpolkit2 ... Removing libhtml-parser-perl ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing python2.6 ... Purging configuration files for python2.6 ... dpkg - warning: while removing python2.6, directory `/usr/share/applications' not empty so not removed. Removing libpixman-1-dev ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing psmisc ... Purging configuration files for psmisc ... Removing libdirectfb-dev ... Removing libhtml-tagset-perl ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libthai-data ... Removing libfontconfig1-dev ... Removing libxext-dev ... Removing libdirectfb-extra ... Removing libxcb-render-util0-dev ... Removing libxrender-dev ... Removing libpng12-dev ... Removing libreadline5 ... Purging configuration files for libreadline5 ... Removing x11proto-render-dev ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libsm-dev ... Removing libncursesw5 ... Purging configuration files for libncursesw5 ... Removing gconf2-common ... Purging configuration files for gconf2-common ... dpkg - warning: while removing gconf2-common, directory `/usr/share/sgml' not empty so not removed. Removing readline-common ... Purging configuration files for readline-common ... Removing libxcb-render0-dev ... Removing liburi-perl ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing libice-dev ... Removing libssl0.9.8 ... Purging configuration files for libssl0.9.8 ... Removing libfreetype6-dev ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing libdirectfb-1.0-0 ... Purging configuration files for libdirectfb-1.0-0 ... Removing mime-support ... Purging configuration files for mime-support ... Removing libts-0.0-0 ... Purging configuration files for libts-0.0-0 ... Removing libpng12-0 ... Purging configuration files for libpng12-0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing zlib1g-dev ... Removing libx11-dev ... Removing libexpat1-dev ... Removing libjpeg62-dev ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libsysfs-dev ... Removing xtrans-dev ... Removing libxcb-render-util0 ... Purging configuration files for libxcb-render-util0 ... Removing x11proto-xext-dev ... Removing pkg-config ... Removing libice6 ... Purging configuration files for libice6 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libsysfs2 ... Purging configuration files for libsysfs2 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libxcb1-dev ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing ttf-dejavu ... Removing libjpeg62 ... Removing x11proto-input-dev ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing libxau-dev ... Removing ttf-dejavu-extra ... Purging configuration files for ttf-dejavu-extra ... Removing libxdmcp-dev ... Removing ttf-dejavu-core ... Purging configuration files for ttf-dejavu-core ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libpthread-stubs0 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing x11proto-core-dev ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing ucf ... Purging configuration files for ucf ... Removing libx11-data ... Removing x11-common ... Purging configuration files for x11-common ... dpkg - warning: while removing x11-common, directory `/usr/X11R6' not empty so not removed. dpkg - warning: while removing x11-common, directory `/usr/share/X11' not empty so not removed. Removing defoma ... Purging configuration files for defoma ... dpkg - warning: while removing defoma, directory `/usr/share/debhelper/autoscripts' not empty so not removed. dpkg - warning: while removing defoma, directory `/usr/share/debhelper' not empty so not removed. Removing whiptail ... Removing file ... Purging configuration files for file ... Removing libnewt0.52 ... Purging configuration files for libnewt0.52 ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing libgamin0 ... Purging configuration files for libgamin0 ... Removing gamin ... Purging configuration files for gamin ... Removing libglib2.0-0 ... Purging configuration files for libglib2.0-0 ... Removing dbus ... * Stopping system message bus dbus ...done. Purging configuration files for dbus ... dpkg - warning: while removing dbus, directory `/var/lib/dbus' not empty so not removed. Removing consolekit ... Purging configuration files for consolekit ... Removing libdbus-1-3 ... Purging configuration files for libdbus-1-3 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing adduser ... Purging configuration files for adduser ... Processing triggers for libc6 ... ldconfig deferred processing now taking place ****************************************************************************** Finished at 20090318-2350 Build needed 00:01:36, 36360k disk space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '910438-2072178'] Scanning for processes to kill in build 910438-2072178... Scanning for processes to kill in build /home/buildd/build-910438-2072178/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '910438-2072178'] Unmounting chroot for build 910438-2072178... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '910438-2072178'] Removing build 910438-2072178