RUN: /bin/echo ['echo', 'Forking build subprocess...'] Forking build subprocess... RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', '67529e7885e182ae39e99b454fbb9ed8ab9539a0', '/home/buildd/filecache-default/25121a7572f17d65ba7d4c7db29be92bd6e19436'] Synching the system clock with the buildd NTP service... 8 Feb 02:05:43 ntpdate[12439]: adjust time server 10.122.37.1 offset -0.000434 sec Unpacking chroot for build 67529e7885e182ae39e99b454fbb9ed8ab9539a0 RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', '67529e7885e182ae39e99b454fbb9ed8ab9539a0'] Mounting chroot for build 67529e7885e182ae39e99b454fbb9ed8ab9539a0 RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', '67529e7885e182ae39e99b454fbb9ed8ab9539a0', 'deb http://ftpmaster.internal/ubuntu natty main universe'] Overriding sources.list in build-67529e7885e182ae39e99b454fbb9ed8ab9539a0 RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', '67529e7885e182ae39e99b454fbb9ed8ab9539a0', 'i386'] Updating debian chroot for build 67529e7885e182ae39e99b454fbb9ed8ab9539a0 Get:1 http://ftpmaster.internal natty Release.gpg [198 B] Ign http://ftpmaster.internal/ubuntu/ natty/main Translation-en Ign http://ftpmaster.internal/ubuntu/ natty/universe Translation-en Get:2 http://ftpmaster.internal natty Release [39.8 kB] Get:3 http://ftpmaster.internal natty/main i386 Packages [1563 kB] Get:4 http://ftpmaster.internal natty/universe i386 Packages [6024 kB] Fetched 7627 kB in 6s (1216 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: busybox-initramfs libdb4.8 libgcrypt11 libglib2.0-0 libssl0.9.8 linux-libc-dev openssl upstart 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 4153 kB of archives. After this operation, 8192 B of additional disk space will be used. WARNING: The following packages cannot be authenticated! libdb4.8 libssl0.9.8 busybox-initramfs libglib2.0-0 upstart libgcrypt11 openssl linux-libc-dev Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ natty/main libdb4.8 i386 4.8.30-3ubuntu1 [657 kB] Get:2 http://ftpmaster.internal/ubuntu/ natty/main libssl0.9.8 i386 0.9.8o-4ubuntu2 [756 kB] Get:3 http://ftpmaster.internal/ubuntu/ natty/main busybox-initramfs i386 1:1.17.1-8ubuntu2 [148 kB] Get:4 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-0 i386 2.27.93-0ubuntu1 [986 kB] Get:5 http://ftpmaster.internal/ubuntu/ natty/main upstart i386 0.6.7-6 [188 kB] Get:6 http://ftpmaster.internal/ubuntu/ natty/main libgcrypt11 i386 1.4.6-4 [250 kB] Get:7 http://ftpmaster.internal/ubuntu/ natty/main openssl i386 0.9.8o-4ubuntu2 [398 kB] Get:8 http://ftpmaster.internal/ubuntu/ natty/main linux-libc-dev i386 2.6.38-2.29 [770 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 4153 kB in 0s (19.1 MB/s) (Reading database ... 13677 files and directories currently installed.) Preparing to replace libdb4.8 4.8.30-3 (using .../libdb4.8_4.8.30-3ubuntu1_i386.deb) ... Unpacking replacement libdb4.8 ... Setting up libdb4.8 (4.8.30-3ubuntu1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13677 files and directories currently installed.) Preparing to replace libssl0.9.8 0.9.8o-4ubuntu1 (using .../libssl0.9.8_0.9.8o-4ubuntu2_i386.deb) ... Unpacking replacement libssl0.9.8 ... Setting up libssl0.9.8 (0.9.8o-4ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place (Reading database ... 13677 files and directories currently installed.) Preparing to replace busybox-initramfs 1:1.17.1-8ubuntu1 (using .../busybox-initramfs_1%3a1.17.1-8ubuntu2_i386.deb) ... Unpacking replacement busybox-initramfs ... Preparing to replace libglib2.0-0 2.27.92-0ubuntu1 (using .../libglib2.0-0_2.27.93-0ubuntu1_i386.deb) ... Unpacking replacement libglib2.0-0 ... Preparing to replace upstart 0.6.7-5 (using .../upstart_0.6.7-6_i386.deb) ... Unpacking replacement upstart ... Preparing to replace libgcrypt11 1.4.5-2ubuntu2 (using .../libgcrypt11_1.4.6-4_i386.deb) ... Unpacking replacement libgcrypt11 ... Preparing to replace openssl 0.9.8o-4ubuntu1 (using .../openssl_0.9.8o-4ubuntu2_i386.deb) ... Unpacking replacement openssl ... Preparing to replace linux-libc-dev 2.6.38-1.28 (using .../linux-libc-dev_2.6.38-2.29_i386.deb) ... Unpacking replacement linux-libc-dev ... Setting up busybox-initramfs (1:1.17.1-8ubuntu2) ... Setting up libglib2.0-0 (2.27.93-0ubuntu1) ... Setting up upstart (0.6.7-6) ... Setting up libgcrypt11 (1.4.6-4) ... Setting up openssl (0.9.8o-4ubuntu2) ... Setting up linux-libc-dev (2.6.38-2.29) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', '67529e7885e182ae39e99b454fbb9ed8ab9539a0', 'i386', 'natty', '--nolog', '--batch', '--archive=ubuntu', '--dist=natty', '-A', '--purpose=PRIMARY', '--architecture=i386', '--comp=universe', 'gnome-color-manager_2.32.0-0ubuntu1.dsc'] Initiating build 67529e7885e182ae39e99b454fbb9ed8ab9539a0 with 2 processor cores. Automatic build of gnome-color-manager_2.32.0-0ubuntu1 on palmer by sbuild/i386 1.170.5 Build started at 20110208-0206 ****************************************************************************** gnome-color-manager_2.32.0-0ubuntu1.dsc exists in cwd sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 7.0.50~), dh-autoreconf, libgconf2-dev, gnome-pkg-tools, gnome-doc-utils, intltool, libgtk2.0-dev (>= 2.14.0), libglib2.0-dev (>= 2.14.0), libgnome-desktop-dev (>= 2.14.0), libvte-dev (>= 0.22.2), libgudev-1.0-dev, liblcms1-dev, libdbus-glib-1-dev (>= 0.73), gtk-doc-tools, libxxf86vm-dev, libxrandr-dev, libunique-dev (>= 1.0.0), scrollkeeper, docbook-utils, libcanberra-gtk-dev (>= 0.10), libtiff4-dev, libcups2-dev, libx11-dev, libnotify-dev, libsane-dev sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: gcc: not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) Checking for already installed source dependencies... debhelper: missing dh-autoreconf: missing libgconf2-dev: missing gnome-pkg-tools: missing gnome-doc-utils: missing intltool: missing libgtk2.0-dev: missing libglib2.0-dev: missing libgnome-desktop-dev: missing libvte-dev: missing libgudev-1.0-dev: missing liblcms1-dev: missing libdbus-glib-1-dev: missing gtk-doc-tools: missing libxxf86vm-dev: missing libxrandr-dev: missing libunique-dev: missing scrollkeeper: missing docbook-utils: missing libcanberra-gtk-dev: missing libtiff4-dev: missing libcups2-dev: missing libx11-dev: missing libnotify-dev: missing libsane-dev: missing Checking for source dependency conflicts... /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper dh-autoreconf libgconf2-dev gnome-pkg-tools gnome-doc-utils intltool libgtk2.0-dev libglib2.0-dev libgnome-desktop-dev libvte-dev libgudev-1.0-dev liblcms1-dev libdbus-glib-1-dev gtk-doc-tools libxxf86vm-dev libxrandr-dev libunique-dev scrollkeeper docbook-utils libcanberra-gtk-dev libtiff4-dev libcups2-dev libx11-dev libnotify-dev libsane-dev Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: autoconf automake autotools-dev bsdmainutils comerr-dev dbus dbus-x11 docbook docbook-dsssl docbook-to-man docbook-xml docbook-xsl ed file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base gir1.2-glib-2.0 gnome-common groff-base html2text intltool-debian jade jadetex krb5-multidev libasound2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client-dev libavahi-client3 libavahi-common-data libavahi-common-dev libavahi-common3 libbsd0 libcairo-gobject2 libcairo2 libcairo2-dev libcanberra-dev libcanberra-gtk-common-dev libcanberra-gtk0 libcanberra0 libcroco3 libcups2 libdatrie1 libdbus-1-dev libdbus-glib-1-2 libexif-dev libexif12 libexpat1 libexpat1-dev libffi5 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgcrypt11-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgirepository-1.0-1 libglib2.0-bin libglib2.0-data libgnome-desktop-2-17 libgnutls-dev libgpg-error-dev libgphoto2-2 libgphoto2-2-dev libgphoto2-port0 libgssrpc4 libgtk2.0-0 libgtk2.0-common libgudev-1.0-0 libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libieee1284-3 libieee1284-3-dev libjasper1 libjpeg62 libjpeg62-dev libkadm5clnt-mit7 libkadm5srv-mit7 libkdb5-4 libkpathsea5 libkrb5-dev liblcms1 libltdl7 libmagic1 libnotify1 libogg0 liborbit2 liborbit2-dev libosp5 libostyle1c2 libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpoppler12 libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librarian0 libsane libsgmls-perl libsm-dev libsm6 libsp1c2 libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libtasn1-3-dev libtdb1 libthai-data libthai0 libtiff4 libtiffxx0c2 libtool libudev-dev libunique-1.0-0 libunistring0 liburi-perl libusb-dev libv4l-0 libv4l-dev libvorbis0a libvorbisfile3 libvte-common libvte9 libwww-perl libx11-6 libx11-data libxau-dev libxau6 libxaw7 libxcb-atom1 libxcb-aux0 libxcb-event1 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-utils libxmu6 libxpm4 libxrandr2 libxrender-dev libxrender1 libxslt1.1 libxt6 libxxf86vm1 luatex lynx lynx-cur m4 man-db mime-support openjade pkg-config po-debconf psmisc python python-cairo python-gobject python-gtk2 python-libxml2 python-support python-vte python2.7 rarian-compat sgml-base sgml-data sgmlspl shared-mime-info sp tex-common texlive-base texlive-binaries texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base texlive-latex-recommended tipa ttf-dejavu-core ucf 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-xf86vidmode-dev x11proto-xinerama-dev xml-core xsltproc xtrans-dev zlib1g-dev Suggested packages: autoconf2.13 autoconf-archive gnu-standards autoconf-doc wamerican wordlist whois vacation doc-base dh-make psgml docbook-defguide docbook-dsssl-doc docbook-xsl-doc-html docbook-xsl-doc-pdf docbook-xsl-doc-text docbook-xsl-doc libsaxon-java libxalan2-java docbook-xsl-saxon fop xalan dbtoepub defoma gconf-defaults-service gettext-doc svn-buildpackage groff curl wget krb5-doc libasound2-plugins libcairo2-doc libcairo-script-interpreter2 libcanberra-pulse cups-common libgcrypt11-doc libglib2.0-doc python-subunit gnutls-doc gnutls-bin guile-gnutls gphoto2 gtkam krb5-user librsvg2-common gvfs libgtk2.0-doc libdata-dump-perl libjasper-runtime liblcms-utils 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 avahi-daemon hpoj hplip libsane-extras sane-utils libsane-extras-dev sgmls-doc libtool-doc automaken gfortran fortran95-compiler gcj libunique-doc libcrypt-ssleay-perl libio-socket-ssl-perl lynx-cur-wrapper less www-browser libmail-box-perl python-doc python-tk python-profiler python-gobject-dbg python-gtk2-doc python-numpy python2.7-doc python2.7-profiler sgml-base-doc perlsgml doc-html-w3 opensp perl-tk ghostscript xpdf-reader pdf-viewer gv postscript-viewer Recommended packages: consolekit autopoint libcanberra-gtk-module hwdata hicolor-icon-theme libgtk2.0-bin notification-daemon orbit2 x-ttcidfont-conf libltdl-dev libmailtools-perl libhtml-format-perl texlive-luatex libmail-sendmail-perl python-gobject-cairo lmodern texlive-fonts-recommended-doc texlive-latex-base-doc texlive-latex-recommended-doc prosper latex-beamer latex-xcolor The following NEW packages will be installed: autoconf automake autotools-dev bsdmainutils comerr-dev dbus dbus-x11 debhelper dh-autoreconf docbook docbook-dsssl docbook-to-man docbook-utils docbook-xml docbook-xsl ed file fontconfig fontconfig-config gconf2 gconf2-common gettext gettext-base gir1.2-glib-2.0 gnome-common gnome-doc-utils gnome-pkg-tools groff-base gtk-doc-tools html2text intltool intltool-debian jade jadetex krb5-multidev libasound2 libatk1.0-0 libatk1.0-data libatk1.0-dev libavahi-client-dev libavahi-client3 libavahi-common-data libavahi-common-dev libavahi-common3 libbsd0 libcairo-gobject2 libcairo2 libcairo2-dev libcanberra-dev libcanberra-gtk-common-dev libcanberra-gtk-dev libcanberra-gtk0 libcanberra0 libcroco3 libcups2 libcups2-dev libdatrie1 libdbus-1-dev libdbus-glib-1-2 libdbus-glib-1-dev libexif-dev libexif12 libexpat1 libexpat1-dev libffi5 libfontconfig1 libfontconfig1-dev libfreetype6 libfreetype6-dev libgconf2-4 libgconf2-dev libgcrypt11-dev libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-dev libgirepository-1.0-1 libglib2.0-bin libglib2.0-data libglib2.0-dev libgnome-desktop-2-17 libgnome-desktop-dev libgnutls-dev libgpg-error-dev libgphoto2-2 libgphoto2-2-dev libgphoto2-port0 libgssrpc4 libgtk2.0-0 libgtk2.0-common libgtk2.0-dev libgudev-1.0-0 libgudev-1.0-dev libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libice-dev libice6 libidl-dev libidl0 libieee1284-3 libieee1284-3-dev libjasper1 libjpeg62 libjpeg62-dev libkadm5clnt-mit7 libkadm5srv-mit7 libkdb5-4 libkpathsea5 libkrb5-dev liblcms1 liblcms1-dev libltdl7 libmagic1 libnotify-dev libnotify1 libogg0 liborbit2 liborbit2-dev libosp5 libostyle1c2 libpango1.0-0 libpango1.0-dev libpipeline1 libpixman-1-0 libpixman-1-dev libpng12-dev libpoppler12 libpopt0 libpthread-stubs0 libpthread-stubs0-dev libpython2.7 librarian0 libsane libsane-dev libsgmls-perl libsm-dev libsm6 libsp1c2 libsqlite3-0 libstartup-notification0 libstartup-notification0-dev libtasn1-3-dev libtdb1 libthai-data libthai0 libtiff4 libtiff4-dev libtiffxx0c2 libtool libudev-dev libunique-1.0-0 libunique-dev libunistring0 liburi-perl libusb-dev libv4l-0 libv4l-dev libvorbis0a libvorbisfile3 libvte-common libvte-dev libvte9 libwww-perl libx11-6 libx11-data libx11-dev libxau-dev libxau6 libxaw7 libxcb-atom1 libxcb-aux0 libxcb-event1 libxcb-render0 libxcb-render0-dev libxcb-shm0 libxcb-shm0-dev libxcb1 libxcb1-dev libxcomposite-dev libxcomposite1 libxcursor-dev libxcursor1 libxdamage-dev libxdamage1 libxdmcp-dev libxdmcp6 libxext-dev libxext6 libxfixes-dev libxfixes3 libxft-dev libxft2 libxi-dev libxi6 libxinerama-dev libxinerama1 libxml-parser-perl libxml2 libxml2-utils libxmu6 libxpm4 libxrandr-dev libxrandr2 libxrender-dev libxrender1 libxslt1.1 libxt6 libxxf86vm-dev libxxf86vm1 luatex lynx lynx-cur m4 man-db mime-support openjade pkg-config po-debconf psmisc python python-cairo python-gobject python-gtk2 python-libxml2 python-support python-vte python2.7 rarian-compat scrollkeeper sgml-base sgml-data sgmlspl shared-mime-info sp tex-common texlive-base texlive-binaries texlive-common texlive-doc-base texlive-fonts-recommended texlive-latex-base texlive-latex-recommended tipa ttf-dejavu-core ucf 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-xf86vidmode-dev x11proto-xinerama-dev xml-core xsltproc xtrans-dev zlib1g-dev 0 upgraded, 260 newly installed, 0 to remove and 0 not upgraded. Need to get 120 MB of archives. After this operation, 374 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! sgml-base xml-core sgml-data docbook-xml x11-common libice6 x11proto-core-dev libice-dev libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxau-dev libxdmcp-dev x11proto-input-dev x11proto-kb-dev xtrans-dev libpthread-stubs0 libpthread-stubs0-dev libxcb1-dev libx11-dev libmagic1 file libexpat1 libpopt0 libsqlite3-0 mime-support python2.7 python ucf bsdmainutils ed ttf-dejavu-core fontconfig-config gettext-base libffi5 libgirepository-1.0-1 gir1.2-glib-2.0 groff-base libbsd0 libfreetype6 libfontconfig1 libpixman-1-0 libxcb-render0 libxcb-shm0 libxrender1 libcairo2 libdbus-glib-1-2 liburi-perl libhtml-tagset-perl libhtml-parser-perl libhtml-tree-perl libpipeline1 libwww-perl libxext6 libxml-parser-perl libxml2 man-db psmisc python-support python-cairo libpython2.7 python-gobject m4 autoconf autotools-dev automake dbus dbus-x11 html2text libcroco3 libunistring0 gettext intltool-debian po-debconf debhelper libtool dh-autoreconf docbook libosp5 libostyle1c2 openjade libsp1c2 jade docbook-dsssl sp docbook-to-man tex-common texlive-common texlive-doc-base libjpeg62 liblcms1 libpoppler12 luatex libkpathsea5 libsm6 libxt6 libxmu6 libxpm4 libxaw7 texlive-binaries texlive-base texlive-latex-base texlive-fonts-recommended texlive-latex-recommended tipa jadetex lynx-cur lynx libsgmls-perl sgmlspl docbook-utils docbook-xsl fontconfig libidl0 liborbit2 gconf2-common libgconf2-4 gconf2 pkg-config intltool gnome-common python-libxml2 libxml2-utils libxslt1.1 xsltproc gnome-doc-utils gnome-pkg-tools gtk-doc-tools libgssrpc4 libkdb5-4 libkadm5srv-mit7 libkadm5clnt-mit7 comerr-dev krb5-multidev libasound2 libatk1.0-data libatk1.0-0 libglib2.0-data libglib2.0-bin zlib1g-dev libglib2.0-dev libatk1.0-dev libavahi-common-data libavahi-common3 libavahi-client3 libavahi-common-dev libdbus-1-dev libavahi-client-dev libcairo-gobject2 libexpat1-dev libfreetype6-dev libfontconfig1-dev x11proto-render-dev libxrender-dev libpng12-dev libsm-dev libpixman-1-dev libxcb-render0-dev libxcb-shm0-dev libcairo2-dev libltdl7 libtdb1 libogg0 libvorbis0a libvorbisfile3 libcanberra0 libcanberra-dev libcanberra-gtk-common-dev libgtk2.0-common libcups2 libjasper1 libtiff4 libgdk-pixbuf2.0-0 libdatrie1 libthai-data libthai0 libxft2 libpango1.0-0 libxcomposite1 libxfixes3 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 shared-mime-info libgtk2.0-0 libcanberra-gtk0 libgdk-pixbuf2.0-dev libxft-dev libpango1.0-dev x11proto-xext-dev libxext-dev x11proto-xinerama-dev libxinerama-dev libxi-dev x11proto-randr-dev libxrandr-dev x11proto-fixes-dev libxfixes-dev libxcursor-dev x11proto-composite-dev libxcomposite-dev x11proto-damage-dev libxdamage-dev libgtk2.0-dev libcanberra-gtk-dev libgpg-error-dev libgcrypt11-dev libtasn1-3-dev libgnutls-dev libkrb5-dev libcups2-dev libdbus-glib-1-dev libexif12 libexif-dev libidl-dev liborbit2-dev libgconf2-dev libxcb-atom1 libxcb-aux0 libxcb-event1 libstartup-notification0 libgnome-desktop-2-17 libstartup-notification0-dev libgnome-desktop-dev libgphoto2-port0 libgphoto2-2 libusb-dev libgphoto2-2-dev libgudev-1.0-0 libudev-dev libgudev-1.0-dev libieee1284-3 libieee1284-3-dev libjpeg62-dev liblcms1-dev libnotify1 libnotify-dev libv4l-0 libsane libtiffxx0c2 libtiff4-dev libv4l-dev libsane-dev libunique-1.0-0 libunique-dev libvte-common libvte9 python-gtk2 python-vte libvte-dev libxxf86vm1 x11proto-xf86vidmode-dev libxxf86vm-dev librarian0 rarian-compat scrollkeeper Authentication warning overridden. Get:1 http://ftpmaster.internal/ubuntu/ natty/main sgml-base all 1.26+nmu1ubuntu1 [8360 B] Get:2 http://ftpmaster.internal/ubuntu/ natty/main xml-core all 0.13 [23.4 kB] Get:3 http://ftpmaster.internal/ubuntu/ natty/main sgml-data all 2.0.5 [275 kB] Get:4 http://ftpmaster.internal/ubuntu/ natty/main docbook-xml all 4.5-7 [345 kB] Get:5 http://ftpmaster.internal/ubuntu/ natty/main x11-common all 1:7.6~3ubuntu3 [66.8 kB] Get:6 http://ftpmaster.internal/ubuntu/ natty/main libice6 i386 2:1.0.7-1 [42.1 kB] Get:7 http://ftpmaster.internal/ubuntu/ natty/main x11proto-core-dev all 7.0.20-1 [294 kB] Get:8 http://ftpmaster.internal/ubuntu/ natty/main libice-dev i386 2:1.0.7-1 [127 kB] Get:9 http://ftpmaster.internal/ubuntu/ natty/main libxau6 i386 1:1.0.6-1 [16.2 kB] Get:10 http://ftpmaster.internal/ubuntu/ natty/main libxdmcp6 i386 1:1.1.0-1 [9582 B] Get:11 http://ftpmaster.internal/ubuntu/ natty/main libxcb1 i386 1.6-1 [40.2 kB] Get:12 http://ftpmaster.internal/ubuntu/ natty/main libx11-data all 2:1.3.3-3ubuntu3 [204 kB] Get:13 http://ftpmaster.internal/ubuntu/ natty/main libx11-6 i386 2:1.3.3-3ubuntu3 [729 kB] Get:14 http://ftpmaster.internal/ubuntu/ natty/main libxau-dev i386 1:1.0.6-1 [19.5 kB] Get:15 http://ftpmaster.internal/ubuntu/ natty/main libxdmcp-dev i386 1:1.1.0-1 [43.9 kB] Get:16 http://ftpmaster.internal/ubuntu/ natty/main x11proto-input-dev all 2.0.1-1 [62.5 kB] Get:17 http://ftpmaster.internal/ubuntu/ natty/main x11proto-kb-dev all 1.0.5-1 [25.4 kB] Get:18 http://ftpmaster.internal/ubuntu/ natty/main xtrans-dev all 1.2.6-1 [80.8 kB] Get:19 http://ftpmaster.internal/ubuntu/ natty/main libpthread-stubs0 i386 0.3-2 [3196 B] Get:20 http://ftpmaster.internal/ubuntu/ natty/main libpthread-stubs0-dev i386 0.3-2 [2414 B] Get:21 http://ftpmaster.internal/ubuntu/ natty/main libxcb1-dev i386 1.6-1 [74.7 kB] Get:22 http://ftpmaster.internal/ubuntu/ natty/main libx11-dev i386 2:1.3.3-3ubuntu3 [3374 kB] Get:23 http://ftpmaster.internal/ubuntu/ natty/main libmagic1 i386 5.04-5ubuntu2 [204 kB] Get:24 http://ftpmaster.internal/ubuntu/ natty/main file i386 5.04-5ubuntu2 [22.1 kB] Get:25 http://ftpmaster.internal/ubuntu/ natty/main libexpat1 i386 2.0.1-7ubuntu1 [139 kB] Get:26 http://ftpmaster.internal/ubuntu/ natty/main libpopt0 i386 1.16-1 [33.9 kB] Get:27 http://ftpmaster.internal/ubuntu/ natty/main libsqlite3-0 i386 3.7.4-2ubuntu2 [308 kB] Get:28 http://ftpmaster.internal/ubuntu/ natty/main mime-support all 3.51-1ubuntu1 [30.7 kB] Get:29 http://ftpmaster.internal/ubuntu/ natty/main python2.7 i386 2.7.1-3 [2497 kB] Get:30 http://ftpmaster.internal/ubuntu/ natty/main python all 2.7.1-0ubuntu5 [163 kB] Get:31 http://ftpmaster.internal/ubuntu/ natty/main ucf all 3.0025+nmu1 [69.1 kB] Get:32 http://ftpmaster.internal/ubuntu/ natty/main bsdmainutils i386 8.2.2 [191 kB] Get:33 http://ftpmaster.internal/ubuntu/ natty/main ed i386 1.5-1 [56.3 kB] Get:34 http://ftpmaster.internal/ubuntu/ natty/main ttf-dejavu-core all 2.31-1 [1450 kB] Get:35 http://ftpmaster.internal/ubuntu/ natty/main fontconfig-config all 2.8.0-2.1ubuntu1 [44.4 kB] Get:36 http://ftpmaster.internal/ubuntu/ natty/main gettext-base i386 0.18.1.1-3ubuntu1 [56.6 kB] Get:37 http://ftpmaster.internal/ubuntu/ natty/main libffi5 i386 3.0.9-3 [15.7 kB] Get:38 http://ftpmaster.internal/ubuntu/ natty/main libgirepository-1.0-1 i386 0.10.1+git20110201-0ubuntu1 [90.2 kB] Get:39 http://ftpmaster.internal/ubuntu/ natty/main gir1.2-glib-2.0 i386 0.10.1+git20110201-0ubuntu1 [126 kB] Get:40 http://ftpmaster.internal/ubuntu/ natty/main groff-base i386 1.21-3 [1021 kB] Get:41 http://ftpmaster.internal/ubuntu/ natty/main libbsd0 i386 0.2.0-1 [41.8 kB] Get:42 http://ftpmaster.internal/ubuntu/ natty/main libfreetype6 i386 2.4.2-2.1 [284 kB] Get:43 http://ftpmaster.internal/ubuntu/ natty/main libfontconfig1 i386 2.8.0-2.1ubuntu1 [97.7 kB] Get:44 http://ftpmaster.internal/ubuntu/ natty/main libpixman-1-0 i386 0.18.4-1build1 [163 kB] Get:45 http://ftpmaster.internal/ubuntu/ natty/main libxcb-render0 i386 1.6-1 [14.8 kB] Get:46 http://ftpmaster.internal/ubuntu/ natty/main libxcb-shm0 i386 1.6-1 [9092 B] Get:47 http://ftpmaster.internal/ubuntu/ natty/main libxrender1 i386 1:0.9.6-1 [29.2 kB] Get:48 http://ftpmaster.internal/ubuntu/ natty/main libcairo2 i386 1.10.2-1ubuntu1 [453 kB] Get:49 http://ftpmaster.internal/ubuntu/ natty/main libdbus-glib-1-2 i386 0.88-2.1 [62.1 kB] Get:50 http://ftpmaster.internal/ubuntu/ natty/main liburi-perl all 1.56-1 [90.6 kB] Get:51 http://ftpmaster.internal/ubuntu/ natty/main libhtml-tagset-perl all 3.20-2 [13.5 kB] Get:52 http://ftpmaster.internal/ubuntu/ natty/main libhtml-parser-perl i386 3.68-1 [100 kB] Get:53 http://ftpmaster.internal/ubuntu/ natty/main libhtml-tree-perl all 4.1-1 [206 kB] Get:54 http://ftpmaster.internal/ubuntu/ natty/main libpipeline1 i386 1.1.0-1 [23.1 kB] Get:55 http://ftpmaster.internal/ubuntu/ natty/main libwww-perl all 5.837-1 [363 kB] Get:56 http://ftpmaster.internal/ubuntu/ natty/main libxext6 i386 2:1.1.2-1 [41.7 kB] Get:57 http://ftpmaster.internal/ubuntu/ natty/main libxml-parser-perl i386 2.36-1.1build3 [323 kB] Get:58 http://ftpmaster.internal/ubuntu/ natty/main libxml2 i386 2.7.8.dfsg-2 [607 kB] Get:59 http://ftpmaster.internal/ubuntu/ natty/main man-db i386 2.5.9-3 [676 kB] Get:60 http://ftpmaster.internal/ubuntu/ natty/main psmisc i386 22.13-1 [49.0 kB] Get:61 http://ftpmaster.internal/ubuntu/ natty/main python-support all 1.0.10ubuntu3 [25.9 kB] Get:62 http://ftpmaster.internal/ubuntu/ natty/main python-cairo i386 1.8.8-1ubuntu1 [69.0 kB] Get:63 http://ftpmaster.internal/ubuntu/ natty/main libpython2.7 i386 2.7.1-3 [1076 kB] Get:64 http://ftpmaster.internal/ubuntu/ natty/main python-gobject i386 2.27.0+git20110131-0ubuntu6 [454 kB] Get:65 http://ftpmaster.internal/ubuntu/ natty/main m4 i386 1.4.14-3 [276 kB] Get:66 http://ftpmaster.internal/ubuntu/ natty/main autoconf all 2.67-2ubuntu1 [569 kB] Get:67 http://ftpmaster.internal/ubuntu/ natty/main autotools-dev all 20100122.1 [70.7 kB] Get:68 http://ftpmaster.internal/ubuntu/ natty/main automake all 1:1.11.1-1ubuntu1 [544 kB] Get:69 http://ftpmaster.internal/ubuntu/ natty/main dbus i386 1.4.1-0ubuntu2 [196 kB] Get:70 http://ftpmaster.internal/ubuntu/ natty/main dbus-x11 i386 1.4.1-0ubuntu2 [28.4 kB] Get:71 http://ftpmaster.internal/ubuntu/ natty/main html2text i386 1.3.2a-15 [101 kB] Get:72 http://ftpmaster.internal/ubuntu/ natty/main libcroco3 i386 0.6.2-1 [92.5 kB] Get:73 http://ftpmaster.internal/ubuntu/ natty/main libunistring0 i386 0.9.3-3 [423 kB] Get:74 http://ftpmaster.internal/ubuntu/ natty/main gettext i386 0.18.1.1-3ubuntu1 [1180 kB] Get:75 http://ftpmaster.internal/ubuntu/ natty/main intltool-debian all 0.35.0+20060710.1 [31.6 kB] Get:76 http://ftpmaster.internal/ubuntu/ natty/main po-debconf all 1.0.16+nmu1 [212 kB] Get:77 http://ftpmaster.internal/ubuntu/ natty/main debhelper all 8.0.0ubuntu2 [384 kB] Get:78 http://ftpmaster.internal/ubuntu/ natty/main libtool i386 2.2.6b-2ubuntu1 [524 kB] Get:79 http://ftpmaster.internal/ubuntu/ natty/main dh-autoreconf all 2 [11.5 kB] Get:80 http://ftpmaster.internal/ubuntu/ natty/main docbook all 4.5-4 [450 kB] Get:81 http://ftpmaster.internal/ubuntu/ natty/main libosp5 i386 1.5.2-8 [1077 kB] Get:82 http://ftpmaster.internal/ubuntu/ natty/main libostyle1c2 i386 1.4devel1-19build1 [851 kB] Get:83 http://ftpmaster.internal/ubuntu/ natty/main openjade i386 1.4devel1-19build1 [332 kB] Get:84 http://ftpmaster.internal/ubuntu/ natty/main libsp1c2 i386 1.3.4-1.2.1-47build3 [1491 kB] Get:85 http://ftpmaster.internal/ubuntu/ natty/main jade i386 1.2.1-47build3 [305 kB] Get:86 http://ftpmaster.internal/ubuntu/ natty/main docbook-dsssl all 1.79-6 [344 kB] Get:87 http://ftpmaster.internal/ubuntu/ natty/main sp i386 1.3.4-1.2.1-47build3 [173 kB] Get:88 http://ftpmaster.internal/ubuntu/ natty/main docbook-to-man i386 1:2.0.0-28 [72.4 kB] Get:89 http://ftpmaster.internal/ubuntu/ natty/main tex-common all 2.08 [725 kB] Get:90 http://ftpmaster.internal/ubuntu/ natty/main texlive-common all 2009-11 [101 kB] Get:91 http://ftpmaster.internal/ubuntu/ natty/main texlive-doc-base all 2009-2 [1339 kB] Get:92 http://ftpmaster.internal/ubuntu/ natty/main libjpeg62 i386 6b1-1 [86.1 kB] Get:93 http://ftpmaster.internal/ubuntu/ natty/main liblcms1 i386 1.18.dfsg-1.2ubuntu1 [95.9 kB] Get:94 http://ftpmaster.internal/ubuntu/ natty/main libpoppler12 i386 0.16.0-0ubuntu2 [672 kB] Get:95 http://ftpmaster.internal/ubuntu/ natty/main luatex i386 0.65.0-1ubuntu2 [2255 kB] Get:96 http://ftpmaster.internal/ubuntu/ natty/main libkpathsea5 i386 2009-8build1 [53.9 kB] Get:97 http://ftpmaster.internal/ubuntu/ natty/main libsm6 i386 2:1.2.0-1 [14.5 kB] Get:98 http://ftpmaster.internal/ubuntu/ natty/main libxt6 i386 1:1.0.9-1 [161 kB] Get:99 http://ftpmaster.internal/ubuntu/ natty/main libxmu6 i386 2:1.1.0-1 [47.9 kB] Get:100 http://ftpmaster.internal/ubuntu/ natty/main libxpm4 i386 1:3.5.9-1ubuntu1 [35.3 kB] Get:101 http://ftpmaster.internal/ubuntu/ natty/main libxaw7 i386 2:1.0.8-2 [180 kB] Get:102 http://ftpmaster.internal/ubuntu/ natty/main texlive-binaries i386 2009-8build1 [7389 kB] Get:103 http://ftpmaster.internal/ubuntu/ natty/main texlive-base all 2009-11 [14.7 MB] Get:104 http://ftpmaster.internal/ubuntu/ natty/main texlive-latex-base all 2009-11 [1342 kB] Get:105 http://ftpmaster.internal/ubuntu/ natty/main texlive-fonts-recommended all 2009-11 [7166 kB] Get:106 http://ftpmaster.internal/ubuntu/ natty/main texlive-latex-recommended all 2009-11 [6588 kB] Get:107 http://ftpmaster.internal/ubuntu/ natty/main tipa all 2:1.3-14 [3197 kB] Get:108 http://ftpmaster.internal/ubuntu/ natty/main jadetex all 3.13-12 [251 kB] Get:109 http://ftpmaster.internal/ubuntu/ natty/main lynx-cur i386 2.8.8dev.7-1 [998 kB] Get:110 http://ftpmaster.internal/ubuntu/ natty/main lynx all 2.8.8dev.7-1 [3682 B] Get:111 http://ftpmaster.internal/ubuntu/ natty/main libsgmls-perl all 1.03ii-32 [29.4 kB] Get:112 http://ftpmaster.internal/ubuntu/ natty/main sgmlspl all 1.03ii-32 [11.4 kB] Get:113 http://ftpmaster.internal/ubuntu/ natty/main docbook-utils all 0.6.14-1.1 [73.4 kB] Get:114 http://ftpmaster.internal/ubuntu/ natty/main docbook-xsl all 1.75.2+dfsg-5ubuntu1 [1499 kB] Get:115 http://ftpmaster.internal/ubuntu/ natty/main fontconfig i386 2.8.0-2.1ubuntu1 [155 kB] Get:116 http://ftpmaster.internal/ubuntu/ natty/main libidl0 i386 0.8.14-0.1 [118 kB] Get:117 http://ftpmaster.internal/ubuntu/ natty/main liborbit2 i386 1:2.14.18-0.1build1 [163 kB] Get:118 http://ftpmaster.internal/ubuntu/ natty/main gconf2-common all 2.32.1-2ubuntu2 [19.7 kB] Get:119 http://ftpmaster.internal/ubuntu/ natty/main libgconf2-4 i386 2.32.1-2ubuntu2 [153 kB] Get:120 http://ftpmaster.internal/ubuntu/ natty/main gconf2 i386 2.32.1-2ubuntu2 [74.7 kB] Get:121 http://ftpmaster.internal/ubuntu/ natty/main pkg-config i386 0.25-1.1 [41.4 kB] Get:122 http://ftpmaster.internal/ubuntu/ natty/main intltool all 0.41.1-1 [103 kB] Get:123 http://ftpmaster.internal/ubuntu/ natty/main gnome-common all 2.28.0-1 [16.0 kB] Get:124 http://ftpmaster.internal/ubuntu/ natty/main python-libxml2 i386 2.7.8.dfsg-2 [287 kB] Get:125 http://ftpmaster.internal/ubuntu/ natty/main libxml2-utils i386 2.7.8.dfsg-2 [77.8 kB] Get:126 http://ftpmaster.internal/ubuntu/ natty/main libxslt1.1 i386 1.1.26-6build1 [152 kB] Get:127 http://ftpmaster.internal/ubuntu/ natty/main xsltproc i386 1.1.26-6build1 [32.5 kB] Get:128 http://ftpmaster.internal/ubuntu/ natty/main gnome-doc-utils all 0.20.4-2build1 [300 kB] Get:129 http://ftpmaster.internal/ubuntu/ natty/main gnome-pkg-tools all 0.16.3ubuntu1 [23.5 kB] Get:130 http://ftpmaster.internal/ubuntu/ natty/main gtk-doc-tools all 1.16-0ubuntu1 [173 kB] Get:131 http://ftpmaster.internal/ubuntu/ natty/main libgssrpc4 i386 1.8.3+dfsg-4 [54.2 kB] Get:132 http://ftpmaster.internal/ubuntu/ natty/main libkdb5-4 i386 1.8.3+dfsg-4 [37.7 kB] Get:133 http://ftpmaster.internal/ubuntu/ natty/main libkadm5srv-mit7 i386 1.8.3+dfsg-4 [51.4 kB] Get:134 http://ftpmaster.internal/ubuntu/ natty/main libkadm5clnt-mit7 i386 1.8.3+dfsg-4 [38.3 kB] Get:135 http://ftpmaster.internal/ubuntu/ natty/main comerr-dev i386 2.1-1.41.14-1ubuntu1 [41.4 kB] Get:136 http://ftpmaster.internal/ubuntu/ natty/main krb5-multidev i386 1.8.3+dfsg-4 [82.2 kB] Get:137 http://ftpmaster.internal/ubuntu/ natty/main libasound2 i386 1.0.23-2.1ubuntu2 [356 kB] Get:138 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-data all 1.33.6-0ubuntu1 [11.7 kB] Get:139 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-0 i386 1.33.6-0ubuntu1 [40.3 kB] Get:140 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-data all 2.27.93-0ubuntu1 [974 B] Get:141 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-bin i386 2.27.93-0ubuntu1 [26.1 kB] Get:142 http://ftpmaster.internal/ubuntu/ natty/main zlib1g-dev i386 1:1.2.3.4.dfsg-3ubuntu1 [188 kB] Get:143 http://ftpmaster.internal/ubuntu/ natty/main libglib2.0-dev i386 2.27.93-0ubuntu1 [1432 kB] Get:144 http://ftpmaster.internal/ubuntu/ natty/main libatk1.0-dev i386 1.33.6-0ubuntu1 [124 kB] Get:145 http://ftpmaster.internal/ubuntu/ natty/main libavahi-common-data i386 0.6.28-2ubuntu2 [22.6 kB] Get:146 http://ftpmaster.internal/ubuntu/ natty/main libavahi-common3 i386 0.6.28-2ubuntu2 [36.6 kB] Get:147 http://ftpmaster.internal/ubuntu/ natty/main libavahi-client3 i386 0.6.28-2ubuntu2 [41.0 kB] Get:148 http://ftpmaster.internal/ubuntu/ natty/main libavahi-common-dev i386 0.6.28-2ubuntu2 [54.5 kB] Get:149 http://ftpmaster.internal/ubuntu/ natty/main libdbus-1-dev i386 1.4.1-0ubuntu2 [26.0 kB] Get:150 http://ftpmaster.internal/ubuntu/ natty/main libavahi-client-dev i386 0.6.28-2ubuntu2 [48.5 kB] Get:151 http://ftpmaster.internal/ubuntu/ natty/main libcairo-gobject2 i386 1.10.2-1ubuntu1 [112 kB] Get:152 http://ftpmaster.internal/ubuntu/ natty/main libexpat1-dev i386 2.0.1-7ubuntu1 [213 kB] Get:153 http://ftpmaster.internal/ubuntu/ natty/main libfreetype6-dev i386 2.4.2-2.1 [703 kB] Get:154 http://ftpmaster.internal/ubuntu/ natty/main libfontconfig1-dev i386 2.8.0-2.1ubuntu1 [660 kB] Get:155 http://ftpmaster.internal/ubuntu/ natty/main x11proto-render-dev all 2:0.11.1-1 [18.5 kB] Get:156 http://ftpmaster.internal/ubuntu/ natty/main libxrender-dev i386 1:0.9.6-1 [36.7 kB] Get:157 http://ftpmaster.internal/ubuntu/ natty/main libpng12-dev i386 1.2.44-1ubuntu1 [208 kB] Get:158 http://ftpmaster.internal/ubuntu/ natty/main libsm-dev i386 2:1.2.0-1 [85.7 kB] Get:159 http://ftpmaster.internal/ubuntu/ natty/main libpixman-1-dev i386 0.18.4-1build1 [187 kB] Get:160 http://ftpmaster.internal/ubuntu/ natty/main libxcb-render0-dev i386 1.6-1 [22.1 kB] Get:161 http://ftpmaster.internal/ubuntu/ natty/main libxcb-shm0-dev i386 1.6-1 [10.5 kB] Get:162 http://ftpmaster.internal/ubuntu/ natty/main libcairo2-dev i386 1.10.2-1ubuntu1 [8716 kB] Get:163 http://ftpmaster.internal/ubuntu/ natty/main libltdl7 i386 2.2.6b-2ubuntu1 [295 kB] Get:164 http://ftpmaster.internal/ubuntu/ natty/main libtdb1 i386 1.2.9-1fakesync1 [33.5 kB] Get:165 http://ftpmaster.internal/ubuntu/ natty/main libogg0 i386 1.2.0~dfsg-1 [16.6 kB] Get:166 http://ftpmaster.internal/ubuntu/ natty/main libvorbis0a i386 1.3.1-1ubuntu1 [95.3 kB] Get:167 http://ftpmaster.internal/ubuntu/ natty/main libvorbisfile3 i386 1.3.1-1ubuntu1 [22.1 kB] Get:168 http://ftpmaster.internal/ubuntu/ natty/main libcanberra0 i386 0.26-1ubuntu9 [37.1 kB] Get:169 http://ftpmaster.internal/ubuntu/ natty/main libcanberra-dev i386 0.26-1ubuntu9 [7112 B] Get:170 http://ftpmaster.internal/ubuntu/ natty/main libcanberra-gtk-common-dev all 0.26-1ubuntu9 [7826 B] Get:171 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-common all 2.24.0-0ubuntu1 [113 kB] Get:172 http://ftpmaster.internal/ubuntu/ natty/main libcups2 i386 1.4.5-1ubuntu6 [158 kB] Get:173 http://ftpmaster.internal/ubuntu/ natty/main libjasper1 i386 1.900.1-7 [143 kB] Get:174 http://ftpmaster.internal/ubuntu/ natty/main libtiff4 i386 3.9.4-5 [136 kB] Get:175 http://ftpmaster.internal/ubuntu/ natty/main libgdk-pixbuf2.0-0 i386 2.23.0-1ubuntu1 [176 kB] Get:176 http://ftpmaster.internal/ubuntu/ natty/main libdatrie1 i386 0.2.4-1 [25.9 kB] Get:177 http://ftpmaster.internal/ubuntu/ natty/main libthai-data all 0.1.14-2 [197 kB] Get:178 http://ftpmaster.internal/ubuntu/ natty/main libthai0 i386 0.1.14-2 [40.5 kB] Get:179 http://ftpmaster.internal/ubuntu/ natty/main libxft2 i386 2.1.14-2ubuntu1 [52.1 kB] Get:180 http://ftpmaster.internal/ubuntu/ natty/main libpango1.0-0 i386 1.28.3-4 [332 kB] Get:181 http://ftpmaster.internal/ubuntu/ natty/main libxcomposite1 i386 1:0.4.3-1 [5624 B] Get:182 http://ftpmaster.internal/ubuntu/ natty/main libxfixes3 i386 1:4.0.5-1 [18.0 kB] Get:183 http://ftpmaster.internal/ubuntu/ natty/main libxcursor1 i386 1:1.1.11-1 [19.2 kB] Get:184 http://ftpmaster.internal/ubuntu/ natty/main libxdamage1 i386 1:1.1.3-1 [13.6 kB] Get:185 http://ftpmaster.internal/ubuntu/ natty/main libxi6 i386 2:1.4.0-1 [29.1 kB] Get:186 http://ftpmaster.internal/ubuntu/ natty/main libxinerama1 i386 2:1.1.1-1 [5552 B] Get:187 http://ftpmaster.internal/ubuntu/ natty/main libxrandr2 i386 2:1.3.1-1 [16.3 kB] Get:188 http://ftpmaster.internal/ubuntu/ natty/main shared-mime-info i386 0.90-0ubuntu1 [435 kB] Get:189 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-0 i386 2.24.0-0ubuntu1 [2011 kB] Get:190 http://ftpmaster.internal/ubuntu/ natty/main libcanberra-gtk0 i386 0.26-1ubuntu9 [7960 B] Get:191 http://ftpmaster.internal/ubuntu/ natty/main libgdk-pixbuf2.0-dev i386 2.23.0-1ubuntu1 [42.4 kB] Get:192 http://ftpmaster.internal/ubuntu/ natty/main libxft-dev i386 2.1.14-2ubuntu1 [65.6 kB] Get:193 http://ftpmaster.internal/ubuntu/ natty/main libpango1.0-dev i386 1.28.3-4 [437 kB] Get:194 http://ftpmaster.internal/ubuntu/ natty/main x11proto-xext-dev all 7.1.99.0~git20110111.9df8b776-0ubuntu2 [254 kB] Get:195 http://ftpmaster.internal/ubuntu/ natty/main libxext-dev i386 2:1.1.2-1 [103 kB] Get:196 http://ftpmaster.internal/ubuntu/ natty/main x11proto-xinerama-dev all 1.2.1-1 [4870 B] Get:197 http://ftpmaster.internal/ubuntu/ natty/main libxinerama-dev i386 2:1.1.1-1 [7878 B] Get:198 http://ftpmaster.internal/ubuntu/ natty/main libxi-dev i386 2:1.4.0-1 [210 kB] Get:199 http://ftpmaster.internal/ubuntu/ natty/main x11proto-randr-dev all 1.4.0+git20101207.0d32bb07-0ubuntu1 [32.0 kB] Get:200 http://ftpmaster.internal/ubuntu/ natty/main libxrandr-dev i386 2:1.3.1-1 [24.1 kB] Get:201 http://ftpmaster.internal/ubuntu/ natty/main x11proto-fixes-dev all 1:4.1.2-1 [11.3 kB] Get:202 http://ftpmaster.internal/ubuntu/ natty/main libxfixes-dev i386 1:4.0.5-1 [20.2 kB] Get:203 http://ftpmaster.internal/ubuntu/ natty/main libxcursor-dev i386 1:1.1.11-1 [26.8 kB] Get:204 http://ftpmaster.internal/ubuntu/ natty/main x11proto-composite-dev all 1:0.4.2-1 [8866 B] Get:205 http://ftpmaster.internal/ubuntu/ natty/main libxcomposite-dev i386 1:0.4.3-1 [9234 B] Get:206 http://ftpmaster.internal/ubuntu/ natty/main x11proto-damage-dev all 1:1.2.1-1 [6586 B] Get:207 http://ftpmaster.internal/ubuntu/ natty/main libxdamage-dev i386 1:1.1.3-1 [13.4 kB] Get:208 http://ftpmaster.internal/ubuntu/ natty/main libgtk2.0-dev i386 2.24.0-0ubuntu1 [3364 kB] Get:209 http://ftpmaster.internal/ubuntu/ natty/main libcanberra-gtk-dev i386 0.26-1ubuntu9 [1838 B] Get:210 http://ftpmaster.internal/ubuntu/ natty/main libgpg-error-dev i386 1.10-0.2 [19.6 kB] Get:211 http://ftpmaster.internal/ubuntu/ natty/main libgcrypt11-dev i386 1.4.6-4 [321 kB] Get:212 http://ftpmaster.internal/ubuntu/ natty/main libtasn1-3-dev i386 2.7-1 [355 kB] Get:213 http://ftpmaster.internal/ubuntu/ natty/main libgnutls-dev i386 2.8.6-1ubuntu1 [399 kB] Get:214 http://ftpmaster.internal/ubuntu/ natty/main libkrb5-dev i386 1.8.3+dfsg-4 [14.7 kB] Get:215 http://ftpmaster.internal/ubuntu/ natty/main libcups2-dev i386 1.4.5-1ubuntu6 [219 kB] Get:216 http://ftpmaster.internal/ubuntu/ natty/main libdbus-glib-1-dev i386 0.88-2.1 [100 kB] Get:217 http://ftpmaster.internal/ubuntu/ natty/main libexif12 i386 0.6.19-1 [99.2 kB] Get:218 http://ftpmaster.internal/ubuntu/ natty/main libexif-dev i386 0.6.19-1 [367 kB] Get:219 http://ftpmaster.internal/ubuntu/ natty/main libidl-dev i386 0.8.14-0.1 [84.0 kB] Get:220 http://ftpmaster.internal/ubuntu/ natty/main liborbit2-dev i386 1:2.14.18-0.1build1 [378 kB] Get:221 http://ftpmaster.internal/ubuntu/ natty/main libgconf2-dev i386 2.32.1-2ubuntu2 [224 kB] Get:222 http://ftpmaster.internal/ubuntu/ natty/main libxcb-atom1 i386 0.3.6-1build1 [9752 B] Get:223 http://ftpmaster.internal/ubuntu/ natty/main libxcb-aux0 i386 0.3.6-1build1 [8714 B] Get:224 http://ftpmaster.internal/ubuntu/ natty/main libxcb-event1 i386 0.3.6-1build1 [8732 B] Get:225 http://ftpmaster.internal/ubuntu/ natty/main libstartup-notification0 i386 0.10-1build1 [18.3 kB] Get:226 http://ftpmaster.internal/ubuntu/ natty/main libgnome-desktop-2-17 i386 1:2.32.1-0ubuntu2 [92.8 kB] Get:227 http://ftpmaster.internal/ubuntu/ natty/main libstartup-notification0-dev i386 0.10-1build1 [18.5 kB] Get:228 http://ftpmaster.internal/ubuntu/ natty/main libgnome-desktop-dev i386 1:2.32.1-0ubuntu2 [115 kB] Get:229 http://ftpmaster.internal/ubuntu/ natty/main libgphoto2-port0 i386 2.4.10.1-2ubuntu4 [39.1 kB] Get:230 http://ftpmaster.internal/ubuntu/ natty/main libgphoto2-2 i386 2.4.10.1-2ubuntu4 [877 kB] Get:231 http://ftpmaster.internal/ubuntu/ natty/main libusb-dev i386 2:0.1.12-16 [38.4 kB] Get:232 http://ftpmaster.internal/ubuntu/ natty/main libgphoto2-2-dev i386 2.4.10.1-2ubuntu4 [4340 kB] Get:233 http://ftpmaster.internal/ubuntu/ natty/main libgudev-1.0-0 i386 1:165-0ubuntu2 [15.2 kB] Get:234 http://ftpmaster.internal/ubuntu/ natty/main libudev-dev i386 165-0ubuntu2 [55.9 kB] Get:235 http://ftpmaster.internal/ubuntu/ natty/main libgudev-1.0-dev i386 1:165-0ubuntu2 [45.3 kB] Get:236 http://ftpmaster.internal/ubuntu/ natty/main libieee1284-3 i386 0.2.11-5ubuntu4 [20.9 kB] Get:237 http://ftpmaster.internal/ubuntu/ natty/main libieee1284-3-dev i386 0.2.11-5ubuntu4 [47.7 kB] Get:238 http://ftpmaster.internal/ubuntu/ natty/main libjpeg62-dev i386 6b1-1 [188 kB] Get:239 http://ftpmaster.internal/ubuntu/ natty/main liblcms1-dev i386 1.18.dfsg-1.2ubuntu1 [189 kB] Get:240 http://ftpmaster.internal/ubuntu/ natty/main libnotify1 i386 0.5.0-2ubuntu1 [28.5 kB] Get:241 http://ftpmaster.internal/ubuntu/ natty/main libnotify-dev i386 0.5.0-2ubuntu1 [16.2 kB] Get:242 http://ftpmaster.internal/ubuntu/ natty/main libv4l-0 i386 0.8.1-2 [89.0 kB] Get:243 http://ftpmaster.internal/ubuntu/ natty/main libsane i386 1.0.21-9ubuntu1 [3654 kB] Get:244 http://ftpmaster.internal/ubuntu/ natty/main libtiffxx0c2 i386 3.9.4-5 [6640 B] Get:245 http://ftpmaster.internal/ubuntu/ natty/main libtiff4-dev i386 3.9.4-5 [247 kB] Get:246 http://ftpmaster.internal/ubuntu/ natty/main libv4l-dev i386 0.8.1-2 [74.3 kB] Get:247 http://ftpmaster.internal/ubuntu/ natty/main libsane-dev i386 1.0.21-9ubuntu1 [3814 kB] Get:248 http://ftpmaster.internal/ubuntu/ natty/main libunique-1.0-0 i386 1.1.6-1.1ubuntu2 [22.5 kB] Get:249 http://ftpmaster.internal/ubuntu/ natty/main libunique-dev i386 1.1.6-1.1ubuntu2 [30.8 kB] Get:250 http://ftpmaster.internal/ubuntu/ natty/main libvte-common all 1:0.27.5-0ubuntu1 [25.0 kB] Get:251 http://ftpmaster.internal/ubuntu/ natty/main libvte9 i386 1:0.27.5-0ubuntu1 [334 kB] Get:252 http://ftpmaster.internal/ubuntu/ natty/main python-gtk2 i386 2.22.0-0ubuntu1 [1396 kB] Get:253 http://ftpmaster.internal/ubuntu/ natty/main python-vte i386 1:0.27.5-0ubuntu1 [29.4 kB] Get:254 http://ftpmaster.internal/ubuntu/ natty/main libvte-dev i386 1:0.27.5-0ubuntu1 [377 kB] Get:255 http://ftpmaster.internal/ubuntu/ natty/main libxxf86vm1 i386 1:1.1.1-1 [10.9 kB] Get:256 http://ftpmaster.internal/ubuntu/ natty/main x11proto-xf86vidmode-dev all 2.3.1-1 [6050 B] Get:257 http://ftpmaster.internal/ubuntu/ natty/main libxxf86vm-dev i386 1:1.1.1-1 [16.5 kB] Get:258 http://ftpmaster.internal/ubuntu/ natty/main librarian0 i386 0.8.1-5 [59.2 kB] Get:259 http://ftpmaster.internal/ubuntu/ natty/main rarian-compat i386 0.8.1-5 [104 kB] Get:260 http://ftpmaster.internal/ubuntu/ natty/main scrollkeeper all 0.8.1-5 [12.3 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 120 MB in 5s (23.1 MB/s) Selecting previously deselected package sgml-base. (Reading database ... 13677 files and directories currently installed.) Unpacking sgml-base (from .../sgml-base_1.26+nmu1ubuntu1_all.deb) ... Selecting previously deselected package xml-core. Unpacking xml-core (from .../archives/xml-core_0.13_all.deb) ... Selecting previously deselected package sgml-data. Unpacking sgml-data (from .../sgml-data_2.0.5_all.deb) ... Setting up sgml-base (1.26+nmu1ubuntu1) ... Setting up xml-core (0.13) ... Selecting previously deselected package docbook-xml. (Reading database ... 13914 files and directories currently installed.) Unpacking docbook-xml (from .../docbook-xml_4.5-7_all.deb) ... Selecting previously deselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.6~3ubuntu3_all.deb) ... Selecting previously deselected package libice6. Unpacking libice6 (from .../libice6_2%3a1.0.7-1_i386.deb) ... Selecting previously deselected package x11proto-core-dev. Unpacking x11proto-core-dev (from .../x11proto-core-dev_7.0.20-1_all.deb) ... Setting up x11-common (1:7.6~3ubuntu3) ... Selecting previously deselected package libice-dev. (Reading database ... 14202 files and directories currently installed.) Unpacking libice-dev (from .../libice-dev_2%3a1.0.7-1_i386.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.6-1_i386.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.1.0-1_i386.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.6-1_i386.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.3.3-3ubuntu3_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.3.3-3ubuntu3_i386.deb) ... Selecting previously deselected package libxau-dev. Unpacking libxau-dev (from .../libxau-dev_1%3a1.0.6-1_i386.deb) ... Selecting previously deselected package libxdmcp-dev. Unpacking libxdmcp-dev (from .../libxdmcp-dev_1%3a1.1.0-1_i386.deb) ... Selecting previously deselected package x11proto-input-dev. Unpacking x11proto-input-dev (from .../x11proto-input-dev_2.0.1-1_all.deb) ... Selecting previously deselected package x11proto-kb-dev. Unpacking x11proto-kb-dev (from .../x11proto-kb-dev_1.0.5-1_all.deb) ... Selecting previously deselected package xtrans-dev. Unpacking xtrans-dev (from .../xtrans-dev_1.2.6-1_all.deb) ... Selecting previously deselected package libpthread-stubs0. Unpacking libpthread-stubs0 (from .../libpthread-stubs0_0.3-2_i386.deb) ... Selecting previously deselected package libpthread-stubs0-dev. Unpacking libpthread-stubs0-dev (from .../libpthread-stubs0-dev_0.3-2_i386.deb) ... Selecting previously deselected package libxcb1-dev. Unpacking libxcb1-dev (from .../libxcb1-dev_1.6-1_i386.deb) ... Selecting previously deselected package libx11-dev. Unpacking libx11-dev (from .../libx11-dev_2%3a1.3.3-3ubuntu3_i386.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.04-5ubuntu2_i386.deb) ... Selecting previously deselected package file. Unpacking file (from .../file_5.04-5ubuntu2_i386.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-7ubuntu1_i386.deb) ... Selecting previously deselected package libpopt0. Unpacking libpopt0 (from .../libpopt0_1.16-1_i386.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.7.4-2ubuntu2_i386.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.51-1ubuntu1_all.deb) ... Selecting previously deselected package python2.7. Unpacking python2.7 (from .../python2.7_2.7.1-3_i386.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.7.1-0ubuntu5_all.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../ucf_3.0025+nmu1_all.deb) ... Moving old data out of the way Selecting previously deselected package bsdmainutils. Unpacking bsdmainutils (from .../bsdmainutils_8.2.2_i386.deb) ... Selecting previously deselected package ed. Unpacking ed (from .../apt/archives/ed_1.5-1_i386.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.31-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.8.0-2.1ubuntu1_all.deb) ... Selecting previously deselected package gettext-base. Unpacking gettext-base (from .../gettext-base_0.18.1.1-3ubuntu1_i386.deb) ... Selecting previously deselected package libffi5. Unpacking libffi5 (from .../libffi5_3.0.9-3_i386.deb) ... Selecting previously deselected package libgirepository-1.0-1. Unpacking libgirepository-1.0-1 (from .../libgirepository-1.0-1_0.10.1+git20110201-0ubuntu1_i386.deb) ... Selecting previously deselected package gir1.2-glib-2.0. Unpacking gir1.2-glib-2.0 (from .../gir1.2-glib-2.0_0.10.1+git20110201-0ubuntu1_i386.deb) ... Selecting previously deselected package groff-base. Unpacking groff-base (from .../groff-base_1.21-3_i386.deb) ... Selecting previously deselected package libbsd0. Unpacking libbsd0 (from .../libbsd0_0.2.0-1_i386.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.4.2-2.1_i386.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.8.0-2.1ubuntu1_i386.deb) ... Selecting previously deselected package libpixman-1-0. Unpacking libpixman-1-0 (from .../libpixman-1-0_0.18.4-1build1_i386.deb) ... Selecting previously deselected package libxcb-render0. Unpacking libxcb-render0 (from .../libxcb-render0_1.6-1_i386.deb) ... Selecting previously deselected package libxcb-shm0. Unpacking libxcb-shm0 (from .../libxcb-shm0_1.6-1_i386.deb) ... Selecting previously deselected package libxrender1. Unpacking libxrender1 (from .../libxrender1_1%3a0.9.6-1_i386.deb) ... Selecting previously deselected package libcairo2. Unpacking libcairo2 (from .../libcairo2_1.10.2-1ubuntu1_i386.deb) ... Selecting previously deselected package libdbus-glib-1-2. Unpacking libdbus-glib-1-2 (from .../libdbus-glib-1-2_0.88-2.1_i386.deb) ... Selecting previously deselected package liburi-perl. Unpacking liburi-perl (from .../liburi-perl_1.56-1_all.deb) ... Selecting previously deselected package libhtml-tagset-perl. Unpacking libhtml-tagset-perl (from .../libhtml-tagset-perl_3.20-2_all.deb) ... Selecting previously deselected package libhtml-parser-perl. Unpacking libhtml-parser-perl (from .../libhtml-parser-perl_3.68-1_i386.deb) ... Selecting previously deselected package libhtml-tree-perl. Unpacking libhtml-tree-perl (from .../libhtml-tree-perl_4.1-1_all.deb) ... Selecting previously deselected package libpipeline1. Unpacking libpipeline1 (from .../libpipeline1_1.1.0-1_i386.deb) ... Selecting previously deselected package libwww-perl. Unpacking libwww-perl (from .../libwww-perl_5.837-1_all.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.1.2-1_i386.deb) ... Selecting previously deselected package libxml-parser-perl. Unpacking libxml-parser-perl (from .../libxml-parser-perl_2.36-1.1build3_i386.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-2_i386.deb) ... Selecting previously deselected package man-db. Unpacking man-db (from .../man-db_2.5.9-3_i386.deb) ... Selecting previously deselected package psmisc. Unpacking psmisc (from .../psmisc_22.13-1_i386.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_1.0.10ubuntu3_all.deb) ... Selecting previously deselected package python-cairo. Unpacking python-cairo (from .../python-cairo_1.8.8-1ubuntu1_i386.deb) ... Selecting previously deselected package libpython2.7. Unpacking libpython2.7 (from .../libpython2.7_2.7.1-3_i386.deb) ... Selecting previously deselected package python-gobject. Unpacking python-gobject (from .../python-gobject_2.27.0+git20110131-0ubuntu6_i386.deb) ... Selecting previously deselected package m4. Unpacking m4 (from .../archives/m4_1.4.14-3_i386.deb) ... Selecting previously deselected package autoconf. Unpacking autoconf (from .../autoconf_2.67-2ubuntu1_all.deb) ... Selecting previously deselected package autotools-dev. Unpacking autotools-dev (from .../autotools-dev_20100122.1_all.deb) ... Selecting previously deselected package automake. Unpacking automake (from .../automake_1%3a1.11.1-1ubuntu1_all.deb) ... Selecting previously deselected package dbus. Unpacking dbus (from .../dbus_1.4.1-0ubuntu2_i386.deb) ... Selecting previously deselected package dbus-x11. Unpacking dbus-x11 (from .../dbus-x11_1.4.1-0ubuntu2_i386.deb) ... Selecting previously deselected package html2text. Unpacking html2text (from .../html2text_1.3.2a-15_i386.deb) ... Selecting previously deselected package libcroco3. Unpacking libcroco3 (from .../libcroco3_0.6.2-1_i386.deb) ... Selecting previously deselected package libunistring0. Unpacking libunistring0 (from .../libunistring0_0.9.3-3_i386.deb) ... Selecting previously deselected package gettext. Unpacking gettext (from .../gettext_0.18.1.1-3ubuntu1_i386.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+nmu1_all.deb) ... Selecting previously deselected package debhelper. Unpacking debhelper (from .../debhelper_8.0.0ubuntu2_all.deb) ... Selecting previously deselected package libtool. Unpacking libtool (from .../libtool_2.2.6b-2ubuntu1_i386.deb) ... Selecting previously deselected package dh-autoreconf. Unpacking dh-autoreconf (from .../dh-autoreconf_2_all.deb) ... Selecting previously deselected package docbook. Unpacking docbook (from .../archives/docbook_4.5-4_all.deb) ... Selecting previously deselected package libosp5. Unpacking libosp5 (from .../libosp5_1.5.2-8_i386.deb) ... Selecting previously deselected package libostyle1c2. Unpacking libostyle1c2 (from .../libostyle1c2_1.4devel1-19build1_i386.deb) ... Selecting previously deselected package openjade. Unpacking openjade (from .../openjade_1.4devel1-19build1_i386.deb) ... Selecting previously deselected package libsp1c2. Unpacking libsp1c2 (from .../libsp1c2_1.3.4-1.2.1-47build3_i386.deb) ... Selecting previously deselected package jade. Unpacking jade (from .../jade_1.2.1-47build3_i386.deb) ... Selecting previously deselected package docbook-dsssl. Unpacking docbook-dsssl (from .../docbook-dsssl_1.79-6_all.deb) ... Selecting previously deselected package sp. Unpacking sp (from .../sp_1.3.4-1.2.1-47build3_i386.deb) ... Selecting previously deselected package docbook-to-man. Unpacking docbook-to-man (from .../docbook-to-man_1%3a2.0.0-28_i386.deb) ... Selecting previously deselected package tex-common. Unpacking tex-common (from .../tex-common_2.08_all.deb) ... Selecting previously deselected package texlive-common. Unpacking texlive-common (from .../texlive-common_2009-11_all.deb) ... Selecting previously deselected package texlive-doc-base. Unpacking texlive-doc-base (from .../texlive-doc-base_2009-2_all.deb) ... Selecting previously deselected package libjpeg62. Unpacking libjpeg62 (from .../libjpeg62_6b1-1_i386.deb) ... Selecting previously deselected package liblcms1. Unpacking liblcms1 (from .../liblcms1_1.18.dfsg-1.2ubuntu1_i386.deb) ... Selecting previously deselected package libpoppler12. Unpacking libpoppler12 (from .../libpoppler12_0.16.0-0ubuntu2_i386.deb) ... Selecting previously deselected package luatex. Unpacking luatex (from .../luatex_0.65.0-1ubuntu2_i386.deb) ... Selecting previously deselected package libkpathsea5. Unpacking libkpathsea5 (from .../libkpathsea5_2009-8build1_i386.deb) ... Selecting previously deselected package libsm6. Unpacking libsm6 (from .../libsm6_2%3a1.2.0-1_i386.deb) ... Selecting previously deselected package libxt6. Unpacking libxt6 (from .../libxt6_1%3a1.0.9-1_i386.deb) ... Selecting previously deselected package libxmu6. Unpacking libxmu6 (from .../libxmu6_2%3a1.1.0-1_i386.deb) ... Selecting previously deselected package libxpm4. Unpacking libxpm4 (from .../libxpm4_1%3a3.5.9-1ubuntu1_i386.deb) ... Selecting previously deselected package libxaw7. Unpacking libxaw7 (from .../libxaw7_2%3a1.0.8-2_i386.deb) ... Selecting previously deselected package texlive-binaries. Unpacking texlive-binaries (from .../texlive-binaries_2009-8build1_i386.deb) ... Selecting previously deselected package texlive-base. Unpacking texlive-base (from .../texlive-base_2009-11_all.deb) ... Selecting previously deselected package texlive-latex-base. Unpacking texlive-latex-base (from .../texlive-latex-base_2009-11_all.deb) ... Selecting previously deselected package texlive-fonts-recommended. Unpacking texlive-fonts-recommended (from .../texlive-fonts-recommended_2009-11_all.deb) ... Selecting previously deselected package texlive-latex-recommended. Unpacking texlive-latex-recommended (from .../texlive-latex-recommended_2009-11_all.deb) ... Selecting previously deselected package tipa. Unpacking tipa (from .../tipa_2%3a1.3-14_all.deb) ... Selecting previously deselected package jadetex. Unpacking jadetex (from .../jadetex_3.13-12_all.deb) ... Selecting previously deselected package lynx-cur. Unpacking lynx-cur (from .../lynx-cur_2.8.8dev.7-1_i386.deb) ... Selecting previously deselected package lynx. Unpacking lynx (from .../lynx_2.8.8dev.7-1_all.deb) ... Selecting previously deselected package libsgmls-perl. Unpacking libsgmls-perl (from .../libsgmls-perl_1.03ii-32_all.deb) ... Selecting previously deselected package sgmlspl. Unpacking sgmlspl (from .../sgmlspl_1.03ii-32_all.deb) ... Selecting previously deselected package docbook-utils. Unpacking docbook-utils (from .../docbook-utils_0.6.14-1.1_all.deb) ... Selecting previously deselected package docbook-xsl. Unpacking docbook-xsl (from .../docbook-xsl_1.75.2+dfsg-5ubuntu1_all.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.8.0-2.1ubuntu1_i386.deb) ... Selecting previously deselected package libidl0. Unpacking libidl0 (from .../libidl0_0.8.14-0.1_i386.deb) ... Selecting previously deselected package liborbit2. Unpacking liborbit2 (from .../liborbit2_1%3a2.14.18-0.1build1_i386.deb) ... Selecting previously deselected package gconf2-common. Unpacking gconf2-common (from .../gconf2-common_2.32.1-2ubuntu2_all.deb) ... Selecting previously deselected package libgconf2-4. Unpacking libgconf2-4 (from .../libgconf2-4_2.32.1-2ubuntu2_i386.deb) ... Selecting previously deselected package gconf2. Unpacking gconf2 (from .../gconf2_2.32.1-2ubuntu2_i386.deb) ... Selecting previously deselected package pkg-config. Unpacking pkg-config (from .../pkg-config_0.25-1.1_i386.deb) ... Selecting previously deselected package intltool. Unpacking intltool (from .../intltool_0.41.1-1_all.deb) ... Selecting previously deselected package gnome-common. Unpacking gnome-common (from .../gnome-common_2.28.0-1_all.deb) ... Selecting previously deselected package python-libxml2. Unpacking python-libxml2 (from .../python-libxml2_2.7.8.dfsg-2_i386.deb) ... Selecting previously deselected package libxml2-utils. Unpacking libxml2-utils (from .../libxml2-utils_2.7.8.dfsg-2_i386.deb) ... Selecting previously deselected package libxslt1.1. Unpacking libxslt1.1 (from .../libxslt1.1_1.1.26-6build1_i386.deb) ... Selecting previously deselected package xsltproc. Unpacking xsltproc (from .../xsltproc_1.1.26-6build1_i386.deb) ... Selecting previously deselected package gnome-doc-utils. Unpacking gnome-doc-utils (from .../gnome-doc-utils_0.20.4-2build1_all.deb) ... Selecting previously deselected package gnome-pkg-tools. Unpacking gnome-pkg-tools (from .../gnome-pkg-tools_0.16.3ubuntu1_all.deb) ... Selecting previously deselected package gtk-doc-tools. Unpacking gtk-doc-tools (from .../gtk-doc-tools_1.16-0ubuntu1_all.deb) ... Selecting previously deselected package libgssrpc4. Unpacking libgssrpc4 (from .../libgssrpc4_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package libkdb5-4. Unpacking libkdb5-4 (from .../libkdb5-4_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package libkadm5srv-mit7. Unpacking libkadm5srv-mit7 (from .../libkadm5srv-mit7_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package libkadm5clnt-mit7. Unpacking libkadm5clnt-mit7 (from .../libkadm5clnt-mit7_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package comerr-dev. Unpacking comerr-dev (from .../comerr-dev_2.1-1.41.14-1ubuntu1_i386.deb) ... Selecting previously deselected package krb5-multidev. Unpacking krb5-multidev (from .../krb5-multidev_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package libasound2. Unpacking libasound2 (from .../libasound2_1.0.23-2.1ubuntu2_i386.deb) ... Selecting previously deselected package libatk1.0-data. Unpacking libatk1.0-data (from .../libatk1.0-data_1.33.6-0ubuntu1_all.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.33.6-0ubuntu1_i386.deb) ... Selecting previously deselected package libglib2.0-data. Unpacking libglib2.0-data (from .../libglib2.0-data_2.27.93-0ubuntu1_all.deb) ... Selecting previously deselected package libglib2.0-bin. Unpacking libglib2.0-bin (from .../libglib2.0-bin_2.27.93-0ubuntu1_i386.deb) ... Selecting previously deselected package zlib1g-dev. Unpacking zlib1g-dev (from .../zlib1g-dev_1%3a1.2.3.4.dfsg-3ubuntu1_i386.deb) ... Selecting previously deselected package libglib2.0-dev. Unpacking libglib2.0-dev (from .../libglib2.0-dev_2.27.93-0ubuntu1_i386.deb) ... Selecting previously deselected package libatk1.0-dev. Unpacking libatk1.0-dev (from .../libatk1.0-dev_1.33.6-0ubuntu1_i386.deb) ... Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from .../libavahi-common-data_0.6.28-2ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-common3. Unpacking libavahi-common3 (from .../libavahi-common3_0.6.28-2ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-client3. Unpacking libavahi-client3 (from .../libavahi-client3_0.6.28-2ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-common-dev. Unpacking libavahi-common-dev (from .../libavahi-common-dev_0.6.28-2ubuntu2_i386.deb) ... Selecting previously deselected package libdbus-1-dev. Unpacking libdbus-1-dev (from .../libdbus-1-dev_1.4.1-0ubuntu2_i386.deb) ... Selecting previously deselected package libavahi-client-dev. Unpacking libavahi-client-dev (from .../libavahi-client-dev_0.6.28-2ubuntu2_i386.deb) ... Selecting previously deselected package libcairo-gobject2. Unpacking libcairo-gobject2 (from .../libcairo-gobject2_1.10.2-1ubuntu1_i386.deb) ... Selecting previously deselected package libexpat1-dev. Unpacking libexpat1-dev (from .../libexpat1-dev_2.0.1-7ubuntu1_i386.deb) ... Selecting previously deselected package libfreetype6-dev. Unpacking libfreetype6-dev (from .../libfreetype6-dev_2.4.2-2.1_i386.deb) ... Selecting previously deselected package libfontconfig1-dev. Unpacking libfontconfig1-dev (from .../libfontconfig1-dev_2.8.0-2.1ubuntu1_i386.deb) ... Selecting previously deselected package x11proto-render-dev. Unpacking x11proto-render-dev (from .../x11proto-render-dev_2%3a0.11.1-1_all.deb) ... Selecting previously deselected package libxrender-dev. Unpacking libxrender-dev (from .../libxrender-dev_1%3a0.9.6-1_i386.deb) ... Selecting previously deselected package libpng12-dev. Unpacking libpng12-dev (from .../libpng12-dev_1.2.44-1ubuntu1_i386.deb) ... Selecting previously deselected package libsm-dev. Unpacking libsm-dev (from .../libsm-dev_2%3a1.2.0-1_i386.deb) ... Selecting previously deselected package libpixman-1-dev. Unpacking libpixman-1-dev (from .../libpixman-1-dev_0.18.4-1build1_i386.deb) ... Selecting previously deselected package libxcb-render0-dev. Unpacking libxcb-render0-dev (from .../libxcb-render0-dev_1.6-1_i386.deb) ... Selecting previously deselected package libxcb-shm0-dev. Unpacking libxcb-shm0-dev (from .../libxcb-shm0-dev_1.6-1_i386.deb) ... Selecting previously deselected package libcairo2-dev. Unpacking libcairo2-dev (from .../libcairo2-dev_1.10.2-1ubuntu1_i386.deb) ... Selecting previously deselected package libltdl7. Unpacking libltdl7 (from .../libltdl7_2.2.6b-2ubuntu1_i386.deb) ... Selecting previously deselected package libtdb1. Unpacking libtdb1 (from .../libtdb1_1.2.9-1fakesync1_i386.deb) ... Selecting previously deselected package libogg0. Unpacking libogg0 (from .../libogg0_1.2.0~dfsg-1_i386.deb) ... Selecting previously deselected package libvorbis0a. Unpacking libvorbis0a (from .../libvorbis0a_1.3.1-1ubuntu1_i386.deb) ... Selecting previously deselected package libvorbisfile3. Unpacking libvorbisfile3 (from .../libvorbisfile3_1.3.1-1ubuntu1_i386.deb) ... Selecting previously deselected package libcanberra0. Unpacking libcanberra0 (from .../libcanberra0_0.26-1ubuntu9_i386.deb) ... Selecting previously deselected package libcanberra-dev. Unpacking libcanberra-dev (from .../libcanberra-dev_0.26-1ubuntu9_i386.deb) ... Selecting previously deselected package libcanberra-gtk-common-dev. Unpacking libcanberra-gtk-common-dev (from .../libcanberra-gtk-common-dev_0.26-1ubuntu9_all.deb) ... Selecting previously deselected package libgtk2.0-common. Unpacking libgtk2.0-common (from .../libgtk2.0-common_2.24.0-0ubuntu1_all.deb) ... Selecting previously deselected package libcups2. Unpacking libcups2 (from .../libcups2_1.4.5-1ubuntu6_i386.deb) ... Selecting previously deselected package libjasper1. Unpacking libjasper1 (from .../libjasper1_1.900.1-7_i386.deb) ... Selecting previously deselected package libtiff4. Unpacking libtiff4 (from .../libtiff4_3.9.4-5_i386.deb) ... Selecting previously deselected package libgdk-pixbuf2.0-0. Unpacking libgdk-pixbuf2.0-0 (from .../libgdk-pixbuf2.0-0_2.23.0-1ubuntu1_i386.deb) ... Selecting previously deselected package libdatrie1. Unpacking libdatrie1 (from .../libdatrie1_0.2.4-1_i386.deb) ... Selecting previously deselected package libthai-data. Unpacking libthai-data (from .../libthai-data_0.1.14-2_all.deb) ... Selecting previously deselected package libthai0. Unpacking libthai0 (from .../libthai0_0.1.14-2_i386.deb) ... Selecting previously deselected package libxft2. Unpacking libxft2 (from .../libxft2_2.1.14-2ubuntu1_i386.deb) ... Selecting previously deselected package libpango1.0-0. Unpacking libpango1.0-0 (from .../libpango1.0-0_1.28.3-4_i386.deb) ... Selecting previously deselected package libxcomposite1. Unpacking libxcomposite1 (from .../libxcomposite1_1%3a0.4.3-1_i386.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.5-1_i386.deb) ... Selecting previously deselected package libxcursor1. Unpacking libxcursor1 (from .../libxcursor1_1%3a1.1.11-1_i386.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.3-1_i386.deb) ... Selecting previously deselected package libxi6. Unpacking libxi6 (from .../libxi6_2%3a1.4.0-1_i386.deb) ... Selecting previously deselected package libxinerama1. Unpacking libxinerama1 (from .../libxinerama1_2%3a1.1.1-1_i386.deb) ... Selecting previously deselected package libxrandr2. Unpacking libxrandr2 (from .../libxrandr2_2%3a1.3.1-1_i386.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.90-0ubuntu1_i386.deb) ... Selecting previously deselected package libgtk2.0-0. Unpacking libgtk2.0-0 (from .../libgtk2.0-0_2.24.0-0ubuntu1_i386.deb) ... Selecting previously deselected package libcanberra-gtk0. Unpacking libcanberra-gtk0 (from .../libcanberra-gtk0_0.26-1ubuntu9_i386.deb) ... Selecting previously deselected package libgdk-pixbuf2.0-dev. Unpacking libgdk-pixbuf2.0-dev (from .../libgdk-pixbuf2.0-dev_2.23.0-1ubuntu1_i386.deb) ... Selecting previously deselected package libxft-dev. Unpacking libxft-dev (from .../libxft-dev_2.1.14-2ubuntu1_i386.deb) ... Selecting previously deselected package libpango1.0-dev. Unpacking libpango1.0-dev (from .../libpango1.0-dev_1.28.3-4_i386.deb) ... Selecting previously deselected package x11proto-xext-dev. Unpacking x11proto-xext-dev (from .../x11proto-xext-dev_7.1.99.0~git20110111.9df8b776-0ubuntu2_all.deb) ... Selecting previously deselected package libxext-dev. Unpacking libxext-dev (from .../libxext-dev_2%3a1.1.2-1_i386.deb) ... Selecting previously deselected package x11proto-xinerama-dev. Unpacking x11proto-xinerama-dev (from .../x11proto-xinerama-dev_1.2.1-1_all.deb) ... Selecting previously deselected package libxinerama-dev. Unpacking libxinerama-dev (from .../libxinerama-dev_2%3a1.1.1-1_i386.deb) ... Selecting previously deselected package libxi-dev. Unpacking libxi-dev (from .../libxi-dev_2%3a1.4.0-1_i386.deb) ... Selecting previously deselected package x11proto-randr-dev. Unpacking x11proto-randr-dev (from .../x11proto-randr-dev_1.4.0+git20101207.0d32bb07-0ubuntu1_all.deb) ... Selecting previously deselected package libxrandr-dev. Unpacking libxrandr-dev (from .../libxrandr-dev_2%3a1.3.1-1_i386.deb) ... Selecting previously deselected package x11proto-fixes-dev. Unpacking x11proto-fixes-dev (from .../x11proto-fixes-dev_1%3a4.1.2-1_all.deb) ... Selecting previously deselected package libxfixes-dev. Unpacking libxfixes-dev (from .../libxfixes-dev_1%3a4.0.5-1_i386.deb) ... Selecting previously deselected package libxcursor-dev. Unpacking libxcursor-dev (from .../libxcursor-dev_1%3a1.1.11-1_i386.deb) ... Selecting previously deselected package x11proto-composite-dev. Unpacking x11proto-composite-dev (from .../x11proto-composite-dev_1%3a0.4.2-1_all.deb) ... Selecting previously deselected package libxcomposite-dev. Unpacking libxcomposite-dev (from .../libxcomposite-dev_1%3a0.4.3-1_i386.deb) ... Selecting previously deselected package x11proto-damage-dev. Unpacking x11proto-damage-dev (from .../x11proto-damage-dev_1%3a1.2.1-1_all.deb) ... Selecting previously deselected package libxdamage-dev. Unpacking libxdamage-dev (from .../libxdamage-dev_1%3a1.1.3-1_i386.deb) ... Selecting previously deselected package libgtk2.0-dev. Unpacking libgtk2.0-dev (from .../libgtk2.0-dev_2.24.0-0ubuntu1_i386.deb) ... Selecting previously deselected package libcanberra-gtk-dev. Unpacking libcanberra-gtk-dev (from .../libcanberra-gtk-dev_0.26-1ubuntu9_i386.deb) ... Selecting previously deselected package libgpg-error-dev. Unpacking libgpg-error-dev (from .../libgpg-error-dev_1.10-0.2_i386.deb) ... Selecting previously deselected package libgcrypt11-dev. Unpacking libgcrypt11-dev (from .../libgcrypt11-dev_1.4.6-4_i386.deb) ... Selecting previously deselected package libtasn1-3-dev. Unpacking libtasn1-3-dev (from .../libtasn1-3-dev_2.7-1_i386.deb) ... Selecting previously deselected package libgnutls-dev. Unpacking libgnutls-dev (from .../libgnutls-dev_2.8.6-1ubuntu1_i386.deb) ... Selecting previously deselected package libkrb5-dev. Unpacking libkrb5-dev (from .../libkrb5-dev_1.8.3+dfsg-4_i386.deb) ... Selecting previously deselected package libcups2-dev. Unpacking libcups2-dev (from .../libcups2-dev_1.4.5-1ubuntu6_i386.deb) ... Selecting previously deselected package libdbus-glib-1-dev. Unpacking libdbus-glib-1-dev (from .../libdbus-glib-1-dev_0.88-2.1_i386.deb) ... Selecting previously deselected package libexif12. Unpacking libexif12 (from .../libexif12_0.6.19-1_i386.deb) ... Selecting previously deselected package libexif-dev. Unpacking libexif-dev (from .../libexif-dev_0.6.19-1_i386.deb) ... Selecting previously deselected package libidl-dev. Unpacking libidl-dev (from .../libidl-dev_0.8.14-0.1_i386.deb) ... Selecting previously deselected package liborbit2-dev. Unpacking liborbit2-dev (from .../liborbit2-dev_1%3a2.14.18-0.1build1_i386.deb) ... Selecting previously deselected package libgconf2-dev. Unpacking libgconf2-dev (from .../libgconf2-dev_2.32.1-2ubuntu2_i386.deb) ... Selecting previously deselected package libxcb-atom1. Unpacking libxcb-atom1 (from .../libxcb-atom1_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libxcb-aux0. Unpacking libxcb-aux0 (from .../libxcb-aux0_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libxcb-event1. Unpacking libxcb-event1 (from .../libxcb-event1_0.3.6-1build1_i386.deb) ... Selecting previously deselected package libstartup-notification0. Unpacking libstartup-notification0 (from .../libstartup-notification0_0.10-1build1_i386.deb) ... Selecting previously deselected package libgnome-desktop-2-17. Unpacking libgnome-desktop-2-17 (from .../libgnome-desktop-2-17_1%3a2.32.1-0ubuntu2_i386.deb) ... Selecting previously deselected package libstartup-notification0-dev. Unpacking libstartup-notification0-dev (from .../libstartup-notification0-dev_0.10-1build1_i386.deb) ... Selecting previously deselected package libgnome-desktop-dev. Unpacking libgnome-desktop-dev (from .../libgnome-desktop-dev_1%3a2.32.1-0ubuntu2_i386.deb) ... Selecting previously deselected package libgphoto2-port0. Unpacking libgphoto2-port0 (from .../libgphoto2-port0_2.4.10.1-2ubuntu4_i386.deb) ... Selecting previously deselected package libgphoto2-2. Unpacking libgphoto2-2 (from .../libgphoto2-2_2.4.10.1-2ubuntu4_i386.deb) ... Selecting previously deselected package libusb-dev. Unpacking libusb-dev (from .../libusb-dev_2%3a0.1.12-16_i386.deb) ... Selecting previously deselected package libgphoto2-2-dev. Unpacking libgphoto2-2-dev (from .../libgphoto2-2-dev_2.4.10.1-2ubuntu4_i386.deb) ... Selecting previously deselected package libgudev-1.0-0. Unpacking libgudev-1.0-0 (from .../libgudev-1.0-0_1%3a165-0ubuntu2_i386.deb) ... Selecting previously deselected package libudev-dev. Unpacking libudev-dev (from .../libudev-dev_165-0ubuntu2_i386.deb) ... Selecting previously deselected package libgudev-1.0-dev. Unpacking libgudev-1.0-dev (from .../libgudev-1.0-dev_1%3a165-0ubuntu2_i386.deb) ... Selecting previously deselected package libieee1284-3. Unpacking libieee1284-3 (from .../libieee1284-3_0.2.11-5ubuntu4_i386.deb) ... Selecting previously deselected package libieee1284-3-dev. Unpacking libieee1284-3-dev (from .../libieee1284-3-dev_0.2.11-5ubuntu4_i386.deb) ... Selecting previously deselected package libjpeg62-dev. Unpacking libjpeg62-dev (from .../libjpeg62-dev_6b1-1_i386.deb) ... Selecting previously deselected package liblcms1-dev. Unpacking liblcms1-dev (from .../liblcms1-dev_1.18.dfsg-1.2ubuntu1_i386.deb) ... Selecting previously deselected package libnotify1. Unpacking libnotify1 (from .../libnotify1_0.5.0-2ubuntu1_i386.deb) ... Selecting previously deselected package libnotify-dev. Unpacking libnotify-dev (from .../libnotify-dev_0.5.0-2ubuntu1_i386.deb) ... Selecting previously deselected package libv4l-0. Unpacking libv4l-0 (from .../libv4l-0_0.8.1-2_i386.deb) ... Selecting previously deselected package libsane. Unpacking libsane (from .../libsane_1.0.21-9ubuntu1_i386.deb) ... Selecting previously deselected package libtiffxx0c2. Unpacking libtiffxx0c2 (from .../libtiffxx0c2_3.9.4-5_i386.deb) ... Selecting previously deselected package libtiff4-dev. Unpacking libtiff4-dev (from .../libtiff4-dev_3.9.4-5_i386.deb) ... Selecting previously deselected package libv4l-dev. Unpacking libv4l-dev (from .../libv4l-dev_0.8.1-2_i386.deb) ... Selecting previously deselected package libsane-dev. Unpacking libsane-dev (from .../libsane-dev_1.0.21-9ubuntu1_i386.deb) ... Selecting previously deselected package libunique-1.0-0. Unpacking libunique-1.0-0 (from .../libunique-1.0-0_1.1.6-1.1ubuntu2_i386.deb) ... Selecting previously deselected package libunique-dev. Unpacking libunique-dev (from .../libunique-dev_1.1.6-1.1ubuntu2_i386.deb) ... Selecting previously deselected package libvte-common. Unpacking libvte-common (from .../libvte-common_1%3a0.27.5-0ubuntu1_all.deb) ... Selecting previously deselected package libvte9. Unpacking libvte9 (from .../libvte9_1%3a0.27.5-0ubuntu1_i386.deb) ... Selecting previously deselected package python-gtk2. Unpacking python-gtk2 (from .../python-gtk2_2.22.0-0ubuntu1_i386.deb) ... Selecting previously deselected package python-vte. Unpacking python-vte (from .../python-vte_1%3a0.27.5-0ubuntu1_i386.deb) ... Selecting previously deselected package libvte-dev. Unpacking libvte-dev (from .../libvte-dev_1%3a0.27.5-0ubuntu1_i386.deb) ... Selecting previously deselected package libxxf86vm1. Unpacking libxxf86vm1 (from .../libxxf86vm1_1%3a1.1.1-1_i386.deb) ... Selecting previously deselected package x11proto-xf86vidmode-dev. Unpacking x11proto-xf86vidmode-dev (from .../x11proto-xf86vidmode-dev_2.3.1-1_all.deb) ... Selecting previously deselected package libxxf86vm-dev. Unpacking libxxf86vm-dev (from .../libxxf86vm-dev_1%3a1.1.1-1_i386.deb) ... Selecting previously deselected package librarian0. Unpacking librarian0 (from .../librarian0_0.8.1-5_i386.deb) ... Selecting previously deselected package rarian-compat. Unpacking rarian-compat (from .../rarian-compat_0.8.1-5_i386.deb) ... Selecting previously deselected package scrollkeeper. Unpacking scrollkeeper (from .../scrollkeeper_0.8.1-5_all.deb) ... Processing triggers for libglib2.0-0 ... Setting up sgml-data (2.0.5) ... Setting up docbook-xml (4.5-7) ... Setting up libice6 (2:1.0.7-1) ... Setting up x11proto-core-dev (7.0.20-1) ... Setting up libice-dev (2:1.0.7-1) ... Setting up libxau6 (1:1.0.6-1) ... Setting up libxdmcp6 (1:1.1.0-1) ... Setting up libxcb1 (1.6-1) ... Setting up libx11-data (2:1.3.3-3ubuntu3) ... Setting up libx11-6 (2:1.3.3-3ubuntu3) ... Setting up libxau-dev (1:1.0.6-1) ... Setting up libxdmcp-dev (1:1.1.0-1) ... Setting up x11proto-input-dev (2.0.1-1) ... Setting up x11proto-kb-dev (1.0.5-1) ... Setting up xtrans-dev (1.2.6-1) ... Setting up libpthread-stubs0 (0.3-2) ... Setting up libpthread-stubs0-dev (0.3-2) ... Setting up libxcb1-dev (1.6-1) ... Setting up libx11-dev (2:1.3.3-3ubuntu3) ... Setting up libmagic1 (5.04-5ubuntu2) ... Setting up file (5.04-5ubuntu2) ... Setting up libexpat1 (2.0.1-7ubuntu1) ... Setting up libpopt0 (1.16-1) ... Setting up libsqlite3-0 (3.7.4-2ubuntu2) ... Setting up mime-support (3.51-1ubuntu1) ... update-alternatives: using /usr/bin/see to provide /usr/bin/view (view) in auto mode. Setting up python2.7 (2.7.1-3) ... Setting up python (2.7.1-0ubuntu5) ... Setting up ucf (3.0025+nmu1) ... Setting up bsdmainutils (8.2.2) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode. update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode. Setting up ed (1.5-1) ... Setting up ttf-dejavu-core (2.31-1) ... Setting up fontconfig-config (2.8.0-2.1ubuntu1) ... Setting up gettext-base (0.18.1.1-3ubuntu1) ... Setting up libffi5 (3.0.9-3) ... Setting up libgirepository-1.0-1 (0.10.1+git20110201-0ubuntu1) ... Setting up gir1.2-glib-2.0 (0.10.1+git20110201-0ubuntu1) ... Setting up groff-base (1.21-3) ... Setting up libbsd0 (0.2.0-1) ... Setting up libfreetype6 (2.4.2-2.1) ... Setting up libfontconfig1 (2.8.0-2.1ubuntu1) ... Setting up libpixman-1-0 (0.18.4-1build1) ... Setting up libxcb-render0 (1.6-1) ... Setting up libxcb-shm0 (1.6-1) ... Setting up libxrender1 (1:0.9.6-1) ... Setting up libcairo2 (1.10.2-1ubuntu1) ... Setting up libdbus-glib-1-2 (0.88-2.1) ... Setting up liburi-perl (1.56-1) ... Setting up libhtml-tagset-perl (3.20-2) ... Setting up libhtml-parser-perl (3.68-1) ... Setting up libhtml-tree-perl (4.1-1) ... Setting up libpipeline1 (1.1.0-1) ... Setting up libwww-perl (5.837-1) ... Setting up libxext6 (2:1.1.2-1) ... Setting up libxml-parser-perl (2.36-1.1build3) ... Setting up libxml2 (2.7.8.dfsg-2) ... Setting up man-db (2.5.9-3) ... Building database of manual pages ... Setting up psmisc (22.13-1) ... Setting up python-support (1.0.10ubuntu3) ... Setting up python-cairo (1.8.8-1ubuntu1) ... Setting up libpython2.7 (2.7.1-3) ... Setting up python-gobject (2.27.0+git20110131-0ubuntu6) ... Setting up m4 (1.4.14-3) ... Setting up autoconf (2.67-2ubuntu1) ... Setting up autotools-dev (20100122.1) ... Setting up automake (1:1.11.1-1ubuntu1) ... update-alternatives: using /usr/bin/automake-1.11 to provide /usr/bin/automake (automake) in auto mode. Setting up dbus (1.4.1-0ubuntu2) ... Setting up dbus-x11 (1.4.1-0ubuntu2) ... Setting up html2text (1.3.2a-15) ... Setting up libcroco3 (0.6.2-1) ... Setting up libunistring0 (0.9.3-3) ... Setting up gettext (0.18.1.1-3ubuntu1) ... Setting up intltool-debian (0.35.0+20060710.1) ... Setting up po-debconf (1.0.16+nmu1) ... Setting up debhelper (8.0.0ubuntu2) ... Setting up libtool (2.2.6b-2ubuntu1) ... Setting up dh-autoreconf (2) ... Setting up docbook (4.5-4) ... Setting up libosp5 (1.5.2-8) ... Setting up libostyle1c2 (1.4devel1-19build1) ... Setting up openjade (1.4devel1-19build1) ... Setting up libsp1c2 (1.3.4-1.2.1-47build3) ... Setting up jade (1.2.1-47build3) ... Setting up docbook-dsssl (1.79-6) ... Setting up sp (1.3.4-1.2.1-47build3) ... Setting up docbook-to-man (1:2.0.0-28) ... Setting up tex-common (2.08) ... Creating config file /etc/texmf/texmf.d/05TeXMF.cnf with new version Creating config file /etc/texmf/texmf.d/15Plain.cnf with new version Creating config file /etc/texmf/texmf.d/45TeXinputs.cnf with new version Creating config file /etc/texmf/texmf.d/55Fonts.cnf with new version Creating config file /etc/texmf/texmf.d/65BibTeX.cnf with new version Creating config file /etc/texmf/texmf.d/75DviPS.cnf with new version Creating config file /etc/texmf/texmf.d/80DVIPDFMx.cnf with new version Creating config file /etc/texmf/texmf.d/85Misc.cnf with new version Creating config file /etc/texmf/texmf.d/90TeXDoc.cnf with new version Creating config file /etc/texmf/texmf.d/95NonPath.cnf with new version Creating config file /etc/texmf/updmap.d/00updmap.cfg with new version Creating config file /etc/texmf/texmf.cnf with new version Running mktexlsr. This may take some time... done. texlive-base is not ready, delaying updmap-sys call texlive-base is not ready, skipping fmtutil-sys --all call Setting up texlive-common (2009-11) ... Setting up texlive-doc-base (2009-2) ... Setting up libjpeg62 (6b1-1) ... Setting up liblcms1 (1.18.dfsg-1.2ubuntu1) ... Setting up libpoppler12 (0.16.0-0ubuntu2) ... Setting up luatex (0.65.0-1ubuntu2) ... texlive-base is not ready, cannot create formats Setting up libkpathsea5 (2009-8build1) ... Setting up libsm6 (2:1.2.0-1) ... Setting up libxt6 (1:1.0.9-1) ... Setting up libxmu6 (2:1.1.0-1) ... Setting up libxpm4 (1:3.5.9-1ubuntu1) ... Setting up libxaw7 (2:1.0.8-2) ... Setting up texlive-binaries (2009-8build1) ... update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin (xdvi.bin) in auto mode. update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex (bibtex) in auto mode. Building format(s) --refresh. This may take some time... done. Setting up lynx-cur (2.8.8dev.7-1) ... update-alternatives: using /usr/bin/lynx.cur to provide /usr/bin/www-browser (www-browser) in auto mode. update-alternatives: using /usr/bin/lynx.cur to provide /usr/bin/lynx (lynx) in auto mode. Setting up lynx (2.8.8dev.7-1) ... Setting up libsgmls-perl (1.03ii-32) ... Setting up sgmlspl (1.03ii-32) ... Setting up docbook-xsl (1.75.2+dfsg-5ubuntu1) ... Setting up fontconfig (2.8.0-2.1ubuntu1) ... Cleaning up old fontconfig caches... done. Regenerating fonts cache... done. Setting up libidl0 (0.8.14-0.1) ... Setting up liborbit2 (1:2.14.18-0.1build1) ... Setting up gconf2-common (2.32.1-2ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libgconf2-4 (2.32.1-2ubuntu2) ... Setting up gconf2 (2.32.1-2ubuntu2) ... update-alternatives: using /usr/bin/gconftool-2 to provide /usr/bin/gconftool (gconftool) in auto mode. Setting up pkg-config (0.25-1.1) ... Setting up intltool (0.41.1-1) ... Setting up gnome-common (2.28.0-1) ... Setting up python-libxml2 (2.7.8.dfsg-2) ... Setting up libxml2-utils (2.7.8.dfsg-2) ... Setting up libxslt1.1 (1.1.26-6build1) ... Setting up xsltproc (1.1.26-6build1) ... Setting up gnome-doc-utils (0.20.4-2build1) ... Setting up gnome-pkg-tools (0.16.3ubuntu1) ... Setting up gtk-doc-tools (1.16-0ubuntu1) ... Setting up libgssrpc4 (1.8.3+dfsg-4) ... Setting up libkdb5-4 (1.8.3+dfsg-4) ... Setting up libkadm5srv-mit7 (1.8.3+dfsg-4) ... Setting up libkadm5clnt-mit7 (1.8.3+dfsg-4) ... Setting up comerr-dev (2.1-1.41.14-1ubuntu1) ... Setting up krb5-multidev (1.8.3+dfsg-4) ... Setting up libasound2 (1.0.23-2.1ubuntu2) ... Setting up libatk1.0-data (1.33.6-0ubuntu1) ... Setting up libatk1.0-0 (1.33.6-0ubuntu1) ... Setting up libglib2.0-data (2.27.93-0ubuntu1) ... Setting up libglib2.0-bin (2.27.93-0ubuntu1) ... Setting up zlib1g-dev (1:1.2.3.4.dfsg-3ubuntu1) ... Setting up libglib2.0-dev (2.27.93-0ubuntu1) ... Setting up libatk1.0-dev (1.33.6-0ubuntu1) ... Setting up libavahi-common-data (0.6.28-2ubuntu2) ... Setting up libavahi-common3 (0.6.28-2ubuntu2) ... Setting up libavahi-client3 (0.6.28-2ubuntu2) ... Setting up libavahi-common-dev (0.6.28-2ubuntu2) ... Setting up libdbus-1-dev (1.4.1-0ubuntu2) ... Setting up libavahi-client-dev (0.6.28-2ubuntu2) ... Setting up libcairo-gobject2 (1.10.2-1ubuntu1) ... Setting up libexpat1-dev (2.0.1-7ubuntu1) ... Setting up libfreetype6-dev (2.4.2-2.1) ... Setting up libfontconfig1-dev (2.8.0-2.1ubuntu1) ... Setting up x11proto-render-dev (2:0.11.1-1) ... Setting up libxrender-dev (1:0.9.6-1) ... Setting up libpng12-dev (1.2.44-1ubuntu1) ... Setting up libsm-dev (2:1.2.0-1) ... Setting up libpixman-1-dev (0.18.4-1build1) ... Setting up libxcb-render0-dev (1.6-1) ... Setting up libxcb-shm0-dev (1.6-1) ... Setting up libcairo2-dev (1.10.2-1ubuntu1) ... Setting up libltdl7 (2.2.6b-2ubuntu1) ... Setting up libtdb1 (1.2.9-1fakesync1) ... Setting up libogg0 (1.2.0~dfsg-1) ... Setting up libvorbis0a (1.3.1-1ubuntu1) ... Setting up libvorbisfile3 (1.3.1-1ubuntu1) ... Setting up libcanberra0 (0.26-1ubuntu9) ... Setting up libcanberra-dev (0.26-1ubuntu9) ... Setting up libcanberra-gtk-common-dev (0.26-1ubuntu9) ... Setting up libgtk2.0-common (2.24.0-0ubuntu1) ... Setting up libcups2 (1.4.5-1ubuntu6) ... Setting up libjasper1 (1.900.1-7) ... Setting up libtiff4 (3.9.4-5) ... Setting up libgdk-pixbuf2.0-0 (2.23.0-1ubuntu1) ... Setting up libdatrie1 (0.2.4-1) ... Setting up libthai-data (0.1.14-2) ... Setting up libthai0 (0.1.14-2) ... Setting up libxft2 (2.1.14-2ubuntu1) ... Setting up libpango1.0-0 (1.28.3-4) ... Setting up libxcomposite1 (1:0.4.3-1) ... Setting up libxfixes3 (1:4.0.5-1) ... Setting up libxcursor1 (1:1.1.11-1) ... Setting up libxdamage1 (1:1.1.3-1) ... Setting up libxi6 (2:1.4.0-1) ... Setting up libxinerama1 (2:1.1.1-1) ... Setting up libxrandr2 (2:1.3.1-1) ... Setting up shared-mime-info (0.90-0ubuntu1) ... Setting up libgtk2.0-0 (2.24.0-0ubuntu1) ... Setting up libcanberra-gtk0 (0.26-1ubuntu9) ... Setting up libgdk-pixbuf2.0-dev (2.23.0-1ubuntu1) ... Setting up libxft-dev (2.1.14-2ubuntu1) ... Setting up libpango1.0-dev (1.28.3-4) ... Setting up x11proto-xext-dev (7.1.99.0~git20110111.9df8b776-0ubuntu2) ... Setting up libxext-dev (2:1.1.2-1) ... Setting up x11proto-xinerama-dev (1.2.1-1) ... Setting up libxinerama-dev (2:1.1.1-1) ... Setting up libxi-dev (2:1.4.0-1) ... Setting up x11proto-randr-dev (1.4.0+git20101207.0d32bb07-0ubuntu1) ... Setting up libxrandr-dev (2:1.3.1-1) ... Setting up x11proto-fixes-dev (1:4.1.2-1) ... Setting up libxfixes-dev (1:4.0.5-1) ... Setting up libxcursor-dev (1:1.1.11-1) ... Setting up x11proto-composite-dev (1:0.4.2-1) ... Setting up libxcomposite-dev (1:0.4.3-1) ... Setting up x11proto-damage-dev (1:1.2.1-1) ... Setting up libxdamage-dev (1:1.1.3-1) ... Setting up libgtk2.0-dev (2.24.0-0ubuntu1) ... Setting up libcanberra-gtk-dev (0.26-1ubuntu9) ... Setting up libgpg-error-dev (1.10-0.2) ... Setting up libgcrypt11-dev (1.4.6-4) ... Setting up libtasn1-3-dev (2.7-1) ... Setting up libgnutls-dev (2.8.6-1ubuntu1) ... Setting up libkrb5-dev (1.8.3+dfsg-4) ... Setting up libcups2-dev (1.4.5-1ubuntu6) ... Setting up libdbus-glib-1-dev (0.88-2.1) ... Setting up libexif12 (0.6.19-1) ... Setting up libexif-dev (0.6.19-1) ... Setting up libidl-dev (0.8.14-0.1) ... Setting up liborbit2-dev (1:2.14.18-0.1build1) ... Setting up libgconf2-dev (2.32.1-2ubuntu2) ... Setting up libxcb-atom1 (0.3.6-1build1) ... Setting up libxcb-aux0 (0.3.6-1build1) ... Setting up libxcb-event1 (0.3.6-1build1) ... Setting up libstartup-notification0 (0.10-1build1) ... Setting up libgnome-desktop-2-17 (1:2.32.1-0ubuntu2) ... Setting up libstartup-notification0-dev (0.10-1build1) ... Setting up libgnome-desktop-dev (1:2.32.1-0ubuntu2) ... Setting up libgphoto2-port0 (2.4.10.1-2ubuntu4) ... Setting up libgphoto2-2 (2.4.10.1-2ubuntu4) ... Setting up libusb-dev (2:0.1.12-16) ... Setting up libgphoto2-2-dev (2.4.10.1-2ubuntu4) ... Setting up libgudev-1.0-0 (1:165-0ubuntu2) ... Setting up libudev-dev (165-0ubuntu2) ... Setting up libgudev-1.0-dev (1:165-0ubuntu2) ... Setting up libieee1284-3 (0.2.11-5ubuntu4) ... Setting up libieee1284-3-dev (0.2.11-5ubuntu4) ... Setting up libjpeg62-dev (6b1-1) ... Setting up liblcms1-dev (1.18.dfsg-1.2ubuntu1) ... Setting up libnotify1 (0.5.0-2ubuntu1) ... Setting up libnotify-dev (0.5.0-2ubuntu1) ... Setting up libv4l-0 (0.8.1-2) ... Setting up libsane (1.0.21-9ubuntu1) ... Setting up libtiffxx0c2 (3.9.4-5) ... Setting up libtiff4-dev (3.9.4-5) ... Setting up libv4l-dev (0.8.1-2) ... Setting up libsane-dev (1.0.21-9ubuntu1) ... Setting up libunique-1.0-0 (1.1.6-1.1ubuntu2) ... Setting up libunique-dev (1.1.6-1.1ubuntu2) ... Setting up libvte-common (1:0.27.5-0ubuntu1) ... Setting up libvte9 (1:0.27.5-0ubuntu1) ... Setting up python-gtk2 (2.22.0-0ubuntu1) ... Setting up python-vte (1:0.27.5-0ubuntu1) ... Setting up libvte-dev (1:0.27.5-0ubuntu1) ... Setting up libxxf86vm1 (1:1.1.1-1) ... Setting up x11proto-xf86vidmode-dev (2.3.1-1) ... Setting up libxxf86vm-dev (1:1.1.1-1) ... Setting up librarian0 (0.8.1-5) ... Setting up rarian-compat (0.8.1-5) ... Setting up scrollkeeper (0.8.1-5) ... Processing triggers for tex-common ... Running mktexlsr. This may take some time... done. Setting up texlive-base (2009-11) ... Running mktexlsr. This may take some time... done. Building format(s) --all --cnffile /etc/texmf/fmt.d/10texlive-base.cnf. This may take some time... done. Processing triggers for tex-common ... Running updmap-sys. This may take some time... done. Building e-tex based formats --byhyphen /var/lib/texmf/tex/generic/config/language.def. This may take some time... done. Setting up texlive-latex-base (2009-11) ... Running mktexlsr. This may take some time... done. Building format(s) --all --cnffile /etc/texmf/fmt.d/10texlive-latex-base.cnf. This may take some time... done. Setting up texlive-fonts-recommended (2009-11) ... Processing triggers for tex-common ... Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... done. Setting up texlive-latex-recommended (2009-11) ... Setting up tipa (2:1.3-14) ... Running mktexlsr. This may take some time... done. Processing triggers for tex-common ... Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... done. Setting up jadetex (3.13-12) ... Replacing config file /etc/texmf/texmf.cnf with new version Running mktexlsr. This may take some time... done. Building format(s) --all --cnffile /etc/texmf/fmt.d/40jadetex.cnf. This may take some time... done. Setting up docbook-utils (0.6.14-1.1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for python-support ... Checking correctness of source dependencies... Toolchain package versions: libc6-dev_2.12.1-0ubuntu14 make_3.81-8 dpkg-dev_1.15.8.7ubuntu2 gcc-4.5_4.5.2-2ubuntu1 g++-4.5_4.5.2-2ubuntu1 binutils_2.21-5ubuntu1 libstdc++6-4.5-dev_4.5.2-2ubuntu1 libstdc++6_4.5.2-2ubuntu1 ------------------------------------------------------------------------------ dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::quilt gpgv: Signature made Tue Feb 8 02:02:57 2011 UTC using DSA key ID 0F7C882E gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./gnome-color-manager_2.32.0-0ubuntu1.dsc dpkg-source: info: extracting gnome-color-manager in gnome-color-manager-2.32.0 dpkg-source: info: unpacking gnome-color-manager_2.32.0.orig.tar.gz dpkg-source: info: unpacking gnome-color-manager_2.32.0-0ubuntu1.debian.tar.gz dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions dpkg-buildpackage: source package gnome-color-manager dpkg-buildpackage: source version 2.32.0-0ubuntu1 dpkg-source --before-build gnome-color-manager-2.32.0 dpkg-buildpackage: host architecture i386 /usr/bin/fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean dh_clean { cat /usr/share/gnome-pkg-tools/control.header ; \ sed "s/@GNOME_TEAM@/Michael Biebl /" debian/control.in ; } \ > debian/control debian/rules build dh --with autoreconf build dh_testdir dh_autoreconf configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./config.guess' libtoolize: copying file `./config.sub' libtoolize: copying file `./install-sh' libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: You should add the contents of `m4/libtool.m4' to `aclocal.m4'. libtoolize: copying file `m4/ltoptions.m4' libtoolize: You should add the contents of `m4/ltoptions.m4' to `aclocal.m4'. libtoolize: copying file `m4/ltsugar.m4' libtoolize: You should add the contents of `m4/ltsugar.m4' to `aclocal.m4'. libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' libtoolize: You should add the contents of `m4/lt~obsolete.m4' to `aclocal.m4'. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager configure.ac:3: warning: AC_INIT: not a literal: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-color-manager gnome-doc-utils.make:74: if $(DOC_H_FILE: non-POSIX variable name gnome-doc-utils.make:74: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:77: if $(DOC_H_FILE: non-POSIX variable name gnome-doc-utils.make:77: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:118: if $(DOC_USER_FORMATS: non-POSIX variable name gnome-doc-utils.make:118: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:123: if $(filter environment,$(origin LINGUAS: non-POSIX variable name gnome-doc-utils.make:123: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:123: filter $(LINGUAS: non-POSIX variable name gnome-doc-utils.make:123: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:134: if $(DOC_ID: non-POSIX variable name gnome-doc-utils.make:134: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:154: shell xmllint --format $(2: non-POSIX variable name gnome-doc-utils.make:154: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:154: notdir $(patsubst %/$(notdir $(2: non-POSIX variable name gnome-doc-utils.make:154: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:154: if $(_ENABLE_SK: non-POSIX variable name gnome-doc-utils.make:154: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:170: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:170: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:170: wildcard $(_DOC_ABS_SRCDIR: non-POSIX variable name gnome-doc-utils.make:170: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:174: if $(_DOC_OMF_IN: non-POSIX variable name gnome-doc-utils.make:174: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:174: foreach lc,C $(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:174: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:183: call db2omf_args,$@,$<,'docbook': non-POSIX variable name gnome-doc-utils.make:183: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:187: if $(_DOC_OMF_IN: non-POSIX variable name gnome-doc-utils.make:187: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:187: foreach lc,C $(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:187: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:198: call db2omf_args,$@,$<,'xhtml': non-POSIX variable name gnome-doc-utils.make:198: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:203: if $(filter docbook,$(_DOC_REAL_FORMATS: non-POSIX variable name gnome-doc-utils.make:203: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:203: if $(filter html HTML,$(_DOC_REAL_FORMATS: non-POSIX variable name gnome-doc-utils.make:203: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:216: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:216: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:220: foreach page,$(DOC_PAGES: non-POSIX variable name gnome-doc-utils.make:220: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:224: foreach ent,$(DOC_ENTITIES: non-POSIX variable name gnome-doc-utils.make:224: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:228: foreach inc,$(DOC_INCLUDES: non-POSIX variable name gnome-doc-utils.make:228: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:245: if $(DOC_FIGURES: non-POSIX variable name gnome-doc-utils.make:245: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:245: foreach fig,$(DOC_FIGURES: non-POSIX variable name gnome-doc-utils.make:245: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:245: patsubst $(srcdir: non-POSIX variable name gnome-doc-utils.make:245: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:245: wildcard $(srcdir: non-POSIX variable name gnome-doc-utils.make:245: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:252: foreach f, \ gnome-doc-utils.make:252: $(shell xsltproc --xinclude \ gnome-doc-utils.make:252: --stringparam db.chunk.basename "$(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:252: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:263: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:263: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:263: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:263: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:271: patsubst %.po,%.mo,$(_DOC_POFILES: non-POSIX variable name gnome-doc-utils.make:271: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:278: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:278: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:278: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:278: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:283: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:283: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:283: foreach page,$(_DOC_C_PAGES: non-POSIX variable name gnome-doc-utils.make:283: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:283: notdir $(page: non-POSIX variable name gnome-doc-utils.make:283: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:289: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:289: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:289: foreach inc,$(_DOC_C_INCLUDES: non-POSIX variable name gnome-doc-utils.make:289: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:289: notdir $(inc: non-POSIX variable name gnome-doc-utils.make:289: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:296: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:296: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:296: foreach doc,$(_DOC_C_HTML: non-POSIX variable name gnome-doc-utils.make:296: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:296: notdir $(doc: non-POSIX variable name gnome-doc-utils.make:296: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:302: if $(filter html HTML,$(_DOC_REAL_FORMATS: non-POSIX variable name gnome-doc-utils.make:302: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:308: foreach lc,$(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:308: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:308: patsubst C/%,$(lc: non-POSIX variable name gnome-doc-utils.make:308: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:311: foreach fig,$(_DOC_C_FIGURES: non-POSIX variable name gnome-doc-utils.make:311: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:311: foreach lc,C $(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:311: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:311: wildcard $(srcdir: non-POSIX variable name gnome-doc-utils.make:311: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:311: patsubst C/%,%,$(fig: non-POSIX variable name gnome-doc-utils.make:311: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:316: dir $@: non-POSIX variable name gnome-doc-utils.make:316: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:343: dir $@: non-POSIX variable name gnome-doc-utils.make:343: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:353: dir $@: non-POSIX variable name gnome-doc-utils.make:353: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:354: notdir $@: non-POSIX variable name gnome-doc-utils.make:354: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:364: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:364: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:376: if $(filter html HTML,$(_DOC_REAL_FORMATS: non-POSIX variable name gnome-doc-utils.make:376: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:379: foreach lc,C $(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:379: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:382: patsubst %.xhtml,%.xml,$@: non-POSIX variable name gnome-doc-utils.make:382: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:427: if $(_DOC_OMF_IN: non-POSIX variable name gnome-doc-utils.make:427: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:428: if $(_DOC_DSK_IN: non-POSIX variable name gnome-doc-utils.make:428: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:429: if $(_DOC_REAL_LINGUAS: non-POSIX variable name gnome-doc-utils.make:429: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:430: if $(DOC_MODULE: non-POSIX variable name gnome-doc-utils.make:430: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:551: if $(DOC_ID: non-POSIX variable name gnome-doc-utils.make:551: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here gnome-doc-utils.make:578: patsubst C/%,%,$(_DOC_C_FIGURES: non-POSIX variable name gnome-doc-utils.make:578: (probably a GNU make extension) help/Makefile.am:1: `gnome-doc-utils.make' included from here dh_auto_configure configure: WARNING: unrecognized options: --disable-maintainer-mode 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 for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking for ranlib... ranlib checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... (cached) ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether gcc and cc understand -c and -o together... yes checking whether NLS is requested... yes checking for intltool >= 0.35.0... 0.41.1 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.10.1 checking for XML::Parser... ok checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes 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.9.0... yes checking gnome-doc-utils >= 0.3.2... yes checking for gtkdoc-check... /usr/bin/gtkdoc-check checking for gtkdoc-rebase... /usr/bin/gtkdoc-rebase checking for gtkdoc-mkpdf... /usr/bin/gtkdoc-mkpdf checking whether to build gtk-doc documentation... no checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for GLIB... yes checking for XORG... yes checking for GTK... yes checking for GNOMEDESKTOP... yes checking for GCONF... yes checking for UNIQUE... yes checking for VTE... yes checking for GUDEV... yes checking for LCMS... yes checking for DBUS_GLIB... yes checking for X11... yes checking for NOTIFY... yes checking for SANE... yes checking for CANBERRA... yes checking for TIFFReadRGBAImageOriented in -ltiff... yes checking cups/cups.h usability... yes checking cups/cups.h presence... yes checking for cups/cups.h... yes checking for cupsGetDefault in -lcups... 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 for docbook2man... /usr/bin/docbook2man configure: creating ./config.status config.status: creating Makefile config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating data/icons/16x16/Makefile config.status: creating data/icons/22x22/Makefile config.status: creating data/icons/24x24/Makefile config.status: creating data/icons/32x32/Makefile config.status: creating data/icons/48x48/Makefile config.status: creating data/icons/64x64/Makefile config.status: creating data/icons/256x256/Makefile config.status: creating data/icons/scalable/Makefile config.status: creating data/tests/Makefile config.status: creating data/targets/Makefile config.status: creating data/figures/Makefile config.status: creating help/Makefile config.status: creating man/Makefile config.status: creating policy/Makefile config.status: creating po/Makefile.in config.status: creating rules/Makefile config.status: creating src/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands configure: WARNING: unrecognized options: --disable-maintainer-mode gnome-color-manager 2.32.0 ================================ prefix: /usr datadir: ${datarootdir} compiler: gcc cflags: -g -O2 cppflags: PackageKit integration: yes building unit tests: yes gconf-schema dir: $(sysconfdir)/gconf/schemas dh_auto_build make[1]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' make all-recursive make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' Making all in data make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data' Making all in tests make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/tests' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/tests' Making all in targets make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' Making all in figures make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' Making all in icons make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' Making all in scalable make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' Making all in 16x16 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' Making all in 22x22 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' Making all in 24x24 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' Making all in 32x32 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' Making all in 48x48 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' Making all in 64x64 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' Making all in 256x256 make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data' LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gcm-apply.desktop.in gcm-apply.desktop Generating and caching the translation database Merging translations into gcm-apply.desktop. LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gcm-prefs.desktop.in gcm-prefs.desktop Found cached translation database Merging translations into gcm-prefs.desktop. LC_ALL=C /usr/bin/intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gcm-import.desktop.in gcm-import.desktop Found cached translation database Merging translations into gcm-import.desktop. LC_ALL=C /usr/bin/intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gnome-color-manager.schemas.in gnome-color-manager.schemas Found cached translation database Merging translations into gnome-color-manager.schemas. make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data' Making all in help make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/help' msgfmt -o cs/cs.mo cs/cs.po msgfmt -o de/de.mo de/de.po msgfmt -o el/el.mo el/el.po msgfmt -o es/es.mo es/es.po msgfmt -o id/id.mo id/id.po msgfmt -o ru/ru.mo ru/ru.po if ! test -d cs/; then mkdir cs/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="cs/cs.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd cs/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) if ! test -d de/; then mkdir de/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="de/de.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd de/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) if ! test -d el/; then mkdir el/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="el/el.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd el/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) if ! test -d es/; then mkdir es/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="es/es.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd es/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) if ! test -d id/; then mkdir id/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="id/id.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd id/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) if ! test -d ru/; then mkdir ru/; fi if [ -f "C/gnome-color-manager.xml" ]; then d="../"; else d="/build/buildd/gnome-color-manager-2.32.0/help/"; fi; \ mo="ru/ru.mo"; \ if [ -f "${mo}" ]; then mo="../${mo}"; else mo="/build/buildd/gnome-color-manager-2.32.0/help/${mo}"; fi; \ (cd ru/ && \ `which xml2po` -m docbook -e -t "${mo}" \ "${d}C/gnome-color-manager.xml" > gnome-color-manager.xml.tmp && \ cp gnome-color-manager.xml.tmp gnome-color-manager.xml && rm -f gnome-color-manager.xml.tmp) xsltproc -o gnome-color-manager-C.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang C --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` C/gnome-color-manager.xml || { rm -f "gnome-color-manager-C.omf"; exit 1; } xsltproc -o gnome-color-manager-cs.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang cs --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` cs/gnome-color-manager.xml || { rm -f "gnome-color-manager-cs.omf"; exit 1; } xsltproc -o gnome-color-manager-de.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang de --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` de/gnome-color-manager.xml || { rm -f "gnome-color-manager-de.omf"; exit 1; } xsltproc -o gnome-color-manager-el.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang el --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` el/gnome-color-manager.xml || { rm -f "gnome-color-manager-el.omf"; exit 1; } xsltproc -o gnome-color-manager-es.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang es --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` es/gnome-color-manager.xml || { rm -f "gnome-color-manager-es.omf"; exit 1; } xsltproc -o gnome-color-manager-id.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang id --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` id/gnome-color-manager.xml || { rm -f "gnome-color-manager-id.omf"; exit 1; } xsltproc -o gnome-color-manager-ru.omf --stringparam db2omf.basename gnome-color-manager --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.3//EN" --stringparam db2omf.lang ru --stringparam db2omf.omf_dir "/usr/share/omf" --stringparam db2omf.help_dir "/usr/share/gnome/help" --stringparam db2omf.omf_in "/build/buildd/gnome-color-manager-2.32.0/help/gnome-color-manager.omf.in" --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/bin/pkg-config --variable db2omf gnome-doc-utils` ru/gnome-color-manager.xml || { rm -f "gnome-color-manager-ru.omf"; exit 1; } make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/help' Making all in man make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/man' docbook2man gcm-apply.sgml > /dev/null docbook2man gcm-prefs.sgml > /dev/null docbook2man gcm-import.sgml > /dev/null make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/man' Making all in po make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.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 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 fr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fr.po file=`echo gl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file gl.po file=`echo he | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file he.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.po file=`echo id | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file id.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 nb | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nb.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_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo pt | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt.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 sl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sl.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.po file=`echo sr@latin | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr@latin.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo ta | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ta.po file=`echo th | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file th.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po file=`echo zh_HK | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_HK.po file=`echo zh_TW | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_TW.po make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/po' Making all in policy make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/policy' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/policy' Making all in rules make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/rules' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/rules' Making all in src make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' /bin/bash ../libtool --mode=execute dbus-binding-tool \ --prefix=gcm_dbus \ --mode=glib-server \ --output=org.gnome.ColorManager.h \ ./org.gnome.ColorManager.xml make all-am make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' CC libgcmshared_a-egg-debug.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-egg-debug.o `test -f 'egg-debug.c' || echo './'`egg-debug.c CC libgcmshared_a-gcm-image.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-image.o `test -f 'gcm-image.c' || echo './'`gcm-image.c CC libgcmshared_a-gcm-screen.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-screen.o `test -f 'gcm-screen.c' || echo './'`gcm-screen.c CC libgcmshared_a-gcm-xyz.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-xyz.o `test -f 'gcm-xyz.c' || echo './'`gcm-xyz.c CC libgcmshared_a-gcm-print.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-print.o `test -f 'gcm-print.c' || echo './'`gcm-print.c CC libgcmshared_a-gcm-utils.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-utils.o `test -f 'gcm-utils.c' || echo './'`gcm-utils.c CC libgcmshared_a-gcm-enum.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-enum.o `test -f 'gcm-enum.c' || echo './'`gcm-enum.c CC libgcmshared_a-gcm-clut.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-clut.o `test -f 'gcm-clut.c' || echo './'`gcm-clut.c CC libgcmshared_a-gcm-edid.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-edid.o `test -f 'gcm-edid.c' || echo './'`gcm-edid.c CC libgcmshared_a-gcm-dmi.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-dmi.o `test -f 'gcm-dmi.c' || echo './'`gcm-dmi.c CC libgcmshared_a-gcm-tables.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-tables.o `test -f 'gcm-tables.c' || echo './'`gcm-tables.c CC libgcmshared_a-gcm-xserver.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-xserver.o `test -f 'gcm-xserver.c' || echo './'`gcm-xserver.c CC libgcmshared_a-gcm-client.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-client.o `test -f 'gcm-client.c' || echo './'`gcm-client.c CC libgcmshared_a-gcm-colorimeter.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-colorimeter.o `test -f 'gcm-colorimeter.c' || echo './'`gcm-colorimeter.c CC libgcmshared_a-gcm-device.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device.o `test -f 'gcm-device.c' || echo './'`gcm-device.c CC libgcmshared_a-gcm-device-xrandr.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device-xrandr.o `test -f 'gcm-device-xrandr.c' || echo './'`gcm-device-xrandr.c CC libgcmshared_a-gcm-device-udev.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device-udev.o `test -f 'gcm-device-udev.c' || echo './'`gcm-device-udev.c CC libgcmshared_a-gcm-device-cups.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device-cups.o `test -f 'gcm-device-cups.c' || echo './'`gcm-device-cups.c CC libgcmshared_a-gcm-device-sane.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device-sane.o `test -f 'gcm-device-sane.c' || echo './'`gcm-device-sane.c CC libgcmshared_a-gcm-device-virtual.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-device-virtual.o `test -f 'gcm-device-virtual.c' || echo './'`gcm-device-virtual.c CC libgcmshared_a-gcm-cie-widget.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-cie-widget.o `test -f 'gcm-cie-widget.c' || echo './'`gcm-cie-widget.c CC libgcmshared_a-gcm-trc-widget.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-trc-widget.o `test -f 'gcm-trc-widget.c' || echo './'`gcm-trc-widget.c CC libgcmshared_a-gcm-gamma-widget.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-gamma-widget.o `test -f 'gcm-gamma-widget.c' || echo './'`gcm-gamma-widget.c CC libgcmshared_a-gcm-profile-store.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-profile-store.o `test -f 'gcm-profile-store.c' || echo './'`gcm-profile-store.c CC libgcmshared_a-gcm-profile-lcms1.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-profile-lcms1.o `test -f 'gcm-profile-lcms1.c' || echo './'`gcm-profile-lcms1.c CC libgcmshared_a-gcm-profile.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o libgcmshared_a-gcm-profile.o `test -f 'gcm-profile.c' || echo './'`gcm-profile.c AR libgcmshared.a CC gcm_inspect-gcm-inspect.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_inspect-gcm-inspect.o `test -f 'gcm-inspect.c' || echo './'`gcm-inspect.c CCLD gcm-inspect CC gcm_dump_profile-gcm-dump-profile.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_dump_profile-gcm-dump-profile.o `test -f 'gcm-dump-profile.c' || echo './'`gcm-dump-profile.c CCLD gcm-dump-profile CC gcm_fix_profile-gcm-fix-profile.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_fix_profile-gcm-fix-profile.o `test -f 'gcm-fix-profile.c' || echo './'`gcm-fix-profile.c CCLD gcm-fix-profile CC gcm_dump_edid-gcm-dump-edid.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_dump_edid-gcm-dump-edid.o `test -f 'gcm-dump-edid.c' || echo './'`gcm-dump-edid.c CCLD gcm-dump-edid CC gcm_apply-gcm-apply.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_apply-gcm-apply.o `test -f 'gcm-apply.c' || echo './'`gcm-apply.c CCLD gcm-apply CC gcm_prefs-gcm-calibrate.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-calibrate.o `test -f 'gcm-calibrate.c' || echo './'`gcm-calibrate.c CC gcm_prefs-gcm-calibrate-argyll.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-calibrate-argyll.o `test -f 'gcm-calibrate-argyll.c' || echo './'`gcm-calibrate-argyll.c CC gcm_prefs-gcm-calibrate-manual.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-calibrate-manual.o `test -f 'gcm-calibrate-manual.c' || echo './'`gcm-calibrate-manual.c CC gcm_prefs-gcm-calibrate-dialog.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-calibrate-dialog.o `test -f 'gcm-calibrate-dialog.c' || echo './'`gcm-calibrate-dialog.c CC gcm_prefs-gcm-brightness.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-brightness.o `test -f 'gcm-brightness.c' || echo './'`gcm-brightness.c CC gcm_prefs-gcm-prefs.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_prefs-gcm-prefs.o `test -f 'gcm-prefs.c' || echo './'`gcm-prefs.c CCLD gcm-prefs CC gcm_session-gcm-dbus.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_session-gcm-dbus.o `test -f 'gcm-dbus.c' || echo './'`gcm-dbus.c CC gcm_session-gcm-session.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_session-gcm-session.o `test -f 'gcm-session.c' || echo './'`gcm-session.c CCLD gcm-session CC gcm_import-gcm-import.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_import-gcm-import.o `test -f 'gcm-import.c' || echo './'`gcm-import.c CCLD gcm-import CC gcm_install_system_wide-gcm-install-system-wide.o gcc -DHAVE_CONFIG_H -I. -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gnome-desktop-2.0 -I/usr/include/gtk-2.0 -I/usr/include/startup-notification-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/unique-1.0 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -DORBIT2=1 -pthread -I/usr/include/gconf/2 -I/usr/include/orbit-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/vte-0.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -D_REENTRANT -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -pthread -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 -DG_UDEV_API_IS_SUBJECT_TO_CHANGE -DGNOME_DESKTOP_USE_UNSTABLE_API -pthread -I/usr/include/gudev-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DSYSCONFDIR=\""/etc"\" -DVERSION="\"2.32.0\"" -DLOCALEDIR=\""/usr/share/locale"\" -DGCM_SYSTEM_PROFILES_DIR="\"/var/lib/color"\" -DGCM_DATA=\"/usr/share/gnome-color-manager\" -Wall -Wcast-align -Wno-uninitialized -Wmissing-declarations -Wpointer-arith -Wcast-align -Wwrite-strings -Winit-self -Wreturn-type -Wformat-nonliteral -Wformat-security -Wmissing-include-dirs -Wmissing-format-attribute -Wclobbered -Wempty-body -Wignored-qualifiers -Wsign-compare -Wtype-limits -Wuninitialized -Waggregate-return -Wdeclaration-after-statement -Wshadow -Wno-strict-aliasing -Winline -Wmissing-parameter-type -Woverride-init -g -O2 -c -o gcm_install_system_wide-gcm-install-system-wide.o `test -f 'gcm-install-system-wide.c' || echo './'`gcm-install-system-wide.c CCLD gcm-install-system-wide make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0' make[1]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0' # Skipping dh_auto_test - empty override /usr/bin/fakeroot debian/rules binary dh --with autoreconf binary dh_testroot dh_prep dh_installdirs dh_auto_install make[1]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' Making install in data make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data' Making install in tests make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/tests' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/tests' 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/gnome-color-manager-2.32.0/data/tests' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/tests' Making install in targets make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/gnome-color-manager/targets" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/targets" /usr/bin/install -c -m 644 unknown.png ColorCheckerDC.png ColorCheckerSG.png ColorChecker24.png CMP-DigitalTarget3.png QPcard_201.png LaserSoftDCPro.png i1_RGB_Scan_14.png CMP_DT_003.png IT872.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/targets' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/targets' Making install in figures make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' make[4]: Nothing to be done for `install-exec-am'. test -z "/usr/share/gnome-color-manager/icons" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/icons" /usr/bin/install -c -m 644 clock.svg calibration-short.svg calibration-normal.svg calibration-long.svg scan-target.svg scan-target-good.svg scan-target-bad.svg i1-attach.svg huey-attach.svg hcfr-attach.svg spyder-attach.svg munki-ambient.svg munki-attach.svg munki-calibrate.svg munki-projector.svg munki-screen.svg '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/icons' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/figures' Making install in icons make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' Making install in scalable make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/gnome-color-manager/icons" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/icons" /usr/bin/install -c -m 644 lcd.svg crt.svg projector.svg '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager/icons' test -z "/usr/share/icons/hicolor/scalable/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/scalable/apps" /usr/bin/install -c -m 644 gnome-color-manager.svg '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/scalable/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/scalable/mimetypes; ln -fs /usr/share/icons/hicolor/scalable/apps/gnome-color-manager.svg /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/scalable/mimetypes/application-vnd.iccprofile.svg; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/scalable' Making install in 16x16 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/16x16/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/16x16/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/16x16/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/16x16/mimetypes; ln -fs /usr/share/icons/hicolor/16x16/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/16x16/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/16x16' Making install in 22x22 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/22x22/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/22x22/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/22x22/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/22x22/mimetypes; ln -fs /usr/share/icons/hicolor/22x22/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/22x22/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/22x22' Making install in 24x24 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/24x24/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/24x24/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/24x24/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/24x24/mimetypes; ln -fs /usr/share/icons/hicolor/24x24/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/24x24/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/24x24' Making install in 32x32 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/32x32/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/32x32/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/32x32/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/32x32/mimetypes; ln -fs /usr/share/icons/hicolor/32x32/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/32x32/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/32x32' Making install in 48x48 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/48x48/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/48x48/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/48x48/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/48x48/mimetypes; ln -fs /usr/share/icons/hicolor/48x48/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/48x48/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/48x48' Making install in 64x64 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/64x64/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/64x64/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/64x64/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/64x64/mimetypes; ln -fs /usr/share/icons/hicolor/64x64/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/64x64/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/64x64' Making install in 256x256 make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[5]: Nothing to be done for `install-exec-am'. test -z "/usr/share/icons/hicolor/256x256/apps" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/256x256/apps" /usr/bin/install -c -m 644 gnome-color-manager.png '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/256x256/apps' make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/256x256/mimetypes; ln -fs /usr/share/icons/hicolor/256x256/apps/gnome-color-manager.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/icons/hicolor/256x256/mimetypes/application-vnd.iccprofile.png; make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons/256x256' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[5]: Nothing to be done for `install-exec-am'. make install-data-hook make[6]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/gnome-color-manager/icons/hicolor make[6]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data/icons' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/data' make[4]: Nothing to be done for `install-exec-am'. test -z "/etc/xdg/autostart" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/etc/xdg/autostart" /usr/bin/install -c -m 644 gcm-apply.desktop '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/etc/xdg/autostart' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule gnome-color-manager.schemas (gconftool-2:11431): GConf-WARNING **: None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/gnome-color-manager/default_gamma' to key `/apps/gnome-color-manager/default_gamma' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/default_gamma', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/default_gamma', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/global_display_correction' to key `/apps/gnome-color-manager/global_display_correction' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/global_display_correction', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/global_display_correction', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes' to key `/apps/gnome-color-manager/use_profiles_from_volumes' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/use_profiles_from_volumes', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/use_profiles_from_volumes', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom' to key `/apps/gnome-color-manager/set_icc_profile_atom' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/set_icc_profile_atom', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/set_icc_profile_atom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/show_fine_tuning' to key `/apps/gnome-color-manager/show_fine_tuning' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/show_fine_tuning', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/show_fine_tuning', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/rendering_intent_display' to key `/apps/gnome-color-manager/rendering_intent_display' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_display', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_display', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof' to key `/apps/gnome-color-manager/rendering_intent_softproof' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/rendering_intent_softproof', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/rendering_intent_softproof', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/colorspace_rgb' to key `/apps/gnome-color-manager/colorspace_rgb' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `ro': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `nb': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_rgb', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_rgb', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/colorspace_cmyk' to key `/apps/gnome-color-manager/colorspace_cmyk' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `ro': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `nb': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/colorspace_cmyk', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/colorspace_cmyk', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/calibration_length' to key `/apps/gnome-color-manager/calibration_length' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `ro': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `ru': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `nb': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/calibration_length', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/calibration_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold' to key `/apps/gnome-color-manager/recalibrate_display_threshold' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `ro': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_display_threshold', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_display_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold' to key `/apps/gnome-color-manager/recalibrate_printer_threshold' WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `de': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `lt': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `pl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `zh_CN': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `sl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `ro': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `he': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `C': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `el': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `ja': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `cs': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `gl': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `pt': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `id': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `es': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `et': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `fr': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `zh_TW': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `zh_HK': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `en_GB': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `hu': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `it': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `sr': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `da': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `sr@latin': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', locale `ko': Unable to store a value at key '/schemas/apps/gnome-color-manager/recalibrate_printer_threshold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf test -z "/usr/share/applications" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/applications" /usr/bin/install -c -m 644 gcm-prefs.desktop gcm-import.desktop '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/applications' test -z "/usr/share/gnome-color-manager" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager" /usr/bin/install -c -m 644 gcm-calibrate.ui gcm-spawn.ui gcm-prefs.ui '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome-color-manager' test -z "/etc/gconf/schemas" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/etc/gconf/schemas" /usr/bin/install -c -m 644 gnome-color-manager.schemas '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/etc/gconf/schemas' test -z "/usr/share/dbus-1/services" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/dbus-1/services" /usr/bin/install -c -m 644 org.gnome.ColorManager.service '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/dbus-1/services' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/data' Making install in help make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/help' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/help' make[3]: Nothing to be done for `install-exec-am'. /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru /usr/bin/install -c -m 644 C/legal.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/legal.xml /usr/bin/install -c -m 644 C/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/gnome-color-manager.xml /usr/bin/install -c -m 644 cs/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/gnome-color-manager.xml /usr/bin/install -c -m 644 de/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/gnome-color-manager.xml /usr/bin/install -c -m 644 el/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/gnome-color-manager.xml /usr/bin/install -c -m 644 es/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/gnome-color-manager.xml /usr/bin/install -c -m 644 id/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/gnome-color-manager.xml /usr/bin/install -c -m 644 ru/gnome-color-manager.xml /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/gnome-color-manager.xml /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/ /usr/bin/install -c -m 644 C/figures/gcm-adjust.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-adjust.png gcm-adjust.png /usr/bin/install -c -m 644 C/figures/gcm-basic.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-basic.png gcm-basic.png /usr/bin/install -c -m 644 C/figures/gcm-scanner.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-scanner.png gcm-scanner.png /usr/bin/install -c -m 644 C/figures/gcm-calibrate-default.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-default.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-calibrate-default.png gcm-calibrate-default.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-calibrate-default.png gcm-calibrate-default.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-calibrate-default.png gcm-calibrate-default.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-calibrate-default.png gcm-calibrate-default.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-calibrate-default.png gcm-calibrate-default.png /usr/bin/install -c -m 644 ru/figures/gcm-calibrate-default.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-calibrate-default.png /usr/bin/install -c -m 644 C/figures/gcm-calibrate-drawing.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-calibrate-drawing.png gcm-calibrate-drawing.png /usr/bin/install -c -m 644 C/figures/gcm-print-mode.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-print-mode.png gcm-print-mode.png /usr/bin/install -c -m 644 C/figures/gcm-screen-type.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-screen-type.png gcm-screen-type.png /usr/bin/install -c -m 644 C/figures/gcm-device-configure.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-device-configure.png gcm-device-configure.png /usr/bin/install -c -m 644 C/figures/gcm-import.png /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/C/figures/gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/cs/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/de/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/el/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/es/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/id/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png cd /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/gnome/help/gnome-color-manager/ru/figures/ && ln -s -f ../../C/figures/gcm-import.png gcm-import.png /bin/bash ../mkinstalldirs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager mkdir -p -- /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager /usr/bin/install -c -m 644 gnome-color-manager-C.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-C.omf /usr/bin/install -c -m 644 gnome-color-manager-cs.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-cs.omf /usr/bin/install -c -m 644 gnome-color-manager-de.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-de.omf /usr/bin/install -c -m 644 gnome-color-manager-el.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-el.omf /usr/bin/install -c -m 644 gnome-color-manager-es.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-es.omf /usr/bin/install -c -m 644 gnome-color-manager-id.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-id.omf /usr/bin/install -c -m 644 gnome-color-manager-ru.omf /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager/gnome-color-manager-ru.omf scrollkeeper-update -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/var/lib/rarian -o /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/omf/gnome-color-manager make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/help' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/help' Making install in man make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/man' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/man' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/man/man1" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/man/man1" /usr/bin/install -c -m 644 gcm-apply.1 gcm-prefs.1 gcm-import.1 '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/man/man1' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/man' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/man' Making install in po make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/po' linguas="ar cs da de el en_GB es et fr gl he hu id it ja ko lt nb pa pl pt_BR pt ro ru sl sr sr@latin sv ta th zh_CN zh_HK zh_TW "; \ for lang in $linguas; do \ dir=/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/$lang/LC_MESSAGES; \ /bin/bash /build/buildd/gnome-color-manager-2.32.0/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/gnome-color-manager.mo; \ echo "installing $lang.gmo as $dir/gnome-color-manager.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/gnome-color-manager.mo; \ echo "installing ./$lang.gmo as" \ "$dir/gnome-color-manager.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/gnome-color-manager.mo.m; \ echo "installing $lang.gmo.m as $dir/gnome-color-manager.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/gnome-color-manager.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/gnome-color-manager.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ar/LC_MESSAGES/gnome-color-manager.mo installing cs.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/cs/LC_MESSAGES/gnome-color-manager.mo installing da.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/da/LC_MESSAGES/gnome-color-manager.mo installing de.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/de/LC_MESSAGES/gnome-color-manager.mo installing el.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/el/LC_MESSAGES/gnome-color-manager.mo installing en_GB.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/en_GB/LC_MESSAGES/gnome-color-manager.mo installing es.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/es/LC_MESSAGES/gnome-color-manager.mo installing et.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/et/LC_MESSAGES/gnome-color-manager.mo installing fr.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/fr/LC_MESSAGES/gnome-color-manager.mo installing gl.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/gl/LC_MESSAGES/gnome-color-manager.mo installing he.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/he/LC_MESSAGES/gnome-color-manager.mo installing hu.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/hu/LC_MESSAGES/gnome-color-manager.mo installing id.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/id/LC_MESSAGES/gnome-color-manager.mo installing it.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/it/LC_MESSAGES/gnome-color-manager.mo installing ja.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ja/LC_MESSAGES/gnome-color-manager.mo installing ko.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ko/LC_MESSAGES/gnome-color-manager.mo installing lt.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/lt/LC_MESSAGES/gnome-color-manager.mo installing nb.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/nb/LC_MESSAGES/gnome-color-manager.mo installing pa.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/pa/LC_MESSAGES/gnome-color-manager.mo installing pl.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/pl/LC_MESSAGES/gnome-color-manager.mo installing pt_BR.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/pt_BR/LC_MESSAGES/gnome-color-manager.mo installing pt.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/pt/LC_MESSAGES/gnome-color-manager.mo installing ro.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ro/LC_MESSAGES/gnome-color-manager.mo installing ru.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ru/LC_MESSAGES/gnome-color-manager.mo installing sl.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/sl/LC_MESSAGES/gnome-color-manager.mo installing sr.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/sr/LC_MESSAGES/gnome-color-manager.mo installing sr@latin.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/sr@latin/LC_MESSAGES/gnome-color-manager.mo installing sv.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/sv/LC_MESSAGES/gnome-color-manager.mo installing ta.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/ta/LC_MESSAGES/gnome-color-manager.mo installing th.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/th/LC_MESSAGES/gnome-color-manager.mo installing zh_CN.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/zh_CN/LC_MESSAGES/gnome-color-manager.mo installing zh_HK.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/zh_HK/LC_MESSAGES/gnome-color-manager.mo installing zh_TW.gmo as /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/locale/zh_TW/LC_MESSAGES/gnome-color-manager.mo make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/po' Making install in policy make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/policy' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/policy' make[3]: Nothing to be done for `install-exec-am'. test -z "/usr/share/polkit-1/actions" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/polkit-1/actions" /usr/bin/install -c -m 644 org.gnome.color.policy '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/share/polkit-1/actions' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/policy' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/policy' Making install in rules make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/rules' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/rules' make[3]: Nothing to be done for `install-exec-am'. test -z "/lib/udev/rules.d" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/lib/udev/rules.d" /usr/bin/install -c -m 644 95-gcm-colorimeters.rules 95-gcm-devices.rules '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/lib/udev/rules.d' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/rules' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/rules' Making install in src make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' make install-am make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' make[4]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' test -z "/usr/bin" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin" /bin/bash ../libtool --mode=install /usr/bin/install -c gcm-inspect gcm-dump-profile gcm-fix-profile gcm-dump-edid gcm-apply gcm-prefs gcm-session gcm-import '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin' libtool: install: /usr/bin/install -c gcm-inspect /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-inspect libtool: install: /usr/bin/install -c gcm-dump-profile /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-dump-profile libtool: install: /usr/bin/install -c gcm-fix-profile /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-fix-profile libtool: install: /usr/bin/install -c gcm-dump-edid /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-dump-edid libtool: install: /usr/bin/install -c gcm-apply /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-apply libtool: install: /usr/bin/install -c gcm-prefs /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-prefs libtool: install: /usr/bin/install -c gcm-session /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-session libtool: install: /usr/bin/install -c gcm-import /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/bin/gcm-import test -z "/usr/sbin" || /bin/mkdir -p "/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/sbin" /bin/bash ../libtool --mode=install /usr/bin/install -c gcm-install-system-wide '/build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/sbin' libtool: install: /usr/bin/install -c gcm-install-system-wide /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/sbin/gcm-install-system-wide make install-data-hook make[5]: Entering directory `/build/buildd/gnome-color-manager-2.32.0/src' if test -w /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/usr/; then \ mkdir -p /build/buildd/gnome-color-manager-2.32.0/debian/gnome-color-manager/var/lib/color; \ fi make[5]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[4]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[3]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0/src' make[2]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' make[3]: Entering directory `/build/buildd/gnome-color-manager-2.32.0' 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/gnome-color-manager-2.32.0' make[2]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0' make[1]: Leaving directory `/build/buildd/gnome-color-manager-2.32.0' dh_install dh_installdocs dh_installchangelogs dh_installexamples dh_installman dh_installcatalogs dh_installcron dh_installdebconf dh_installemacsen dh_installifupdown dh_installinfo dh_pysupport dh_installinit dh_installmenu dh_installmime dh_installmodules dh_installlogcheck dh_installlogrotate dh_installpam dh_installppp dh_installudev dh_installwm dh_installxfonts dh_bugfiles dh_lintian dh_gconf dh_icons dh_perl dh_usrlocal dh_link dh_compress dh_fixperms dh_strip dh_strip debug symbol extraction: all non-arch-all packages for this build platform i386: gnome-color-manager dh_strip debug symbol extraction: packages to act on: gnome-color-manager dh_strip debug symbol extraction: ignored packages: dpkg-deb: building package `gnome-color-manager-dbgsym' in `../gnome-color-manager-dbgsym_2.32.0-0ubuntu1_i386.ddeb'. dh_makeshlibs dh_shlibdeps dh_installdeb dh_gencontrol dh_md5sums dh_builddeb INFO: pkgstriptranslations version 91 pkgstriptranslations: processing control file: ./debian/gnome-color-manager/DEBIAN/control, package gnome-color-manager, directory ./debian/gnome-color-manager ./debian/gnome-color-manager/usr/share/applications/gcm-prefs.desktop: does not have gettext domain, not stripping ./debian/gnome-color-manager/usr/share/applications/gcm-import.desktop: does not have gettext domain, not stripping ./debian/gnome-color-manager/etc/xdg/autostart/gcm-apply.desktop: does not have gettext domain, not stripping pkgstriptranslations: preparing translation tarball gnome-color-manager_2.32.0-0ubuntu1_i386_translations.tar.gz...done (72 files) pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers " pkgstripfiles: processing control file: debian/gnome-color-manager/DEBIAN/control, package gnome-color-manager, directory debian/gnome-color-manager OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/unknown.png 200x140 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 233 colors in palette Input IDAT size = 1976 bytes Input file size = 2160 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 802 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 802 Output IDAT size = 802 bytes (1174 bytes decrease) Output file size = 1692 bytes (468 bytes = 21.67% decrease) 1692 1557 92% ./usr/share/gnome-color-manager/targets/unknown.png 1692 1557 92% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/ColorCheckerDC.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 41467 bytes Input file size = 41637 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 41467 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 41265 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 41265 Output IDAT size = 41265 bytes (202 bytes decrease) Output file size = 41375 bytes (262 bytes = 0.63% decrease) 41375 41375 100% ./usr/share/gnome-color-manager/targets/ColorCheckerDC.png (Bigger 64912) 41375 41375 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/ColorCheckerSG.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 35827 bytes Input file size = 35945 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 35827 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Output IDAT size = 35827 bytes (no change) Output file size = 35897 bytes (48 bytes = 0.13% decrease) 35897 35897 100% ./usr/share/gnome-color-manager/targets/ColorCheckerSG.png (Bigger 53673) 35897 35897 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/ColorChecker24.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 32811 bytes Input file size = 32929 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 31804 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 30799 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 30799 Output IDAT size = 30799 bytes (2012 bytes decrease) Output file size = 30869 bytes (2060 bytes = 6.26% decrease) 30869 30869 100% ./usr/share/gnome-color-manager/targets/ColorChecker24.png (Bigger 46826) 30869 30869 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/CMP-DigitalTarget3.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 44384 bytes Input file size = 44514 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 44035 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 43685 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 43685 Output IDAT size = 43685 bytes (699 bytes decrease) Output file size = 43755 bytes (759 bytes = 1.71% decrease) 43755 43755 100% ./usr/share/gnome-color-manager/targets/CMP-DigitalTarget3.png (Bigger 74870) 43755 43755 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/QPcard_201.png 200x140 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 14793 bytes Input file size = 14875 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 14793 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 IDAT size = 14765 Selecting parameters: zc = 9 zm = 8 zs = 3 f = 5 IDAT size = 14765 Output IDAT size = 14765 bytes (28 bytes decrease) Output file size = 14835 bytes (40 bytes = 0.27% decrease) 14835 14835 100% ./usr/share/gnome-color-manager/targets/QPcard_201.png (Bigger 20129) 14835 14835 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/LaserSoftDCPro.png 200x140 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 37464 bytes Input file size = 37582 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 37146 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 36945 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 36945 Output IDAT size = 36945 bytes (519 bytes decrease) Output file size = 37015 bytes (567 bytes = 1.51% decrease) 37015 37015 100% ./usr/share/gnome-color-manager/targets/LaserSoftDCPro.png (Bigger 56713) 37015 37015 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/i1_RGB_Scan_14.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 34961 bytes Input file size = 35079 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 34618 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 34218 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 34218 Output IDAT size = 34218 bytes (743 bytes decrease) Output file size = 34288 bytes (791 bytes = 2.25% decrease) 34288 34288 100% ./usr/share/gnome-color-manager/targets/i1_RGB_Scan_14.png (Bigger 52970) 34288 34288 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/CMP_DT_003.png 200x140 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 39155 bytes Input file size = 39273 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 39155 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 39141 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 39141 Output IDAT size = 39141 bytes (14 bytes decrease) Output file size = 39211 bytes (62 bytes = 0.16% decrease) 39211 39211 100% ./usr/share/gnome-color-manager/targets/CMP_DT_003.png (Bigger 61284) 39211 39211 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome-color-manager/targets/IT872.png 200x140 pixels, 3x8 bits/pixel, RGB Input IDAT size = 31518 bytes Input file size = 31624 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 30698 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 30228 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 30228 Output IDAT size = 30228 bytes (1290 bytes decrease) Output file size = 30298 bytes (1326 bytes = 4.19% decrease) 30298 30298 100% ./usr/share/gnome-color-manager/targets/IT872.png (Bigger 51088) 30298 30298 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/16x16/apps/gnome-color-manager.png 16x16 pixels, 4x8 bits/pixel, RGB+alpha Reducing image to 8 bits/pixel, 90 colors (42 transparent) in palette Input IDAT size = 671 bytes Input file size = 837 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 215 zc = 9 zm = 8 zs = 1 f = 0 IDAT size = 212 zc = 1 zm = 8 zs = 2 f = 0 IDAT size = 209 zc = 9 zm = 8 zs = 3 f = 0 IDAT size = 209 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 IDAT size = 207 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 IDAT size = 204 zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 199 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 1 zm = 8 zs = 2 f = 5 IDAT size = 199 Output IDAT size = 199 bytes (472 bytes decrease) Output file size = 700 bytes (137 bytes = 16.37% decrease) 700 604 86% ./usr/share/icons/hicolor/16x16/apps/gnome-color-manager.png 700 604 86% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/22x22/apps/gnome-color-manager.png 22x22 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 1365 bytes Input file size = 1531 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1273 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1273 Output IDAT size = 1273 bytes (92 bytes decrease) Output file size = 1439 bytes (92 bytes = 6.01% decrease) 1439 1329 92% ./usr/share/icons/hicolor/22x22/apps/gnome-color-manager.png 1439 1329 92% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/24x24/apps/gnome-color-manager.png 24x24 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 1396 bytes Input file size = 1562 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1240 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 1240 Output IDAT size = 1240 bytes (156 bytes decrease) Output file size = 1406 bytes (156 bytes = 9.99% decrease) 1406 1288 91% ./usr/share/icons/hicolor/24x24/apps/gnome-color-manager.png 1406 1288 91% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/32x32/apps/gnome-color-manager.png 32x32 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 2200 bytes Input file size = 2366 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2010 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 2010 Output IDAT size = 2010 bytes (190 bytes decrease) Output file size = 2176 bytes (190 bytes = 8.03% decrease) 2176 2057 94% ./usr/share/icons/hicolor/32x32/apps/gnome-color-manager.png 2176 2057 94% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/48x48/apps/gnome-color-manager.png 48x48 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 4187 bytes Input file size = 4353 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3716 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 3716 Output IDAT size = 3716 bytes (471 bytes decrease) Output file size = 3882 bytes (471 bytes = 10.82% decrease) 3882 3724 95% ./usr/share/icons/hicolor/48x48/apps/gnome-color-manager.png 3882 3724 95% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/64x64/apps/gnome-color-manager.png 64x64 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 5755 bytes Input file size = 5883 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 5728 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 5728 Output IDAT size = 5728 bytes (27 bytes decrease) Output file size = 5856 bytes (27 bytes = 0.46% decrease) 5856 5712 97% ./usr/share/icons/hicolor/64x64/apps/gnome-color-manager.png 5856 5712 97% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/icons/hicolor/256x256/apps/gnome-color-manager.png 256x256 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 44442 bytes Input file size = 44668 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 40583 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 40583 Output IDAT size = 40583 bytes (3859 bytes decrease) Output file size = 40749 bytes (3919 bytes = 8.77% decrease) 40749 39243 96% ./usr/share/icons/hicolor/256x256/apps/gnome-color-manager.png 40749 39243 96% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-adjust.png 895x482 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 60758 bytes Input file size = 60970 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 56291 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 56291 Output IDAT size = 56291 bytes (4467 bytes decrease) Output file size = 56419 bytes (4551 bytes = 7.46% decrease) 56419 55983 99% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-adjust.png 56419 55983 99% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-basic.png 812x450 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 50052 bytes Input file size = 50252 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 47090 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 47090 Output IDAT size = 47090 bytes (2962 bytes decrease) Output file size = 47218 bytes (3034 bytes = 6.04% decrease) 47218 46727 98% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-basic.png 47218 46727 98% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-scanner.png 830x538 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 93600 bytes Input file size = 93860 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 90825 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 90825 Output IDAT size = 90825 bytes (2775 bytes decrease) Output file size = 90953 bytes (2907 bytes = 3.10% decrease) 90953 89136 98% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-scanner.png 90953 89136 98% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-default.png 366x184 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 16523 bytes Input file size = 16657 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 13681 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 13681 Output IDAT size = 13681 bytes (2842 bytes decrease) Output file size = 13791 bytes (2866 bytes = 17.21% decrease) 13791 13522 98% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-default.png 13791 13522 98% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-drawing.png 410x168 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 15757 bytes Input file size = 15879 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 13265 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 13265 Output IDAT size = 13265 bytes (2492 bytes decrease) Output file size = 13375 bytes (2504 bytes = 15.77% decrease) 13375 13114 98% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-drawing.png 13375 13114 98% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-print-mode.png 688x412 pixels, 3x8 bits/pixel, RGB Input IDAT size = 52471 bytes Input file size = 52652 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 51246 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 IDAT size = 50013 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 5 IDAT size = 50013 Output IDAT size = 50013 bytes (2458 bytes decrease) Output file size = 50122 bytes (2530 bytes = 4.81% decrease) 50122 49171 98% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-print-mode.png 50122 49171 98% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-screen-type.png 574x412 pixels, 3x8 bits/pixel, RGB Input IDAT size = 41459 bytes Input file size = 41628 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 IDAT size = 40362 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 IDAT size = 39700 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 5 IDAT size = 39700 Output IDAT size = 39700 bytes (1759 bytes decrease) Output file size = 39809 bytes (1819 bytes = 4.37% decrease) 39809 39809 100% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-screen-type.png (Bigger 43578) 39809 39809 100% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-device-configure.png 459x425 pixels, 3x8 bits/pixel, RGB Input IDAT size = 39821 bytes Input file size = 39978 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 33572 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 33572 Output IDAT size = 33572 bytes (6249 bytes decrease) Output file size = 33681 bytes (6297 bytes = 15.75% decrease) 33681 31560 93% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-device-configure.png 33681 31560 93% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-import.png 373x167 pixels, 4x8 bits/pixel, RGB+alpha Input IDAT size = 13399 bytes Input file size = 13521 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 10822 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 10822 Output IDAT size = 10822 bytes (2577 bytes decrease) Output file size = 10932 bytes (2589 bytes = 19.15% decrease) 10932 10709 97% ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-import.png 10932 10709 97% OptiPNG 0.6.4: Advanced PNG optimizer. Copyright (C) 2001-2010 Cosmin Truta. ** Processing: ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-calibrate-default.png 341x182 pixels, 3x8 bits/pixel, RGB Input IDAT size = 13682 bytes Input file size = 13803 bytes Trying: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 12625 zc = 9 zm = 8 zs = 1 f = 0 zc = 1 zm = 8 zs = 2 f = 0 zc = 9 zm = 8 zs = 3 f = 0 zc = 9 zm = 8 zs = 0 f = 1 zc = 9 zm = 8 zs = 1 f = 1 zc = 1 zm = 8 zs = 2 f = 1 zc = 9 zm = 8 zs = 3 f = 1 zc = 9 zm = 8 zs = 0 f = 2 zc = 9 zm = 8 zs = 1 f = 2 zc = 1 zm = 8 zs = 2 f = 2 zc = 9 zm = 8 zs = 3 f = 2 zc = 9 zm = 8 zs = 0 f = 3 zc = 9 zm = 8 zs = 1 f = 3 zc = 1 zm = 8 zs = 2 f = 3 zc = 9 zm = 8 zs = 3 f = 3 zc = 9 zm = 8 zs = 0 f = 4 zc = 9 zm = 8 zs = 1 f = 4 zc = 1 zm = 8 zs = 2 f = 4 zc = 9 zm = 8 zs = 3 f = 4 zc = 9 zm = 8 zs = 0 f = 5 zc = 9 zm = 8 zs = 1 f = 5 zc = 1 zm = 8 zs = 2 f = 5 zc = 9 zm = 8 zs = 3 f = 5 Selecting parameters: zc = 9 zm = 8 zs = 0 f = 0 IDAT size = 12625 Output IDAT size = 12625 bytes (1057 bytes decrease) Output file size = 12734 bytes (1069 bytes = 7.74% decrease) 12734 12378 97% ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-calibrate-default.png 12734 12378 97% dpkg-deb: warning: 'debian/gnome-color-manager/DEBIAN/control' contains user-defined field 'Original-Maintainer' dpkg-deb: warning: ignoring 1 warning about the control file(s) dpkg-deb: building package `gnome-color-manager' in `../gnome-color-manager_2.32.0-0ubuntu1_i386.deb'. dpkg-genchanges -b -mUbuntu/i386 Build Daemon >../gnome-color-manager_2.32.0-0ubuntu1_i386.changes dpkg-genchanges: binary-only upload - not including any source code dpkg-source --after-build gnome-color-manager-2.32.0 dpkg-buildpackage: binary only upload (no source included) ****************************************************************************** Build finished at 20110208-0215 Publishing chroot-autobuild/build/buildd/gnome-color-manager_2.32.0-0ubuntu1_i386_translations.tar.gz for rosetta. Publishing debug debs. chroot-autobuild/build/buildd/gnome-color-manager_2.32.0-0ubuntu1_i386.deb: new debian package, version 2.0. size 1977504 bytes: control archive= 4416 bytes. 37 bytes, 1 lines conffiles 1232 bytes, 15 lines control 10435 bytes, 119 lines md5sums Package: gnome-color-manager Version: 2.32.0-0ubuntu1 Architecture: i386 Maintainer: Ubuntu Developers Original-Maintainer: Debian GNOME Maintainers Installed-Size: 5100 Depends: policykit-1, gconf2 (>= 2.28.1-2), libc6 (>= 2.4), libcairo2 (>= 1.2.4), libcanberra-gtk0 (>= 0.10), libcanberra0 (>= 0.2), libcups2 (>= 1.4.0), libdbus-glib-1-2 (>= 0.88), libgconf2-4 (>= 2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), libgnome-desktop-2-17 (>= 1:2.29.92), libgtk2.0-0 (>= 2.18.0), libgudev-1.0-0 (>= 147), liblcms1 (>= 1.15-1), libnotify1 (>= 0.5.0), libnotify1-gtk2.10, libpango1.0-0 (>= 1.18.0), libsane (>= 1.0.11-3), libtiff4, libunique-1.0-0 (>= 1.0.0), libvte9 (>= 1:0.24.0), libx11-6, libxrandr2 (>= 2:1.2.0), libxxf86vm1 Recommends: argyll, hwdata (>= 0.227-1~) Section: gnome Priority: optional Homepage: http://projects.gnome.org/gnome-color-manager/ Description: Color management integration for the Gnome desktop environment GNOME Color Manager is a set of graphical utilities for color management to be used in the GNOME desktop. With the help of ArgyllCMS, it can create and apply display ICC color profiles. chroot-autobuild/build/buildd/gnome-color-manager_2.32.0-0ubuntu1_i386.deb: drwxr-xr-x root/root 0 2011-02-08 02:14 ./ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome-color-manager/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/gnome-color-manager/targets/ -rw-r--r-- root/root 1557 2011-02-08 02:15 ./usr/share/gnome-color-manager/targets/unknown.png -rw-r--r-- root/root 41375 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/ColorCheckerDC.png -rw-r--r-- root/root 35897 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/ColorCheckerSG.png -rw-r--r-- root/root 30869 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/ColorChecker24.png -rw-r--r-- root/root 43755 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/CMP-DigitalTarget3.png -rw-r--r-- root/root 14835 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/QPcard_201.png -rw-r--r-- root/root 37015 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/LaserSoftDCPro.png -rw-r--r-- root/root 34288 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/i1_RGB_Scan_14.png -rw-r--r-- root/root 39211 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/CMP_DT_003.png -rw-r--r-- root/root 30298 2011-02-08 02:14 ./usr/share/gnome-color-manager/targets/IT872.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/ -rw-r--r-- root/root 47588 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/clock.svg -rw-r--r-- root/root 32523 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/calibration-short.svg -rw-r--r-- root/root 47214 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/calibration-normal.svg -rw-r--r-- root/root 68181 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/calibration-long.svg -rw-r--r-- root/root 21692 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/scan-target.svg -rw-r--r-- root/root 21971 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/scan-target-good.svg -rw-r--r-- root/root 21958 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/scan-target-bad.svg -rw-r--r-- root/root 62630 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/i1-attach.svg -rw-r--r-- root/root 61011 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/huey-attach.svg -rw-r--r-- root/root 11409 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/hcfr-attach.svg -rw-r--r-- root/root 62945 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/spyder-attach.svg -rw-r--r-- root/root 66992 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/munki-ambient.svg -rw-r--r-- root/root 118916 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/munki-attach.svg -rw-r--r-- root/root 66143 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/munki-calibrate.svg -rw-r--r-- root/root 66408 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/munki-projector.svg -rw-r--r-- root/root 66272 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/munki-screen.svg -rw-r--r-- root/root 12111 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/lcd.svg -rw-r--r-- root/root 43632 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/crt.svg -rw-r--r-- root/root 26928 2011-02-08 02:14 ./usr/share/gnome-color-manager/icons/projector.svg -rw-r--r-- root/root 55825 2011-02-08 02:14 ./usr/share/gnome-color-manager/gcm-calibrate.ui -rw-r--r-- root/root 9105 2011-02-08 02:14 ./usr/share/gnome-color-manager/gcm-spawn.ui -rw-r--r-- root/root 125534 2011-02-08 02:14 ./usr/share/gnome-color-manager/gcm-prefs.ui drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/scalable/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/scalable/apps/ -rw-r--r-- root/root 102301 2011-02-08 02:14 ./usr/share/icons/hicolor/scalable/apps/gnome-color-manager.svg drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/scalable/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/16x16/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/16x16/apps/ -rw-r--r-- root/root 604 2011-02-08 02:15 ./usr/share/icons/hicolor/16x16/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/16x16/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/22x22/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/22x22/apps/ -rw-r--r-- root/root 1329 2011-02-08 02:15 ./usr/share/icons/hicolor/22x22/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/22x22/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/24x24/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/24x24/apps/ -rw-r--r-- root/root 1288 2011-02-08 02:15 ./usr/share/icons/hicolor/24x24/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/24x24/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/32x32/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/32x32/apps/ -rw-r--r-- root/root 2057 2011-02-08 02:15 ./usr/share/icons/hicolor/32x32/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/32x32/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/48x48/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/48x48/apps/ -rw-r--r-- root/root 3724 2011-02-08 02:15 ./usr/share/icons/hicolor/48x48/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/48x48/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/64x64/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/64x64/apps/ -rw-r--r-- root/root 5712 2011-02-08 02:15 ./usr/share/icons/hicolor/64x64/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/64x64/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/256x256/ drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/icons/hicolor/256x256/apps/ -rw-r--r-- root/root 39243 2011-02-08 02:15 ./usr/share/icons/hicolor/256x256/apps/gnome-color-manager.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/256x256/mimetypes/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/applications/ -rw-r--r-- root/root 3923 2011-02-08 02:14 ./usr/share/applications/gcm-prefs.desktop -rw-r--r-- root/root 4197 2011-02-08 02:14 ./usr/share/applications/gcm-import.desktop drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/dbus-1/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/dbus-1/services/ -rw-r--r-- root/root 70 2011-02-08 02:14 ./usr/share/dbus-1/services/org.gnome.ColorManager.service drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/C/ -rw-r--r-- root/root 3672 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/C/legal.xml -rw-r--r-- root/root 20685 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/C/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/ -rw-r--r-- root/root 55983 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-adjust.png -rw-r--r-- root/root 46727 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-basic.png -rw-r--r-- root/root 89136 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-scanner.png -rw-r--r-- root/root 13522 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-default.png -rw-r--r-- root/root 13114 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-calibrate-drawing.png -rw-r--r-- root/root 49171 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-print-mode.png -rw-r--r-- root/root 39809 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-screen-type.png -rw-r--r-- root/root 31560 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-device-configure.png -rw-r--r-- root/root 10709 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/C/figures/gcm-import.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/ -rw-r--r-- root/root 23582 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/ -rw-r--r-- root/root 25124 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/ -rw-r--r-- root/root 33802 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/ -rw-r--r-- root/root 24287 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/ -rw-r--r-- root/root 24859 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/ -rw-r--r-- root/root 29691 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/gnome-color-manager.xml drwxr-xr-x root/root 0 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/ru/figures/ -rw-r--r-- root/root 12378 2011-02-08 02:15 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-calibrate-default.png drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/omf/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/ -rw-r--r-- root/root 976 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-C.omf -rw-r--r-- root/root 975 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-cs.omf -rw-r--r-- root/root 977 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-de.omf -rw-r--r-- root/root 1191 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-el.omf -rw-r--r-- root/root 977 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-es.omf -rw-r--r-- root/root 968 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-id.omf -rw-r--r-- root/root 1050 2011-02-08 02:14 ./usr/share/omf/gnome-color-manager/gnome-color-manager-ru.omf drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/man/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/man/man1/ -rw-r--r-- root/root 491 2011-02-08 02:14 ./usr/share/man/man1/gcm-import.1.gz -rw-r--r-- root/root 496 2011-02-08 02:14 ./usr/share/man/man1/gcm-apply.1.gz -rw-r--r-- root/root 505 2011-02-08 02:14 ./usr/share/man/man1/gcm-prefs.1.gz drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ar/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ar/LC_MESSAGES/ -rw-r--r-- root/root 7822 2011-02-08 02:14 ./usr/share/locale/ar/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/cs/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/cs/LC_MESSAGES/ -rw-r--r-- root/root 40351 2011-02-08 02:14 ./usr/share/locale/cs/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/da/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/da/LC_MESSAGES/ -rw-r--r-- root/root 39122 2011-02-08 02:14 ./usr/share/locale/da/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/de/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/de/LC_MESSAGES/ -rw-r--r-- root/root 41959 2011-02-08 02:14 ./usr/share/locale/de/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/el/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/el/LC_MESSAGES/ -rw-r--r-- root/root 56315 2011-02-08 02:14 ./usr/share/locale/el/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/en_GB/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/en_GB/LC_MESSAGES/ -rw-r--r-- root/root 38583 2011-02-08 02:14 ./usr/share/locale/en_GB/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/es/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/es/LC_MESSAGES/ -rw-r--r-- root/root 41441 2011-02-08 02:14 ./usr/share/locale/es/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/et/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/et/LC_MESSAGES/ -rw-r--r-- root/root 38819 2011-02-08 02:14 ./usr/share/locale/et/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/fr/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/fr/LC_MESSAGES/ -rw-r--r-- root/root 42711 2011-02-08 02:14 ./usr/share/locale/fr/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/gl/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/gl/LC_MESSAGES/ -rw-r--r-- root/root 40680 2011-02-08 02:14 ./usr/share/locale/gl/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/he/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/he/LC_MESSAGES/ -rw-r--r-- root/root 43569 2011-02-08 02:14 ./usr/share/locale/he/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/hu/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/hu/LC_MESSAGES/ -rw-r--r-- root/root 40880 2011-02-08 02:14 ./usr/share/locale/hu/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/id/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/id/LC_MESSAGES/ -rw-r--r-- root/root 26444 2011-02-08 02:14 ./usr/share/locale/id/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/it/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/it/LC_MESSAGES/ -rw-r--r-- root/root 41900 2011-02-08 02:14 ./usr/share/locale/it/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ja/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ja/LC_MESSAGES/ -rw-r--r-- root/root 44595 2011-02-08 02:14 ./usr/share/locale/ja/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ko/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ko/LC_MESSAGES/ -rw-r--r-- root/root 41734 2011-02-08 02:14 ./usr/share/locale/ko/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/lt/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/lt/LC_MESSAGES/ -rw-r--r-- root/root 40056 2011-02-08 02:14 ./usr/share/locale/lt/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/nb/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/nb/LC_MESSAGES/ -rw-r--r-- root/root 23218 2011-02-08 02:14 ./usr/share/locale/nb/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pa/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pa/LC_MESSAGES/ -rw-r--r-- root/root 26282 2011-02-08 02:14 ./usr/share/locale/pa/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pl/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pl/LC_MESSAGES/ -rw-r--r-- root/root 40853 2011-02-08 02:14 ./usr/share/locale/pl/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pt_BR/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pt_BR/LC_MESSAGES/ -rw-r--r-- root/root 40886 2011-02-08 02:14 ./usr/share/locale/pt_BR/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pt/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/pt/LC_MESSAGES/ -rw-r--r-- root/root 41028 2011-02-08 02:14 ./usr/share/locale/pt/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ro/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ro/LC_MESSAGES/ -rw-r--r-- root/root 34440 2011-02-08 02:14 ./usr/share/locale/ro/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ru/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ru/LC_MESSAGES/ -rw-r--r-- root/root 41970 2011-02-08 02:14 ./usr/share/locale/ru/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sl/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sl/LC_MESSAGES/ -rw-r--r-- root/root 38914 2011-02-08 02:14 ./usr/share/locale/sl/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sr/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sr/LC_MESSAGES/ -rw-r--r-- root/root 49079 2011-02-08 02:14 ./usr/share/locale/sr/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sr@latin/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sr@latin/LC_MESSAGES/ -rw-r--r-- root/root 38257 2011-02-08 02:14 ./usr/share/locale/sr@latin/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sv/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/sv/LC_MESSAGES/ -rw-r--r-- root/root 10432 2011-02-08 02:14 ./usr/share/locale/sv/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ta/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/ta/LC_MESSAGES/ -rw-r--r-- root/root 62662 2011-02-08 02:14 ./usr/share/locale/ta/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/th/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/th/LC_MESSAGES/ -rw-r--r-- root/root 1655 2011-02-08 02:14 ./usr/share/locale/th/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_CN/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_CN/LC_MESSAGES/ -rw-r--r-- root/root 35556 2011-02-08 02:14 ./usr/share/locale/zh_CN/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_HK/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_HK/LC_MESSAGES/ -rw-r--r-- root/root 36350 2011-02-08 02:14 ./usr/share/locale/zh_HK/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_TW/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/locale/zh_TW/LC_MESSAGES/ -rw-r--r-- root/root 36347 2011-02-08 02:14 ./usr/share/locale/zh_TW/LC_MESSAGES/gnome-color-manager.mo drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/polkit-1/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/polkit-1/actions/ -rw-r--r-- root/root 7363 2011-02-08 02:14 ./usr/share/polkit-1/actions/org.gnome.color.policy drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/doc/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/doc/gnome-color-manager/ -rw-r--r-- root/root 680 2011-02-08 01:48 ./usr/share/doc/gnome-color-manager/copyright -rw-r--r-- root/root 904 2011-02-08 02:00 ./usr/share/doc/gnome-color-manager/changelog.Debian.gz drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gconf/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/share/gconf/schemas/ -rw-r--r-- root/root 104162 2011-02-08 02:14 ./usr/share/gconf/schemas/gnome-color-manager.schemas drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/bin/ -rwxr-xr-x root/root 75940 2011-02-08 02:14 ./usr/bin/gcm-inspect -rwxr-xr-x root/root 47032 2011-02-08 02:14 ./usr/bin/gcm-dump-profile -rwxr-xr-x root/root 9620 2011-02-08 02:14 ./usr/bin/gcm-fix-profile -rwxr-xr-x root/root 34676 2011-02-08 02:14 ./usr/bin/gcm-dump-edid -rwxr-xr-x root/root 113008 2011-02-08 02:14 ./usr/bin/gcm-apply -rwxr-xr-x root/root 257364 2011-02-08 02:14 ./usr/bin/gcm-prefs -rwxr-xr-x root/root 129608 2011-02-08 02:14 ./usr/bin/gcm-session -rwxr-xr-x root/root 67692 2011-02-08 02:14 ./usr/bin/gcm-import drwxr-xr-x root/root 0 2011-02-08 02:14 ./usr/sbin/ -rwxr-xr-x root/root 9664 2011-02-08 02:14 ./usr/sbin/gcm-install-system-wide drwxr-xr-x root/root 0 2011-02-08 02:14 ./etc/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./etc/xdg/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./etc/xdg/autostart/ -rw-r--r-- root/root 6247 2011-02-08 02:14 ./etc/xdg/autostart/gcm-apply.desktop drwxr-xr-x root/root 0 2011-02-08 02:14 ./lib/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./lib/udev/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./lib/udev/rules.d/ -rw-r--r-- root/root 3090 2011-02-08 02:14 ./lib/udev/rules.d/95-gcm-colorimeters.rules -rw-r--r-- root/root 1098 2011-02-08 02:14 ./lib/udev/rules.d/95-gcm-devices.rules drwxr-xr-x root/root 0 2011-02-08 02:14 ./var/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./var/lib/ drwxr-xr-x root/root 0 2011-02-08 02:14 ./var/lib/color/ lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/scalable/mimetypes/application-vnd.iccprofile.svg -> ../apps/gnome-color-manager.svg lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/16x16/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/22x22/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/24x24/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/32x32/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/48x48/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/64x64/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/icons/hicolor/256x256/mimetypes/application-vnd.iccprofile.png -> ../apps/gnome-color-manager.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-calibrate-default.png -> ../../C/figures/gcm-calibrate-default.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/cs/figures/gcm-import.png -> ../../C/figures/gcm-import.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-calibrate-default.png -> ../../C/figures/gcm-calibrate-default.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/de/figures/gcm-import.png -> ../../C/figures/gcm-import.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-calibrate-default.png -> ../../C/figures/gcm-calibrate-default.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/el/figures/gcm-import.png -> ../../C/figures/gcm-import.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-calibrate-default.png -> ../../C/figures/gcm-calibrate-default.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/es/figures/gcm-import.png -> ../../C/figures/gcm-import.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-calibrate-default.png -> ../../C/figures/gcm-calibrate-default.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/id/figures/gcm-import.png -> ../../C/figures/gcm-import.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-adjust.png -> ../../C/figures/gcm-adjust.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-basic.png -> ../../C/figures/gcm-basic.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-scanner.png -> ../../C/figures/gcm-scanner.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-calibrate-drawing.png -> ../../C/figures/gcm-calibrate-drawing.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-print-mode.png -> ../../C/figures/gcm-print-mode.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-screen-type.png -> ../../C/figures/gcm-screen-type.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-device-configure.png -> ../../C/figures/gcm-device-configure.png lrwxrwxrwx root/root 0 2011-02-08 02:14 ./usr/share/gnome/help/gnome-color-manager/ru/figures/gcm-import.png -> ../../C/figures/gcm-import.png gnome-color-manager_2.32.0-0ubuntu1_i386.changes: Format: 1.8 Date: Tue, 08 Feb 2011 12:54:14 +1100 Source: gnome-color-manager Binary: gnome-color-manager Architecture: i386 i386_translations Version: 2.32.0-0ubuntu1 Distribution: natty Urgency: low Maintainer: Ubuntu/i386 Build Daemon Changed-By: Robert Ancell Description: gnome-color-manager - Color management integration for the Gnome desktop environment Changes: gnome-color-manager (2.32.0-0ubuntu1) natty; urgency=low . * New upstream release. * debian/control: - Lower libvte-dev version - Add build-depends on dh-autoreconf - Use standards version 3.9.1 - Drop Vcs-Bzr link, use lp:ubuntu/gnome-color-manager * debian/rules: - Use --with autoreconf Checksums-Sha1: ea7b0a5bc96041fe8595290a7d014f57e95bba40 1977504 gnome-color-manager_2.32.0-0ubuntu1_i386.deb 51fc4b07ee1d990f723e6ec0a67c24f5357027c3 1045178 gnome-color-manager_2.32.0-0ubuntu1_i386_translations.tar.gz Checksums-Sha256: 98c881fb8dd323c8f8e0fb60f12419165e4c3b3823d91aef1ab3841e9c1cece0 1977504 gnome-color-manager_2.32.0-0ubuntu1_i386.deb 55b4606ba2f90ba4d2f90e84cbb8f23b88748e6851c03a84449039a80baff2c3 1045178 gnome-color-manager_2.32.0-0ubuntu1_i386_translations.tar.gz Files: 7e6021f731792b58a68892559cd143a9 1977504 gnome optional gnome-color-manager_2.32.0-0ubuntu1_i386.deb f0afeb737625f955f8872177d4950f2e 1045178 raw-translations - gnome-color-manager_2.32.0-0ubuntu1_i386_translations.tar.gz ****************************************************************************** Built successfully Purging chroot-autobuild/build/buildd/gnome-color-manager-2.32.0 ------------------------------------------------------------------------------ /usr/bin/sudo dpkg --purge sp groff-base libavahi-common3 libx11-data m4 libxaw7 x11-common libgphoto2-2 libidl-dev libvorbis0a docbook-dsssl libxi6 automake libv4l-dev libxcursor1 x11proto-input-dev libexpat1-dev x11proto-xf86vidmode-dev libjpeg62-dev libtiffxx0c2 libdbus-glib-1-2 docbook-xml librarian0 python-cairo libx11-6 libvte-dev xtrans-dev libsgmls-perl gnome-doc-utils libxdamage1 libxt6 libffi5 sgml-data texlive-base libdbus-1-dev libhtml-tree-perl texlive-doc-base libglib2.0-dev libkrb5-dev x11proto-xext-dev gtk-doc-tools pkg-config python-libxml2 libtool libxrender1 libfontconfig1-dev libpython2.7 libcups2-dev xml-core libtasn1-3-dev libxrandr-dev libcups2 libxau-dev libdatrie1 libpng12-dev libgudev-1.0-dev jade libxft2 libxext6 libpipeline1 libltdl7 libasound2 libsqlite3-0 libnotify1 libkadm5srv-mit7 libxcb-aux0 gnome-common libxmu6 libgudev-1.0-0 libcairo2-dev libexif12 fontconfig liburi-perl libstartup-notification0 libxpm4 libavahi-common-dev libcroco3 libcanberra-gtk-dev libkdb5-4 gir1.2-glib-2.0 libfreetype6 texlive-latex-recommended libatk1.0-0 python2.7 x11proto-damage-dev libidl0 libxcb1 html2text libxrandr2 debhelper libthai0 python-vte python libxslt1.1 libmagic1 libgnutls-dev libtiff4 gnome-pkg-tools libexpat1 libxau6 libpango1.0-dev libxcomposite1 docbook-xsl libieee1284-3 x11proto-composite-dev libgconf2-4 sgmlspl mime-support libcanberra0 libxi-dev libwww-perl shared-mime-info libxfixes3 libgtk2.0-dev liblcms1 ed x11proto-kb-dev x11proto-xinerama-dev libpthread-stubs0-dev libgnome-desktop-dev libpango1.0-0 gettext-base libunistring0 libostyle1c2 libcanberra-gtk0 libgphoto2-port0 libxcb-render0 texlive-binaries libunique-1.0-0 libglib2.0-bin libgssrpc4 jadetex libxfixes-dev fontconfig-config libgconf2-dev file gettext libstartup-notification0-dev zlib1g-dev libhtml-parser-perl libkadm5clnt-mit7 libcairo2 libvte9 lynx texlive-common tipa libcairo-gobject2 libx11-dev libcanberra-dev libatk1.0-data libjpeg62 docbook-utils libnotify-dev libvte-common libieee1284-3-dev libxcb-event1 python-gtk2 libv4l-0 libexif-dev libgdk-pixbuf2.0-0 libgphoto2-2-dev libcanberra-gtk-common-dev libjasper1 libpixman-1-dev libxcomposite-dev libfontconfig1 sgml-base libosp5 libxcb-shm0-dev libbsd0 xsltproc texlive-fonts-recommended psmisc x11proto-randr-dev libxinerama-dev libglib2.0-data libkpathsea5 comerr-dev libxml2-utils libgdk-pixbuf2.0-dev gconf2 libgpg-error-dev libunique-dev libhtml-tagset-perl dbus libxml2 libthai-data libice6 intltool-debian libavahi-client3 liborbit2-dev libxext-dev texlive-latex-base openjade libxrender-dev lynx-cur libavahi-common-data x11proto-render-dev docbook-to-man libxinerama1 libxxf86vm-dev libdbus-glib-1-dev libsm-dev libxdamage-dev gconf2-common libxdmcp-dev ttf-dejavu-core libpoppler12 libxcb-render0-dev libgcrypt11-dev libavahi-client-dev autotools-dev docbook dh-autoreconf liborbit2 libpopt0 python-support libice-dev libvorbisfile3 rarian-compat libfreetype6-dev x11proto-fixes-dev libgtk2.0-0 libgnome-desktop-2-17 libxcb-atom1 tex-common libsp1c2 libpthread-stubs0 libudev-dev python-gobject libxcb-shm0 bsdmainutils libtdb1 liblcms1-dev libsane-dev libxcursor-dev x11proto-core-dev intltool libogg0 libxcb1-dev libxdmcp6 libsane po-debconf libatk1.0-dev libxml-parser-perl libxft-dev krb5-multidev libxxf86vm1 man-db dbus-x11 scrollkeeper libpixman-1-0 libusb-dev luatex ucf libgtk2.0-common libgirepository-1.0-1 libtiff4-dev libsm6 autoconf (Reading database ... 33657 files and directories currently installed.) Removing libvte-dev ... Removing gnome-doc-utils ... Removing gtk-doc-tools ... Purging configuration files for gtk-doc-tools ... Removing python-libxml2 ... Removing libcups2-dev ... Removing libgudev-1.0-dev ... Removing jade ... Purging configuration files for jade ... Removing gnome-common ... Removing libgudev-1.0-0 ... Purging configuration files for libgudev-1.0-0 ... Removing libcanberra-gtk-dev ... Removing python-vte ... Removing libgnutls-dev ... Removing gnome-pkg-tools ... Removing docbook-xsl ... Purging configuration files for docbook-xsl ... Removing libgnome-desktop-dev ... Removing libcanberra-gtk0 ... Purging configuration files for libcanberra-gtk0 ... Removing libgconf2-dev ... Removing libstartup-notification0-dev ... Removing libvte9 ... Purging configuration files for libvte9 ... Removing libcanberra-dev ... Removing docbook-utils ... Removing libnotify-dev ... Removing libvte-common ... Removing python-gtk2 ... Removing libcanberra-gtk-common-dev ... Removing xsltproc ... Removing gconf2 ... Purging configuration files for gconf2 ... Removing libunique-dev ... Removing liborbit2-dev ... Removing docbook-to-man ... Removing libxxf86vm-dev ... Removing libdbus-glib-1-dev ... Removing libgcrypt11-dev ... Removing docbook ... Purging configuration files for docbook ... Removing dh-autoreconf ... Removing libgnome-desktop-2-17 ... Purging configuration files for libgnome-desktop-2-17 ... Removing libudev-dev ... Removing python-gobject ... Purging configuration files for python-gobject ... Removing liblcms1-dev ... Removing libsane-dev ... Removing intltool ... Removing libsane ... Purging configuration files for libsane ... Removing directory /etc/sane.d/ ... Removing libxml-parser-perl ... Removing libxxf86vm1 ... Purging configuration files for libxxf86vm1 ... Removing scrollkeeper ... Removing libtiff4-dev ... Removing sp ... Removing libidl-dev ... Removing docbook-dsssl ... Purging configuration files for docbook-dsssl ... Removing automake ... Removing libv4l-dev ... Removing x11proto-xf86vidmode-dev ... Removing libjpeg62-dev ... Removing libtiffxx0c2 ... Purging configuration files for libtiffxx0c2 ... Removing python-cairo ... Removing libkrb5-dev ... Removing libtool ... Removing libtasn1-3-dev ... Removing libnotify1 ... Purging configuration files for libnotify1 ... Removing libstartup-notification0 ... Purging configuration files for libstartup-notification0 ... Removing gir1.2-glib-2.0 ... Removing debhelper ... Removing libxslt1.1 ... Purging configuration files for libxslt1.1 ... Removing libgconf2-4 ... Purging configuration files for libgconf2-4 ... Removing sgmlspl ... Removing libcanberra0 ... Purging configuration files for libcanberra0 ... Removing libwww-perl ... Removing libgtk2.0-dev ... Removing libunique-1.0-0 ... Purging configuration files for libunique-1.0-0 ... Removing jadetex ... Purging configuration files for jadetex ... Replacing config file /etc/texmf/texmf.cnf with new version Removing file ... Removing lynx ... Removing tipa ... Running 'mktexlsr /usr/share/texmf /var/lib/texmf'. This may take some time... done. Purging configuration files for tipa ... Removing libieee1284-3-dev ... Removing libxcb-event1 ... Purging configuration files for libxcb-event1 ... Removing libv4l-0 ... Purging configuration files for libv4l-0 ... Removing libgphoto2-2-dev ... Removing libxcomposite-dev ... Removing texlive-fonts-recommended ... Purging configuration files for texlive-fonts-recommended ... Removing psmisc ... Purging configuration files for psmisc ... Removing libxinerama-dev ... Removing libxml2-utils ... Removing libgdk-pixbuf2.0-dev ... Removing libgpg-error-dev ... Removing openjade ... Purging configuration files for openjade ... Removing lynx-cur ... Purging configuration files for lynx-cur ... Removing libxdamage-dev ... Removing gconf2-common ... Purging configuration files for gconf2-common ... Removing libavahi-client-dev ... Removing autotools-dev ... Removing liborbit2 ... Purging configuration files for liborbit2 ... Removing python-support ... Purging configuration files for python-support ... Removing libvorbisfile3 ... Purging configuration files for libvorbisfile3 ... Removing rarian-compat ... Purging configuration files for rarian-compat ... Removing libgtk2.0-0 ... Purging configuration files for libgtk2.0-0 ... dpkg: warning: while removing libgtk2.0-0, directory '/usr/lib/gtk-2.0/2.10.0' not empty so not removed. dpkg: warning: while removing libgtk2.0-0, directory '/usr/lib/gtk-2.0' not empty so not removed. Removing libxcb-atom1 ... Purging configuration files for libxcb-atom1 ... Removing libsp1c2 ... Purging configuration files for libsp1c2 ... Removing libtdb1 ... Purging configuration files for libtdb1 ... Removing libxcursor-dev ... Removing po-debconf ... Removing libatk1.0-dev ... Removing krb5-multidev ... Removing man-db ... Purging configuration files for man-db ... Removing catpages as well as /var/cache/man hierarchy. Removing dbus-x11 ... Purging configuration files for dbus-x11 ... Removing libusb-dev ... Removing libgtk2.0-common ... Removing libgirepository-1.0-1 ... Purging configuration files for libgirepository-1.0-1 ... Removing autoconf ... Purging configuration files for autoconf ... Removing groff-base ... Purging configuration files for groff-base ... Removing m4 ... Removing libgphoto2-2 ... Purging configuration files for libgphoto2-2 ... Removing libvorbis0a ... Purging configuration files for libvorbis0a ... Removing libxcursor1 ... Purging configuration files for libxcursor1 ... Removing libdbus-glib-1-2 ... Purging configuration files for libdbus-glib-1-2 ... Removing docbook-xml ... Purging configuration files for docbook-xml ... Removing librarian0 ... Purging configuration files for librarian0 ... Removing libsgmls-perl ... Removing libxdamage1 ... Purging configuration files for libxdamage1 ... Removing libffi5 ... Purging configuration files for libffi5 ... Removing sgml-data ... Purging configuration files for sgml-data ... Removing libdbus-1-dev ... Removing libhtml-tree-perl ... Removing xml-core ... Purging configuration files for xml-core ... dpkg: warning: while removing xml-core, directory '/etc/sgml' not empty so not removed. Removing libxrandr-dev ... Removing libcups2 ... Purging configuration files for libcups2 ... Removing libpipeline1 ... Purging configuration files for libpipeline1 ... Removing libasound2 ... Purging configuration files for libasound2 ... Removing libkadm5srv-mit7 ... Purging configuration files for libkadm5srv-mit7 ... Removing libxcb-aux0 ... Purging configuration files for libxcb-aux0 ... Removing libavahi-common-dev ... Removing libkdb5-4 ... Purging configuration files for libkdb5-4 ... Removing texlive-latex-recommended ... Purging configuration files for texlive-latex-recommended ... Removing libatk1.0-0 ... Purging configuration files for libatk1.0-0 ... Removing x11proto-damage-dev ... Removing libidl0 ... Purging configuration files for libidl0 ... Removing html2text ... Purging configuration files for html2text ... Removing libxrandr2 ... Purging configuration files for libxrandr2 ... Removing python ... Purging configuration files for python ... Removing libmagic1 ... Purging configuration files for libmagic1 ... Removing libpango1.0-dev ... Removing libxcomposite1 ... Purging configuration files for libxcomposite1 ... Removing libieee1284-3 ... Purging configuration files for libieee1284-3 ... Removing x11proto-composite-dev ... Removing libxi-dev ... Removing shared-mime-info ... Purging configuration files for shared-mime-info ... Removing x11proto-xinerama-dev ... Removing libpango1.0-0 ... Purging configuration files for libpango1.0-0 ... Removing libostyle1c2 ... Purging configuration files for libostyle1c2 ... Removing libgphoto2-port0 ... Purging configuration files for libgphoto2-port0 ... Removing libxfixes-dev ... Removing libhtml-parser-perl ... Removing libkadm5clnt-mit7 ... Purging configuration files for libkadm5clnt-mit7 ... Removing libatk1.0-data ... Removing libexif-dev ... Removing libgdk-pixbuf2.0-0 ... Purging configuration files for libgdk-pixbuf2.0-0 ... Removing libjasper1 ... Purging configuration files for libjasper1 ... Removing sgml-base ... Purging configuration files for sgml-base ... Removing libosp5 ... Purging configuration files for libosp5 ... Removing libbsd0 ... Purging configuration files for libbsd0 ... Removing x11proto-randr-dev ... Removing comerr-dev ... Removing libhtml-tagset-perl ... Removing dbus ... Purging configuration files for dbus ... rmdir: failed to remove `/var/lib/dbus': No such file or directory Removing intltool-debian ... Removing libavahi-client3 ... Purging configuration files for libavahi-client3 ... Removing libxext-dev ... Removing texlive-latex-base ... Purging configuration files for texlive-latex-base ... Removing libxinerama1 ... Purging configuration files for libxinerama1 ... Removing x11proto-fixes-dev ... Removing bsdmainutils ... Purging configuration files for bsdmainutils ... Removing libogg0 ... Purging configuration files for libogg0 ... Removing libxft-dev ... Removing libavahi-common3 ... Purging configuration files for libavahi-common3 ... Removing libxi6 ... Purging configuration files for libxi6 ... Removing texlive-base ... Purging configuration files for texlive-base ... Removing texlive-doc-base ... Purging configuration files for texlive-doc-base ... Removing x11proto-xext-dev ... Removing libpython2.7 ... Purging configuration files for libpython2.7 ... Removing libxft2 ... Purging configuration files for libxft2 ... Removing libltdl7 ... Purging configuration files for libltdl7 ... Removing libcairo2-dev ... Removing libexif12 ... Purging configuration files for libexif12 ... Removing fontconfig ... Purging configuration files for fontconfig ... Removing liburi-perl ... Removing python2.7 ... Purging configuration files for python2.7 ... Removing libthai0 ... Purging configuration files for libthai0 ... Removing libtiff4 ... Purging configuration files for libtiff4 ... Removing mime-support ... Purging configuration files for mime-support ... Removing libxfixes3 ... Purging configuration files for libxfixes3 ... Removing texlive-binaries ... Removing libgssrpc4 ... Purging configuration files for libgssrpc4 ... Removing gettext ... Removing texlive-common ... Removing libcairo-gobject2 ... Purging configuration files for libcairo-gobject2 ... Removing libpixman-1-dev ... Removing libxcb-shm0-dev ... Removing libkpathsea5 ... Purging configuration files for libkpathsea5 ... Removing libthai-data ... Removing libxrender-dev ... Removing libavahi-common-data ... Removing x11proto-render-dev ... Removing libsm-dev ... Removing libxcb-render0-dev ... Removing libice-dev ... Removing tex-common ... Purging configuration files for tex-common ... Removing luatex ... Removing libxaw7 ... Purging configuration files for libxaw7 ... Removing libglib2.0-dev ... dpkg: warning: while removing libglib2.0-dev, directory '/usr/share/glib-2.0/schemas' not empty so not removed. dpkg: warning: while removing libglib2.0-dev, directory '/usr/share/glib-2.0' not empty so not removed. Removing libfontconfig1-dev ... Removing libdatrie1 ... Purging configuration files for libdatrie1 ... Removing libpng12-dev ... Removing libsqlite3-0 ... Purging configuration files for libsqlite3-0 ... Removing libxmu6 ... Purging configuration files for libxmu6 ... Removing libxpm4 ... Purging configuration files for libxpm4 ... Removing libcroco3 ... Purging configuration files for libcroco3 ... Removing ed ... Removing gettext-base ... Removing libunistring0 ... Purging configuration files for libunistring0 ... Removing libglib2.0-bin ... Removing libcairo2 ... Purging configuration files for libcairo2 ... Removing libx11-dev ... Removing libglib2.0-data ... Removing libpoppler12 ... Purging configuration files for libpoppler12 ... Removing libfreetype6-dev ... Removing libxcb-shm0 ... Purging configuration files for libxcb-shm0 ... Removing libxcb1-dev ... Removing libpixman-1-0 ... Purging configuration files for libpixman-1-0 ... Removing x11proto-input-dev ... Removing libexpat1-dev ... Removing xtrans-dev ... Removing libxt6 ... Purging configuration files for libxt6 ... Removing pkg-config ... Removing libxrender1 ... Purging configuration files for libxrender1 ... Removing libxau-dev ... Removing libxext6 ... Purging configuration files for libxext6 ... Removing liblcms1 ... Purging configuration files for liblcms1 ... Removing x11proto-kb-dev ... Removing libpthread-stubs0-dev ... Removing libxcb-render0 ... Purging configuration files for libxcb-render0 ... Removing zlib1g-dev ... Removing libjpeg62 ... Removing libfontconfig1 ... Purging configuration files for libfontconfig1 ... Removing libxml2 ... Purging configuration files for libxml2 ... Removing libxdmcp-dev ... Removing libpopt0 ... Purging configuration files for libpopt0 ... Removing libpthread-stubs0 ... Removing x11proto-core-dev ... Removing libsm6 ... Purging configuration files for libsm6 ... Removing libx11-6 ... Purging configuration files for libx11-6 ... Removing libfreetype6 ... Purging configuration files for libfreetype6 ... Removing libxcb1 ... Purging configuration files for libxcb1 ... Removing libexpat1 ... Purging configuration files for libexpat1 ... Removing libxau6 ... Purging configuration files for libxau6 ... Removing fontconfig-config ... Purging configuration files for fontconfig-config ... Removing libice6 ... Purging configuration files for libice6 ... Removing ttf-dejavu-core ... Removing libxdmcp6 ... Purging configuration files for libxdmcp6 ... Removing ucf ... Purging configuration files for ucf ... Removing libx11-data ... Removing x11-common ... Purging configuration files for x11-common ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for libglib2.0-0 ... No schema files found: removed existing output file. ****************************************************************************** Finished at 20110208-0218 Build needed 00:02:13, 26920k disk space RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['/usr/share/launchpad-buildd/slavebin/scan-for-processes', '67529e7885e182ae39e99b454fbb9ed8ab9539a0'] Scanning for processes to kill in build /home/buildd/build-67529e7885e182ae39e99b454fbb9ed8ab9539a0/chroot-autobuild... RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', '67529e7885e182ae39e99b454fbb9ed8ab9539a0'] Unmounting chroot for build 67529e7885e182ae39e99b454fbb9ed8ab9539a0... RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', '67529e7885e182ae39e99b454fbb9ed8ab9539a0'] Removing build 67529e7885e182ae39e99b454fbb9ed8ab9539a0