RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '1125662-2429975', '/home/buildd/filecache-default/30161bb19c60dd2aabf0721a4cfb012c8cc2ace3'] Synching the system clock with the buildd NTP service... 20 Jul 15:46:21 ntpdate[17844]: adjust time server 10.211.37.1 offset -0.000117 sec Unpacking chroot for build 1125662-2429975 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '1125662-2429975'] Mounting chroot for build 1125662-2429975 RUN: /usr/share/launchpad-buildd/slavebin/apply-ogre-model ['apply-ogre-model', '1125662-2429975', 'universe'] Attempting OGRE for universe in build-1125662-2429975 RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '1125662-2429975', 'deb http://ftpmaster.internal/ubuntu karmic main universe'] Overriding sources.list in build-1125662-2429975 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '1125662-2429975'] Updating debian chroot for build 1125662-2429975 Get:1 http://ftpmaster.internal karmic Release.gpg [189B] Get:2 http://ftpmaster.internal karmic Release [65.9kB] Get:3 http://ftpmaster.internal karmic/main Packages [1292kB] Get:4 http://ftpmaster.internal karmic/universe Packages [4980kB] Fetched 6338kB in 3s (1765kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following packages will be REMOVED: upstart-compat-sysv* The following NEW packages will be installed: libdbus-1-3 The following packages will be upgraded: base-files bash binutils bsdutils bzip2 cpp-4.4 debconf debconf-english dpkg dpkg-dev e2fslibs e2fsprogs g++-4.4 gcc-4.4 gcc-4.4-base initscripts libattr1 libblkid1 libbz2-1.0 libc6 libc6-dev libcomerr2 libdb4.7 libgcc1 libgomp1 libncurses5 libpam-modules libpam-runtime libpam0g libselinux1 libsepol1 libss2 libstdc++6 libstdc++6-4.4-dev libuuid1 linux-libc-dev lockfile-progs mount ncurses-base ncurses-bin perl perl-base perl-modules sysv-rc sysvinit-utils upstart util-linux 47 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Need to get 0B/39.2MB of archives. After this operation, 217kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! linux-libc-dev libc6-dev libgomp1 cpp-4.4 gcc-4.4-base libgcc1 gcc-4.4 g++-4.4 libstdc++6-4.4-dev libstdc++6 binutils libc6 libselinux1 base-files libpam-modules bash dpkg e2fslibs e2fsprogs libsepol1 mount ncurses-bin perl-modules perl perl-base util-linux bsdutils libncurses5 ncurses-base sysvinit-utils debconf-english debconf libdbus-1-3 upstart libattr1 libuuid1 libblkid1 libcomerr2 libdb4.7 libpam-runtime libpam0g libss2 bzip2 libbz2-1.0 lockfile-progs initscripts sysv-rc dpkg-dev Extracting templates from packages: 62% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. (Reading database ... 9278 files and directories currently installed.) Removing upstart-compat-sysv ... Purging configuration files for upstart-compat-sysv ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9255 files and directories currently installed.) Preparing to replace linux-libc-dev 2.6.30-10.12 (using .../linux-libc-dev_2.6.31-3.19_lpia.deb) ... Unpacking replacement linux-libc-dev ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libc6-dev 2.9-9ubuntu2 (using .../libc6-dev_2.9-20ubuntu2_lpia.deb) ... Unpacking replacement libc6-dev ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libgomp1 4.4.0-8ubuntu2 (using .../libgomp1_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement libgomp1 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace cpp-4.4 4.4.0-8ubuntu2 (using .../cpp-4.4_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement cpp-4.4 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace gcc-4.4-base 4.4.0-8ubuntu2 (using .../gcc-4.4-base_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement gcc-4.4-base ... Setting up gcc-4.4-base (4.4.0-11ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9286 files and directories currently installed.) Preparing to replace libgcc1 1:4.4.0-8ubuntu2 (using .../libgcc1_1%3a4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement libgcc1 ... Setting up libgcc1 (1:4.4.0-11ubuntu1) ... 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 ... 9286 files and directories currently installed.) Preparing to replace gcc-4.4 4.4.0-8ubuntu2 (using .../gcc-4.4_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement gcc-4.4 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace g++-4.4 4.4.0-8ubuntu2 (using .../g++-4.4_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement g++-4.4 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libstdc++6-4.4-dev 4.4.0-8ubuntu2 (using .../libstdc++6-4.4-dev_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement libstdc++6-4.4-dev ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libstdc++6 4.4.0-8ubuntu2 (using .../libstdc++6_4.4.0-11ubuntu1_lpia.deb) ... Unpacking replacement libstdc++6 ... Setting up libstdc++6 (4.4.0-11ubuntu1) ... 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 ... 9286 files and directories currently installed.) Preparing to replace binutils 2.19.51.20090622-0ubuntu1 (using .../binutils_2.19.51.20090714-0ubuntu1_lpia.deb) ... Unpacking replacement binutils ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libc6 2.9-9ubuntu2 (using .../libc6_2.9-20ubuntu2_lpia.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.9-20ubuntu2) ... Installing new version of config file /etc/init.d/glibc.sh ... Installing new version of config file /etc/bindresvport.blacklist ... 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 ... 9286 files and directories currently installed.) Preparing to replace libselinux1 2.0.65-5build1 (using .../libselinux1_2.0.82-1ubuntu2_lpia.deb) ... Unpacking replacement libselinux1 ... Setting up libselinux1 (2.0.82-1ubuntu2) ... init: Not being executed as init 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 ... 9286 files and directories currently installed.) Preparing to replace base-files 5.0.0ubuntu2 (using .../base-files_5.0.0ubuntu6_lpia.deb) ... Unpacking replacement base-files ... Setting up base-files (5.0.0ubuntu6) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9290 files and directories currently installed.) Preparing to replace libpam-modules 1.0.1-9ubuntu1 (using .../libpam-modules_1.0.1-9ubuntu3_lpia.deb) ... Unpacking replacement libpam-modules ... Setting up libpam-modules (1.0.1-9ubuntu3) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9290 files and directories currently installed.) Preparing to replace bash 3.2-5ubuntu1 (using .../bash_3.2-5ubuntu2_lpia.deb) ... Unpacking replacement bash ... Setting up bash (3.2-5ubuntu2) ... Installing new version of config file /etc/bash.bashrc ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9290 files and directories currently installed.) Preparing to replace dpkg 1.14.24ubuntu2 (using .../dpkg_1.15.3.1ubuntu1_lpia.deb) ... Unpacking replacement dpkg ... Setting up dpkg (1.15.3.1ubuntu1) ... Installing new version of config file /etc/logrotate.d/dpkg ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9289 files and directories currently installed.) Preparing to replace e2fslibs 1.41.5-1ubuntu3 (using .../e2fslibs_1.41.8-1ubuntu2_lpia.deb) ... Unpacking replacement e2fslibs ... Setting up e2fslibs (1.41.8-1ubuntu2) ... 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 ... 9289 files and directories currently installed.) Preparing to replace e2fsprogs 1.41.5-1ubuntu3 (using .../e2fsprogs_1.41.8-1ubuntu2_lpia.deb) ... Unpacking replacement e2fsprogs ... Setting up e2fsprogs (1.41.8-1ubuntu2) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9289 files and directories currently installed.) Preparing to replace libsepol1 2.0.32-1ubuntu1 (using .../libsepol1_2.0.36-1_lpia.deb) ... Unpacking replacement libsepol1 ... Setting up libsepol1 (2.0.36-1) ... init: Not being executed as init 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 ... 9289 files and directories currently installed.) Preparing to replace mount 2.15.1~rc1-1ubuntu2 (using .../mount_2.16-1ubuntu1_lpia.deb) ... Unpacking replacement mount ... Setting up mount (2.16-1ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9289 files and directories currently installed.) Preparing to replace ncurses-bin 5.7+20090523-1ubuntu1 (using .../ncurses-bin_5.7+20090607-1ubuntu1_lpia.deb) ... Unpacking replacement ncurses-bin ... Setting up ncurses-bin (5.7+20090607-1ubuntu1) ... (Reading database ... 9289 files and directories currently installed.) Preparing to replace perl-modules 5.10.0-23ubuntu1 (using .../perl-modules_5.10.0-24ubuntu1_all.deb) ... Unpacking replacement perl-modules ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace perl 5.10.0-23ubuntu1 (using .../perl_5.10.0-24ubuntu1_lpia.deb) ... Unpacking replacement perl ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace perl-base 5.10.0-23ubuntu1 (using .../perl-base_5.10.0-24ubuntu1_lpia.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.10.0-24ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9293 files and directories currently installed.) Preparing to replace util-linux 2.15.1~rc1-1ubuntu2 (using .../util-linux_2.16-1ubuntu1_lpia.deb) ... Unpacking replacement util-linux ... Setting up util-linux (2.16-1ubuntu1) ... Installing new version of config file /etc/init.d/hwclock.sh ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9298 files and directories currently installed.) Preparing to replace bsdutils 1:2.15.1~rc1-1ubuntu2 (using .../bsdutils_1%3a2.16-1ubuntu1_lpia.deb) ... Unpacking replacement bsdutils ... Setting up bsdutils (1:2.16-1ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9298 files and directories currently installed.) Preparing to replace libncurses5 5.7+20090523-1ubuntu1 (using .../libncurses5_5.7+20090607-1ubuntu1_lpia.deb) ... Unpacking replacement libncurses5 ... Setting up libncurses5 (5.7+20090607-1ubuntu1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place (Reading database ... 9298 files and directories currently installed.) Preparing to replace ncurses-base 5.7+20090523-1ubuntu1 (using .../ncurses-base_5.7+20090607-1ubuntu1_all.deb) ... Unpacking replacement ncurses-base ... Setting up ncurses-base (5.7+20090607-1ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9298 files and directories currently installed.) Preparing to replace sysvinit-utils 2.86.ds1-61ubuntu13 (using .../sysvinit-utils_2.86.ds1-61ubuntu15_lpia.deb) ... Unpacking replacement sysvinit-utils ... Setting up sysvinit-utils (2.86.ds1-61ubuntu15) ... (Reading database ... 9298 files and directories currently installed.) Preparing to replace debconf-english 1.5.26ubuntu3 (using .../debconf-english_1.5.27ubuntu1_all.deb) ... Unpacking replacement debconf-english ... Setting up debconf-english (1.5.27ubuntu1) ... (Reading database ... 9298 files and directories currently installed.) Preparing to replace debconf 1.5.26ubuntu3 (using .../debconf_1.5.27ubuntu1_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.27ubuntu1) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdbus-1-3. (Reading database ... 9298 files and directories currently installed.) Unpacking libdbus-1-3 (from .../libdbus-1-3_1.2.16-0ubuntu2_lpia.deb) ... Setting up libdbus-1-3 (1.2.16-0ubuntu2) ... 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 ... 9306 files and directories currently installed.) Preparing to replace upstart 0.3.10-2 (using .../upstart_0.6.1-1_lpia.deb) ... Unpacking replacement upstart ... dpkg: warning - unable to delete old directory `/etc/event.d': Directory not empty dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libattr1 1:2.4.43-2 (using .../libattr1_1%3a2.4.43-3_lpia.deb) ... Unpacking replacement libattr1 ... Setting up libattr1 (1:2.4.43-3) ... 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 ... 9350 files and directories currently installed.) Preparing to replace libuuid1 1.41.5-1ubuntu3 (using .../libuuid1_2.16-1ubuntu1_lpia.deb) ... Unpacking replacement libuuid1 ... Setting up libuuid1 (2.16-1ubuntu1) ... 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 ... 9350 files and directories currently installed.) Preparing to replace libblkid1 2.15.1~rc1-1ubuntu2 (using .../libblkid1_2.16-1ubuntu1_lpia.deb) ... Unpacking replacement libblkid1 ... Setting up libblkid1 (2.16-1ubuntu1) ... 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 ... 9350 files and directories currently installed.) Preparing to replace libcomerr2 1.41.5-1ubuntu3 (using .../libcomerr2_1.41.8-1ubuntu2_lpia.deb) ... Unpacking replacement libcomerr2 ... Setting up libcomerr2 (1.41.8-1ubuntu2) ... 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 ... 9350 files and directories currently installed.) Preparing to replace libdb4.7 4.7.25-6ubuntu1 (using .../libdb4.7_4.7.25-7ubuntu2_lpia.deb) ... Unpacking replacement libdb4.7 ... Setting up libdb4.7 (4.7.25-7ubuntu2) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place (Reading database ... 9350 files and directories currently installed.) Preparing to replace libpam-runtime 1.0.1-9ubuntu1 (using .../libpam-runtime_1.0.1-9ubuntu3_all.deb) ... Unpacking replacement libpam-runtime ... Setting up libpam-runtime (1.0.1-9ubuntu3) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) (Reading database ... 9350 files and directories currently installed.) Preparing to replace libpam0g 1.0.1-9ubuntu1 (using .../libpam0g_1.0.1-9ubuntu3_lpia.deb) ... Unpacking replacement libpam0g ... Setting up libpam0g (1.0.1-9ubuntu3) ... 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 ... 9350 files and directories currently installed.) Preparing to replace libss2 1.41.5-1ubuntu3 (using .../libss2_1.41.8-1ubuntu2_lpia.deb) ... Unpacking replacement libss2 ... Setting up libss2 (1.41.8-1ubuntu2) ... 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 ... 9350 files and directories currently installed.) Preparing to replace bzip2 1.0.5-2ubuntu1 (using .../bzip2_1.0.5-3_lpia.deb) ... Unpacking replacement bzip2 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace libbz2-1.0 1.0.5-2ubuntu1 (using .../libbz2-1.0_1.0.5-3_lpia.deb) ... Unpacking replacement libbz2-1.0 ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace lockfile-progs 0.1.11ubuntu2 (using .../lockfile-progs_0.1.13_lpia.deb) ... Unpacking replacement lockfile-progs ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Preparing to replace initscripts 2.86.ds1-61ubuntu13 (using .../initscripts_2.86.ds1-61ubuntu15_lpia.deb) ... Unpacking replacement initscripts ... Preparing to replace sysv-rc 2.86.ds1-61ubuntu13 (using .../sysv-rc_2.86.ds1-61ubuntu15_all.deb) ... Unpacking replacement sysv-rc ... Preparing to replace dpkg-dev 1.14.24ubuntu2 (using .../dpkg-dev_1.15.3.1ubuntu1_all.deb) ... Unpacking replacement dpkg-dev ... Setting up linux-libc-dev (2.6.31-3.19) ... Setting up libc6-dev (2.9-20ubuntu2) ... Setting up libgomp1 (4.4.0-11ubuntu1) ... Setting up cpp-4.4 (4.4.0-11ubuntu1) ... Setting up binutils (2.19.51.20090714-0ubuntu1) ... Setting up gcc-4.4 (4.4.0-11ubuntu1) ... Setting up libbz2-1.0 (1.0.5-3) ... Setting up bzip2 (1.0.5-3) ... Setting up lockfile-progs (0.1.13) ... Setting up initscripts (2.86.ds1-61ubuntu15) ... Installing new version of config file /etc/init.d/mountkernfs.sh ... Setting up sysv-rc (2.86.ds1-61ubuntu15) ... Setting up upstart (0.6.1-1) ... Setting up g++-4.4 (4.4.0-11ubuntu1) ... Setting up perl-modules (5.10.0-24ubuntu1) ... Setting up libstdc++6-4.4-dev (4.4.0-11ubuntu1) ... Setting up perl (5.10.0-24ubuntu1) ... Setting up dpkg-dev (1.15.3.1ubuntu1) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', '1125662-2429975', '--nolog', '--batch', '--archive=ubuntu', '--purpose=PRIMARY', '--dist=karmic', '--comp=universe', 'muine_0.8.10-5.dsc'] Initiating build Automatic build of muine_0.8.10-5 on molybdenum by sbuild/lpia 1.170.5 Build started at 20090720-1547 ****************************************************************************** muine_0.8.10-5.dsc exists in cwd ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7.0.50), mono-devel (>= 2.0), libgtk2.0-dev (>= 2.6.0), libgdbm-dev (>= 1.8.0), libogg-dev (>= 1.0), libvorbis-dev (>= 1.0), libid3tag0-dev (>= 0.15.1b-3), libflac-dev (>= 1.1.2), autotools-dev, libmono-dev (>= 1.1.6), libgconf2-dev (>= 2.4.0), libgnomevfs2-dev (>= 2.4.0), libgnome2-dev (>= 2.4.0), libgstreamer0.10-dev (>= 0.10.0), gstreamer0.10-plugins-good (>= 0.10.0), intltool, libgtk2.0-cil (>= 2.12.9), libgnome2.24-cil, libglade2.0-cil (>= 1.9.2), libgconf2.0-cil (>= 1.9.2), libndesk-dbus1.0-cil (>= 0.4), libndesk-dbus-glib1.0-cil (>= 0.3), gnome-icon-theme (>= 2.8.0), cli-common-dev (>= 0.5.7), monodoc-base (>= 1.1.10), libmono-cairo2.0-cil (>= 1.1.13), libnotify-dev, libmusicbrainz4-dev, quilt Checking for already installed source dependencies... debhelper: missing mono-devel: missing libgtk2.0-dev: missing libgdbm-dev: missing libogg-dev: missing libvorbis-dev: missing libid3tag0-dev: missing libflac-dev: missing autotools-dev: missing libmono-dev: missing libgconf2-dev: missing libgnomevfs2-dev: missing libgnome2-dev: missing libgstreamer0.10-dev: missing gstreamer0.10-plugins-good: missing intltool: missing libgtk2.0-cil: missing libgnome2.24-cil: missing libglade2.0-cil: missing libgconf2.0-cil: missing libndesk-dbus1.0-cil: missing libndesk-dbus-glib1.0-cil: missing gnome-icon-theme: missing cli-common-dev: missing monodoc-base: missing libmono-cairo2.0-cil: missing libnotify-dev: missing libmusicbrainz4-dev: missing quilt: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper mono-devel libgtk2.0-dev libgdbm-dev libogg-dev libvorbis-dev libid3tag0-dev libflac-dev autotools-dev libmono-dev libgconf2-dev libgnomevfs2-dev libgnome2-dev libgstreamer0.10-dev gstreamer0.10-plugins-good intltool libgtk2.0-cil libgnome2.24-cil libglade2.0-cil libgconf2.0-cil libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil gnome-icon-theme cli-common-dev monodoc-base libmono-cairo2.0-cil libnotify-dev libmusicbrainz4-dev quilt Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libvolume-id1 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: adduser autoconf automake bsdmainutils check cli-common consolekit dbus dbus-x11 defoma devicekit-disks diffstat esound-common file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-mime-data groff-base gstreamer0.10-plugins-base gvfs hicolor-icon-theme html2text intltool-debian libaa1 libart-2.0-2 libart2.0-cil libasound2 libatasmart0 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 libavc1394-0 libbonobo2-0 libbonobo2-common libbonobo2-dev libbonoboui2-0 libbonoboui2-common libcaca0 libcairo2 libcairo2-dev libcdparanoia0 libck-connector0 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdevmapper1.02.1 libdirectfb-1.2-0 libdirectfb-dev libdirectfb-extra libdv4 libeggdbus-1-0 libesd-alsa0 libesd0-dev libexif12 libexpat1 libexpat1-dev libflac8 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail-common libgail18 libgamin0 libgconf2-4 libgcrypt11 libgcrypt11-dev libgdiplus libgdu0 libgif4 libglade2-0 libglib2.0-0 libglib2.0-cil libglib2.0-dev libgnome-keyring0 libgnome-vfs2.0-cil libgnome2-0 libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgnutls-dev libgnutls26 libgpg-error-dev libgpg-error0 libgpm2 libgsf-1-114 libgsf-1-common libgssapi-krb5-2 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgudev-1.0-0 libgvfscommon0 libhal-storage1 libhal1 libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libid3tag0 libidl-dev libidl0 libiec61883-0 libjasper1 libjpeg62 libjpeg62-dev libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libmagic1 libmono-cecil-private-cil libmono-corlib1.0-cil libmono-corlib2.0-cil libmono-data-tds1.0-cil libmono-data-tds2.0-cil libmono-getoptions2.0-cil libmono-peapi2.0-cil libmono-posix2.0-cil libmono-relaxng1.0-cil libmono-security1.0-cil libmono-security2.0-cil libmono-sharpzip0.84-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system-data1.0-cil libmono-system-data2.0-cil libmono-system-runtime1.0-cil libmono-system-web1.0-cil libmono-system-web2.0-cil libmono-system1.0-cil libmono-system2.0-cil libmono0 libmono2.0-cil libmusicbrainz4c2a libncursesw5 libnewt0.52 libnotify1 libogg0 liboil0.3 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libparted1.8-12 libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.6 libraw1394-11 libraw1394-8 libreadline5 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules libselinux1-dev libsepol1-dev libsgutils2-2 libshout3 libsm-dev libsm6 libsoup2.4-1 libspeex1 libsqlite0 libsqlite3-0 libssl0.9.8 libsysfs-dev libsysfs2 libtag1-vanilla libtag1c2a libtasn1-3 libtasn1-3-dev libthai-data libthai0 libtheora0 libtiff4 libts-0.0-0 libudev0 liburi-perl libv4l-0 libvisual-0.4-0 libvorbis0a libvorbisenc2 libvorbisfile3 libwavpack1 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-dom-perl libxml-parser-perl libxml-perl libxml-regexp-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxv1 m4 man-db mime-support mono-2.0-devel mono-2.0-gac mono-gac mono-gmcs mono-runtime mono-utils netbase pkg-config po-debconf policykit-1 policykit-1-gnome psmisc python python2.6 readline-common shared-mime-info tsconf 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 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 dh-make defoma-doc psfontmgr x-ttcidfont-conf dfontmgr libft-perl gconf-defaults-service cvs gettext-doc groff monodoc-gtk2.0-manual libasound2-plugins libbonobo2-bin libcairo2-doc cups-common libdv-bin esound rng-tools libgcrypt11-doc libglib2.0-doc desktop-base libgnome2-doc libgnomevfs2-bin gnutls-doc gnutls-bin guile-gnutls gpm krb5-doc krb5-user libvisual-0.4-plugins gstreamer-codec-install gnome-codec-install gstreamer0.10-tools gstreamer0.10-plugins gstreamer0.10-doc libgtk2.0-doc libdata-dump-perl libjasper-runtime libmono-i18n1.0-cil libmono-i18n2.0-cil libmono-winforms2.0-cil libmono-winforms1.0-cil 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 parted nparted libparted1.8-dev libparted1.8-i18n libraw1394-doc librsvg2-bin libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal sg3-utils speex libcrypt-ssleay-perl libio-socket-ssl-perl less www-browser libmail-box-perl python-doc python-tk python-profiler python2.6-doc python2.6-profiler procmail graphviz Recommended packages: libpam-ck-connector esound-clients curl wget lynx gstreamer0.10-x gvfs-backends libatk1.0-data dmsetup libglib2.0-data gnome-keyring libgnomevfs2-extra gnome-mount libmono-i18n-west1.0-cil libmono-i18n-west2.0-cil libfribidi0 notification-daemon orbit2 libmailtools-perl libhtml-format-perl libcompress-bzip2-perl xml-core mono-csharp-shell binfmt-support ifupdown libmail-sendmail-perl The following NEW packages will be installed: adduser autoconf automake autotools-dev bsdmainutils check cli-common cli-common-dev consolekit dbus dbus-x11 debhelper defoma devicekit-disks diffstat esound-common file fontconfig fontconfig-config gamin gconf2 gconf2-common gettext gettext-base gnome-icon-theme gnome-mime-data groff-base gstreamer0.10-plugins-base gstreamer0.10-plugins-good gvfs hicolor-icon-theme html2text intltool intltool-debian libaa1 libart-2.0-2 libart2.0-cil libasound2 libatasmart0 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 libavc1394-0 libbonobo2-0 libbonobo2-common libbonobo2-dev libbonoboui2-0 libbonoboui2-common libcaca0 libcairo2 libcairo2-dev libcdparanoia0 libck-connector0 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libdevmapper1.02.1 libdirectfb-1.2-0 libdirectfb-dev libdirectfb-extra libdv4 libeggdbus-1-0 libesd-alsa0 libesd0-dev libexif12 libexpat1 libexpat1-dev libflac-dev libflac8 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgail-common libgail18 libgamin0 libgconf2-4 libgconf2-dev libgconf2.0-cil libgcrypt11 libgcrypt11-dev libgdbm-dev libgdiplus libgdu0 libgif4 libglade2-0 libglade2.0-cil libglib2.0-0 libglib2.0-cil libglib2.0-dev libgnome-keyring0 libgnome-vfs2.0-cil libgnome2-0 libgnome2-common libgnome2-dev libgnome2.24-cil libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgnomevfs2-dev libgnutls-dev libgnutls26 libgpg-error-dev libgpg-error0 libgpm2 libgsf-1-114 libgsf-1-common libgssapi-krb5-2 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libgstreamer0.10-dev libgtk2.0-0 libgtk2.0-bin libgtk2.0-cil libgtk2.0-common libgtk2.0-dev libgudev-1.0-0 libgvfscommon0 libhal-storage1 libhal1 libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libid3tag0 libid3tag0-dev libidl-dev libidl0 libiec61883-0 libjasper1 libjpeg62 libjpeg62-dev libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.4-2 libmagic1 libmono-cairo2.0-cil libmono-cecil-private-cil libmono-corlib1.0-cil libmono-corlib2.0-cil libmono-data-tds1.0-cil libmono-data-tds2.0-cil libmono-dev libmono-getoptions2.0-cil libmono-peapi2.0-cil libmono-posix2.0-cil libmono-relaxng1.0-cil libmono-security1.0-cil libmono-security2.0-cil libmono-sharpzip0.84-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system-data1.0-cil libmono-system-data2.0-cil libmono-system-runtime1.0-cil libmono-system-web1.0-cil libmono-system-web2.0-cil libmono-system1.0-cil libmono-system2.0-cil libmono0 libmono2.0-cil libmusicbrainz4-dev libmusicbrainz4c2a libncursesw5 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libnewt0.52 libnotify-dev libnotify1 libogg-dev libogg0 liboil0.3 liborbit2 liborbit2-dev libpango1.0-0 libpango1.0-common libpango1.0-dev libparted1.8-12 libpixman-1-0 libpixman-1-dev libpng12-0 libpng12-dev libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpopt-dev libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.6 libraw1394-11 libraw1394-8 libreadline5 librsvg2-2 librsvg2-common libsasl2-2 libsasl2-modules libselinux1-dev libsepol1-dev libsgutils2-2 libshout3 libsm-dev libsm6 libsoup2.4-1 libspeex1 libsqlite0 libsqlite3-0 libssl0.9.8 libsysfs-dev libsysfs2 libtag1-vanilla libtag1c2a libtasn1-3 libtasn1-3-dev libthai-data libthai0 libtheora0 libtiff4 libts-0.0-0 libudev0 liburi-perl libv4l-0 libvisual-0.4-0 libvorbis-dev libvorbis0a libvorbisenc2 libvorbisfile3 libwavpack1 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-dom-perl libxml-parser-perl libxml-perl libxml-regexp-perl libxml2 libxml2-dev libxml2-utils libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxv1 m4 man-db mime-support mono-2.0-devel mono-2.0-gac mono-devel mono-gac mono-gmcs mono-runtime mono-utils monodoc-base netbase pkg-config po-debconf policykit-1 policykit-1-gnome psmisc python python2.6 quilt readline-common shared-mime-info tsconf 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 xtrans-dev zlib1g-dev 0 upgraded, 328 newly installed, 0 to remove and 0 not upgraded. Need to get 23.9MB/78.3MB of archives. After this operation, 313MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! x11-common libice6 x11proto-core-dev libice-dev libsm6 libsm-dev libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev libxext6 libxfixes3 libxcomposite1 x11proto-xext-dev x11proto-fixes-dev libxfixes-dev x11proto-composite-dev libxext-dev libxcomposite-dev libxrender1 libxcursor1 x11proto-render-dev libxrender-dev libxcursor-dev libxdamage1 x11proto-damage-dev libxdamage-dev libexpat1 libfreetype6 ucf libnewt0.52 libpopt0 whiptail libmagic1 file defoma ttf-dejavu-core ttf-dejavu-extra ttf-dejavu fontconfig-config libfontconfig1 libxft2 libexpat1-dev zlib1g-dev libfreetype6-dev libglib2.0-0 pkg-config libfontconfig1-dev libxft-dev libxi6 libxi-dev libxinerama1 x11proto-xinerama-dev libxinerama-dev libxrandr2 x11proto-randr-dev libxrandr-dev adduser libdevmapper1.02.1 libgpg-error0 libgcrypt11 libtasn1-3 libgnutls26 libgpm2 libkeyutils1 libkrb5support0 libk5crypto3 libkrb5-3 libgssapi-krb5-2 libssl0.9.8 libsasl2-modules libsasl2-2 libldap-2.4-2 libncursesw5 readline-common libreadline5 libsqlite3-0 libudev0 libxml2 mime-support netbase python2.6 python shared-mime-info bsdmainutils gettext-base groff-base libhtml-tagset-perl liburi-perl libhtml-parser-perl libhtml-tree-perl libparted1.8-12 libwww-perl libxml-parser-perl man-db psmisc m4 autoconf autotools-dev automake check cli-common html2text libcroco3 gettext intltool-debian po-debconf debhelper libmono0 libmono-system2.0-cil libmono-security2.0-cil mono-2.0-gac mono-gac mono-runtime libmono-corlib2.0-cil libmono-corlib1.0-cil mono-utils libmono-cecil-private-cil libmono-getoptions2.0-cil libmono-system1.0-cil libmono-relaxng1.0-cil libmono-security1.0-cil libmono-data-tds2.0-cil libmono-system-data2.0-cil libmono-data-tds1.0-cil libmono-system-data1.0-cil libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0 libpixman-1-0 libpng12-0 libxcb-render0 libxcb-render-util0 libcairo2 libexif12 libgif4 libjpeg62 libtiff4 libgdiplus libmono-system-web1.0-cil libmono-system-runtime1.0-cil libmono-peapi2.0-cil libmono-posix2.0-cil libmono-sharpzip2.84-cil libsqlite0 libmono-sqlite2.0-cil libmono2.0-cil libmono-system-web2.0-cil mono-gmcs libglib2.0-dev libmono-dev mono-2.0-devel mono-devel libxml-perl libxml-regexp-perl libxml-dom-perl cli-common-dev libck-connector0 libdbus-glib-1-2 libeggdbus-1-0 libpolkit-gobject-1-0 dbus consolekit dbus-x11 libatasmart0 libgudev-1.0-0 libpolkit-backend-1-0 libsgutils2-2 devicekit-disks diffstat esound-common fontconfig libgamin0 gamin libidl0 liborbit2 gconf2-common libgconf2-4 gconf2 hicolor-icon-theme libgtk2.0-common libatk1.0-0 libcups2 libjasper1 libpango1.0-common libdatrie1 libthai-data libthai0 libpango1.0-0 libgtk2.0-0 libgtk2.0-bin libgsf-1-common libgsf-1-114 librsvg2-2 librsvg2-common gnome-icon-theme gnome-mime-data libcdparanoia0 libgstreamer0.10-0 libogg0 liboil0.3 libtheora0 libvisual-0.4-0 libvorbis0a libvorbisenc2 libxv1 libgstreamer-plugins-base0.10-0 gstreamer0.10-plugins-base libaa1 libraw1394-8 libavc1394-0 libcaca0 libdv4 libflac8 libhal1 libraw1394-11 libiec61883-0 libspeex1 libshout3 libsoup2.4-1 libtag1-vanilla libtag1c2a libv4l-0 libwavpack1 gstreamer0.10-plugins-good libgnome-keyring0 libgdu0 libavahi-common-data libavahi-common3 libavahi-client3 libavahi-glib1 libgvfscommon0 libpolkit-agent-1-0 policykit-1 policykit-1-gnome gvfs intltool libart-2.0-2 libglib2.0-cil libart2.0-cil libpython2.6 libasound2 libatk1.0-dev libaudiofile0 libaudiofile-dev libavahi-common-dev libdbus-1-dev libavahi-client-dev libavahi-glib-dev libbonobo2-common libbonobo2-0 libidl-dev liborbit2-dev libpopt-dev libbonobo2-dev libglade2-0 libesd-alsa0 libhal-storage1 libgnomevfs2-common libgnomevfs2-0 libgnome2-common libgnome2-0 libgail18 libgail-common libgnomecanvas2-common libgnomecanvas2-0 libbonoboui2-common libbonoboui2-0 libpng12-dev libdirectfb-extra libjpeg62-dev libsysfs-dev libdirectfb-dev libpixman-1-dev libxcb-render0-dev libxcb-render-util0-dev libcairo2-dev libdbus-glib-1-dev libesd0-dev libogg-dev libflac-dev libgconf2-dev libgconf2.0-cil libgpg-error-dev libgcrypt11-dev libgdbm-dev libmono-cairo2.0-cil libgtk2.0-cil libglade2.0-cil libgnome-vfs2.0-cil libtasn1-3-dev libgnutls-dev libxml2-dev libsepol1-dev libselinux1-dev libgnomevfs2-dev libgnome2-dev libgnomeui-common libgnomeui-0 libgnome2.24-cil libgstreamer0.10-dev libpango1.0-dev libxml2-utils libgtk2.0-dev libid3tag0 libid3tag0-dev libmono-sharpzip0.84-cil libmusicbrainz4c2a libmusicbrainz4-dev libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil libnotify1 libnotify-dev libvorbisfile3 libvorbis-dev monodoc-base quilt Authentication warning overridden. Get:1 http://ftpmaster.internal karmic/main libgpm2 1.20.4-3.2 [33.6kB] Get:2 http://ftpmaster.internal karmic/main check 0.9.6-2 [104kB] Get:3 http://ftpmaster.internal karmic/main cli-common 0.6.2 [176kB] Get:4 http://ftpmaster.internal karmic/main libmono0 2.4+dfsg-5ubuntu1 [963kB] Get:5 http://ftpmaster.internal karmic/main libmono-system2.0-cil 2.4+dfsg-5ubuntu1 [1519kB] Get:6 http://ftpmaster.internal karmic/main libmono-security2.0-cil 2.4+dfsg-5ubuntu1 [137kB] Get:7 http://ftpmaster.internal karmic/main mono-2.0-gac 2.4+dfsg-5ubuntu1 [34.1kB] Get:8 http://ftpmaster.internal karmic/main mono-gac 2.4+dfsg-5ubuntu1 [26.6kB] Get:9 http://ftpmaster.internal karmic/main mono-runtime 2.4+dfsg-5ubuntu1 [1167kB] Get:10 http://ftpmaster.internal karmic/main libmono-corlib2.0-cil 2.4+dfsg-5ubuntu1 [901kB] Get:11 http://ftpmaster.internal karmic/main libmono-corlib1.0-cil 2.4+dfsg-5ubuntu1 [744kB] Get:12 http://ftpmaster.internal karmic/main mono-utils 2.4+dfsg-5ubuntu1 [730kB] Get:13 http://ftpmaster.internal karmic/main libmono-cecil-private-cil 2.4+dfsg-5ubuntu1 [170kB] Get:14 http://ftpmaster.internal karmic/main libmono-getoptions2.0-cil 2.4+dfsg-5ubuntu1 [41.3kB] Get:15 http://ftpmaster.internal karmic/main libmono-system1.0-cil 2.4+dfsg-5ubuntu1 [946kB] Get:16 http://ftpmaster.internal karmic/main libmono-relaxng1.0-cil 2.4+dfsg-5ubuntu1 [104kB] Get:17 http://ftpmaster.internal karmic/main libmono-security1.0-cil 2.4+dfsg-5ubuntu1 [137kB] Get:18 http://ftpmaster.internal karmic/main libmono-data-tds2.0-cil 2.4+dfsg-5ubuntu1 [54.9kB] Get:19 http://ftpmaster.internal karmic/main libmono-system-data2.0-cil 2.4+dfsg-5ubuntu1 [339kB] Get:20 http://ftpmaster.internal karmic/main libmono-data-tds1.0-cil 2.4+dfsg-5ubuntu1 [52.0kB] Get:21 http://ftpmaster.internal karmic/main libmono-system-data1.0-cil 2.4+dfsg-5ubuntu1 [243kB] Get:22 http://ftpmaster.internal karmic/main libgdiplus 2.4.2-1 [156kB] Get:23 http://ftpmaster.internal karmic/main libmono-system-web1.0-cil 2.4+dfsg-5ubuntu1 [434kB] Get:24 http://ftpmaster.internal karmic/main libmono-system-runtime1.0-cil 2.4+dfsg-5ubuntu1 [101kB] Get:25 http://ftpmaster.internal karmic/main libmono-peapi2.0-cil 2.4+dfsg-5ubuntu1 [64.3kB] Get:26 http://ftpmaster.internal karmic/main libmono-posix2.0-cil 2.4+dfsg-5ubuntu1 [95.5kB] Get:27 http://ftpmaster.internal karmic/main libmono-sharpzip2.84-cil 2.4+dfsg-5ubuntu1 [77.8kB] Get:28 http://ftpmaster.internal karmic/main libmono-sqlite2.0-cil 2.4+dfsg-5ubuntu1 [87.5kB] Get:29 http://ftpmaster.internal karmic/main libmono2.0-cil 2.4+dfsg-5ubuntu1 [61.0kB] Get:30 http://ftpmaster.internal karmic/main libmono-system-web2.0-cil 2.4+dfsg-5ubuntu1 [1279kB] Get:31 http://ftpmaster.internal karmic/main mono-gmcs 2.4+dfsg-5ubuntu1 [388kB] Get:32 http://ftpmaster.internal karmic/main libmono-dev 2.4+dfsg-5ubuntu1 [1335kB] Get:33 http://ftpmaster.internal karmic/main mono-2.0-devel 2.4+dfsg-5ubuntu1 [212kB] Get:34 http://ftpmaster.internal karmic/main mono-devel 2.4+dfsg-5ubuntu1 [262kB] Get:35 http://ftpmaster.internal karmic/main libxml-perl 0.08-1 [119kB] Get:36 http://ftpmaster.internal karmic/main libxml-regexp-perl 0.03-7 [7510B] Get:37 http://ftpmaster.internal karmic/main libxml-dom-perl 1.44-1 [185kB] Get:38 http://ftpmaster.internal karmic/main cli-common-dev 0.6.2 [40.4kB] Get:39 http://ftpmaster.internal karmic/main hicolor-icon-theme 0.10-2 [9652B] Get:40 http://ftpmaster.internal karmic/main libgtk2.0-bin 2.17.4-0ubuntu2 [138kB] Get:41 http://ftpmaster.internal karmic/main librsvg2-common 2.26.0-1 [17.4kB] Get:42 http://ftpmaster.internal karmic/main gnome-icon-theme 2.26.0-1ubuntu1 [3608kB] Get:43 http://ftpmaster.internal karmic/main libcdparanoia0 3.10.2+debian-5 [54.4kB] Get:44 http://ftpmaster.internal karmic/main liboil0.3 0.3.16-1ubuntu1 [139kB] Get:45 http://ftpmaster.internal karmic/main libtheora0 1.0-2 [288kB] Get:46 http://ftpmaster.internal karmic/main libvisual-0.4-0 0.4.0-2.1+build1 [103kB] Get:47 http://ftpmaster.internal karmic/main libxv1 2:1.0.4-1 [16.1kB] Get:48 http://ftpmaster.internal karmic/main gstreamer0.10-plugins-base 0.10.23.2-1 [573kB] Get:49 http://ftpmaster.internal karmic/main libaa1 1.4p5-38 [57.9kB] Get:50 http://ftpmaster.internal karmic/main libavc1394-0 0.5.3-1build2 [21.6kB] Get:51 http://ftpmaster.internal karmic/main libcaca0 0.99.beta16-1 [307kB] Get:52 http://ftpmaster.internal karmic/main libiec61883-0 1.2.0-0.1 [25.0kB] Get:53 http://ftpmaster.internal karmic/main libspeex1 1.2~rc1-1 [54.5kB] Get:54 http://ftpmaster.internal karmic/main libshout3 2.2.2-5 [37.1kB] Get:55 http://ftpmaster.internal karmic/main libtag1-vanilla 1.5-6 [162kB] Get:56 http://ftpmaster.internal karmic/main libtag1c2a 1.5-6 [7224B] Get:57 http://ftpmaster.internal karmic/main libwavpack1 4.50.1-1 [80.2kB] Get:58 http://ftpmaster.internal karmic/main gstreamer0.10-plugins-good 0.10.15-2ubuntu1 [1235kB] Get:59 http://ftpmaster.internal karmic/main libglib2.0-cil 2.12.9-1 [182kB] Get:60 http://ftpmaster.internal karmic/main libart2.0-cil 2.24.1-4ubuntu1 [144kB] Get:61 http://ftpmaster.internal karmic/main libgconf2.0-cil 2.24.1-4ubuntu1 [135kB] Get:62 http://ftpmaster.internal karmic/main libgdbm-dev 1.8.3-4 [49.7kB] Get:63 http://ftpmaster.internal karmic/main libmono-cairo2.0-cil 2.4+dfsg-5ubuntu1 [43.1kB] Get:64 http://ftpmaster.internal karmic/main libgtk2.0-cil 2.12.9-1 [921kB] Get:65 http://ftpmaster.internal karmic/main libglade2.0-cil 2.12.9-1 [157kB] Get:66 http://ftpmaster.internal karmic/main libgnome-vfs2.0-cil 2.24.1-4ubuntu1 [187kB] Get:67 http://ftpmaster.internal karmic/main libgnome2.24-cil 2.24.1-4ubuntu1 [242kB] Get:68 http://ftpmaster.internal karmic/main libgstreamer0.10-dev 0.10.23.2-1 [679kB] Get:69 http://ftpmaster.internal karmic/main libid3tag0 0.15.1b-10build1 [32.5kB] Get:70 http://ftpmaster.internal karmic/main libid3tag0-dev 0.15.1b-10build1 [33.5kB] Get:71 http://ftpmaster.internal karmic/main libmono-sharpzip0.84-cil 2.4+dfsg-5ubuntu1 [77.7kB] Get:72 http://ftpmaster.internal karmic/main libmusicbrainz4c2a 2.1.5-2ubuntu1 [88.6kB] Get:73 http://ftpmaster.internal karmic/main libmusicbrainz4-dev 2.1.5-2ubuntu1 [116kB] Get:74 http://ftpmaster.internal karmic/main libndesk-dbus1.0-cil 0.6.0-2 [35.8kB] Get:75 http://ftpmaster.internal karmic/main libndesk-dbus-glib1.0-cil 0.4.1-2 [7446B] Get:76 http://ftpmaster.internal karmic/main libnotify1 0.4.5-1 [19.8kB] Get:77 http://ftpmaster.internal karmic/main libnotify-dev 0.4.5-1 [15.8kB] Get:78 http://ftpmaster.internal karmic/main monodoc-base 2.4+dfsg-5ubuntu1 [304kB] dpkg-preconfigure: unable to re-open stdin: Fetched 23.9MB in 1s (17.2MB/s) Selecting previously deselected package x11-common. (Reading database ... 9351 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.4+3ubuntu5_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.5-1_lpia.deb) ... Setting up x11-common (1:7.4+3ubuntu5) ... Selecting previously deselected package x11proto-core-dev. (Reading database ... 9433 files and directories currently installed.) Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.15-1_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.5-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-2_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-2_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-2_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.3-2_lpia.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.2.1-1ubuntu1_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.2.1-1ubuntu1_lpia.deb) ... dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. 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-2_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-2ubuntu1_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-3_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.3-2_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.2.1-1ubuntu1_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-0ubuntu3_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-2build1_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-2_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-2build1_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-0ubuntu3_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-1build1_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-1build1_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-4build1_lpia.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0018_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.10-4_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.10-4_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_5.03-1ubuntu1_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_5.03-1ubuntu1_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.29-2_all.deb) ... Selecting previously deselected package ttf-dejavu-extra. Unpacking ttf-dejavu-extra (from .../ttf-dejavu-extra_2.29-2_all.deb) ... Selecting previously deselected package ttf-dejavu. Unpacking ttf-dejavu (from .../ttf-dejavu_2.29-2_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.6.0-1ubuntu12_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-1ubuntu12_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-13ubuntu1_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-4build1_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.21.3-0ubuntu1_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-1build1_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-1ubuntu12_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.1-2ubuntu1_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.1-2ubuntu1_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-2_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-2_lpia.deb) ... Selecting previously deselected package adduser. Unpacking adduser (from .../adduser_3.110ubuntu5_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdevmapper1.02.1. Unpacking libdevmapper1.02.1 (from .../libdevmapper1.02.1_2%3a1.02.27-4ubuntu6_lpia.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.6-1ubuntu1_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.4-2ubuntu2_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_2.2-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.6.6-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgpm2. Unpacking libgpm2 (from .../libgpm2_1.20.4-3.2_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-10_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libkrb5support0. Unpacking libkrb5support0 (from .../libkrb5support0_1.7dfsg~beta3-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libk5crypto3. Unpacking libk5crypto3 (from .../libk5crypto3_1.7dfsg~beta3-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libkrb5-3. Unpacking libkrb5-3 (from .../libkrb5-3_1.7dfsg~beta3-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgssapi-krb5-2. Unpacking libgssapi-krb5-2 (from .../libgssapi-krb5-2_1.7dfsg~beta3-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-16ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsasl2-modules. Unpacking libsasl2-modules (from .../libsasl2-modules_2.1.23.dfsg1-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsasl2-2. Unpacking libsasl2-2 (from .../libsasl2-2_2.1.23.dfsg1-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libldap-2.4-2. Unpacking libldap-2.4-2 (from .../libldap-2.4-2_2.4.15-1.1ubuntu1_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+20090607-1ubuntu1_lpia.deb) ... Selecting previously deselected package readline-common. Unpacking readline-common (from .../readline-common_6.0-0ubuntu1_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.14.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libudev0. Unpacking libudev0 (from .../libudev0_145-1_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.7.3.dfsg-1ubuntu1_lpia.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.46-1_all.deb) ... Selecting previously deselected package netbase. Unpacking netbase (from .../netbase_4.35ubuntu1_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.2-0ubuntu2_lpia.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.6.2-0ubuntu1_all.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-2_lpia.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.10ubuntu4_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-22build1_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.61-1_lpia.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_3.23-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libparted1.8-12. Unpacking libparted1.8-12 (from .../libparted1.8-12_1.8.8.git.2009.06.03-1ubuntu2_lpia.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.827-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 man-db. Unpacking man-db (from .../man-db_2.5.5-2_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.7-1_lpia.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.13-1_lpia.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.63-3ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20090427.1_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.10.2-1ubuntu2_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.6-2_lpia.deb) ... Selecting previously deselected package cli-common. Unpacking cli-common (from .../cli-common_0.6.2_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-14_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.16_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_7.2.14ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmono0. Unpacking libmono0 (from .../libmono0_2.4+dfsg-5ubuntu1_lpia.deb) ... Selecting previously deselected package libmono-system2.0-cil. Unpacking libmono-system2.0-cil (from .../libmono-system2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-security2.0-cil. Unpacking libmono-security2.0-cil (from .../libmono-security2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package mono-2.0-gac. Unpacking mono-2.0-gac (from .../mono-2.0-gac_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package mono-gac. Unpacking mono-gac (from .../mono-gac_2.4+dfsg-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package mono-runtime. Unpacking mono-runtime (from .../mono-runtime_2.4+dfsg-5ubuntu1_lpia.deb) ... Selecting previously deselected package libmono-corlib2.0-cil. Unpacking libmono-corlib2.0-cil (from .../libmono-corlib2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-corlib1.0-cil. Unpacking libmono-corlib1.0-cil (from .../libmono-corlib1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package mono-utils. Unpacking mono-utils (from .../mono-utils_2.4+dfsg-5ubuntu1_lpia.deb) ... Selecting previously deselected package libmono-cecil-private-cil. Unpacking libmono-cecil-private-cil (from .../libmono-cecil-private-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-getoptions2.0-cil. Unpacking libmono-getoptions2.0-cil (from .../libmono-getoptions2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-system1.0-cil. Unpacking libmono-system1.0-cil (from .../libmono-system1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-relaxng1.0-cil. Unpacking libmono-relaxng1.0-cil (from .../libmono-relaxng1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-security1.0-cil. Unpacking libmono-security1.0-cil (from .../libmono-security1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-data-tds2.0-cil. Unpacking libmono-data-tds2.0-cil (from .../libmono-data-tds2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-system-data2.0-cil. Unpacking libmono-system-data2.0-cil (from .../libmono-system-data2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-data-tds1.0-cil. Unpacking libmono-data-tds1.0-cil (from .../libmono-data-tds1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-system-data1.0-cil. Unpacking libmono-system-data1.0-cil (from .../libmono-system-data1.0-cil_2.4+dfsg-5ubuntu1_all.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) ... Selecting previously deselected package tsconf. Unpacking tsconf (from .../archives/tsconf_1.0-7_all.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-7_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdirectfb-1.2-0. Unpacking libdirectfb-1.2-0 (from .../libdirectfb-1.2-0_1.2.7-2ubuntu1_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.14.0-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.37-1_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.3-2_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.3.5-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.8-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libexif12. Unpacking libexif12 (from .../libexif12_0.6.17-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgif4. Unpacking libgif4 (from .../libgif4_4.1.6-6_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-14build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.8.2-13_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgdiplus. Unpacking libgdiplus (from .../libgdiplus_2.4.2-1_lpia.deb) ... Selecting previously deselected package libmono-system-web1.0-cil. Unpacking libmono-system-web1.0-cil (from .../libmono-system-web1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-system-runtime1.0-cil. Unpacking libmono-system-runtime1.0-cil (from .../libmono-system-runtime1.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-peapi2.0-cil. Unpacking libmono-peapi2.0-cil (from .../libmono-peapi2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-posix2.0-cil. Unpacking libmono-posix2.0-cil (from .../libmono-posix2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-sharpzip2.84-cil. Unpacking libmono-sharpzip2.84-cil (from .../libmono-sharpzip2.84-cil_2.4+dfsg-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsqlite0. Unpacking libsqlite0 (from .../libsqlite0_2.8.17-4build2_lpia.deb) ... Selecting previously deselected package libmono-sqlite2.0-cil. Unpacking libmono-sqlite2.0-cil (from .../libmono-sqlite2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono2.0-cil. Unpacking libmono2.0-cil (from .../libmono2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libmono-system-web2.0-cil. Unpacking libmono-system-web2.0-cil (from .../libmono-system-web2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package mono-gmcs. Unpacking mono-gmcs (from .../mono-gmcs_2.4+dfsg-5ubuntu1_all.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.21.3-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmono-dev. Unpacking libmono-dev (from .../libmono-dev_2.4+dfsg-5ubuntu1_lpia.deb) ... Selecting previously deselected package mono-2.0-devel. Unpacking mono-2.0-devel (from .../mono-2.0-devel_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package mono-devel. Unpacking mono-devel (from .../mono-devel_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package libxml-perl. Unpacking libxml-perl (from .../libxml-perl_0.08-1_all.deb) ... Selecting previously deselected package libxml-regexp-perl. Unpacking libxml-regexp-perl (from .../libxml-regexp-perl_0.03-7_all.deb) ... Selecting previously deselected package libxml-dom-perl. Unpacking libxml-dom-perl (from .../libxml-dom-perl_1.44-1_all.deb) ... Selecting previously deselected package cli-common-dev. Unpacking cli-common-dev (from .../cli-common-dev_0.6.2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libck-connector0. Unpacking libck-connector0 (from .../libck-connector0_0.3.0-2ubuntu6_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-4_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libeggdbus-1-0. Unpacking libeggdbus-1-0 (from .../libeggdbus-1-0_0.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpolkit-gobject-1-0. Unpacking libpolkit-gobject-1-0 (from .../libpolkit-gobject-1-0_0.92-0ubuntu1_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.16-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-2ubuntu6_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.2.16-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libatasmart0. Unpacking libatasmart0 (from .../libatasmart0_0.13-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgudev-1.0-0. Unpacking libgudev-1.0-0 (from .../libgudev-1.0-0_1%3a145-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpolkit-backend-1-0. Unpacking libpolkit-backend-1-0 (from .../libpolkit-backend-1-0_0.92-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libsgutils2-2. Unpacking libsgutils2-2 (from .../libsgutils2-2_1.27-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package devicekit-disks. Unpacking devicekit-disks (from .../devicekit-disks_005-0ubuntu5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package diffstat. Unpacking diffstat (from .../diffstat_1.47-1_lpia.deb) ... Selecting previously deselected package esound-common. Unpacking esound-common (from .../esound-common_0.2.41-5_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-1ubuntu12_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.10-1ubuntu1_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.10-1ubuntu1_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.13-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) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.26.2-1ubuntu1_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.2-1ubuntu1_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.2-1ubuntu1_lpia.deb) ... Selecting previously deselected package hicolor-icon-theme. Unpacking hicolor-icon-theme (from .../hicolor-icon-theme_0.10-2_all.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.17.4-0ubuntu2_all.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-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.3.11-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-6_lpia.deb) ... Selecting previously deselected package libpango1.0-common. Unpacking libpango1.0-common (from .../libpango1.0-common_1.24.4-1ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.2-1_lpia.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.12-1_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.12-1_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.24.4-1ubuntu1_lpia.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.17.4-0ubuntu2_lpia.deb) ... Selecting previously deselected package libgtk2.0-bin. Unpacking libgtk2.0-bin (from .../libgtk2.0-bin_2.17.4-0ubuntu2_all.deb) ... Selecting previously deselected package libgsf-1-common. Unpacking libgsf-1-common (from .../libgsf-1-common_1.14.15-1ubuntu1_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.15-1ubuntu1_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-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package librsvg2-common. Unpacking librsvg2-common (from .../librsvg2-common_2.26.0-1_lpia.deb) ... Selecting previously deselected package gnome-icon-theme. Unpacking gnome-icon-theme (from .../gnome-icon-theme_2.26.0-1ubuntu1_all.deb) ... Selecting previously deselected package gnome-mime-data. Unpacking gnome-mime-data (from .../gnome-mime-data_2.18.0-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcdparanoia0. Unpacking libcdparanoia0 (from .../libcdparanoia0_3.10.2+debian-5_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.23.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libogg0. Unpacking libogg0 (from .../libogg0_1.1.3-5build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package liboil0.3. Unpacking liboil0.3 (from .../liboil0.3_0.3.16-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtheora0. Unpacking libtheora0 (from .../libtheora0_1.0-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libvisual-0.4-0. Unpacking libvisual-0.4-0 (from .../libvisual-0.4-0_0.4.0-2.1+build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libvorbis0a. Unpacking libvorbis0a (from .../libvorbis0a_1.2.0.dfsg-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libvorbisenc2. Unpacking libvorbisenc2 (from .../libvorbisenc2_1.2.0.dfsg-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libxv1. Unpacking libxv1 (from .../libxv1_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 libgstreamer-plugins-base0.10-0. Unpacking libgstreamer-plugins-base0.10-0 (from .../libgstreamer-plugins-base0.10-0_0.10.23.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gstreamer0.10-plugins-base. Unpacking gstreamer0.10-plugins-base (from .../gstreamer0.10-plugins-base_0.10.23.2-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libaa1. Unpacking libaa1 (from .../libaa1_1.4p5-38_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libraw1394-8. Unpacking libraw1394-8 (from .../libraw1394-8_1.3.0-4ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libavc1394-0. Unpacking libavc1394-0 (from .../libavc1394-0_0.5.3-1build2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libcaca0. Unpacking libcaca0 (from .../libcaca0_0.99.beta16-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libdv4. Unpacking libdv4 (from .../libdv4_1.0.0-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libflac8. Unpacking libflac8 (from .../libflac8_1.2.1-1.2_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.13-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libraw1394-11. Unpacking libraw1394-11 (from .../libraw1394-11_2.0.2-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libiec61883-0. Unpacking libiec61883-0 (from .../libiec61883-0_1.2.0-0.1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libspeex1. Unpacking libspeex1 (from .../libspeex1_1.2~rc1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libshout3. Unpacking libshout3 (from .../libshout3_2.2.2-5_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.27.4-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtag1-vanilla. Unpacking libtag1-vanilla (from .../libtag1-vanilla_1.5-6_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libtag1c2a. Unpacking libtag1c2a (from .../libtag1c2a_1.5-6_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libv4l-0. Unpacking libv4l-0 (from .../libv4l-0_0.5.9-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libwavpack1. Unpacking libwavpack1 (from .../libwavpack1_4.50.1-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gstreamer0.10-plugins-good. Unpacking gstreamer0.10-plugins-good (from .../gstreamer0.10-plugins-good_0.10.15-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnome-keyring0. Unpacking libgnome-keyring0 (from .../libgnome-keyring0_2.27.4-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgdu0. Unpacking libgdu0 (from .../libgdu0_0.4-0ubuntu1_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.25-1ubuntu1_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.25-1ubuntu1_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.25-1ubuntu1_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.25-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgvfscommon0. Unpacking libgvfscommon0 (from .../libgvfscommon0_1.3.2-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpolkit-agent-1-0. Unpacking libpolkit-agent-1-0 (from .../libpolkit-agent-1-0_0.92-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package policykit-1. Unpacking policykit-1 (from .../policykit-1_0.92-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package policykit-1-gnome. Unpacking policykit-1-gnome (from .../policykit-1-gnome_0.92-0ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package gvfs. Unpacking gvfs (from .../gvfs_1.3.2-0ubuntu2_lpia.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.40.6-2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libart-2.0-2. Unpacking libart-2.0-2 (from .../libart-2.0-2_2.3.20-2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libglib2.0-cil. Unpacking libglib2.0-cil (from .../libglib2.0-cil_2.12.9-1_lpia.deb) ... Selecting previously deselected package libart2.0-cil. Unpacking libart2.0-cil (from .../libart2.0-cil_2.24.1-4ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libpython2.6. Unpacking libpython2.6 (from .../libpython2.6_2.6.2-0ubuntu2_lpia.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.20-3ubuntu2_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-1_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-7ubuntu2_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-7ubuntu2_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.25-1ubuntu1_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.16-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.25-1ubuntu1_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.25-1ubuntu1_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.13-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 libglade2-0. Unpacking libglade2-0 (from .../libglade2-0_1%3a2.6.4-1_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.41-5_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.13-0ubuntu1_lpia.deb) ... Selecting previously deselected package libgnomevfs2-common. Unpacking libgnomevfs2-common (from .../libgnomevfs2-common_1%3a2.24.1-1ubuntu2_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.1-1ubuntu2_lpia.deb) ... Selecting previously deselected package libgnome2-common. Unpacking libgnome2-common (from .../libgnome2-common_2.26.0-1ubuntu1_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-1ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgail18. Unpacking libgail18 (from .../libgail18_2.17.4-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgail-common. Unpacking libgail-common (from .../libgail-common_2.17.4-0ubuntu2_lpia.deb) ... Selecting previously deselected package libgnomecanvas2-common. Unpacking libgnomecanvas2-common (from .../libgnomecanvas2-common_2.26.0-1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgnomecanvas2-0. Unpacking libgnomecanvas2-0 (from .../libgnomecanvas2-0_2.26.0-1_lpia.deb) ... Selecting previously deselected package libbonoboui2-common. Unpacking libbonoboui2-common (from .../libbonoboui2-common_2.24.1-1ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libbonoboui2-0. Unpacking libbonoboui2-0 (from .../libbonoboui2-0_2.24.1-1ubuntu1_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.37-1_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.2.7-2ubuntu1_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-14build1_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.2.7-2ubuntu1_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.14.0-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.3-2_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.3.5-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.8-2ubuntu1_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-4_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.41-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libogg-dev. Unpacking libogg-dev (from .../libogg-dev_1.1.3-5build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libflac-dev. Unpacking libflac-dev (from .../libflac-dev_1.2.1-1.2_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.2-1ubuntu1_lpia.deb) ... Selecting previously deselected package libgconf2.0-cil. Unpacking libgconf2.0-cil (from .../libgconf2.0-cil_2.24.1-4ubuntu1_all.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.6-1ubuntu1_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.4-2ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgdbm-dev. Unpacking libgdbm-dev (from .../libgdbm-dev_1.8.3-4_lpia.deb) ... Selecting previously deselected package libmono-cairo2.0-cil. Unpacking libmono-cairo2.0-cil (from .../libmono-cairo2.0-cil_2.4+dfsg-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libgtk2.0-cil. Unpacking libgtk2.0-cil (from .../libgtk2.0-cil_2.12.9-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libglade2.0-cil. (Reading database ... 25407 files and directories currently installed.) Unpacking libglade2.0-cil (from .../libglade2.0-cil_2.12.9-1_lpia.deb) ... Selecting previously deselected package libgnome-vfs2.0-cil. Unpacking libgnome-vfs2.0-cil (from .../libgnome-vfs2.0-cil_2.24.1-4ubuntu1_all.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_2.2-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.6.6-1_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.7.3.dfsg-1ubuntu1_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.36-1_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.82-1ubuntu2_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.1-1ubuntu2_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-1ubuntu1_lpia.deb) ... Selecting previously deselected package libgnomeui-common. Unpacking libgnomeui-common (from .../libgnomeui-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 libgnomeui-0. Unpacking libgnomeui-0 (from .../libgnomeui-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 libgnome2.24-cil. Unpacking libgnome2.24-cil (from .../libgnome2.24-cil_2.24.1-4ubuntu1_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.23.2-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.24.4-1ubuntu1_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.7.3.dfsg-1ubuntu1_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.17.4-0ubuntu2_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libid3tag0. Unpacking libid3tag0 (from .../libid3tag0_0.15.1b-10build1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libid3tag0-dev. Unpacking libid3tag0-dev (from .../libid3tag0-dev_0.15.1b-10build1_lpia.deb) ... Selecting previously deselected package libmono-sharpzip0.84-cil. Unpacking libmono-sharpzip0.84-cil (from .../libmono-sharpzip0.84-cil_2.4+dfsg-5ubuntu1_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmusicbrainz4c2a. Unpacking libmusicbrainz4c2a (from .../libmusicbrainz4c2a_2.1.5-2ubuntu1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libmusicbrainz4-dev. Unpacking libmusicbrainz4-dev (from .../libmusicbrainz4-dev_2.1.5-2ubuntu1_lpia.deb) ... Selecting previously deselected package libndesk-dbus1.0-cil. Unpacking libndesk-dbus1.0-cil (from .../libndesk-dbus1.0-cil_0.6.0-2_all.deb) ... Selecting previously deselected package libndesk-dbus-glib1.0-cil. Unpacking libndesk-dbus-glib1.0-cil (from .../libndesk-dbus-glib1.0-cil_0.4.1-2_all.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnotify1. Unpacking libnotify1 (from .../libnotify1_0.4.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.4.5-1_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libvorbisfile3. Unpacking libvorbisfile3 (from .../libvorbisfile3_1.2.0.dfsg-5_lpia.deb) ... dpkg - warning, overriding problem because --force enabled: package architecture (lpia) does not match system (i386) Selecting previously deselected package libvorbis-dev. Unpacking libvorbis-dev (from .../libvorbis-dev_1.2.0.dfsg-5_lpia.deb) ... Selecting previously deselected package monodoc-base. Unpacking monodoc-base (from .../monodoc-base_2.4+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package quilt. Unpacking quilt (from .../archives/quilt_0.46-7_all.deb) ... Setting up libice6 (2:1.0.5-1) ... Setting up x11proto-core-dev (7.0.15-1) ... Setting up libice-dev (2:1.0.5-1) ... Setting up libsm6 (2:1.1.0-2) ... Setting up libsm-dev (2:1.1.0-2) ... Setting up libxau6 (1:1.0.4-2) ... Setting up libxdmcp6 (1:1.0.2-3) ... Setting up libxcb1 (1.3-2) ... Setting up libx11-data (2:1.2.1-1ubuntu1) ... Setting up libx11-6 (2:1.2.1-1ubuntu1) ... Setting up libxau-dev (1:1.0.4-2) ... Setting up libxdmcp-dev (1:1.0.2-3) ... Setting up x11proto-input-dev (1.5.0-2ubuntu1) ... Setting up x11proto-kb-dev (1.0.3-3ubuntu1) ... Setting up xtrans-dev (1.2.3-3) ... Setting up libpthread-stubs0 (0.1-2) ... Setting up libpthread-stubs0-dev (0.1-2) ... Setting up libxcb1-dev (1.3-2) ... Setting up libx11-dev (2:1.2.1-1ubuntu1) ... Setting up libxext6 (2:1.0.99.1-0ubuntu3) ... Setting up libxfixes3 (1:4.0.3-2build1) ... Setting up libxcomposite1 (1:0.4.0-3) ... Setting up x11proto-xext-dev (7.0.4-2) ... Setting up x11proto-fixes-dev (1:4.0-3) ... Setting up libxfixes-dev (1:4.0.3-2build1) ... Setting up x11proto-composite-dev (1:0.4-2) ... Setting up libxext-dev (2:1.0.99.1-0ubuntu3) ... Setting up libxcomposite-dev (1:0.4.0-3) ... Setting up libxrender1 (1:0.9.4-2) ... Setting up libxcursor1 (1:1.1.9-1build1) ... 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-1build1) ... 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-4build1) ... Setting up ucf (3.0018) ... Setting up libnewt0.52 (0.52.10-4) ... Setting up libpopt0 (1.14-4) ... Setting up whiptail (0.52.10-4) ... Setting up libmagic1 (5.03-1ubuntu1) ... Setting up file (5.03-1ubuntu1) ... Setting up defoma (0.11.10-0.2ubuntu1) ... Setting up ttf-dejavu-core (2.29-2) ... Setting up ttf-dejavu-extra (2.29-2) ... Setting up ttf-dejavu (2.29-2) ... Setting up fontconfig-config (2.6.0-1ubuntu12) ... Setting up libfontconfig1 (2.6.0-1ubuntu12) ... Setting up libxft2 (2.1.13-3ubuntu1) ... Setting up libexpat1-dev (2.0.1-4) ... Setting up zlib1g-dev (1:1.2.3.3.dfsg-13ubuntu1) ... Setting up libfreetype6-dev (2.3.9-4build1) ... Setting up libglib2.0-0 (2.21.3-0ubuntu1) ... Setting up pkg-config (0.22-1build1) ... Setting up libfontconfig1-dev (2.6.0-1ubuntu12) ... Setting up libxft-dev (2.1.13-3ubuntu1) ... Setting up libxi6 (2:1.2.1-2ubuntu1) ... Setting up libxi-dev (2:1.2.1-2ubuntu1) ... 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-2) ... Setting up x11proto-randr-dev (1.3.0-1) ... Setting up libxrandr-dev (2:1.3.0-2) ... Setting up adduser (3.110ubuntu5) ... Setting up libdevmapper1.02.1 (2:1.02.27-4ubuntu6) ... Setting up libgpg-error0 (1.6-1ubuntu1) ... Setting up libgcrypt11 (1.4.4-2ubuntu2) ... Setting up libtasn1-3 (2.2-1) ... Setting up libgnutls26 (2.6.6-1) ... Setting up libgpm2 (1.20.4-3.2) ... Setting up libkeyutils1 (1.2-10) ... Setting up libkrb5support0 (1.7dfsg~beta3-1) ... Setting up libk5crypto3 (1.7dfsg~beta3-1) ... Setting up libkrb5-3 (1.7dfsg~beta3-1) ... Setting up libgssapi-krb5-2 (1.7dfsg~beta3-1) ... Setting up libssl0.9.8 (0.9.8g-16ubuntu2) ... Setting up libncursesw5 (5.7+20090607-1ubuntu1) ... Setting up readline-common (6.0-0ubuntu1) ... Setting up libreadline5 (5.2-4) ... Setting up libsqlite3-0 (3.6.14.2-1) ... Setting up libudev0 (145-1) ... Setting up libxml2 (2.7.3.dfsg-1ubuntu1) ... Setting up mime-support (3.46-1) ... update-alternatives: warning: /etc/alternatives/view is dangling, it will be updated with best choice. update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up netbase (4.35ubuntu1) ... Setting up python2.6 (2.6.2-0ubuntu2) ... Setting up python (2.6.2-0ubuntu1) ... Setting up shared-mime-info (0.60-2) ... Setting up bsdmainutils (6.1.10ubuntu4) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. Setting up gettext-base (0.17-6ubuntu2) ... Setting up groff-base (1.18.1.1-22build1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up liburi-perl (1.37+dfsg-1ubuntu1) ... Setting up libhtml-parser-perl (3.61-1) ... Setting up libhtml-tree-perl (3.23-1) ... Setting up libparted1.8-12 (1.8.8.git.2009.06.03-1ubuntu2) ... Setting up libwww-perl (5.827-1) ... Setting up libxml-parser-perl (2.36-1.1build2) ... Setting up man-db (2.5.5-2) ... Building database of manual pages ... ... skipping, since this is a buildd Setting up psmisc (22.7-1) ... Setting up m4 (1.4.13-1) ... Setting up autoconf (2.63-3ubuntu1) ... Setting up autotools-dev (20090427.1) ... Setting up automake (1:1.10.2-1ubuntu2) ... update-alternatives: using /usr/bin/automake-1.10 to provide /usr/bin/automake (automake) in auto mode. Setting up check (0.9.6-2) ... Setting up cli-common (0.6.2) ... Setting up html2text (1.3.2a-14) ... 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.16) ... Setting up debhelper (7.2.14ubuntu1) ... Setting up libmono0 (2.4+dfsg-5ubuntu1) ... Setting up libsysfs2 (2.1.0-5) ... Setting up tsconf (1.0-7) ... Setting up libts-0.0-0 (1.0-7) ... Setting up libdirectfb-1.2-0 (1.2.7-2ubuntu1) ... Setting up libpixman-1-0 (0.14.0-1) ... Setting up libpng12-0 (1.2.37-1) ... Setting up libxcb-render0 (1.3-2) ... Setting up libxcb-render-util0 (0.3.5-1) ... Setting up libcairo2 (1.8.8-2ubuntu1) ... Setting up libexif12 (0.6.17-1) ... Setting up libgif4 (4.1.6-6) ... Setting up libjpeg62 (6b-14build1) ... Setting up libtiff4 (3.8.2-13) ... Setting up libgdiplus (2.4.2-1) ... Setting up libsqlite0 (2.8.17-4build2) ... Setting up libglib2.0-dev (2.21.3-0ubuntu1) ... Setting up libmono-dev (2.4+dfsg-5ubuntu1) ... Setting up libxml-perl (0.08-1) ... Setting up libxml-regexp-perl (0.03-7) ... Setting up libxml-dom-perl (1.44-1) ... Setting up libck-connector0 (0.3.0-2ubuntu6) ... Setting up libdbus-glib-1-2 (0.80-4) ... Setting up libeggdbus-1-0 (0.5-1) ... Setting up libpolkit-gobject-1-0 (0.92-0ubuntu1) ... Setting up dbus (1.2.16-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  [ OK ] Setting up consolekit (0.3.0-2ubuntu6) ... Setting up dbus-x11 (1.2.16-0ubuntu2) ... Setting up libatasmart0 (0.13-1) ... Setting up libgudev-1.0-0 (1:145-1) ... Setting up libpolkit-backend-1-0 (0.92-0ubuntu1) ... Setting up libsgutils2-2 (1.27-0.1) ... Setting up devicekit-disks (005-0ubuntu5) ... Setting up diffstat (1.47-1) ... Setting up esound-common (0.2.41-5) ... Setting up fontconfig (2.6.0-1ubuntu12) ... Updating font configuration of fontconfig... Cleaning up category cid.. Cleaning up category truetype.. Cleaning up category type1.. Updating category type1.. Updating category truetype.. Updating category cid.. Updating fontconfig cache for /usr/share/fonts/truetype/ttf-dejavu Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libidl0 (0.8.13-0.1) ... Setting up liborbit2 (1:2.14.17-0.1) ... Setting up gconf2-common (2.26.2-1ubuntu1) ... Creating config file /etc/gconf/2/path with new version Setting up hicolor-icon-theme (0.10-2) ... Setting up libgtk2.0-common (2.17.4-0ubuntu2) ... Setting up libatk1.0-0 (1.26.0-1) ... Setting up libcups2 (1.3.11-1) ... Setting up libjasper1 (1.900.1-6) ... Setting up libpango1.0-common (1.24.4-1ubuntu1) ... Cleaning up font configuration of pango... Updating font configuration of pango... Cleaning up category xfont.. Updating category xfont.. *** You don't have any defomized font packages. *** So we are trying to force to generate pangox.aliases... Setting up libdatrie1 (0.2.2-1) ... Setting up libthai-data (0.1.12-1) ... Setting up libthai0 (0.1.12-1) ... Setting up libpango1.0-0 (1.24.4-1ubuntu1) ... Setting up libgtk2.0-0 (2.17.4-0ubuntu2) ... Setting up libgtk2.0-bin (2.17.4-0ubuntu2) ... Setting up libgsf-1-common (1.14.15-1ubuntu1) ... Setting up libgsf-1-114 (1.14.15-1ubuntu1) ... Setting up librsvg2-2 (2.26.0-1) ... Setting up librsvg2-common (2.26.0-1) ... Setting up gnome-icon-theme (2.26.0-1ubuntu1) ... Setting up gnome-mime-data (2.18.0-1) ... Setting up libcdparanoia0 (3.10.2+debian-5) ... Setting up libgstreamer0.10-0 (0.10.23.2-1) ... Setting up libogg0 (1.1.3-5build1) ... Setting up liboil0.3 (0.3.16-1ubuntu1) ... Setting up libtheora0 (1.0-2) ... Setting up libvisual-0.4-0 (0.4.0-2.1+build1) ... Setting up libvorbis0a (1.2.0.dfsg-5) ... Setting up libvorbisenc2 (1.2.0.dfsg-5) ... Setting up libxv1 (2:1.0.4-1) ... Setting up libgstreamer-plugins-base0.10-0 (0.10.23.2-1) ... Setting up gstreamer0.10-plugins-base (0.10.23.2-1) ... Setting up libaa1 (1.4p5-38) ... Setting up libraw1394-8 (1.3.0-4ubuntu1) ... Creating device node /dev/raw1394... done. Setting up libavc1394-0 (0.5.3-1build2) ... Setting up libcaca0 (0.99.beta16-1) ... Setting up libdv4 (1.0.0-2ubuntu1) ... Setting up libflac8 (1.2.1-1.2) ... Setting up libhal1 (0.5.13-0ubuntu1) ... Setting up libraw1394-11 (2.0.2-2ubuntu1) ... Creating device node /dev/raw1394... done. Setting up libiec61883-0 (1.2.0-0.1) ... Setting up libspeex1 (1.2~rc1-1) ... Setting up libshout3 (2.2.2-5) ... Setting up libsoup2.4-1 (2.27.4-0ubuntu1) ... Setting up libtag1-vanilla (1.5-6) ... Setting up libtag1c2a (1.5-6) ... Setting up libv4l-0 (0.5.9-1ubuntu1) ... Setting up libwavpack1 (4.50.1-1) ... Setting up libgnome-keyring0 (2.27.4-0ubuntu1) ... Setting up libgdu0 (0.4-0ubuntu1) ... Setting up libavahi-common-data (0.6.25-1ubuntu1) ... Setting up libavahi-common3 (0.6.25-1ubuntu1) ... Setting up libavahi-client3 (0.6.25-1ubuntu1) ... Setting up libavahi-glib1 (0.6.25-1ubuntu1) ... Setting up libgvfscommon0 (1.3.2-0ubuntu2) ... Setting up libpolkit-agent-1-0 (0.92-0ubuntu1) ... Setting up policykit-1 (0.92-0ubuntu1) ... Setting up policykit-1-gnome (0.92-0ubuntu1) ... Setting up intltool (0.40.6-2) ... Setting up libart-2.0-2 (2.3.20-2) ... Setting up libpython2.6 (2.6.2-0ubuntu2) ... Setting up libasound2 (1.0.20-3ubuntu2) ... Setting up libatk1.0-dev (1.26.0-1) ... Setting up libaudiofile0 (0.2.6-7ubuntu2) ... Setting up libaudiofile-dev (0.2.6-7ubuntu2) ... Setting up libavahi-common-dev (0.6.25-1ubuntu1) ... Setting up libdbus-1-dev (1.2.16-0ubuntu2) ... Setting up libavahi-client-dev (0.6.25-1ubuntu1) ... Setting up libavahi-glib-dev (0.6.25-1ubuntu1) ... Setting up libbonobo2-common (2.24.1-1) ... Setting up libbonobo2-0 (2.24.1-1) ... Setting up libidl-dev (0.8.13-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 libglade2-0 (1:2.6.4-1) ... Setting up libesd-alsa0 (0.2.41-5) ... Setting up libhal-storage1 (0.5.13-0ubuntu1) ... Setting up libgail18 (2.17.4-0ubuntu2) ... Setting up libgail-common (2.17.4-0ubuntu2) ... Setting up libgnomecanvas2-common (2.26.0-1) ... Setting up libgnomecanvas2-0 (2.26.0-1) ... Setting up libbonoboui2-common (2.24.1-1ubuntu1) ... Setting up libpng12-dev (1.2.37-1) ... Setting up libdirectfb-extra (1.2.7-2ubuntu1) ... Setting up libjpeg62-dev (6b-14build1) ... Setting up libsysfs-dev (2.1.0-5) ... Setting up libdirectfb-dev (1.2.7-2ubuntu1) ... Setting up libpixman-1-dev (0.14.0-1) ... Setting up libxcb-render0-dev (1.3-2) ... Setting up libxcb-render-util0-dev (0.3.5-1) ... Setting up libcairo2-dev (1.8.8-2ubuntu1) ... Setting up libdbus-glib-1-dev (0.80-4) ... Setting up libesd0-dev (0.2.41-5) ... Setting up libogg-dev (1.1.3-5build1) ... Setting up libflac-dev (1.2.1-1.2) ... Setting up libgpg-error-dev (1.6-1ubuntu1) ... Setting up libgcrypt11-dev (1.4.4-2ubuntu2) ... Setting up libgdbm-dev (1.8.3-4) ... Setting up libtasn1-3-dev (2.2-1) ... Setting up libgnutls-dev (2.6.6-1) ... Setting up libxml2-dev (2.7.3.dfsg-1ubuntu1) ... Setting up libsepol1-dev (2.0.36-1) ... Setting up libselinux1-dev (2.0.82-1ubuntu2) ... Setting up libgnomeui-common (2.24.1-1) ... Setting up libgstreamer0.10-dev (0.10.23.2-1) ... Setting up libpango1.0-dev (1.24.4-1ubuntu1) ... Setting up libxml2-utils (2.7.3.dfsg-1ubuntu1) ... Setting up libgtk2.0-dev (2.17.4-0ubuntu2) ... Setting up libid3tag0 (0.15.1b-10build1) ... Setting up libid3tag0-dev (0.15.1b-10build1) ... Setting up libmusicbrainz4c2a (2.1.5-2ubuntu1) ... Setting up libmusicbrainz4-dev (2.1.5-2ubuntu1) ... Setting up libnotify1 (0.4.5-1) ... Setting up libnotify-dev (0.4.5-1) ... Setting up libvorbisfile3 (1.2.0.dfsg-5) ... Setting up libvorbis-dev (1.2.0.dfsg-5) ... Setting up quilt (0.46-7) ... Setting up libmono-corlib2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up mono-utils (2.4+dfsg-5ubuntu1) ... update-alternatives: using /usr/bin/monodis to provide /usr/bin/cli-ildasm (cil-disassembler) in auto mode. Setting up libmono-peapi2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up gamin (0.1.10-1ubuntu1) ... Setting up libgamin0 (0.1.10-1ubuntu1) ... Setting up libmono-cairo2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libsasl2-modules (2.1.23.dfsg1-1ubuntu1) ... Setting up libmono-security2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up mono-2.0-gac (2.4+dfsg-5ubuntu1) ... Setting up mono-gac (2.4+dfsg-5ubuntu1) ... * Installing 6 assemblies from libart2.0-cil into Mono * Installing 6 assemblies from libgconf2.0-cil into Mono * Installing 6 assemblies from libgnome-vfs2.0-cil into Mono * Installing 2 assemblies from libgnome2.24-cil into Mono * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono * Installing 1 assembly from libndesk-dbus1.0-cil into Mono update-alternatives: using /usr/bin/gacutil to provide /usr/bin/cli-gacutil (global-assembly-cache-tool) in auto mode. Setting up mono-runtime (2.4+dfsg-5ubuntu1) ... update-alternatives: using /usr/bin/mono to provide /usr/bin/cli (cli) in auto mode. Setting up libmono-system2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-corlib1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-cecil-private-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-getoptions2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-system1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-relaxng1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-security1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-data-tds2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-system-data2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-data-tds1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-system-data1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-system-web1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-system-runtime1.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-posix2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-sharpzip2.84-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono-sqlite2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up libmono2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up mono-gmcs (2.4+dfsg-5ubuntu1) ... Setting up libglib2.0-cil (2.12.9-1) ... Setting up libart2.0-cil (2.24.1-4ubuntu1) ... * Installing 6 assemblies from libart2.0-cil into Mono Setting up libgtk2.0-cil (2.12.9-1) ... Setting up libglade2.0-cil (2.12.9-1) ... Setting up libmono-sharpzip0.84-cil (2.4+dfsg-5ubuntu1) ... Setting up libndesk-dbus1.0-cil (0.6.0-2) ... * Installing 1 assembly from libndesk-dbus1.0-cil into Mono Setting up libndesk-dbus-glib1.0-cil (0.4.1-2) ... * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono Setting up monodoc-base (2.4+dfsg-5ubuntu1) ... Setting up libsasl2-2 (2.1.23.dfsg1-1ubuntu1) ... Setting up libldap-2.4-2 (2.4.15-1.1ubuntu1) ... Setting up libmono-system-web2.0-cil (2.4+dfsg-5ubuntu1) ... Setting up mono-2.0-devel (2.4+dfsg-5ubuntu1) ... Setting up mono-devel (2.4+dfsg-5ubuntu1) ... update-alternatives: using /usr/bin/csc to provide /usr/bin/cli-csc (c-sharp-compiler) in auto mode. update-alternatives: warning: skip creation of /usr/share/man/man1/cli-csc.1.gz because associated file /usr/share/man/man1/csc.1.gz (of link group c-sharp-compiler) doesn't exist. update-alternatives: warning: forcing reinstallation of alternative /usr/bin/resgen because link group resource-file-generator is broken. update-alternatives: using /usr/bin/al to provide /usr/bin/cli-al (assembly-linker) in auto mode. update-alternatives: using /usr/bin/sn to provide /usr/bin/cli-sn (strong-name-tool) in auto mode. Setting up cli-common-dev (0.6.2) ... Setting up libgconf2-4 (2.26.2-1ubuntu1) ... Setting up gconf2 (2.26.2-1ubuntu1) ... Setting up gstreamer0.10-plugins-good (0.10.15-2ubuntu1) ... Setting up gvfs (1.3.2-0ubuntu2) ... Setting up libgnomevfs2-common (1:2.24.1-1ubuntu2) ... Setting up libgnomevfs2-0 (1:2.24.1-1ubuntu2) ... Setting up libgnome2-common (2.26.0-1ubuntu1) ... Setting up libgnome2-0 (2.26.0-1ubuntu1) ... Setting up libbonoboui2-0 (2.24.1-1ubuntu1) ... Setting up libgconf2-dev (2.26.2-1ubuntu1) ... Setting up libgconf2.0-cil (2.24.1-4ubuntu1) ... * Installing 6 assemblies from libgconf2.0-cil into Mono Setting up libgnome-vfs2.0-cil (2.24.1-4ubuntu1) ... * Installing 6 assemblies from libgnome-vfs2.0-cil into Mono Setting up libgnomevfs2-dev (1:2.24.1-1ubuntu2) ... Setting up libgnome2-dev (2.26.0-1ubuntu1) ... Setting up libgnomeui-0 (2.24.1-1) ... Setting up libgnome2.24-cil (2.24.1-4ubuntu1) ... * Installing 2 assemblies from libgnome2.24-cil into Mono Processing triggers for libc6 ... ldconfig deferred processing now taking place Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.9-20ubuntu2 make_3.81-6 dpkg-dev_1.15.3.1ubuntu1 g++-4.4_4.4.0-11ubuntu1 gcc-4.4_4.4.0-11ubuntu1 binutils_2.19.51.20090714-0ubuntu1 libstdc++6_4.4.0-11ubuntu1 libstdc++6-4.4-dev_4.4.0-11ubuntu1 ------------------------------------------------------------------------------ sh: gcc: not found dpkg-source: warning: Couldn't determine gcc system type, falling back to default (native compilation) gpg: Signature made Thu Jul 16 21:30:16 2009 BST using RSA key ID 3B244761 gpg: Can't check signature: public key not found dpkg-source: extracting muine in muine-0.8.10 dpkg-source: unpacking muine_0.8.10.orig.tar.gz dpkg-source: applying /home/buildd/build-1125662-2429975/muine_0.8.10-5.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 muine dpkg-buildpackage: source version 0.8.10-5 dpkg-buildpackage: host architecture lpia /usr/bin/fakeroot debian/rules clean QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 No patch removed rm -rf .pc debian/stamp-patched dh clean dh_testdir Unknown option: with dh_testdir: warning: ignored unknown options in DH_OPTIONS debian/rules override_dh_auto_clean make[1]: Entering directory `/build/buildd/muine-0.8.10' [ ! -f Makefile ] || /usr/bin/make distclean rm -f ./libtool src/AmazonSearchService.cs rm -rf /.wapi rm -f debian/muine.substvars.new find . -name \*.mdb -print | xargs rm -f dh_clean Unknown option: with Unknown option: with dh_clean: warning: ignored unknown options in DH_OPTIONS make[1]: Leaving directory `/build/buildd/muine-0.8.10' dh_clean Unknown option: with dh_clean: warning: ignored unknown options in DH_OPTIONS debian/rules build # quilt exits with 2 as return when there was nothing to do. # That's not an error here (but it's useful to break loops in crude scripts) QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $? = 2 Applying patch metadata-crash.diff patching file src/Metadata.cs patching file src/SongDatabase.cs Applying patch correct-glade-signals.diff patching file data/glade/AddWindow.glade patching file src/AddWindow.cs Applying patch gtk_sharp_api patching file src/HandleModel.cs patching file configure.in Now at patch gtk_sharp_api touch debian/stamp-patched dh build dh_testdir Unknown option: with dh_testdir: warning: ignored unknown options in DH_OPTIONS debian/rules override_dh_auto_configure make[1]: Entering directory `/build/buildd/muine-0.8.10' dh_auto_configure -- MCS=/usr/bin/csc --enable-gstreamer=0.10 Unknown option: with Unknown option: with dh_auto_configure: warning: ignored unknown options in DH_OPTIONS checking build system type... i686-pc-linux-gnulp checking host system type... i686-pc-linux-gnulp checking target system type... i686-pc-linux-gnulp 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 intltool >= 0.37.1... 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 perl... /usr/bin/perl checking for XML::Parser... ok 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 library containing strerror... none required 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 for a sed that does not truncate output... /bin/sed checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... pass_all 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 dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 805306365 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... 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 configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking whether gcc understands -Wno-sign-compare... yes checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror checking what language compliance flags to pass to the C compiler... checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.16... yes checking for GLIB - version >= 2.0.0... yes (version 2.21.3) checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for MUINE... yes checking for MONO... yes checking for GTKSHARP... yes checking for DBUS... yes checking sys/inotify.h usability... yes checking sys/inotify.h presence... yes checking for sys/inotify.h... 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 checking gdbm.h usability... yes checking gdbm.h presence... yes checking for gdbm.h... yes checking for Ogg... yes checking for Vorbis... yes checking for FLAC... yes checking for ID3TAG... yes checking id3tag.h usability... yes checking id3tag.h presence... yes checking for id3tag.h... yes checking mp4ff.h usability... no checking mp4ff.h presence... no checking for mp4ff.h... no checking for gmcs... /usr/bin/csc checking for mono... /usr/bin/mono checking for gacutil... /usr/bin/gacutil checking for MONODOC... yes checking for mdassembler... /usr/bin/mdassembler checking for monodocer... /usr/bin/monodocer 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... /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext configure: creating ./config.status config.status: creating Makefile config.status: creating muine.spec config.status: creating data/Makefile config.status: creating data/muine-dbus.pc config.status: creating data/muine-plugin.pc config.status: creating data/org.gnome.Muine.service config.status: creating data/glade/Makefile config.status: creating data/images/Makefile config.status: creating data/ui/Makefile config.status: creating libmuine/Makefile config.status: creating libmuine/id3-vfs/Makefile config.status: creating PluginLib/Makefile config.status: creating DBusLib/Makefile config.status: creating src/Makefile config.status: creating plugins/Makefile config.status: creating doc/Makefile config.status: creating m4/Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands make[1]: Leaving directory `/build/buildd/muine-0.8.10' dh_auto_build Unknown option: with dh_auto_build: warning: ignored unknown options in DH_OPTIONS make[1]: Entering directory `/build/buildd/muine-0.8.10' make all-recursive make[2]: Entering directory `/build/buildd/muine-0.8.10' Making all in data make[3]: Entering directory `/build/buildd/muine-0.8.10/data' Making all in glade make[4]: Entering directory `/build/buildd/muine-0.8.10/data/glade' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/glade' Making all in images make[4]: Entering directory `/build/buildd/muine-0.8.10/data/images' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/images' Making all in ui make[4]: Entering directory `/build/buildd/muine-0.8.10/data/ui' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/ui' make[4]: Entering directory `/build/buildd/muine-0.8.10/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po muine.desktop.in muine.desktop Generating and caching the translation database Merging translations into muine.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po muine.schemas.in muine.schemas Found cached translation database Merging translations into muine.schemas. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data' make[3]: Leaving directory `/build/buildd/muine-0.8.10/data' Making all in libmuine make[3]: Entering directory `/build/buildd/muine-0.8.10/libmuine' Making all in id3-vfs make[4]: Entering directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c -o id3-vfs.lo id3-vfs.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c id3-vfs.c -fPIC -DPIC -o .libs/id3-vfs.o gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c id3-vfs.c -o id3-vfs.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c -o mp3bitrate.lo mp3bitrate.c gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c mp3bitrate.c -fPIC -DPIC -o .libs/mp3bitrate.o gcc -DHAVE_CONFIG_H -I. -I../.. -DG_LOG_DOMAIN=\"id3-vfs\" -I../.. -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -g -O2 -c mp3bitrate.c -o mp3bitrate.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -Wl,-Bsymbolic-functions -o libid3-vfs.la id3-vfs.lo mp3bitrate.lo ar cru .libs/libid3-vfs.a .libs/id3-vfs.o .libs/mp3bitrate.o ranlib .libs/libid3-vfs.a creating libid3-vfs.la (cd .libs && rm -f libid3-vfs.la && ln -s ../libid3-vfs.la libid3-vfs.la) make[4]: Leaving directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' make[4]: Entering directory `/build/buildd/muine-0.8.10/libmuine' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o player-gst.lo player-gst.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c player-gst.c -fPIC -DPIC -o .libs/player-gst.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c player-gst.c -o player-gst.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o metadata.lo metadata.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c metadata.c -fPIC -DPIC -o .libs/metadata.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c metadata.c -o metadata.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o ogg-helper.lo ogg-helper.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c ogg-helper.c -fPIC -DPIC -o .libs/ogg-helper.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c ogg-helper.c -o ogg-helper.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o gsequence.lo gsequence.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c gsequence.c -fPIC -DPIC -o .libs/gsequence.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c gsequence.c -o gsequence.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o pointer-list-model.lo pointer-list-model.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c pointer-list-model.c -fPIC -DPIC -o .libs/pointer-list-model.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c pointer-list-model.c -o pointer-list-model.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o rb-cell-renderer-pixbuf.lo rb-cell-renderer-pixbuf.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c rb-cell-renderer-pixbuf.c -fPIC -DPIC -o .libs/rb-cell-renderer-pixbuf.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c rb-cell-renderer-pixbuf.c -o rb-cell-renderer-pixbuf.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o db.lo db.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c db.c -fPIC -DPIC -o .libs/db.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c db.c -o db.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\""/usr/share/locale"\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c -o mm-keys.lo mm-keys.c gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c mm-keys.c -fPIC -DPIC -o .libs/mm-keys.o gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DG_LOG_DOMAIN=\"libmuine\" -DGNOMELOCALEDIR=\"/usr/share/locale\" -DORBIT2=1 -pthread -D_REENTRANT -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/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -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/gstreamer-0.10 -I/usr/include/libxml2 -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Werror -DG_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGNOME_DISABLE_DEPRECATED -g -O2 -c mm-keys.c -o mm-keys.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -Wl,-Bsymbolic-functions -o libmuine.la -rpath /usr/lib/muine player-gst.lo metadata.lo ogg-helper.lo gsequence.lo pointer-list-model.lo rb-cell-renderer-pixbuf.lo db.lo mm-keys.lo id3-vfs/libid3-vfs.la -pthread -lgnomevfs-2 -lgconf-2 -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 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lxml2 -lglib-2.0 -L/usr/lib -logg -L/usr/lib -lvorbis -lm -lvorbisfile -lgdbm -lid3tag -lz -lFLAC -lm gcc -shared .libs/player-gst.o .libs/metadata.o .libs/ogg-helper.o .libs/gsequence.o .libs/pointer-list-model.o .libs/rb-cell-renderer-pixbuf.o .libs/db.o .libs/mm-keys.o -Wl,--whole-archive id3-vfs/.libs/libid3-vfs.a -Wl,--no-whole-archive /usr/lib/libgnomevfs-2.so /usr/lib/libgconf-2.so /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 /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 -lfontconfig /usr/lib/libgstreamer-0.10.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libgthread-2.0.so -lrt /usr/lib/libxml2.so /usr/lib/libglib-2.0.so -L/usr/lib /usr/lib/libogg.so /usr/lib/libvorbis.so /usr/lib/libvorbisfile.so /usr/lib/libgdbm.so /usr/lib/libid3tag.so -lz /usr/lib/libFLAC.so -lm -Wl,-Bsymbolic-functions -pthread -Wl,-soname -Wl,libmuine.so.0 -o .libs/libmuine.so.0.0.0 (cd .libs && rm -f libmuine.so.0 && ln -s libmuine.so.0.0.0 libmuine.so.0) (cd .libs && rm -f libmuine.so && ln -s libmuine.so.0.0.0 libmuine.so) rm -fr .libs/libmuine.lax mkdir .libs/libmuine.lax rm -fr .libs/libmuine.lax/libid3-vfs.a mkdir .libs/libmuine.lax/libid3-vfs.a (cd .libs/libmuine.lax/libid3-vfs.a && ar x /build/buildd/muine-0.8.10/libmuine/id3-vfs/.libs/libid3-vfs.a) ar cru .libs/libmuine.a player-gst.o metadata.o ogg-helper.o gsequence.o pointer-list-model.o rb-cell-renderer-pixbuf.o db.o mm-keys.o .libs/libmuine.lax/libid3-vfs.a/id3-vfs.o .libs/libmuine.lax/libid3-vfs.a/mp3bitrate.o ranlib .libs/libmuine.a rm -fr .libs/libmuine.lax creating libmuine.la (cd .libs && rm -f libmuine.la && ln -s ../libmuine.la libmuine.la) make[4]: Leaving directory `/build/buildd/muine-0.8.10/libmuine' make[3]: Leaving directory `/build/buildd/muine-0.8.10/libmuine' Making all in PluginLib make[3]: Entering directory `/build/buildd/muine-0.8.10/PluginLib' cp ../muine.snk . /usr/bin/csc -codepage:utf8 -target:library -out:muine-plugin.dll ./Plugin.cs ./IPlayer.cs ./ISong.cs ./AssemblyInfo.cs -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll -r:/usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll -r:/usr/lib/cli/art-sharp-2.0/art-sharp.dll -r:/usr/lib/cli/gnome-vfs-sharp-2.0/gnome-vfs-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll -r:/usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll make[3]: Leaving directory `/build/buildd/muine-0.8.10/PluginLib' Making all in DBusLib make[3]: Entering directory `/build/buildd/muine-0.8.10/DBusLib' cp ../muine.snk . /usr/bin/csc -codepage:utf8 -target:library -out:muine-dbus.dll ./IPlayer.cs ./Player.cs ./AssemblyInfo.cs -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll -r:/usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll -r:/usr/lib/cli/art-sharp-2.0/art-sharp.dll -r:/usr/lib/cli/gnome-vfs-sharp-2.0/gnome-vfs-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll -r:/usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll -r:../PluginLib/muine-plugin.dll -r:/usr/lib/cli/ndesk-dbus-1.0/NDesk.DBus.dll -r:/usr/lib/cli/ndesk-dbus-glib-1.0/NDesk.DBus.GLib.dll make[3]: Leaving directory `/build/buildd/muine-0.8.10/DBusLib' Making all in src make[3]: Entering directory `/build/buildd/muine-0.8.10/src' sed -e "s|\@prefix\@|/usr|g" \ -e "s|\@pkglibdir\@|/usr/lib/muine|g" \ -e "s|\@target\@|muine.exe|g" \ -e "s|\@mono\@|/usr/bin/mono|g" \ -e "s|\@mono_flags\@||g" \ < muine.in > muine MONO_XMLSERIALIZER_THS=no wsdl -namespace:Amazon ./AmazonSearchService.wsdl Web Services Description Language Utility Mono Framework v2.0.50727.1433 There where some warnings while generating the code: ./AmazonSearchService.wsdl - This web reference does not conform to WS-I Basic Profile v1.1 R2706: A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements * Binding 'AmazonSearchBinding', in Service Description 'http://soap.amazon.com' R2209: A wsdl:binding in a DESCRIPTION SHOULD bind every wsdl:part of a wsdl:message in the wsdl:portType to which it refers to one of soapbind:body, soapbind:header, soapbind:fault or soapbind:headerfault * Binding 'AmazonSearchBinding', in Service Description 'http://soap.amazon.com' R2102: A QName reference to a Schema component in a DESCRIPTION MUST use the namespace defined in the targetNamespace attribute on the xsd:schema element, or to a namespace defined in the namespace attribute on an xsd:import element within the xsd:schema element * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' R2110: In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaComplexContentRestriction in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' R2111: In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' * XmlSchemaAttribute in Schema Schema 'http://soap.amazon.com', in Service Description 'http://soap.amazon.com' Writing file 'AmazonSearchService.cs' sed -e "s|\@version\@|0.8.10|" \ -e "s|\@datadir\@|/usr/share|" \ -e "s|\@pkglibdir\@|/usr/lib/muine|" \ < Defines.cs.in > Defines.cs /usr/bin/csc -codepage:utf8 -target:winexe -out:muine.exe ./AddSongWindow.cs ./AddAlbumWindow.cs ./Global.cs ./PlaylistWindow.cs ./Song.cs ./Album.cs ./SongDatabase.cs ./About.cs ./Metadata.cs ./Player.cs ./FileSelector.cs ./StringUtils.cs ./KeyUtils.cs ./SkipToWindow.cs ./ProgressWindow.cs ./ErrorDialog.cs ./OverwriteDialog.cs ./VolumeButton.cs ./HandleView.cs ./HandleModel.cs ./StockIcons.cs ./ColoredCellRendererPixbuf.cs ./CoverDatabase.cs ./CoverGetter.cs ./MusicBrainz.cs ./GnomeProxy.cs ./CoverImage.cs ./MmKeys.cs ./GnomeMMKeys.cs ./FileUtils.cs ./SignalUtils.cs ./Database.cs ./DBusService.cs ./PluginManager.cs ./AddWindow.cs ./Config.cs ./DndUtils.cs ./Item.cs ./ThreadBase.cs ./AddWindowList.cs ./AddWindowEntry.cs ./Actions.cs ./ImportDialog.cs ./OpenDialog.cs ./SaveDialog.cs AmazonSearchService.cs Defines.cs -r:../PluginLib/muine-plugin.dll -r:../DBusLib/muine-dbus.dll -r:/usr/lib/cli/ndesk-dbus-1.0/NDesk.DBus.dll -r:/usr/lib/cli/ndesk-dbus-glib-1.0/NDesk.DBus.GLib.dll -r:System.Web.Services -r:Mono.Posix -resource:../data/glade/PlaylistWindow.glade,PlaylistWindow.glade -resource:../data/glade/SkipToWindow.glade,SkipToWindow.glade -resource:../data/glade/ErrorDialog.glade,ErrorDialog.glade -resource:../data/glade/OverwriteDialog.glade,OverwriteDialog.glade -resource:../data/glade/AddWindow.glade,AddWindow.glade -resource:../data/glade/ProgressWindow.glade,ProgressWindow.glade -resource:../data/ui/PlaylistWindow.xml,PlaylistWindow.xml -resource:../data/images/muine-playing.png,muine-playing.png -resource:../data/images/muine-paused.png,muine-paused.png -resource:../data/images/muine-nothing.png,muine-nothing.png -resource:../data/images/muine-default-cover.png,muine-default-cover.png -resource:../data/images/muine-cover-downloading.png,muine-cover-downloading.png -resource:../data/images/muine-about.png,muine-about.png -resource:../data/images/muine-32.png,muine.png -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll -r:/usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll -r:/usr/lib/cli/art-sharp-2.0/art-sharp.dll -r:/usr/lib/cli/gnome-vfs-sharp-2.0/gnome-vfs-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll -r:/usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll ./PlaylistWindow.cs(169,25): warning CS0612: `Gtk.Tooltips' is obsolete ./VolumeButton.cs(55,17): warning CS0612: `Gtk.Tooltips' is obsolete ./PlaylistWindow.cs(885,40): warning CS0612: `Gtk.Tooltips' is obsolete ./SongDatabase.cs(137,52): warning CS0168: The variable `e' is declared but never used ./About.cs(99,30): warning CS0618: `Gtk.AboutDialog.Name' is obsolete: `Use ProgramName instead' ./VolumeButton.cs(55,41): warning CS0612: `Gtk.Tooltips' is obsolete ./HandleModel.cs(113,38): warning CS0618: `GLib.ListBase.Managed' is obsolete: `Replaced by owned parameter on ctor.' ./HandleModel.cs(340,29): warning CS0618: `GLib.DelegateWrapper.DelegateWrapper(object)' is obsolete: `Callback wrappers should be manually managed for persistence.' ./HandleModel.cs(1010,99): warning CS0618: `GLib.DelegateWrapper.DelegateWrapper(object)' is obsolete: `Callback wrappers should be manually managed for persistence.' ./CoverImage.cs(186,39): warning CS0618: `Gtk.Image.FromPixbuf' is obsolete: `Use the Pixbuf property instead' ./CoverImage.cs(189,39): warning CS0618: `Gtk.Image.FromPixbuf' is obsolete: `Use the Pixbuf property instead' ./DBusService.cs(96,37): warning CS0618: `NDesk.DBus.Connection.Register(string, NDesk.DBus.ObjectPath, object)' is obsolete: `Use the overload of Register() which does not take a bus_name parameter' ./SkipToWindow.cs(160,38): warning CS0169: The private method `Muine.SkipToWindow.OnScrollEvent(object, Gtk.ScrollEventArgs)' is never used ./HandleModel.cs(589,37): warning CS0169: The private method `Muine.HandleModel.OverrideRowsReordered(GLib.GType)' is never used ./HandleModel.cs(658,37): warning CS0169: The private method `Muine.HandleModel.OverrideRowChanged(GLib.GType)' is never used ./HandleModel.cs(722,37): warning CS0169: The private method `Muine.HandleModel.OverrideRowDeleted(GLib.GType)' is never used ./HandleModel.cs(785,37): warning CS0169: The private method `Muine.HandleModel.OverrideRowInserted(GLib.GType)' is never used ./HandleModel.cs(850,37): warning CS0169: The private method `Muine.HandleModel.OverrideRowHasChildToggled(GLib.GType)' is never used ./MusicBrainz.cs(138,25): warning CS0169: The private method `musicbrainz.MusicBrainz.FromUTF8Native(System.IntPtr, int)' is never used Compilation succeeded - 19 warning(s) sed -e "s|\@pkglibdir\@|/usr/lib/muine|" \ < muine.exe.config.in > muine.exe.config make[3]: Leaving directory `/build/buildd/muine-0.8.10/src' Making all in plugins make[3]: Entering directory `/build/buildd/muine-0.8.10/plugins' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -c -o inotify-glue.lo inotify-glue.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -c inotify-glue.c -fPIC -DPIC -o .libs/inotify-glue.o gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -c inotify-glue.c -o inotify-glue.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -Wl,-Bsymbolic-functions -o libinotifyglue.la -rpath /usr/lib/muine inotify-glue.lo gcc -shared .libs/inotify-glue.o -Wl,-Bsymbolic-functions -Wl,-soname -Wl,libinotifyglue.so.0 -o .libs/libinotifyglue.so.0.0.0 (cd .libs && rm -f libinotifyglue.so.0 && ln -s libinotifyglue.so.0.0.0 libinotifyglue.so.0) (cd .libs && rm -f libinotifyglue.so && ln -s libinotifyglue.so.0.0.0 libinotifyglue.so) ar cru .libs/libinotifyglue.a inotify-glue.o ranlib .libs/libinotifyglue.a creating libinotifyglue.la (cd .libs && rm -f libinotifyglue.la && ln -s ../libinotifyglue.la libinotifyglue.la) /usr/bin/csc -codepage:utf8 -target:library -out:TrayIcon.dll ./TrayIcon.cs ./NotificationArea.cs ../src/Defines.cs ../src/StringUtils.cs -r:../PluginLib/muine-plugin.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll -r:/usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll -r:/usr/lib/cli/art-sharp-2.0/art-sharp.dll -r:/usr/lib/cli/gnome-vfs-sharp-2.0/gnome-vfs-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll -r:/usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll -r:Mono.Posix -resource:./TrayIcon.xml,TrayIcon.xml -resource:./muine-tray-playing.png,muine-tray-playing.png -resource:./muine-tray-paused.png,muine-tray-paused.png ./TrayIcon.cs(59,25): warning CS0612: `Gtk.Tooltips' is obsolete ./TrayIcon.cs(125,40): warning CS0612: `Gtk.Tooltips' is obsolete ./TrayIcon.cs(76,38): warning CS0169: The private field `Muine.TrayIcon.gconf_client' is never used ./NotificationArea.cs(44,29): warning CS0414: The private field `NotificationArea.orientation' is assigned but its value is never used Compilation succeeded - 4 warning(s) /usr/bin/csc -codepage:utf8 -unsafe -target:library -out:InotifyPlugin.dll ./Inotify.cs ./InotifyPlugin.cs -r:../PluginLib/muine-plugin.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glib-sharp.dll -r:/usr/lib/cli/gnome-sharp-2.24/gnome-sharp.dll -r:/usr/lib/cli/art-sharp-2.0/art-sharp.dll -r:/usr/lib/cli/gnome-vfs-sharp-2.0/gnome-vfs-sharp.dll -r:/usr/lib/pkgconfig/../../lib/mono/gtk-sharp-2.0/glade-sharp.dll -r:/usr/lib/cli/gconf-sharp-2.0/gconf-sharp.dll -r:Mono.Posix sed -e "s|\@pkglibdir\@|/usr/lib/muine|" \ < InotifyPlugin.dll.config.in > InotifyPlugin.dll.config make[3]: Leaving directory `/build/buildd/muine-0.8.10/plugins' Making all in doc make[3]: Entering directory `/build/buildd/muine-0.8.10/doc' /usr/bin/mdassembler --ecma ./en -o muine-docs make[3]: Leaving directory `/build/buildd/muine-0.8.10/doc' Making all in m4 make[3]: Entering directory `/build/buildd/muine-0.8.10/m4' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/muine-0.8.10/m4' Making all in po make[3]: Entering directory `/build/buildd/muine-0.8.10/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo az | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file az.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file cs.po file=`echo da | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file da.po file=`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file de.po file=`echo el | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file el.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file dz.po file=`echo en_CA | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_CA.po file=`echo en_GB | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file en_GB.po file=`echo es | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file es.po file=`echo et | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file et.po file=`echo eu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file eu.po file=`echo fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo hr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hr.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.po file=`echo is | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file is.po file=`echo it | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file it.po file=`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ja.po file=`echo ko | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ko.po file=`echo lt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file lt.po file=`echo lv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file lv.po file=`echo mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file mk.po file=`echo ms | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ms.po file=`echo nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.po file=`echo ne | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ne.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo oc | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file oc.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pa.po file=`echo pl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pl.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo ro | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ro.po file=`echo ru | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ru.po file=`echo rw | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file rw.po file=`echo sk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sk.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.po file=`echo sr@Latn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr@Latn.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file th.po file=`echo tr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file tr.po file=`echo uk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file uk.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po make[3]: Leaving directory `/build/buildd/muine-0.8.10/po' make[3]: Entering directory `/build/buildd/muine-0.8.10' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/muine-0.8.10' make[2]: Leaving directory `/build/buildd/muine-0.8.10' make[1]: Leaving directory `/build/buildd/muine-0.8.10' debian/rules override_dh_auto_test make[1]: Entering directory `/build/buildd/muine-0.8.10' dh override_dh_auto_test make[1]: Leaving directory `/build/buildd/muine-0.8.10' touch build-stamp dh build /usr/bin/fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a Unknown option: with dh_prep: warning: ignored unknown options in DH_OPTIONS dh_installdirs -a Unknown option: with dh_installdirs: warning: ignored unknown options in DH_OPTIONS dh_auto_install -a Unknown option: with dh_auto_install: warning: ignored unknown options in DH_OPTIONS make[1]: Entering directory `/build/buildd/muine-0.8.10' Making install in data make[2]: Entering directory `/build/buildd/muine-0.8.10/data' Making install in glade make[3]: Entering directory `/build/buildd/muine-0.8.10/data/glade' make[4]: Entering directory `/build/buildd/muine-0.8.10/data/glade' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/glade' make[3]: Leaving directory `/build/buildd/muine-0.8.10/data/glade' Making install in images make[3]: Entering directory `/build/buildd/muine-0.8.10/data/images' make[4]: Entering directory `/build/buildd/muine-0.8.10/data/images' make[4]: Nothing to be done for `install-exec-am'. Installing application icons... for icon in muine-16.png muine-22.png muine-24.png muine-32.png muine-48.png muine-scalable.svg; do \ SIZE=`echo $icon | cut -d- -f2 | cut -d. -f1`; \ EXTENSION=`echo $icon | cut -d. -f2`; \ if test "$SIZE" = "scalable"; then \ SIZE="scalable"; \ else \ SIZE="${SIZE}x${SIZE}"; \ fi; \ mkdir -p /build/buildd/muine-0.8.10/debian/tmp/usr/share/icons/hicolor/$SIZE/apps; \ /usr/bin/install -c -m 644 ./$icon /build/buildd/muine-0.8.10/debian/tmp/usr/share/icons/hicolor/$SIZE/apps/muine.$EXTENSION; \ done *** Icon cache not updated. After install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/images' make[3]: Leaving directory `/build/buildd/muine-0.8.10/data/images' Making install in ui make[3]: Entering directory `/build/buildd/muine-0.8.10/data/ui' make[4]: Entering directory `/build/buildd/muine-0.8.10/data/ui' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/data/ui' make[3]: Leaving directory `/build/buildd/muine-0.8.10/data/ui' make[3]: Entering directory `/build/buildd/muine-0.8.10/data' make[4]: Entering directory `/build/buildd/muine-0.8.10/data' make[4]: Nothing to be done for `install-exec-am'. GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule muine.schemas (gconftool-2:30414): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/muine/playlist_window/width' to key `/apps/muine/playlist_window/width' WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `oc': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `C': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `el': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `mk': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ko': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `cs': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `es': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `et': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `eu': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `it': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `is': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `az': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `sr': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `sk': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `sv': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `da': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ja': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `de': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `bg': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `nb': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `pa': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ne': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `fi': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `th': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `nl': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `pl': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `fr': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ro': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `lt': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `uk': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `pt': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ru': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `hu': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `ca': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `dz': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `vi': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/width', locale `lv': Unable to store a value at key '/schemas/apps/muine/playlist_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/playlist_window/height' to key `/apps/muine/playlist_window/height' WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `oc': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `C': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `el': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `mk': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ko': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `cs': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `es': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `et': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `eu': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `it': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `is': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `az': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `sr': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `sk': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `sv': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `da': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ja': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `de': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `bg': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `nb': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `pa': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ne': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `fi': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `th': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `nl': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `pl': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `fr': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ro': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `lt': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `uk': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `pt': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ru': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `hu': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `ca': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `dz': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `vi': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/height', locale `lv': Unable to store a value at key '/schemas/apps/muine/playlist_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/playlist_window/pos_x' to key `/apps/muine/playlist_window/pos_x' WARNING: failed to install schema `/schemas/apps/muine/playlist_window/pos_x', locale `C': Unable to store a value at key '/schemas/apps/muine/playlist_window/pos_x', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/pos_x', locale `nl': Unable to store a value at key '/schemas/apps/muine/playlist_window/pos_x', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/playlist_window/pos_y' to key `/apps/muine/playlist_window/pos_y' WARNING: failed to install schema `/schemas/apps/muine/playlist_window/pos_y', locale `C': Unable to store a value at key '/schemas/apps/muine/playlist_window/pos_y', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/playlist_window/pos_y', locale `nl': Unable to store a value at key '/schemas/apps/muine/playlist_window/pos_y', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/add_song_window/width' to key `/apps/muine/add_song_window/width' WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `oc': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `C': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `el': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `mk': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ko': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `cs': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `es': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `et': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `eu': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `it': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `is': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `az': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `sr': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `sk': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `sv': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `da': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ja': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `de': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `bg': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `nb': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `pa': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ne': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `fi': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `th': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `nl': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `pl': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `fr': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ro': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `lt': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `uk': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `pt': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ru': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `hu': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `ca': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `dz': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `vi': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/width', locale `lv': Unable to store a value at key '/schemas/apps/muine/add_song_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/add_song_window/height' to key `/apps/muine/add_song_window/height' WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `oc': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `C': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `el': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `mk': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ko': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `cs': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `es': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `et': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `eu': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `it': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `is': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `az': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `sr': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `sk': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `sv': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `da': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ja': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `de': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `bg': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `nb': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `pa': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ne': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `fi': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `th': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `nl': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `pl': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `fr': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ro': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `lt': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `uk': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `pt': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ru': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `hu': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `ca': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `dz': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `vi': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_song_window/height', locale `lv': Unable to store a value at key '/schemas/apps/muine/add_song_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/add_album_window/width' to key `/apps/muine/add_album_window/width' WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `oc': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `C': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `el': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `mk': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ko': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `cs': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `es': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `et': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `eu': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `it': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `is': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `az': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `sr': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `sk': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `sv': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `da': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ja': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `de': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `bg': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `nb': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `pa': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ne': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `fi': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `th': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `nl': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `pl': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `fr': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ro': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `lt': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `uk': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `pt': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ru': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `hu': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `ca': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `dz': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `vi': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/width', locale `lv': Unable to store a value at key '/schemas/apps/muine/add_album_window/width', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/add_album_window/height' to key `/apps/muine/add_album_window/height' WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `oc': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `C': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `el': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `mk': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ko': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `cs': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `es': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `et': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `eu': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `it': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `is': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `az': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `sr': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `sk': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `sv': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `da': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ja': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `de': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `bg': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `nb': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `pa': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ne': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `fi': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `th': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `nl': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `pl': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `fr': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ro': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `lt': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `uk': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `pt': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ru': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `hu': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `ca': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `dz': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `vi': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/add_album_window/height', locale `lv': Unable to store a value at key '/schemas/apps/muine/add_album_window/height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/volume' to key `/apps/muine/volume' WARNING: failed to install schema `/schemas/apps/muine/volume', locale `oc': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `C': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `el': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `mk': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ko': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `cs': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `es': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `et': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `eu': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `it': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `is': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `az': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `sr': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `sk': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `sv': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `da': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ja': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `de': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `bg': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `nb': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `pa': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ne': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `fi': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `th': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `nl': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `pl': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `fr': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ro': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `lt': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `uk': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `pt': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ru': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `hu': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `ca': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `dz': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `vi': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/volume', locale `lv': Unable to store a value at key '/schemas/apps/muine/volume', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/repeat' to key `/apps/muine/repeat' WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `C': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `el': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `mk': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ar': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ko': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `cs': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `es': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `et': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `eu': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ms': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `is': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `it': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `sr': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `az': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `sk': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `sv': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `da': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ja': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `de': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `bg': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `nb': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `pa': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ne': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `fi': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `th': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `nl': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `pl': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `fr': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ro': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `hu': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `lt': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `uk': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ru': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `dz': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `ca': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `lv': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `vi': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/repeat', locale `pt': Unable to store a value at key '/schemas/apps/muine/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/watched_folders' to key `/apps/muine/watched_folders' WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `oc': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `C': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `el': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `mk': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ko': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `cs': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `es': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `et': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `eu': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `it': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `is': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `az': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `sr': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `sk': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `sv': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `da': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ja': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `de': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `bg': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `nb': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `pa': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ne': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `fi': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `th': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `nl': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `pl': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `fr': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ro': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `lt': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `uk': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `pt': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ru': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `hu': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `ca': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `dz': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `vi': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/watched_folders', locale `lv': Unable to store a value at key '/schemas/apps/muine/watched_folders', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/only_complete_albums' to key `/apps/muine/only_complete_albums' WARNING: failed to install schema `/schemas/apps/muine/only_complete_albums', locale `C': Unable to store a value at key '/schemas/apps/muine/only_complete_albums', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/only_complete_albums', locale `nl': Unable to store a value at key '/schemas/apps/muine/only_complete_albums', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/default_import_folder' to key `/apps/muine/default_import_folder' WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `oc': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `C': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `el': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `mk': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ko': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `cs': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `es': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `et': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `eu': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `it': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `is': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `az': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `sr': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `sk': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `sv': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `da': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ja': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `de': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `bg': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `nb': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `pa': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ne': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `fi': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `th': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `nl': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `pl': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `fr': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ro': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `lt': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `uk': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `pt': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ru': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `hu': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `ca': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `dz': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `vi': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_import_folder', locale `lv': Unable to store a value at key '/schemas/apps/muine/default_import_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/default_playlist_folder' to key `/apps/muine/default_playlist_folder' WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `oc': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `C': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `el': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `mk': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `zh_CN': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ko': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `cs': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `es': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `et': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `eu': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `it': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `is': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `az': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `sr': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `sk': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `sv': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `da': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ja': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `de': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `bg': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `nb': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `pa': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ne': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `fi': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `th': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `nl': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `pl': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `fr': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ro': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `lt': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `uk': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `pt': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ru': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `hu': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `ca': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `dz': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `vi': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/default_playlist_folder', locale `lv': Unable to store a value at key '/schemas/apps/muine/default_playlist_folder', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/amazon_locale' to key `/apps/muine/amazon_locale' WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `C': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `el': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `mk': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ko': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `cs': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `es': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `et': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `eu': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `it': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `is': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `az': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `sr': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `sk': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `sv': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `da': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ja': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `de': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `bg': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `nb': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ne': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `fi': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `th': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `nl': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `pl': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `fr': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `sr@Latn': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ro': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `lt': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `uk': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `pt': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ru': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `hu': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `ca': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `dz': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `vi': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_locale', locale `lv': Unable to store a value at key '/schemas/apps/muine/amazon_locale', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/amazon_dev_tag' to key `/apps/muine/amazon_dev_tag' WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `pt': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `en_CA': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `da': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `C': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `nb': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `en_GB': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `de': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `ne': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `bg': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `th': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `fi': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `vi': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `ja': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `el': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `nl': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `mk': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `pl': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `pt_BR': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `fr': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `cs': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `es': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `et': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `eu': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `it': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `hu': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `lv': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `dz': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `ru': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/amazon_dev_tag', locale `sv': Unable to store a value at key '/schemas/apps/muine/amazon_dev_tag', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/muine/show_notifications' to key `/apps/muine/show_notifications' WARNING: failed to install schema `/schemas/apps/muine/show_notifications', locale `C': Unable to store a value at key '/schemas/apps/muine/show_notifications', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/muine/show_notifications', locale `nl': Unable to store a value at key '/schemas/apps/muine/show_notifications', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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/dbus-1/services" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/share/dbus-1/services" /usr/bin/install -c -m 644 'org.gnome.Muine.service' '/build/buildd/muine-0.8.10/debian/tmp/usr/share/dbus-1/services/org.gnome.Muine.service' test -z "/usr/share/applications" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/share/applications" /usr/bin/install -c -m 644 'muine.desktop' '/build/buildd/muine-0.8.10/debian/tmp/usr/share/applications/muine.desktop' test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/pkgconfig" /usr/bin/install -c -m 644 'muine-plugin.pc' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/pkgconfig/muine-plugin.pc' /usr/bin/install -c -m 644 'muine-dbus.pc' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/pkgconfig/muine-dbus.pc' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/etc/gconf/schemas" /usr/bin/install -c -m 644 'muine.schemas' '/build/buildd/muine-0.8.10/debian/tmp/etc/gconf/schemas/muine.schemas' make[4]: Leaving directory `/build/buildd/muine-0.8.10/data' make[3]: Leaving directory `/build/buildd/muine-0.8.10/data' make[2]: Leaving directory `/build/buildd/muine-0.8.10/data' Making install in libmuine make[2]: Entering directory `/build/buildd/muine-0.8.10/libmuine' Making install in id3-vfs make[3]: Entering directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' make[4]: Entering directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' make[4]: Nothing to be done for `install-exec-am'. make[4]: Nothing to be done for `install-data-am'. make[4]: Leaving directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' make[3]: Leaving directory `/build/buildd/muine-0.8.10/libmuine/id3-vfs' make[3]: Entering directory `/build/buildd/muine-0.8.10/libmuine' make[4]: Entering directory `/build/buildd/muine-0.8.10/libmuine' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine" /bin/bash ../libtool --mode=install /usr/bin/install -c 'libmuine.la' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.la' /usr/bin/install -c .libs/libmuine.so.0.0.0 /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.so.0.0.0 (cd /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine && { ln -s -f libmuine.so.0.0.0 libmuine.so.0 || { rm -f libmuine.so.0 && ln -s libmuine.so.0.0.0 libmuine.so.0; }; }) (cd /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine && { ln -s -f libmuine.so.0.0.0 libmuine.so || { rm -f libmuine.so && ln -s libmuine.so.0.0.0 libmuine.so; }; }) /usr/bin/install -c .libs/libmuine.lai /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.la /usr/bin/install -c .libs/libmuine.a /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.a chmod 644 /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.a ranlib /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libmuine.a libtool: install: warning: remember to run `libtool --finish /usr/lib/muine' make[4]: Leaving directory `/build/buildd/muine-0.8.10/libmuine' make[3]: Leaving directory `/build/buildd/muine-0.8.10/libmuine' make[2]: Leaving directory `/build/buildd/muine-0.8.10/libmuine' Making install in PluginLib make[2]: Entering directory `/build/buildd/muine-0.8.10/PluginLib' make[3]: Entering directory `/build/buildd/muine-0.8.10/PluginLib' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine" /usr/bin/install -c -m 644 'muine-plugin.dll' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/muine-plugin.dll' make[3]: Leaving directory `/build/buildd/muine-0.8.10/PluginLib' make[2]: Leaving directory `/build/buildd/muine-0.8.10/PluginLib' Making install in DBusLib make[2]: Entering directory `/build/buildd/muine-0.8.10/DBusLib' make[3]: Entering directory `/build/buildd/muine-0.8.10/DBusLib' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine" /usr/bin/install -c -m 644 'muine-dbus.dll' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/muine-dbus.dll' make[3]: Leaving directory `/build/buildd/muine-0.8.10/DBusLib' make[2]: Leaving directory `/build/buildd/muine-0.8.10/DBusLib' Making install in src make[2]: Entering directory `/build/buildd/muine-0.8.10/src' make[3]: Entering directory `/build/buildd/muine-0.8.10/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/bin" /usr/bin/install -c 'muine' '/build/buildd/muine-0.8.10/debian/tmp/usr/bin/muine' test -z "/usr/lib/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine" /usr/bin/install -c -m 644 'muine.exe' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/muine.exe' /usr/bin/install -c -m 644 'muine.exe.config' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/muine.exe.config' make[3]: Leaving directory `/build/buildd/muine-0.8.10/src' make[2]: Leaving directory `/build/buildd/muine-0.8.10/src' Making install in plugins make[2]: Entering directory `/build/buildd/muine-0.8.10/plugins' make[3]: Entering directory `/build/buildd/muine-0.8.10/plugins' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine" /bin/bash ../libtool --mode=install /usr/bin/install -c 'libinotifyglue.la' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.la' /usr/bin/install -c .libs/libinotifyglue.so.0.0.0 /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.so.0.0.0 (cd /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine && { ln -s -f libinotifyglue.so.0.0.0 libinotifyglue.so.0 || { rm -f libinotifyglue.so.0 && ln -s libinotifyglue.so.0.0.0 libinotifyglue.so.0; }; }) (cd /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine && { ln -s -f libinotifyglue.so.0.0.0 libinotifyglue.so || { rm -f libinotifyglue.so && ln -s libinotifyglue.so.0.0.0 libinotifyglue.so; }; }) /usr/bin/install -c .libs/libinotifyglue.lai /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.la /usr/bin/install -c .libs/libinotifyglue.a /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.a chmod 644 /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.a ranlib /build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/libinotifyglue.a libtool: install: warning: remember to run `libtool --finish /usr/lib/muine' test -z "/usr/lib/muine/plugins" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/plugins" /usr/bin/install -c -m 644 'TrayIcon.dll' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/plugins/TrayIcon.dll' /usr/bin/install -c -m 644 'TrayIcon.dll.config' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/plugins/TrayIcon.dll.config' /usr/bin/install -c -m 644 'InotifyPlugin.dll' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/plugins/InotifyPlugin.dll' /usr/bin/install -c -m 644 'InotifyPlugin.dll.config' '/build/buildd/muine-0.8.10/debian/tmp/usr/lib/muine/plugins/InotifyPlugin.dll.config' make[3]: Leaving directory `/build/buildd/muine-0.8.10/plugins' make[2]: Leaving directory `/build/buildd/muine-0.8.10/plugins' Making install in doc make[2]: Entering directory `/build/buildd/muine-0.8.10/doc' make[3]: Entering directory `/build/buildd/muine-0.8.10/doc' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/doc/muine" || /bin/mkdir -p "/build/buildd/muine-0.8.10/debian/tmp/usr/share/doc/muine" /usr/bin/install -c -m 644 'muine-docs.zip' '/build/buildd/muine-0.8.10/debian/tmp/usr/share/doc/muine/muine-docs.zip' /usr/bin/install -c -m 644 'muine-docs.tree' '/build/buildd/muine-0.8.10/debian/tmp/usr/share/doc/muine/muine-docs.tree' /usr/bin/install -c -m 644 'muine-docs.source' '/build/buildd/muine-0.8.10/debian/tmp/usr/share/doc/muine/muine-docs.source' make[3]: Leaving directory `/build/buildd/muine-0.8.10/doc' make[2]: Leaving directory `/build/buildd/muine-0.8.10/doc' Making install in m4 make[2]: Entering directory `/build/buildd/muine-0.8.10/m4' make[3]: Entering directory `/build/buildd/muine-0.8.10/m4' 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/muine-0.8.10/m4' make[2]: Leaving directory `/build/buildd/muine-0.8.10/m4' Making install in po make[2]: Entering directory `/build/buildd/muine-0.8.10/po' linguas="ar az bg ca cs da de el dz en_CA en_GB es et eu fi fr hr hu is it ja ko lt lv mk ms nb ne nl oc pa pl pt pt_BR ro ru rw sk sr sr@Latn sv th tr uk vi zh_CN "; \ for lang in $linguas; do \ dir=/build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/$lang/LC_MESSAGES; \ /bin/sh /build/buildd/muine-0.8.10/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/muine.mo; \ echo "installing $lang.gmo as $dir/muine.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/muine.mo; \ echo "installing ./$lang.gmo as" \ "$dir/muine.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/muine.mo.m; \ echo "installing $lang.gmo.m as $dir/muine.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/muine.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/muine.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ar/LC_MESSAGES/muine.mo installing az.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/az/LC_MESSAGES/muine.mo installing bg.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/bg/LC_MESSAGES/muine.mo installing ca.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ca/LC_MESSAGES/muine.mo installing cs.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/cs/LC_MESSAGES/muine.mo installing da.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/da/LC_MESSAGES/muine.mo installing de.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/de/LC_MESSAGES/muine.mo installing el.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/el/LC_MESSAGES/muine.mo installing dz.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/dz/LC_MESSAGES/muine.mo installing en_CA.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/en_CA/LC_MESSAGES/muine.mo installing en_GB.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/muine.mo installing es.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/es/LC_MESSAGES/muine.mo installing et.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/et/LC_MESSAGES/muine.mo installing eu.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/eu/LC_MESSAGES/muine.mo installing fi.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/fi/LC_MESSAGES/muine.mo installing fr.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/fr/LC_MESSAGES/muine.mo installing hr.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/hr/LC_MESSAGES/muine.mo installing hu.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/hu/LC_MESSAGES/muine.mo installing is.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/is/LC_MESSAGES/muine.mo installing it.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/it/LC_MESSAGES/muine.mo installing ja.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ja/LC_MESSAGES/muine.mo installing ko.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ko/LC_MESSAGES/muine.mo installing lt.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/lt/LC_MESSAGES/muine.mo installing lv.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/lv/LC_MESSAGES/muine.mo installing mk.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/mk/LC_MESSAGES/muine.mo installing ms.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ms/LC_MESSAGES/muine.mo installing nb.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/nb/LC_MESSAGES/muine.mo installing ne.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ne/LC_MESSAGES/muine.mo installing nl.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/nl/LC_MESSAGES/muine.mo installing oc.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/oc/LC_MESSAGES/muine.mo installing pa.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/pa/LC_MESSAGES/muine.mo installing pl.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/pl/LC_MESSAGES/muine.mo installing pt.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/pt/LC_MESSAGES/muine.mo installing pt_BR.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/pt_BR/LC_MESSAGES/muine.mo installing ro.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ro/LC_MESSAGES/muine.mo installing ru.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/ru/LC_MESSAGES/muine.mo installing rw.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/rw/LC_MESSAGES/muine.mo installing sk.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/sk/LC_MESSAGES/muine.mo installing sr.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/sr/LC_MESSAGES/muine.mo installing sr@Latn.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/sr@Latn/LC_MESSAGES/muine.mo installing sv.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/sv/LC_MESSAGES/muine.mo installing th.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/th/LC_MESSAGES/muine.mo installing tr.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/tr/LC_MESSAGES/muine.mo installing uk.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/uk/LC_MESSAGES/muine.mo installing vi.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/vi/LC_MESSAGES/muine.mo installing zh_CN.gmo as /build/buildd/muine-0.8.10/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/muine.mo make[2]: Leaving directory `/build/buildd/muine-0.8.10/po' make[2]: Entering directory `/build/buildd/muine-0.8.10' make[3]: Entering directory `/build/buildd/muine-0.8.10' 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/muine-0.8.10' make[2]: Leaving directory `/build/buildd/muine-0.8.10' make[1]: Leaving directory `/build/buildd/muine-0.8.10' dh_install -a Unknown option: with dh_install: warning: ignored unknown options in DH_OPTIONS dh_installdocs -a Unknown option: with dh_installdocs: warning: ignored unknown options in DH_OPTIONS dh_installchangelogs -a Unknown option: with dh_installchangelogs: warning: ignored unknown options in DH_OPTIONS dh_installexamples -a Unknown option: with dh_installexamples: warning: ignored unknown options in DH_OPTIONS dh_installman -a Unknown option: with dh_installman: warning: ignored unknown options in DH_OPTIONS dh_installcatalogs -a Unknown option: with dh_installcatalogs: warning: ignored unknown options in DH_OPTIONS dh_installcron -a Unknown option: with dh_installcron: warning: ignored unknown options in DH_OPTIONS dh_installdebconf -a Unknown option: with dh_installdebconf: warning: ignored unknown options in DH_OPTIONS dh_installcatalogs -a Unknown option: with dh_installcatalogs: warning: ignored unknown options in DH_OPTIONS dh_installemacsen -a Unknown option: with dh_installemacsen: warning: ignored unknown options in DH_OPTIONS dh_installifupdown -a Unknown option: with dh_installifupdown: warning: ignored unknown options in DH_OPTIONS dh_installinfo -a Unknown option: with dh_installinfo: warning: ignored unknown options in DH_OPTIONS dh_installinit -a Unknown option: with dh_installinit: warning: ignored unknown options in DH_OPTIONS dh_installmenu -a Unknown option: with dh_installmenu: warning: ignored unknown options in DH_OPTIONS dh_installmime -a Unknown option: with dh_installmime: warning: ignored unknown options in DH_OPTIONS dh_installmodules -a Unknown option: with dh_installmodules: warning: ignored unknown options in DH_OPTIONS dh_installlogcheck -a Unknown option: with dh_installlogcheck: warning: ignored unknown options in DH_OPTIONS dh_installlogrotate -a Unknown option: with dh_installlogrotate: warning: ignored unknown options in DH_OPTIONS dh_installpam -a Unknown option: with dh_installpam: warning: ignored unknown options in DH_OPTIONS dh_installppp -a Unknown option: with dh_installppp: warning: ignored unknown options in DH_OPTIONS dh_installudev -a Unknown option: with dh_installudev: warning: ignored unknown options in DH_OPTIONS dh_installwm -a Unknown option: with dh_installwm: warning: ignored unknown options in DH_OPTIONS dh_installxfonts -a Unknown option: with dh_installxfonts: warning: ignored unknown options in DH_OPTIONS dh_bugfiles -a Unknown option: with dh_bugfiles: warning: ignored unknown options in DH_OPTIONS dh_lintian -a Unknown option: with dh_lintian: warning: ignored unknown options in DH_OPTIONS dh_gconf -a Unknown option: with dh_gconf: warning: ignored unknown options in DH_OPTIONS dh_icons -a Unknown option: with dh_icons: warning: ignored unknown options in DH_OPTIONS dh_perl -a Unknown option: with dh_perl: warning: ignored unknown options in DH_OPTIONS dh_scrollkeeper -a Unknown option: with dh_scrollkeeper: warning: ignored unknown options in DH_OPTIONS dh_usrlocal -a Unknown option: with dh_usrlocal: warning: ignored unknown options in DH_OPTIONS dh_link -a Unknown option: with dh_link: warning: ignored unknown options in DH_OPTIONS dh_compress -a Unknown option: with dh_compress: warning: ignored unknown options in DH_OPTIONS dh_fixperms -a Unknown option: with dh_fixperms: warning: ignored unknown options in DH_OPTIONS dh_clifixperms -a Unknown option: with dh_clifixperms: warning: ignored unknown options in DH_OPTIONS dh_strip -a dh_strip debug symbol extraction: all non-arch-all packages for this build platform lpia: muine muine-plugin-inotify dh_strip debug symbol extraction: packages to act on: muine muine-plugin-inotify dh_strip debug symbol extraction: ignored packages: dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. pkgstriptranslations: processing control file: ./debian/muine-dbgsym/DEBIAN/control, package muine-dbgsym, directory ./debian/muine-dbgsym pkgstriptranslations: muine-dbgsym does not contain translations, skipping pkgstriptranslations: preparing translation tarball muine_0.8.10-5_lpia_translations.tar.gz...done (46 files) pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " dpkg-deb: warning: '/build/buildd/muine-0.8.10/debian/muine-dbgsym/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `muine-dbgsym' in `../muine-dbgsym_0.8.10-5_lpia.ddeb'. dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. pkgstriptranslations: processing control file: ./debian/muine-plugin-inotify-dbgsym/DEBIAN/control, package muine-plugin-inotify-dbgsym, directory ./debian/muine-plugin-inotify-dbgsym pkgstriptranslations: muine-plugin-inotify-dbgsym does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " dpkg-deb: warning: '/build/buildd/muine-0.8.10/debian/muine-plugin-inotify-dbgsym/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `muine-plugin-inotify-dbgsym' in `../muine-plugin-inotify-dbgsym_0.8.10-5_lpia.ddeb'. Unknown option: with dh_strip.pkg-create-dbgsym: warning: ignored unknown options in DH_OPTIONS dh_makeshlibs -a Unknown option: with dh_makeshlibs: warning: ignored unknown options in DH_OPTIONS dh_shlibdeps -a Unknown option: with dh_shlibdeps: warning: ignored unknown options in DH_OPTIONS dpkg-shlibdeps: warning: debian/muine/usr/lib/muine/libmuine.so.0.0.0 contains an unresolvable reference to symbol XKeysymToKeycode: it's probably a plugin. dpkg-shlibdeps: warning: 1 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: dependency on libz.so.1 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgconf-2.so.4 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgio-2.0.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libcairo.so.2 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpango-1.0.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpangocairo-1.0.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libogg.so.0 could be avoided if "debian/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" 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/muine/usr/lib/muine/libmuine.so.0.0.0" were not uselessly linked against it (they use none of its symbols). dh_clistrip -a Unknown option: with dh_clistrip: warning: ignored unknown options in DH_OPTIONS dh_cligacpolicy -a Unknown option: with dh_cligacpolicy: warning: ignored unknown options in DH_OPTIONS dh_cligacpolicy: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.5.7)! debian/rules override_dh_makeclilibs make[1]: Entering directory `/build/buildd/muine-0.8.10' dh_makeclilibs -V 'muine (= 0.8.10-5 )' Unknown option: with Unknown option: with dh_makeclilibs: warning: ignored unknown options in DH_OPTIONS dh_makeclilibs: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)! dh_makeclilibs: debian/muine-plugin-inotify/usr/lib/muine/plugins/InotifyPlugin.dll has no valid signature, ignoring make[1]: Leaving directory `/build/buildd/muine-0.8.10' dh_installcligac -a Unknown option: with dh_installcligac: warning: ignored unknown options in DH_OPTIONS dh_clideps -a Unknown option: with dh_clideps: warning: ignored unknown options in DH_OPTIONS dh_clideps: Warning! No Build-Depends(-Indep) on cli-common-dev (>= 0.4.4)! dh_installdeb -a Unknown option: with dh_installdeb: warning: ignored unknown options in DH_OPTIONS dh_gencontrol -a Unknown option: with dh_gencontrol: warning: ignored unknown options in DH_OPTIONS dh_md5sums -a Unknown option: with dh_md5sums: warning: ignored unknown options in DH_OPTIONS dh_builddeb -a Unknown option: with dh_builddeb: warning: ignored unknown options in DH_OPTIONS dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. pkgstriptranslations: processing control file: ./debian/muine/DEBIAN/control, package muine, directory ./debian/muine ./debian/muine/usr/share/applications/muine.desktop: does not have gettext domain, not stripping pkgstriptranslations: processing control file: ./debian/muine-plugin-inotify/DEBIAN/control, package muine-plugin-inotify, directory ./debian/muine-plugin-inotify pkgstriptranslations: muine-plugin-inotify does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " dpkg-deb: warning: 'debian/muine/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `muine' in `../muine_0.8.10-5_lpia.deb'. dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. pkgstriptranslations: processing control file: ./debian/muine/DEBIAN/control, package muine, directory ./debian/muine ./debian/muine/usr/share/applications/muine.desktop: does not have gettext domain, not stripping pkgstriptranslations: processing control file: ./debian/muine-plugin-inotify/DEBIAN/control, package muine-plugin-inotify, directory ./debian/muine-plugin-inotify pkgstriptranslations: muine-plugin-inotify does not contain translations, skipping pkgstriptranslations: tarball already exists pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " dpkg-deb: warning: 'debian/muine-plugin-inotify/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: ignoring 1 warnings about the control file(s) dpkg-deb: building package `muine-plugin-inotify' in `../muine-plugin-inotify_0.8.10-5_lpia.deb'. dpkg-genchanges -B -mUbuntu/lpia Build Daemon >../muine_0.8.10-5_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 501. Use of uninitialized value within @_ in list assignment at /usr/share/perl5/Dpkg/Arch.pm line 299. Use of uninitialized value $b in string eq at /usr/share/perl5/Dpkg/Arch.pm line 301. Use of uninitialized value $_ in pattern match (m//) at /usr/share/perl5/Dpkg/Arch.pm line 250. Use of uninitialized value $arch in hash element at /usr/share/perl5/Dpkg/Arch.pm line 257. dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20090720-1549 Publishing chroot-autobuild/build/buildd/muine_0.8.10-5_lpia_translations.tar.gz for rosetta. Publishing debug debs. chroot-autobuild/build/buildd/muine_0.8.10-5_lpia.deb: new debian package, version 2.0. size 348038 bytes: control archive= 3572 bytes. 120 bytes, 2 lines clilibs 1724 bytes, 18 lines control 5238 bytes, 72 lines md5sums 447 bytes, 17 lines * postinst #!/bin/sh 575 bytes, 22 lines * postrm #!/bin/sh 180 bytes, 7 lines * prerm #!/bin/sh 17 bytes, 1 lines shlibs Package: muine Version: 0.8.10-5 Architecture: lpia Maintainer: Ubuntu Developers Original-Maintainer: Debian CLI Applications Team Installed-Size: 1752 Depends: libatk1.0-0 (>= 1.20.0), libc6 (>= 2.9), libcairo2 (>= 1.2.4), libflac8, libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.2.1), libgconf2-4 (>= 2.23.2), libgdbm3, libglib2.0-0 (>= 2.20.0), libgnomevfs2-0 (>= 1:2.17.90), libgstreamer0.10-0 (>= 0.10.0), libgtk2.0-0 (>= 2.17.4), libid3tag0 (>= 0.15.1b), libogg0 (>= 1.0rc3), libpango1.0-0 (>= 1.14.0), libvorbis0a (>= 1.1.2), libvorbisfile3 (>= 1.1.2), libxml2 (>= 2.6.27), zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2), mono-runtime (>= 1.1.8.1), libgconf2.0-cil (>= 2.24.0), libglade2.0-cil (>= 2.12.9), libglib2.0-cil (>= 2.12.9), libgnome-vfs2.0-cil (>= 2.24.0), libgnome2.24-cil (>= 2.24.0), libgtk2.0-cil (>= 2.12.9), libmono-corlib2.0-cil (>= 1.2.2.1), libmono-posix2.0-cil (>= 2.4), libmono-system-web2.0-cil (>= 1.9.1), libmono-system2.0-cil (>= 2.4), libmusicbrainz4c2a (>= 2.1.5), libndesk-dbus-glib1.0-cil (>= 0.4.0), libndesk-dbus1.0-cil (>= 0.6.0), gstreamer0.10-plugins-base, gstreamer0.10-plugins-good Section: gnome Priority: optional Homepage: http://muine-player.org/ Description: Simple playlist based music player Muine is an innovative music player. It has a simple interface designed to allow the user to easily construct playlists from albums and/or single songs. Its goal is to be simply a music player, not to become a robust music management application. It includes a plugin interface. . The package includes the CIL assemblies to access the D-Bus interface to Muine and to compile plugins for Muine. chroot-autobuild/build/buildd/muine-plugin-inotify_0.8.10-5_lpia.deb: new debian package, version 2.0. size 58552 bytes: control archive= 957 bytes. 646 bytes, 15 lines control 477 bytes, 6 lines md5sums 135 bytes, 7 lines * postinst #!/bin/sh 132 bytes, 7 lines * postrm #!/bin/sh 38 bytes, 1 lines shlibs Package: muine-plugin-inotify Source: muine Version: 0.8.10-5 Architecture: lpia Maintainer: Ubuntu Developers Original-Maintainer: Debian CLI Applications Team Installed-Size: 128 Depends: libgtk2.0-cil (>= 2.12.9), libmono-corlib2.0-cil (>= 1.2.2.1), muine (= 0.8.10-5), libc6 (>= 2.9) Section: gnome Priority: optional Homepage: http://muine-player.org/ Description: INotify Plugin for the Muine music player This package enables INotify support for the Muine music player to enable watching of music directories for new and removed files and directories. chroot-autobuild/build/buildd/muine_0.8.10-5_lpia.deb: drwxr-xr-x root/root 0 2009-07-20 15:49 ./ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/mono/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/mono/muine/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/mono/muine/plugins/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/muine/ -rw-r--r-- root/root 8192 2009-07-20 15:49 ./usr/lib/muine/muine-dbus.dll -rw-r--r-- root/root 7168 2009-07-20 15:49 ./usr/lib/muine/muine-plugin.dll -rwxr-xr-x root/root 318464 2009-07-20 15:49 ./usr/lib/muine/muine.exe -rw-r--r-- root/root 415 2009-07-20 15:49 ./usr/lib/muine/muine.exe.config -rw-r--r-- root/root 67656 2009-07-20 15:49 ./usr/lib/muine/libmuine.so.0.0.0 drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/pkgconfig/ -rw-r--r-- root/root 249 2009-07-20 15:49 ./usr/lib/pkgconfig/muine-dbus.pc -rw-r--r-- root/root 275 2009-07-20 15:49 ./usr/lib/pkgconfig/muine-plugin.pc drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/gconf/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 105209 2009-07-20 15:49 ./usr/share/gconf/schemas/muine.schemas drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/applications/ -rw-r--r-- root/root 3631 2009-07-20 15:49 ./usr/share/applications/muine.desktop drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/dbus-1/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/dbus-1/services/ -rw-r--r-- root/root 57 2009-07-20 15:49 ./usr/share/dbus-1/services/org.gnome.Muine.service drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 1722 2009-07-20 15:49 ./usr/share/locale/ar/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/az/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/az/LC_MESSAGES/ -rw-r--r-- root/root 11574 2009-07-20 15:49 ./usr/share/locale/az/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/bg/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/bg/LC_MESSAGES/ -rw-r--r-- root/root 13623 2009-07-20 15:49 ./usr/share/locale/bg/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ca/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ca/LC_MESSAGES/ -rw-r--r-- root/root 10593 2009-07-20 15:49 ./usr/share/locale/ca/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 10324 2009-07-20 15:49 ./usr/share/locale/cs/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 9958 2009-07-20 15:49 ./usr/share/locale/da/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 10405 2009-07-20 15:49 ./usr/share/locale/de/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 13588 2009-07-20 15:49 ./usr/share/locale/el/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/dz/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/dz/LC_MESSAGES/ -rw-r--r-- root/root 16880 2009-07-20 15:49 ./usr/share/locale/dz/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/en_CA/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/en_CA/LC_MESSAGES/ -rw-r--r-- root/root 9537 2009-07-20 15:49 ./usr/share/locale/en_CA/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 9573 2009-07-20 15:49 ./usr/share/locale/en_GB/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 10744 2009-07-20 15:49 ./usr/share/locale/es/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 9635 2009-07-20 15:49 ./usr/share/locale/et/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/eu/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/eu/LC_MESSAGES/ -rw-r--r-- root/root 10379 2009-07-20 15:49 ./usr/share/locale/eu/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/fi/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/fi/LC_MESSAGES/ -rw-r--r-- root/root 9955 2009-07-20 15:49 ./usr/share/locale/fi/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 10870 2009-07-20 15:49 ./usr/share/locale/fr/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/hr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/hr/LC_MESSAGES/ -rw-r--r-- root/root 1154 2009-07-20 15:49 ./usr/share/locale/hr/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 10363 2009-07-20 15:49 ./usr/share/locale/hu/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/is/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/is/LC_MESSAGES/ -rw-r--r-- root/root 5996 2009-07-20 15:49 ./usr/share/locale/is/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 10072 2009-07-20 15:49 ./usr/share/locale/it/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 11224 2009-07-20 15:49 ./usr/share/locale/ja/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 9971 2009-07-20 15:49 ./usr/share/locale/ko/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 9990 2009-07-20 15:49 ./usr/share/locale/lt/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/lv/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/lv/LC_MESSAGES/ -rw-r--r-- root/root 10386 2009-07-20 15:49 ./usr/share/locale/lv/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/mk/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/mk/LC_MESSAGES/ -rw-r--r-- root/root 12958 2009-07-20 15:49 ./usr/share/locale/mk/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ms/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ms/LC_MESSAGES/ -rw-r--r-- root/root 7954 2009-07-20 15:49 ./usr/share/locale/ms/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 9810 2009-07-20 15:49 ./usr/share/locale/nb/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ne/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ne/LC_MESSAGES/ -rw-r--r-- root/root 14960 2009-07-20 15:49 ./usr/share/locale/ne/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/nl/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/nl/LC_MESSAGES/ -rw-r--r-- root/root 11016 2009-07-20 15:49 ./usr/share/locale/nl/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/oc/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/oc/LC_MESSAGES/ -rw-r--r-- root/root 5177 2009-07-20 15:49 ./usr/share/locale/oc/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pa/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pa/LC_MESSAGES/ -rw-r--r-- root/root 9857 2009-07-20 15:49 ./usr/share/locale/pa/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 10626 2009-07-20 15:49 ./usr/share/locale/pl/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 10430 2009-07-20 15:49 ./usr/share/locale/pt/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 10564 2009-07-20 15:49 ./usr/share/locale/pt_BR/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 9953 2009-07-20 15:49 ./usr/share/locale/ro/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 13293 2009-07-20 15:49 ./usr/share/locale/ru/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/rw/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/rw/LC_MESSAGES/ -rw-r--r-- root/root 610 2009-07-20 15:49 ./usr/share/locale/rw/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sk/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sk/LC_MESSAGES/ -rw-r--r-- root/root 10129 2009-07-20 15:49 ./usr/share/locale/sk/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 12603 2009-07-20 15:49 ./usr/share/locale/sr/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sr@Latn/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sr@Latn/LC_MESSAGES/ -rw-r--r-- root/root 10134 2009-07-20 15:49 ./usr/share/locale/sr@Latn/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 10054 2009-07-20 15:49 ./usr/share/locale/sv/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 14186 2009-07-20 15:49 ./usr/share/locale/th/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/tr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/tr/LC_MESSAGES/ -rw-r--r-- root/root 369 2009-07-20 15:49 ./usr/share/locale/tr/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/uk/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/uk/LC_MESSAGES/ -rw-r--r-- root/root 12635 2009-07-20 15:49 ./usr/share/locale/uk/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/vi/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/vi/LC_MESSAGES/ -rw-r--r-- root/root 10392 2009-07-20 15:49 ./usr/share/locale/vi/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 8223 2009-07-20 15:49 ./usr/share/locale/zh_CN/LC_MESSAGES/muine.mo drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 925 2009-07-20 15:49 ./usr/share/icons/hicolor/16x16/apps/muine.png drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 1260 2009-07-20 15:49 ./usr/share/icons/hicolor/22x22/apps/muine.png drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 1317 2009-07-20 15:49 ./usr/share/icons/hicolor/24x24/apps/muine.png drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 1955 2009-07-20 15:49 ./usr/share/icons/hicolor/32x32/apps/muine.png drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 3423 2009-07-20 15:49 ./usr/share/icons/hicolor/48x48/apps/muine.png drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 31145 2009-07-20 15:49 ./usr/share/icons/hicolor/scalable/apps/muine.svg drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/doc/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/doc/muine/ -rw-r--r-- root/root 2178 2008-09-28 16:28 ./usr/share/doc/muine/README -rw-r--r-- root/root 879 2008-09-28 16:28 ./usr/share/doc/muine/PLUGINS -rw-r--r-- root/root 3375 2008-09-28 16:28 ./usr/share/doc/muine/TODO -rw-r--r-- root/root 2881 2009-07-20 15:48 ./usr/share/doc/muine/copyright -rw-r--r-- root/root 38159 2008-09-29 09:57 ./usr/share/doc/muine/changelog.gz -rw-r--r-- root/root 6330 2008-09-29 09:41 ./usr/share/doc/muine/NEWS.gz -rw-r--r-- root/root 6187 2009-07-20 15:48 ./usr/share/doc/muine/changelog.Debian.gz drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/man/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/man/man1/ -rw-r--r-- root/root 389 2009-07-20 15:49 ./usr/share/man/man1/muine.1.gz drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/menu/ -rw-r--r-- root/root 113 2009-07-20 15:48 ./usr/share/menu/muine drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/pixmaps/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/bin/ -rwxr-xr-x root/root 120 2009-07-20 15:49 ./usr/bin/muine lrwxrwxrwx root/root 0 2009-07-20 15:49 ./usr/lib/muine/libmuine.so -> libmuine.so.0.0.0 lrwxrwxrwx root/root 0 2009-07-20 15:49 ./usr/lib/muine/libmuine.so.0 -> libmuine.so.0.0.0 lrwxrwxrwx root/root 0 2009-07-20 15:49 ./usr/share/pixmaps/muine.svg -> ../icons/hicolor/scalable/apps/muine.svg chroot-autobuild/build/buildd/muine-plugin-inotify_0.8.10-5_lpia.deb: drwxr-xr-x root/root 0 2009-07-20 15:49 ./ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/muine/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/lib/muine/plugins/ -rw-r--r-- root/root 15872 2009-07-20 15:49 ./usr/lib/muine/plugins/InotifyPlugin.dll -rw-r--r-- root/root 108 2009-07-20 15:49 ./usr/lib/muine/plugins/InotifyPlugin.dll.config -rw-r--r-- root/root 5508 2009-07-20 15:49 ./usr/lib/muine/libinotifyglue.so.0.0.0 drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/doc/ drwxr-xr-x root/root 0 2009-07-20 15:49 ./usr/share/doc/muine-plugin-inotify/ -rw-r--r-- root/root 2881 2009-07-20 15:48 ./usr/share/doc/muine-plugin-inotify/copyright -rw-r--r-- root/root 38159 2008-09-29 09:57 ./usr/share/doc/muine-plugin-inotify/changelog.gz -rw-r--r-- root/root 6187 2009-07-20 15:48 ./usr/share/doc/muine-plugin-inotify/changelog.Debian.gz lrwxrwxrwx root/root 0 2009-07-20 15:49 ./usr/lib/muine/libinotifyglue.so -> libinotifyglue.so.0.0.0 lrwxrwxrwx root/root 0 2009-07-20 15:49 ./usr/lib/muine/libinotifyglue.so.0 -> libinotifyglue.so.0.0.0 muine_0.8.10-5_lpia.changes: Format: 1.8 Date: Sat, 11 Jul 2009 15:28:16 +0100 Source: muine Binary: muine muine-plugin-trayicon muine-plugin-inotify Architecture: lpia_translations lpia Version: 0.8.10-5 Distribution: karmic Urgency: low Maintainer: Ubuntu/lpia Build Daemon Changed-By: Iain Lane Description: muine - Simple playlist based music player muine-plugin-inotify - INotify Plugin for the Muine music player muine-plugin-trayicon - TrayIcon Plugin for the Muine music player Closes: 533941 Changes: muine (0.8.10-5) unstable; urgency=low . [ Iain Lane ] * debian/rules: Fix typo MAkefile -> Makefile. * debian/patches/gtk_sharp_api: Upstream has altered the signature of EmitRowsRecorded in the TreeModel interface. Update HandleModel.cs to be compatible. (Closes: #533941) . [ Tim Retout ] * Remove self from Uploaders. Checksums-Sha1: 69af69c8e2bee549f423ed97329b392abf22979d 112553 muine_0.8.10-5_lpia_translations.tar.gz b11f089a3e831e6ac1a9791eff2a61f06884bdb3 348038 muine_0.8.10-5_lpia.deb 16543ce9eca05182b04dd47c1ab359c2995ba177 58552 muine-plugin-inotify_0.8.10-5_lpia.deb Checksums-Sha256: 040ea55558b3365e1c32c9c02b70ad2243aff1193b661f14f0dc04fc3b08b85b 112553 muine_0.8.10-5_lpia_translations.tar.gz 7661220bda3fc1b08635925636d47e3e250bac340b060109e5cad371323b41e2 348038 muine_0.8.10-5_lpia.deb 5ddb723742849f1b0f83bb17023e82098eddacda976dc20b7d3c7993883bc2f9 58552 muine-plugin-inotify_0.8.10-5_lpia.deb Files: 5052eb42e42a6888aab016b406322d2e 112553 raw-translations - muine_0.8.10-5_lpia_translations.tar.gz 77836e2db73c7ae196244e8b88defc5e 348038 gnome optional muine_0.8.10-5_lpia.deb b21328f43cb8920a2101d34c9aaad12f 58552 gnome optional muine-plugin-inotify_0.8.10-5_lpia.deb ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/muine-0.8.10 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --root=/home/buildd/build-1125662-2429975/chroot-autobuild --purge groff-base libavahi-common3 libx11-data libgnome2-0 esound-common m4 mono-devel libshout3 x11-common libidl-dev libvorbis0a libmusicbrainz4-dev libvorbisenc2 libxi6 policykit-1-gnome automake libmono2.0-cil libmono-cecil-private-cil libiec61883-0 libmono0 libxcursor1 libgstreamer0.10-0 libavahi-glib-dev x11proto-input-dev libldap-2.4-2 libexpat1-dev libraw1394-8 libgnome2.24-cil libjpeg62-dev libpolkit-backend-1-0 libdbus-glib-1-2 libmono-sharpzip2.84-cil libgstreamer-plugins-base0.10-0 libsysfs-dev libx11-6 xtrans-dev cli-common-dev libgif4 libsasl2-2 libmono-corlib1.0-cil libhal1 libxdamage1 libaudiofile0 libtasn1-3 libtag1-vanilla libmono-system-runtime1.0-cil libdbus-1-dev libmono-posix2.0-cil libhtml-tree-perl libglib2.0-dev libdevmapper1.02.1 libxcb-render-util0 x11proto-xext-dev pkg-config libmono-relaxng1.0-cil libxrender1 libfontconfig1-dev libtasn1-3-dev libglib2.0-cil libxrandr-dev libcups2 libxau-dev libdatrie1 check libmono-system2.0-cil ttf-dejavu-extra libpng12-dev libxft2 libreadline5 consolekit libxext6 libsysfs2 libpolkit-gobject-1-0 libasound2 libsqlite3-0 libnotify1 libxml-perl libbonobo2-0 libesd0-dev libncursesw5 libgsf-1-common libgudev-1.0-0 defoma libcairo2-dev libgail18 libexif12 fontconfig liburi-perl libmono-sharpzip0.84-cil mono-gac libavahi-common-dev libcroco3 libgamin0 libgnomeui-0 libfreetype6 libmono-security2.0-cil libgtk2.0-cil libatk1.0-0 libglade2.0-cil x11proto-damage-dev libidl0 libxcb1 libflac8 libgtk2.0-bin policykit-1 libxv1 html2text libgcrypt11 libgsf-1-114 libxrandr2 debhelper libthai0 python devicekit-disks libart2.0-cil libgnome-keyring0 libmagic1 libgnutls-dev mono-runtime libtiff4 libexpat1 libxau6 libpango1.0-dev mono-gmcs libxcomposite1 x11proto-composite-dev adduser libgconf2-4 mono-2.0-gac mime-support libmono-dev libgconf2.0-cil libts-0.0-0 libxi-dev gamin libwww-perl libpolkit-agent-1-0 shared-mime-info libxfixes3 libgtk2.0-dev libmono-system-data1.0-cil libavahi-glib1 libdirectfb-1.2-0 netbase libpython2.6 x11proto-kb-dev libid3tag0-dev gnome-icon-theme x11proto-xinerama-dev libgdbm-dev libpthread-stubs0-dev libpango1.0-0 libudev0 libatasmart0 libgnomeui-common liboil0.3 gettext-base gstreamer0.10-plugins-base libmono-security1.0-cil libgnome2-dev libmono-corlib2.0-cil libgnomevfs2-0 libxcb-render0 libsgutils2-2 libxfixes-dev fontconfig-config libgconf2-dev file gettext libmono-sqlite2.0-cil zlib1g-dev libhtml-parser-perl libvorbis-dev libselinux1-dev libmono-peapi2.0-cil ttf-dejavu libbonobo2-dev libcairo2 libgdiplus gvfs python2.6 libx11-dev libspeex1 libjpeg62 libbonobo2-common libbonoboui2-common libnotify-dev libxml-dom-perl libv4l-0 cli-common libparted1.8-12 libjasper1 libmono-system-web1.0-cil libpixman-1-dev libxcomposite-dev libaa1 libfontconfig1 libgdu0 libgnutls26 libart-2.0-2 libsasl2-modules libxml-regexp-perl libgstreamer0.10-dev libtheora0 x11proto-randr-dev psmisc libhal-storage1 libglib2.0-0 libvisual-0.4-0 libnewt0.52 libxinerama-dev libpango1.0-common libxml2-utils gconf2 libk5crypto3 libtag1c2a libgpg-error-dev tsconf libdirectfb-dev hicolor-icon-theme libhtml-tagset-perl libxml2 dbus gstreamer0.10-plugins-good libthai-data libice6 intltool-debian libavahi-client3 libmono-system-data2.0-cil liborbit2-dev libgail-common libxml2-dev libmono-cairo2.0-cil mono-2.0-devel libxext-dev libaudiofile-dev libdirectfb-extra libgnomevfs2-dev libgpg-error0 libmono-system-web2.0-cil libxcb-render-util0-dev libxrender-dev libogg-dev libck-connector0 libavahi-common-data libraw1394-11 libpopt-dev x11proto-render-dev libxinerama1 libgssapi-krb5-2 libkrb5-3 libdbus-glib-1-dev libxdamage-dev libsm-dev gconf2-common libxdmcp-dev libgnomevfs2-common ttf-dejavu-core readline-common libgnomecanvas2-0 librsvg2-2 libxcb-render0-dev libgcrypt11-dev libavahi-client-dev libmusicbrainz4c2a libndesk-dbus-glib1.0-cil autotools-dev libcdparanoia0 liborbit2 mono-utils libpopt0 libsepol1-dev libice-dev libssl0.9.8 libvorbisfile3 x11proto-fixes-dev libfreetype6-dev libgtk2.0-0 diffstat libmono-data-tds2.0-cil libglade2-0 libpthread-stubs0 libkeyutils1 libgnomecanvas2-common gnome-mime-data libmono-data-tds1.0-cil bsdmainutils libxcursor-dev libflac-dev librsvg2-common x11proto-core-dev whiptail intltool libid3tag0 libogg0 libxcb1-dev libcaca0 libgnome2-common libxdmcp6 libdv4 libwavpack1 po-debconf libatk1.0-dev quilt libxml-parser-perl libmono-system1.0-cil libxft-dev libgvfscommon0 libeggdbus-1-0 libkrb5support0 libpng12-0 man-db libsoup2.4-1 monodoc-base dbus-x11 libgpm2 libavc1394-0 libpixman-1-0 libbonoboui2-0 libndesk-dbus1.0-cil ucf libgtk2.0-common libgnome-vfs2.0-cil libsqlite0 libsm6 libesd-alsa0 libmono-getoptions2.0-cil autoconf (Reading database ... 26843 files and directories currently installed.) Removing libmusicbrainz4-dev ... Removing libgnome2.24-cil ... Removing libgnome2.24-cil from Mono Removing cli-common-dev ... Removing libgnomeui-0 ... Purging configuration files for libgnomeui-0 ... Removing libglade2.0-cil ... Removing debhelper ... Removing libart2.0-cil ... Removing libart2.0-cil from Mono Removing libgconf2.0-cil ... Removing libgconf2.0-cil from Mono Removing libid3tag0-dev ... Removing gnome-icon-theme ... Removing libgdbm-dev ... Removing libgnomeui-common ... Removing libgnome2-dev ... Removing libvorbis-dev ... Removing libbonobo2-dev ... Removing libnotify-dev ... Removing libxml-dom-perl ... Removing libxml-regexp-perl ... Removing libgstreamer0.10-dev ... Removing hicolor-icon-theme ... Removing gstreamer0.10-plugins-good ... Purging configuration files for gstreamer0.10-plugins-good ... Removing libgnomevfs2-dev ... Removing libpopt-dev ... Removing libdbus-glib-1-dev ... Removing libavahi-client-dev ... Removing libmusicbrainz4c2a ... Purging configuration files for libmusicbrainz4c2a ... Removing libndesk-dbus-glib1.0-cil ... Removing libndesk-dbus-glib1.0-cil from Mono Removing mono-utils ... Removing libvorbisfile3 ... Purging configuration files for libvorbisfile3 ... Removing libflac-dev ... Removing librsvg2-common ... Removing intltool ... Removing libid3tag0 ... Purging configuration files for libid3tag0 ... Removing libcaca0 ... Purging configuration files for libcaca0 ... Removing libdv4 ... Purging configuration files for libdv4 ... Removing libwavpack1 ... Purging configuration files for libwavpack1 ... Removing po-debconf ... Removing quilt ... Purging configuration files for quilt ... 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/id/man5' 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 libsoup2.4-1 ... Purging configuration files for libsoup2.4-1 ... Removing monodoc-base ... Removing libavc1394-0 ... Purging configuration files for libavc1394-0 ... Removing libbonoboui2-0 ... Purging configuration files for libbonoboui2-0 ... Removing libndesk-dbus1.0-cil ... Removing libndesk-dbus1.0-cil from Mono Removing libgnome-vfs2.0-cil ... Removing libgnome-vfs2.0-cil from Mono Removing groff-base ... Purging configuration files for groff-base ... Removing libgnome2-0 ... Purging configuration files for libgnome2-0 ... Removing mono-devel ... update-alternatives: removing manually selected alternative - switching resource-file-generator to auto mode Removing libshout3 ... Purging configuration files for libshout3 ... Removing automake ... Removing libmono-cecil-private-cil ... Removing libiec61883-0 ... Purging configuration files for libiec61883-0 ... Removing libavahi-glib-dev ... Removing libraw1394-8 ... Purging configuration files for libraw1394-8 ... Removing libmono-system-runtime1.0-cil ... Removing libmono-relaxng1.0-cil ... Removing check ... Removing libnotify1 ... Purging configuration files for libnotify1 ... Removing libxml-perl ... Removing libbonobo2-0 ... Purging configuration files for libbonobo2-0 ... Removing libesd0-dev ... Removing libmono-sharpzip0.84-cil ... Removing libavahi-common-dev ... Removing libgtk2.0-cil ... Removing libflac8 ... Purging configuration files for libflac8 ... Removing libgtk2.0-bin ... Removing html2text ... Purging configuration files for html2text ... Removing libgnutls-dev ... Removing libgtk2.0-dev ... Removing gstreamer0.10-plugins-base ... Removing libgnomevfs2-0 ... Purging configuration files for libgnomevfs2-0 ... Removing libgconf2-dev ... Removing libselinux1-dev ... Removing gvfs ... Removing libspeex1 ... Purging configuration files for libspeex1 ... Removing libbonobo2-common ... Purging configuration files for libbonobo2-common ... Removing libbonoboui2-common ... Removing libv4l-0 ... Purging configuration files for libv4l-0 ... Removing cli-common ... Removing libmono-system-web1.0-cil ... Removing libxcomposite-dev ... Removing libaa1 ... Purging configuration files for libaa1 ... Removing libgdu0 ... Purging configuration files for libgdu0 ... Removing libtheora0 ... Purging configuration files for libtheora0 ... Removing libhal-storage1 ... Purging configuration files for libhal-storage1 ... Removing libvisual-0.4-0 ... Purging configuration files for libvisual-0.4-0 ... Removing libxinerama-dev ... Removing libxml2-utils ... Removing libtag1c2a ... Removing intltool-debian ... 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 libmono-cairo2.0-cil ... Removing mono-2.0-devel ... Purging configuration files for mono-2.0-devel ... Removing libaudiofile-dev ... Removing libogg-dev ... Removing libraw1394-11 ... Purging configuration files for libraw1394-11 ... Removing libxdamage-dev ... Removing libgnomevfs2-common ... Purging configuration files for libgnomevfs2-common ... Removing libgnomecanvas2-0 ... Purging configuration files for libgnomecanvas2-0 ... Removing librsvg2-2 ... Purging configuration files for librsvg2-2 ... Removing libgcrypt11-dev ... Removing autotools-dev ... Removing libcdparanoia0 ... Purging configuration files for libcdparanoia0 ... Removing libsepol1-dev ... Removing diffstat ... Removing libglade2-0 ... Purging configuration files for libglade2-0 ... Removing libgnomecanvas2-common ... Removing gnome-mime-data ... Purging configuration files for gnome-mime-data ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libxcursor-dev ... Removing libgnome2-common ... Purging configuration files for libgnome2-common ... Removing libatk1.0-dev ... Removing libxml-parser-perl ... Removing libgvfscommon0 ... Purging configuration files for libgvfscommon0 ... Removing libgpm2 ... Purging configuration files for libgpm2 ... Removing libesd-alsa0 ... Purging configuration files for libesd-alsa0 ... Removing libmono-getoptions2.0-cil ... Removing autoconf ... Purging configuration files for autoconf ... Removing esound-common ... Purging configuration files for esound-common ... Removing m4 ... Removing libidl-dev ... Removing libvorbisenc2 ... Purging configuration files for libvorbisenc2 ... Removing policykit-1-gnome ... Removing libgstreamer-plugins-base0.10-0 ... Purging configuration files for libgstreamer-plugins-base0.10-0 ... Removing libhal1 ... Purging configuration files for libhal1 ... Removing libaudiofile0 ... Purging configuration files for libaudiofile0 ... Removing libtag1-vanilla ... Purging configuration files for libtag1-vanilla ... Removing libdbus-1-dev ... Removing libtasn1-3-dev ... Removing libglib2.0-cil ... Removing libxrandr-dev ... Removing libasound2 ... Purging configuration files for libasound2 ... Removing x11proto-damage-dev ... Removing policykit-1 ... Purging configuration files for policykit-1 ... Removing libxv1 ... Purging configuration files for libxv1 ... Removing libgsf-1-114 ... Purging configuration files for libgsf-1-114 ... Removing devicekit-disks ... Purging configuration files for devicekit-disks ... Removing libgnome-keyring0 ... Purging configuration files for libgnome-keyring0 ... Removing libpango1.0-dev ... Removing mono-gmcs ... Removing x11proto-composite-dev ... Removing libmono-dev ... Removing libxi-dev ... Removing libwww-perl ... Removing libpolkit-agent-1-0 ... Purging configuration files for libpolkit-agent-1-0 ... Removing libmono-system-data1.0-cil ... Removing libavahi-glib1 ... Purging configuration files for libavahi-glib1 ... Removing netbase ... Purging configuration files for netbase ... Removing libpython2.6 ... Purging configuration files for libpython2.6 ... Removing x11proto-xinerama-dev ... Removing libatasmart0 ... Purging configuration files for libatasmart0 ... Removing liboil0.3 ... Purging configuration files for liboil0.3 ... Removing libsgutils2-2 ... Purging configuration files for libsgutils2-2 ... Removing libxfixes-dev ... Removing gettext ... Removing libmono-peapi2.0-cil ... Removing libparted1.8-12 ... Purging configuration files for libparted1.8-12 ... Removing libart-2.0-2 ... Purging configuration files for libart-2.0-2 ... Removing x11proto-randr-dev ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libgpg-error-dev ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libgail-common ... Removing x11proto-fixes-dev ... Removing libmono-data-tds1.0-cil ... Removing libxft-dev ... Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing libvorbis0a ... Purging configuration files for libvorbis0a ... Removing libgstreamer0.10-0 ... Purging configuration files for libgstreamer0.10-0 ... Removing libpolkit-backend-1-0 ... Purging configuration files for libpolkit-backend-1-0 ... Removing libhtml-tree-perl ... Removing libglib2.0-dev ... Removing libdevmapper1.02.1 ... Purging configuration files for libdevmapper1.02.1 ... Removing consolekit ... Purging configuration files for consolekit ... Removing libpolkit-gobject-1-0 ... Purging configuration files for libpolkit-gobject-1-0 ... Removing libgsf-1-common ... Removing libgudev-1.0-0 ... Purging configuration files for libgudev-1.0-0 ... Removing libcairo2-dev ... Removing libgail18 ... Purging configuration files for libgail18 ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing python ... Purging configuration files for python ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing libudev0 ... Purging configuration files for libudev0 ... Removing gettext-base ... Removing libmono-security1.0-cil ... Removing libhtml-parser-perl ... 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 psmisc ... Purging configuration files for psmisc ... Removing libdirectfb-dev ... Removing libhtml-tagset-perl ... Removing libxext-dev ... Removing libdirectfb-extra ... Removing libxcb-render-util0-dev ... Removing libxrender-dev ... Removing libck-connector0 ... Purging configuration files for libck-connector0 ... Removing libavahi-common-data ... Removing x11proto-render-dev ... Removing libsm-dev ... 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 libxcb-render0-dev ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing libice-dev ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... Removing libogg0 ... Purging configuration files for libogg0 ... Removing libmono-system1.0-cil ... Removing libeggdbus-1-0 ... Purging configuration files for libeggdbus-1-0 ... Removing libgtk2.0-common ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing libldap-2.4-2 ... Purging configuration files for libldap-2.4-2 ... Removing libjpeg62-dev ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing libsysfs-dev ... Removing libmono-corlib1.0-cil ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing x11proto-xext-dev ... Removing libfontconfig1-dev ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libpng12-dev ... Removing libreadline5 ... Purging configuration files for libreadline5 ... Removing libncursesw5 ... Purging configuration files for libncursesw5 ... Removing liburi-perl ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing mime-support ... Purging configuration files for mime-support ... 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 libxfixes3 ... Purging configuration files for libxfixes3 ... Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libx11-dev ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing libgnutls26 ... Purging configuration files for libgnutls26 ... Removing libpango1.0-common ... Purging font configuration of pango... Purging category xfont.. Purging configuration files for libpango1.0-common ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing dbus ... * Stopping system message bus dbus ...done. Purging configuration files for dbus ... rmdir: failed to remove `/var/run/dbus': Directory not empty dpkg - warning: while removing dbus, directory `/var/lib/dbus' not empty so not removed. Removing libice6 ... Purging configuration files for libice6 ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing libgssapi-krb5-2 ... Purging configuration files for libgssapi-krb5-2 ... Removing libkrb5-3 ... Purging configuration files for libkrb5-3 ... Removing readline-common ... Purging configuration files for readline-common ... Removing libfreetype6-dev ... Removing libxcb1-dev ... Removing x11proto-input-dev ... Removing libexpat1-dev ... Removing xtrans-dev ... Removing libtasn1-3 ... Purging configuration files for libtasn1-3 ... Removing pkg-config ... Removing libxau-dev ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing libxext6 ... Purging configuration files for libxext6 ... 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 libgcrypt11 ... Purging configuration files for libgcrypt11 ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing adduser ... Purging configuration files for adduser ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing zlib1g-dev ... Removing libk5crypto3 ... Purging configuration files for libk5crypto3 ... Removing libthai-data ... Removing libgpg-error0 ... Purging configuration files for libgpg-error0 ... Removing libxdmcp-dev ... Removing libpthread-stubs0 ... Removing x11proto-core-dev ... Removing libkrb5support0 ... Purging configuration files for libkrb5support0 ... Removing x11-common ... Purging configuration files for x11-common ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libkeyutils1 ... Purging configuration files for libkeyutils1 ... Removing libsasl2-2 ... Purging configuration files for libsasl2-2 ... Removing libgamin0 ... Purging configuration files for libgamin0 ... Removing gamin ... Purging configuration files for gamin ... Removing libsasl2-modules ... Removing libmono-system-web2.0-cil ... Removing libssl0.9.8 ... Purging configuration files for libssl0.9.8 ... Removing libmono2.0-cil ... Removing libmono-sharpzip2.84-cil ... Removing libmono-posix2.0-cil ... Removing libmono-sqlite2.0-cil ... Removing libgdiplus ... Removing libmono-system-data2.0-cil ... Removing libmono-data-tds2.0-cil ... Removing libsqlite0 ... Purging configuration files for libsqlite0 ... Removing libgif4 ... Purging configuration files for libgif4 ... Removing libmono-system2.0-cil ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libexif12 ... Purging configuration files for libexif12 ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing libmono-corlib2.0-cil ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libjpeg62 ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libpng12-0 ... Purging configuration files for libpng12-0 ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing libxcb-render-util0 ... Purging configuration files for libxcb-render-util0 ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing mono-runtime ... Purging configuration files for mono-runtime ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libdirectfb-1.2-0 ... Purging configuration files for libdirectfb-1.2-0 ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing ttf-dejavu ... Removing ucf ... Purging configuration files for ucf ... Removing libmono0 ... Purging configuration files for libmono0 ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing ttf-dejavu-extra ... Purging configuration files for ttf-dejavu-extra ... Removing libsysfs2 ... Purging configuration files for libsysfs2 ... Removing mono-gac ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing mono-2.0-gac ... Removing libts-0.0-0 ... Purging configuration files for libts-0.0-0 ... Removing libglib2.0-0 ... Purging configuration files for libglib2.0-0 ... Removing tsconf ... Purging configuration files for tsconf ... Removing ttf-dejavu-core ... Purging configuration files for ttf-dejavu-core ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing libx11-data ... dpkg - warning: while removing libx11-data, directory `/usr/share/X11' not empty so not removed. Removing defoma ... Purging configuration files for defoma ... Removing libmono-security2.0-cil ... Removing file ... Purging configuration files for file ... Removing whiptail ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing libnewt0.52 ... Purging configuration files for libnewt0.52 ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Processing triggers for libc6 ... ldconfig deferred processing now taking place ****************************************************************************** Finished at 20090720-1549 Build needed 00:00:47, 12860k disk space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '1125662-2429975'] Scanning for processes to kill in build 1125662-2429975... Scanning for processes to kill in build /home/buildd/build-1125662-2429975/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '1125662-2429975'] Unmounting chroot for build 1125662-2429975... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '1125662-2429975'] Removing build 1125662-2429975