Installing /builddir/build/SRPMS/istanbul-0.2.2-4.fc8.src.rpm Building target platforms: i386 Building for target i386 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.46512 + umask 022 + cd /builddir/build/BUILD + LANG=C + export LANG + unset DISPLAY + cd /builddir/build/BUILD + rm -rf istanbul-0.2.2 + /usr/bin/bzip2 -dc /builddir/build/SOURCES/istanbul-0.2.2.tar.bz2 + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd istanbul-0.2.2 ++ /usr/bin/id -u + '[' 101 = 0 ']' ++ /usr/bin/id -u + '[' 101 = 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + echo 'Patch #0 (istanbul-configure.patch):' Patch #0 (istanbul-configure.patch): + patch -p0 -s + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.46512 + umask 022 + cd /builddir/build/BUILD + cd istanbul-0.2.2 + LANG=C + export LANG + unset DISPLAY + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' + export FFLAGS ++ find . -name config.guess -o -name config.sub + for i in '$(find . -name config.guess -o -name config.sub)' ++ basename ./config.sub + '[' -f /usr/lib/rpm/redhat/config.sub ']' + /bin/rm -f ./config.sub ++ basename ./config.sub + /bin/cp -fv /usr/lib/rpm/redhat/config.sub ./config.sub `/usr/lib/rpm/redhat/config.sub' -> `./config.sub' + for i in '$(find . -name config.guess -o -name config.sub)' ++ basename ./config.guess + '[' -f /usr/lib/rpm/redhat/config.guess ']' + /bin/rm -f ./config.guess ++ basename ./config.guess + /bin/cp -fv /usr/lib/rpm/redhat/config.guess ./config.guess `/usr/lib/rpm/redhat/config.guess' -> `./config.guess' + ./configure --build=i386-redhat-linux-gnu --host=i386-redhat-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info configure: configuring istanbul for release 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... gawk checking whether make sets $(MAKE)... yes configure: Storing library files in /usr/lib configure: Storing data files in /usr/share configure: Storing configuration files in /etc configure: Using localstatedir /var checking build system type... i386-redhat-linux-gnu checking host system type... i386-redhat-linux-gnu checking for style of include used by make... GNU checking for i386-redhat-linux-gnu-gcc... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 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 ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all 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 dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for i386-redhat-linux-gnu-g++... no checking for i386-redhat-linux-gnu-c++... no checking for i386-redhat-linux-gnu-gpp... no checking for i386-redhat-linux-gnu-aCC... no checking for i386-redhat-linux-gnu-CC... no checking for i386-redhat-linux-gnu-cxx... no checking for i386-redhat-linux-gnu-cc++... no checking for i386-redhat-linux-gnu-cl.exe... no checking for i386-redhat-linux-gnu-FCC... no checking for i386-redhat-linux-gnu-KCC... no checking for i386-redhat-linux-gnu-RCC... no checking for i386-redhat-linux-gnu-xlC_r... no checking for i386-redhat-linux-gnu-xlC... no checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for i386-redhat-linux-gnu-g77... no checking for i386-redhat-linux-gnu-xlf... no checking for i386-redhat-linux-gnu-f77... no checking for i386-redhat-linux-gnu-frt... no checking for i386-redhat-linux-gnu-pgf77... no checking for i386-redhat-linux-gnu-cf77... no checking for i386-redhat-linux-gnu-fort77... no checking for i386-redhat-linux-gnu-fl32... no checking for i386-redhat-linux-gnu-af77... no checking for i386-redhat-linux-gnu-xlf90... no checking for i386-redhat-linux-gnu-f90... no checking for i386-redhat-linux-gnu-pgf90... no checking for i386-redhat-linux-gnu-pghpf... no checking for i386-redhat-linux-gnu-epcf90... no checking for i386-redhat-linux-gnu-gfortran... no checking for i386-redhat-linux-gnu-g95... no checking for i386-redhat-linux-gnu-xlf95... no checking for i386-redhat-linux-gnu-f95... no checking for i386-redhat-linux-gnu-fort... no checking for i386-redhat-linux-gnu-ifort... no checking for i386-redhat-linux-gnu-ifc... no checking for i386-redhat-linux-gnu-efc... no checking for i386-redhat-linux-gnu-pgf95... no checking for i386-redhat-linux-gnu-lf95... no checking for i386-redhat-linux-gnu-ftn... no checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments... 32768 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for i386-redhat-linux-gnu-ar... no checking for ar... ar checking for i386-redhat-linux-gnu-ranlib... no checking for ranlib... ranlib checking for i386-redhat-linux-gnu-strip... no checking for strip... strip checking for correct ltmain.sh version... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... cat: ld.so.conf.d/*.conf: No such file or directory 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... no configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... cat: ld.so.conf.d/*.conf: No such file or directory GNU/Linux ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool configure: Looking for Python version >= 2.3 checking for python... /usr/bin/python checking "/usr/bin/python":... okay checking local Python configuration... looks good checking for python version... 2.5 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.5/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages checking for headers required to compile python extensions... found configure: Using pythondir /usr/lib/python2.5/site-packages checking for intltool >= 0.35.0... 0.35.0 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext 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... /usr/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for i386-redhat-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GST... yes checking for PYGTK... yes configure: Using pygtk installed in /usr/lib/python2.5/site-packages checking for GTK... yes checking for PYGST... yes configure: Using gstreamer-python 0.10 installed in /usr/lib/python2.5/site-packages checking for python module gst... found checking for GNOME_PYTHON_EXTRAS... yes checking for python module gconf... found found checking for python module Xlib.X... found checking for i386-redhat-linux-gnu-gcc... gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for GST_BASE... yes checking for GSTPB_BASE... checking for X... libraries , headers configure: *** checking feature: X libraries and plugins *** configure: *** for plug-ins: istximagesrc *** checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... no checking X11/Xlib.h usability... yes checking X11/Xlib.h presence... yes checking for X11/Xlib.h... yes checking for XFIXES... yes checking for XDAMAGE... configure: *** These plugins will be built: istximagesrc configure: *** checking feature: X Shared Memory extension *** checking for XShmAttach in -lXext... yes Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files configure: *** checking feature: GConf schemas *** checking for gconftool-2... /usr/bin/gconftool-2 configure: creating ./config.status config.status: creating Makefile config.status: creating bin/istanbul config.status: creating bin/Makefile config.status: creating common/Makefile config.status: creating gst/Makefile config.status: creating istanbul/Makefile config.status: creating istanbul/configure/config.py config.status: creating istanbul/configure/Makefile config.status: creating istanbul/main/Makefile config.status: creating data/Makefile config.status: creating doc/Makefile config.status: creating doc/man/Makefile config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands config.status: executing po/stamp-it commands + make -j4 Making all in . make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2' make[1]: Nothing to be done for `all-am'. make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2' Making all in common make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/common' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/common' Making all in gst make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/gst' /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"istanbul\" -DPACKAGE_TARNAME=\"istanbul\" -DPACKAGE_VERSION=\"0.2.2\" -DPACKAGE_STRING=\"istanbul\ 0.2.2\" -DPACKAGE_BUGREPORT=\"\" -DISTANBUL=\"0.2.2\" -DISTANBUL_RELEASE=\"1\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DGETTEXT_PACKAGE=\"istanbul\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_X= -DHAVE_XSHM= -DHAVE_GCONFTOOL= -I. -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_XFIXES -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -MT libistximagesrc_la-gstximagesrc.lo -MD -MP -MF .deps/libistximagesrc_la-gstximagesrc.Tpo -c -o libistximagesrc_la-gstximagesrc.lo `test -f 'gstximagesrc.c' || echo './'`gstximagesrc.c /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"istanbul\" -DPACKAGE_TARNAME=\"istanbul\" -DPACKAGE_VERSION=\"0.2.2\" -DPACKAGE_STRING=\"istanbul\ 0.2.2\" -DPACKAGE_BUGREPORT=\"\" -DISTANBUL=\"0.2.2\" -DISTANBUL_RELEASE=\"1\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DGETTEXT_PACKAGE=\"istanbul\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_X= -DHAVE_XSHM= -DHAVE_GCONFTOOL= -I. -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_XFIXES -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -MT libistximagesrc_la-ximageutil.lo -MD -MP -MF .deps/libistximagesrc_la-ximageutil.Tpo -c -o libistximagesrc_la-ximageutil.lo `test -f 'ximageutil.c' || echo './'`ximageutil.c mkdir .libs gcc -DPACKAGE_NAME=\"istanbul\" -DPACKAGE_TARNAME=\"istanbul\" -DPACKAGE_VERSION=\"0.2.2\" "-DPACKAGE_STRING=\"istanbul 0.2.2\"" -DPACKAGE_BUGREPORT=\"\" -DISTANBUL=\"0.2.2\" -DISTANBUL_RELEASE=\"1\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DGETTEXT_PACKAGE=\"istanbul\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_X= -DHAVE_XSHM= -DHAVE_GCONFTOOL= -I. -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_XFIXES -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -MT libistximagesrc_la-gstximagesrc.lo -MD -MP -MF .deps/libistximagesrc_la-gstximagesrc.Tpo -c gstximagesrc.c -fPIC -DPIC -o .libs/libistximagesrc_la-gstximagesrc.o gcc -DPACKAGE_NAME=\"istanbul\" -DPACKAGE_TARNAME=\"istanbul\" -DPACKAGE_VERSION=\"0.2.2\" "-DPACKAGE_STRING=\"istanbul 0.2.2\"" -DPACKAGE_BUGREPORT=\"\" -DISTANBUL=\"0.2.2\" -DISTANBUL_RELEASE=\"1\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DPACKAGE=\"istanbul\" -DVERSION=\"0.2.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DGETTEXT_PACKAGE=\"istanbul\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DHAVE_X= -DHAVE_XSHM= -DHAVE_GCONFTOOL= -I. -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_XFIXES -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -MT libistximagesrc_la-ximageutil.lo -MD -MP -MF .deps/libistximagesrc_la-ximageutil.Tpo -c ximageutil.c -fPIC -DPIC -o .libs/libistximagesrc_la-ximageutil.o mv -f .deps/libistximagesrc_la-ximageutil.Tpo .deps/libistximagesrc_la-ximageutil.Plo mv -f .deps/libistximagesrc_la-gstximagesrc.Tpo .deps/libistximagesrc_la-gstximagesrc.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DHAVE_XFIXES -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -o libistximagesrc.la -rpath /usr/lib/gstreamer-0.10 libistximagesrc_la-gstximagesrc.lo libistximagesrc_la-ximageutil.lo -pthread -lgstbase-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -ldl -lgthread-2.0 -lrt -lxml2 -lglib-2.0 -lX11 -lXext -lXfixes gcc -shared .libs/libistximagesrc_la-gstximagesrc.o .libs/libistximagesrc_la-ximageutil.o -lgstbase-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -ldl -lgthread-2.0 -lrt -lxml2 -lglib-2.0 -lX11 -lXext -lXfixes -pthread -pthread -m32 -march=i386 -mtune=generic -pthread -Wl,-soname -Wl,libistximagesrc.so.0 -o .libs/libistximagesrc.so.0.0.0 (cd .libs && rm -f libistximagesrc.so.0 && ln -s libistximagesrc.so.0.0.0 libistximagesrc.so.0) (cd .libs && rm -f libistximagesrc.so && ln -s libistximagesrc.so.0.0.0 libistximagesrc.so) creating libistximagesrc.la (cd .libs && rm -f libistximagesrc.la && ln -s ../libistximagesrc.la libistximagesrc.la) make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/gst' Making all in istanbul make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' Making all in configure make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' Making all in main make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' Making all in bin make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/bin' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/bin' Making all in data make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/data' LC_ALL=C ../intltool-merge -d -u -c ../po/.intltool-merge-cache ../po istanbul.desktop.in istanbul.desktop LC_ALL=C ../intltool-merge -s -u -c ../po/.intltool-merge-cache ../po istanbul.schemas.in istanbul.schemas Generating and caching the translation database Generating and caching the translation database Merging translations into istanbul.desktop. Merging translations into istanbul.schemas. make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/data' Making all in doc make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc' Making all in man make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc' Making all in po make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/po' file=`echo ar | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ar.po file=`echo bg | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file bg.po file=`echo ca | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file ca.po file=`echo dz | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file dz.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 fi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file fi.po file=`echo hi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hi.po file=`echo hu | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file hu.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 mk | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file mk.po file=`echo nl | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file nl.po file=`echo pa | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pa.po file=`echo pt_BR | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file pt_BR.po file=`echo sr | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr.po file=`echo sr@Latn | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sr@Latn.po file=`echo sv | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file sv.po file=`echo vi | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file vi.po file=`echo zh_CN | sed 's,.*/,,'`.gmo \ && rm -f $file && /usr/bin/msgfmt -o $file zh_CN.po make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/po' + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.23242 + umask 022 + cd /builddir/build/BUILD + cd istanbul-0.2.2 + LANG=C + export LANG + unset DISPLAY + rm -rf /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder + /usr/bin/make prefix=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr exec_prefix=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr bindir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/bin sbindir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/sbin sysconfdir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/etc datadir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share includedir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/include libdir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib libexecdir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/libexec localstatedir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/var sharedstatedir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/com mandir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/man infodir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/info install Making install in . make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2' Making install in common make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/common' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/common' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/common' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/common' Making install in gst make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/gst' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/gst' make[2]: Nothing to be done for `install-exec-am'. test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10" /bin/sh ../libtool --mode=install /usr/bin/install -c 'libistximagesrc.la' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10/libistximagesrc.la' /usr/bin/install -c .libs/libistximagesrc.so.0.0.0 /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10/libistximagesrc.so.0.0.0 (cd /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10 && { ln -s -f libistximagesrc.so.0.0.0 libistximagesrc.so.0 || { rm -f libistximagesrc.so.0 && ln -s libistximagesrc.so.0.0.0 libistximagesrc.so.0; }; }) (cd /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10 && { ln -s -f libistximagesrc.so.0.0.0 libistximagesrc.so || { rm -f libistximagesrc.so && ln -s libistximagesrc.so.0.0.0 libistximagesrc.so; }; }) /usr/bin/install -c .libs/libistximagesrc.lai /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10/libistximagesrc.la libtool: install: warning: remember to run `libtool --finish /usr/lib/gstreamer-0.10' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/gst' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/gst' Making install in istanbul make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' Making install in configure make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' make[3]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' make[3]: Nothing to be done for `install-exec-am'. test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/configure" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/configure" /usr/bin/install -c -m 644 '__init__.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/configure/__init__.py' /usr/bin/install -c -m 644 'config.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/configure/config.py' Byte-compiling python modules... __init__.py config.py Byte-compiling python modules (optimized versions) ... __init__.py config.py make[3]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/configure' Making install in main make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[3]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[3]: Nothing to be done for `install-exec-am'. test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main" /usr/bin/install -c -m 644 '__init__.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/__init__.py' /usr/bin/install -c -m 644 'main.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/main.py' /usr/bin/install -c -m 644 'area_select.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/area_select.py' /usr/bin/install -c -m 644 'window_select.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/window_select.py' /usr/bin/install -c -m 644 'preferences.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/preferences.py' /usr/bin/install -c -m 644 'command_line.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/command_line.py' /usr/bin/install -c -m 644 'gconf_client.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/gconf_client.py' /usr/bin/install -c -m 644 'tray_icon.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/tray_icon.py' /usr/bin/install -c -m 644 'screencast.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/screencast.py' /usr/bin/install -c -m 644 'tray_popup.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/tray_popup.py' /usr/bin/install -c -m 644 'constants.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/constants.py' /usr/bin/install -c -m 644 'screen.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/screen.py' /usr/bin/install -c -m 644 'save_window.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/save_window.py' /usr/bin/install -c -m 644 'gst_player.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/gst_player.py' /usr/bin/install -c -m 644 'checkradio_widget.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/main/checkradio_widget.py' Byte-compiling python modules... __init__.py main.py area_select.py window_select.py preferences.py command_line.py gconf_client.py tray_icon.py screencast.py tray_popup.py constants.py screen.py save_window.py gst_player.py checkradio_widget.py Byte-compiling python modules (optimized versions) ... __init__.py main.py area_select.py window_select.py preferences.py command_line.py gconf_client.py tray_icon.py screencast.py tray_popup.py constants.py screen.py save_window.py gst_player.py checkradio_widget.py make[3]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul/main' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[3]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[3]: Nothing to be done for `install-exec-am'. test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul" /usr/bin/install -c -m 644 '__init__.py' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/python2.5/site-packages/istanbul/__init__.py' Byte-compiling python modules... __init__.py Byte-compiling python modules (optimized versions) ... __init__.py make[3]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/istanbul' Making install in bin make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/bin' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/bin' test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/bin" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/bin" /usr/bin/install -c 'istanbul' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/bin/istanbul' make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/bin' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/bin' Making install in data make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/data' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/data' make[2]: Nothing to be done for `install-exec-am'. Resolved address "xml:merged:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 0 None of the resolved addresses are writable; saving configuration settings will not be possible Attached schema `/schemas/apps/istanbul/video_size' to key `/apps/istanbul/video_size' WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `fi': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `C': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `es': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `vi': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `pa': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `bg': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `en_GB': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `ja': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `pt_BR': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `hu': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `ca': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `nl': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `sv': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `dz': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_size' locale `mk': Unable to store a value at key '/schemas/apps/istanbul/video_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/istanbul/video_framerate' to key `/apps/istanbul/video_framerate' WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `fi': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `C': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `es': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `vi': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `pa': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `bg': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `en_GB': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `ja': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `pt_BR': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `hu': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `ca': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `nl': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `sv': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `dz': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/video_framerate' locale `mk': Unable to store a value at key '/schemas/apps/istanbul/video_framerate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/istanbul/record_3d' to key `/apps/istanbul/record_3d' WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `fi': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `C': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `es': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `vi': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `pa': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `bg': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `en_GB': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `ja': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `pt_BR': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `hu': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `ca': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `nl': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `sv': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `dz': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_3d' locale `mk': Unable to store a value at key '/schemas/apps/istanbul/record_3d', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/istanbul/record_mousepointer' to key `/apps/istanbul/record_mousepointer' WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `fi': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `C': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `es': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `vi': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `pa': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `bg': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `en_GB': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `ja': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `pt_BR': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `hu': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `ca': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `nl': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `sv': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `dz': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/istanbul/record_mousepointer' locale `mk': Unable to store a value at key '/schemas/apps/istanbul/record_mousepointer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only 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 "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/applications" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/applications" /usr/bin/install -c -m 644 'istanbul.desktop' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/applications/istanbul.desktop' test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/pixmaps" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/pixmaps" /usr/bin/install -c -m 644 'istanbul.png' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/pixmaps/istanbul.png' test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/etc/gconf/schemas" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/etc/gconf/schemas" /usr/bin/install -c -m 644 'istanbul.schemas' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/etc/gconf/schemas/istanbul.schemas' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/data' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/data' Making install in doc make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc' Making install in man make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[3]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[3]: Nothing to be done for `install-exec-am'. test -z "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/man/man1" || /bin/mkdir -p "/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/man/man1" /usr/bin/install -c -m 644 './istanbul.1' '/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/man/man1/istanbul.1' make[3]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc/man' make[2]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[3]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[2]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc' make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/doc' Making install in po make[1]: Entering directory `/builddir/build/BUILD/istanbul-0.2.2/po' /bin/sh /builddir/build/BUILD/istanbul-0.2.2/install-sh -d /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale if test -n "ar bg ca dz en_GB es fi hi hu it ja mk nl pa pt_BR sr sr@Latn sv vi zh_CN"; then \ linguas="ar bg ca dz en_GB es fi hi hu it ja mk nl pa pt_BR sr sr@Latn sv vi zh_CN"; \ else \ linguas=""; \ fi; \ for lang in $linguas; do \ dir=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/$lang/LC_MESSAGES; \ /bin/sh /builddir/build/BUILD/istanbul-0.2.2/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/istanbul.mo; \ echo "installing $lang.gmo as $dir/istanbul.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/istanbul.mo; \ echo "installing ./$lang.gmo as" \ "$dir/istanbul.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/istanbul.mo.m; \ echo "installing $lang.gmo.m as $dir/istanbul.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/istanbul.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/istanbul.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/ar/LC_MESSAGES/istanbul.mo installing bg.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/bg/LC_MESSAGES/istanbul.mo installing ca.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/ca/LC_MESSAGES/istanbul.mo installing dz.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/dz/LC_MESSAGES/istanbul.mo installing en_GB.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/en_GB/LC_MESSAGES/istanbul.mo installing es.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/es/LC_MESSAGES/istanbul.mo installing fi.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/fi/LC_MESSAGES/istanbul.mo installing hi.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/hi/LC_MESSAGES/istanbul.mo installing hu.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/hu/LC_MESSAGES/istanbul.mo installing it.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/it/LC_MESSAGES/istanbul.mo installing ja.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/ja/LC_MESSAGES/istanbul.mo installing mk.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/mk/LC_MESSAGES/istanbul.mo installing nl.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/nl/LC_MESSAGES/istanbul.mo installing pa.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/pa/LC_MESSAGES/istanbul.mo installing pt_BR.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/pt_BR/LC_MESSAGES/istanbul.mo installing sr.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/sr/LC_MESSAGES/istanbul.mo installing sr@Latn.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/sr@Latn/LC_MESSAGES/istanbul.mo installing sv.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/sv/LC_MESSAGES/istanbul.mo installing vi.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/vi/LC_MESSAGES/istanbul.mo installing zh_CN.gmo as /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/locale/zh_CN/LC_MESSAGES/istanbul.mo make[1]: Leaving directory `/builddir/build/BUILD/istanbul-0.2.2/po' + rm -f /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10/libistximagesrc.la + desktop-file-install --vendor gnome --delete-original --dir /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/applications --add-category X-Fedora-Extra /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/applications/istanbul.desktop + /usr/lib/rpm/find-lang.sh /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder istanbul + /usr/lib/rpm/find-debuginfo.sh /builddir/build/BUILD/istanbul-0.2.2 extracting debug info from /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/lib/gstreamer-0.10/libistximagesrc.so.0.0.0 symlinked /usr/lib/debug/usr/lib/gstreamer-0.10/libistximagesrc.so.0.0.0.debug to /usr/lib/debug/usr/lib/gstreamer-0.10/libistximagesrc.so.debug symlinked /usr/lib/debug/usr/lib/gstreamer-0.10/libistximagesrc.so.0.0.0.debug to /usr/lib/debug/usr/lib/gstreamer-0.10/libistximagesrc.so.0.debug 111 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: istanbul-0.2.2-4.fc8 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.63895 + umask 022 + cd /builddir/build/BUILD + cd istanbul-0.2.2 + DOCDIR=/var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/doc/istanbul-0.2.2 + export DOCDIR + rm -rf /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/doc/istanbul-0.2.2 + /bin/mkdir -p /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/doc/istanbul-0.2.2 + cp -pr COPYING ChangeLog /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder/usr/share/doc/istanbul-0.2.2 + exit 0 Provides: libistximagesrc.so.0 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: /usr/bin/python gnome-desktop >= 2.6.0 gnome-python2-extras gnome-python2-gconf gnome-python2-libegg gstreamer >= 0.10.9 gstreamer-plugins-good >= 0.10.3 gstreamer-python libX11.so.6 libXext.so.6 libXfixes.so.3 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.4) libdl.so.2 libglib-2.0.so.0 libgmodule-2.0.so.0 libgobject-2.0.so.0 libgstbase-0.10.so.0 libgstreamer-0.10.so.0 libgthread-2.0.so.0 libistximagesrc.so.0 libpthread.so.0 libpthread.so.0(GLIBC_2.0) librt.so.1 libxml2.so.2 pygtk2 >= 2.8.6 python(abi) = 2.5 python-xlib rtld(GNU_HASH) Processing files: istanbul-debuginfo-0.2.2-4.fc8 Provides: libistximagesrc.so.0.0.0.debug Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libistximagesrc.so.0 Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder warning: Could not canonicalize hostname: xenbuilder2.fedora.redhat.com Wrote: /builddir/build/RPMS/istanbul-0.2.2-4.fc8.i386.rpm Wrote: /builddir/build/RPMS/istanbul-debuginfo-0.2.2-4.fc8.i386.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.45620 + umask 022 + cd /builddir/build/BUILD + cd istanbul-0.2.2 + rm -rf /var/tmp/istanbul-0.2.2-4.fc8-root-kojibuilder + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.45620 + umask 022 + cd /builddir/build/BUILD + rm -rf istanbul-0.2.2 + exit 0