>>> Install ekiga-3.0.0 into /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image/ category net-im
Making install in man
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/man'
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/man'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/man/man1" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/man/man1"
 /usr/bin/install -c -m 644 './ekiga.1' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/man/man1/ekiga.1'
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/man'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/man'
Making install in sounds
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/sounds'
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/sounds'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/sounds/ekiga" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga"
 /usr/bin/install -c -m 644 'ring.wav' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga/ring.wav'
 /usr/bin/install -c -m 644 'busytone.wav' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga/busytone.wav'
 /usr/bin/install -c -m 644 'newmessage.wav' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga/newmessage.wav'
 /usr/bin/install -c -m 644 'dialtone.wav' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga/dialtone.wav'
 /usr/bin/install -c -m 644 'voicemail.wav' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/sounds/ekiga/voicemail.wav'
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/sounds'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/sounds'
Making install in pixmaps
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/icons/hicolor" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor"
test -z "/usr/share/pixmaps/ekiga" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/pixmaps/ekiga"
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '16x16/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/16x16/apps/ekiga.png'
 /usr/bin/install -c -m 644 'ekiga-logo.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/pixmaps/ekiga/ekiga-logo.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '22x22/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/22x22/apps/ekiga.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '32x32/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/32x32/apps/ekiga.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '48x48/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/48x48/apps/ekiga.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '64x64/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/64x64/apps/ekiga.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '72x72/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/72x72/apps/ekiga.png'
 /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -c -m 644 '128x128/apps/ekiga.png' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/icons/hicolor/128x128/apps/ekiga.png'
make  install-data-hook
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
*** Icon cache not updated.  After (un)install, run this:
***   gtk-update-icon-cache -f -t /usr/share/icons/hicolor
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/pixmaps'
Making install in lib
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make  install-recursive
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
Making install in gmconf
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gmconf'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gmconf'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gmconf'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gmconf'
Making install in gui
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/gui'
Making install in toolbox
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/toolbox'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/toolbox'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/toolbox'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/toolbox'
Making install in platform
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/platform'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/platform'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/platform'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/platform'
Making install in pixops
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/pixops'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/pixops'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/pixops'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/pixops'
Making install in engine
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
Making install in framework
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/framework'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/framework'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/framework'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/framework'
Making install in account
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account/skel'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/account'
Making install in addressbook
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/skel'
Making install in call-history
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/call-history'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/call-history'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/call-history'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/call-history'
Making install in ldap
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/ldap'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/ldap'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/ldap'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook/ldap'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/addressbook'
Making install in presence
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/skel'
Making install in local-roster
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/local-roster'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/local-roster'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/local-roster'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/local-roster'
Making install in avahi
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/avahi'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/avahi'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/avahi'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence/avahi'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/presence'
Making install in chat
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/skel'
Making install in echo
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/echo'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/echo'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/echo'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat/echo'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/chat'
Making install in gui
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
Making install in gtk-core
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-core'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-core'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-core'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-core'
Making install in gtk-frontend
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-frontend'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-frontend'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-frontend'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui/gtk-frontend'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/gui'
Making install in protocol
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol/skel'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/protocol'
Making install in videooutput
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/skel'
Making install in x
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/x'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/x'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/x'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput/x'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videooutput'
Making install in videoinput
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/skel'
Making install in mlogo
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/mlogo'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/mlogo'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/mlogo'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/mlogo'
Making install in ptlib
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/ptlib'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/ptlib'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/ptlib'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput/ptlib'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/videoinput'
Making install in audioinput
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/skel'
Making install in null
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/null'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/null'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/null'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/null'
Making install in ptlib
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/ptlib'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/ptlib'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/ptlib'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput/ptlib'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audioinput'
Making install in audiooutput
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/skel'
Making install in null
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/null'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/null'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/null'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/null'
Making install in ptlib
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/ptlib'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/ptlib'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/ptlib'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput/ptlib'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/audiooutput'
Making install in hal
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
Making install in skel
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/skel'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/skel'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/skel'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/skel'
Making install in dbus
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make  install-am
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make[7]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make[7]: Nothing to be done for `install-exec-am'.
make[7]: Nothing to be done for `install-data-am'.
make[7]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal/dbus'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/hal'
Making install in components
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
Making install in gmconf-personal-details
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/gmconf-personal-details'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/gmconf-personal-details'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/gmconf-personal-details'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/gmconf-personal-details'
Making install in avahi-publisher
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/avahi-publisher'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/avahi-publisher'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/avahi-publisher'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components/avahi-publisher'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
make[6]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine/components'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
make[5]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib/engine'
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make[4]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/lib'
Making install in src
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
make  install-am
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
make[3]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
test -z "/usr/bin" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin"
test -z "/usr/bin" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin"
 /usr/bin/install -c 'ekiga-config-tool' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin/ekiga-config-tool'
test -z "/usr/share/dbus-1/services" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/dbus-1/services"
  /bin/sh ../libtool   --mode=install /usr/bin/install -c 'ekiga' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin/ekiga'
 /usr/bin/install -c -m 644 'components/org.ekiga.Ekiga.service' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/dbus-1/services/org.ekiga.Ekiga.service'
 /usr/bin/install -c -m 644 'components/org.ekiga.Helper.service' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/dbus-1/services/org.ekiga.Helper.service'
/usr/bin/install -c ekiga /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin/ekiga
  /bin/sh ../libtool   --mode=install /usr/bin/install -c 'ekiga-helper' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin/ekiga-helper'
/usr/bin/install -c ekiga-helper /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/bin/ekiga-helper
make[3]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/src'
Making install in po
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/po'
/bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -d /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale
linguas="am ar as az be bg bn bn_IN bs ca cs cy da de dz el en_CA en_GB eo es et eu fa fi fr ga gl gu he hi hr hu id is it ja ka ko kn ku lt lv mai mk ml mn mr ms nb ne nl nn oc pa pl pt pt_BR ro ru rw si sk sl sq sr sr@latin sv ta te th tr uk vi wa xh zh_CN zh_HK zh_TW "; \
	for lang in $linguas; do \
	  dir=/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/$lang/LC_MESSAGES; \
	  /bin/sh /usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/install-sh -d $dir; \
	  if test -r $lang.gmo; then \
	    /usr/bin/install -c -m 644 $lang.gmo $dir/ekiga.mo; \
	    echo "installing $lang.gmo as $dir/ekiga.mo"; \
	  else \
	    /usr/bin/install -c -m 644 ./$lang.gmo $dir/ekiga.mo; \
	    echo "installing ./$lang.gmo as" \
		 "$dir/ekiga.mo"; \
	  fi; \
	  if test -r $lang.gmo.m; then \
	    /usr/bin/install -c -m 644 $lang.gmo.m $dir/ekiga.mo.m; \
	    echo "installing $lang.gmo.m as $dir/ekiga.mo.m"; \
	  else \
	    if test -r ./$lang.gmo.m ; then \
	      /usr/bin/install -c -m 644 ./$lang.gmo.m \
		$dir/ekiga.mo.m; \
	      echo "installing ./$lang.gmo.m as" \
		   "$dir/ekiga.mo.m"; \
	    else \
	      true; \
	    fi; \
	  fi; \
	done
installing am.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/am/LC_MESSAGES/ekiga.mo
installing ar.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ar/LC_MESSAGES/ekiga.mo
installing as.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/as/LC_MESSAGES/ekiga.mo
installing az.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/az/LC_MESSAGES/ekiga.mo
installing be.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/be/LC_MESSAGES/ekiga.mo
installing bg.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/bg/LC_MESSAGES/ekiga.mo
installing bn.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/bn/LC_MESSAGES/ekiga.mo
installing bn_IN.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/bn_IN/LC_MESSAGES/ekiga.mo
installing bs.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/bs/LC_MESSAGES/ekiga.mo
installing ca.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ca/LC_MESSAGES/ekiga.mo
installing cs.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/cs/LC_MESSAGES/ekiga.mo
installing cy.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/cy/LC_MESSAGES/ekiga.mo
installing da.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/da/LC_MESSAGES/ekiga.mo
installing de.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/de/LC_MESSAGES/ekiga.mo
installing dz.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/dz/LC_MESSAGES/ekiga.mo
installing el.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/el/LC_MESSAGES/ekiga.mo
installing en_CA.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/en_CA/LC_MESSAGES/ekiga.mo
installing en_GB.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/en_GB/LC_MESSAGES/ekiga.mo
installing eo.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/eo/LC_MESSAGES/ekiga.mo
installing es.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/es/LC_MESSAGES/ekiga.mo
installing et.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/et/LC_MESSAGES/ekiga.mo
installing eu.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/eu/LC_MESSAGES/ekiga.mo
installing fa.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/fa/LC_MESSAGES/ekiga.mo
installing fi.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/fi/LC_MESSAGES/ekiga.mo
installing fr.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/fr/LC_MESSAGES/ekiga.mo
installing ga.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ga/LC_MESSAGES/ekiga.mo
installing gl.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/gl/LC_MESSAGES/ekiga.mo
installing gu.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/gu/LC_MESSAGES/ekiga.mo
installing he.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/he/LC_MESSAGES/ekiga.mo
installing hi.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/hi/LC_MESSAGES/ekiga.mo
installing hr.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/hr/LC_MESSAGES/ekiga.mo
installing hu.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/hu/LC_MESSAGES/ekiga.mo
installing id.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/id/LC_MESSAGES/ekiga.mo
installing is.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/is/LC_MESSAGES/ekiga.mo
installing it.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/it/LC_MESSAGES/ekiga.mo
installing ja.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ja/LC_MESSAGES/ekiga.mo
installing ka.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ka/LC_MESSAGES/ekiga.mo
installing ko.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ko/LC_MESSAGES/ekiga.mo
installing kn.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/kn/LC_MESSAGES/ekiga.mo
installing ku.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ku/LC_MESSAGES/ekiga.mo
installing lt.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/lt/LC_MESSAGES/ekiga.mo
installing lv.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/lv/LC_MESSAGES/ekiga.mo
installing mai.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/mai/LC_MESSAGES/ekiga.mo
installing mk.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/mk/LC_MESSAGES/ekiga.mo
installing ml.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ml/LC_MESSAGES/ekiga.mo
installing mn.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/mn/LC_MESSAGES/ekiga.mo
installing mr.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/mr/LC_MESSAGES/ekiga.mo
installing ms.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ms/LC_MESSAGES/ekiga.mo
installing nb.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/nb/LC_MESSAGES/ekiga.mo
installing ne.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ne/LC_MESSAGES/ekiga.mo
installing nl.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/nl/LC_MESSAGES/ekiga.mo
installing nn.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/nn/LC_MESSAGES/ekiga.mo
installing oc.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/oc/LC_MESSAGES/ekiga.mo
installing pa.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/pa/LC_MESSAGES/ekiga.mo
installing pl.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/pl/LC_MESSAGES/ekiga.mo
installing pt.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/pt/LC_MESSAGES/ekiga.mo
installing pt_BR.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/pt_BR/LC_MESSAGES/ekiga.mo
installing ro.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ro/LC_MESSAGES/ekiga.mo
installing ru.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ru/LC_MESSAGES/ekiga.mo
installing rw.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/rw/LC_MESSAGES/ekiga.mo
installing si.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/si/LC_MESSAGES/ekiga.mo
installing sk.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sk/LC_MESSAGES/ekiga.mo
installing sl.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sl/LC_MESSAGES/ekiga.mo
installing sq.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sq/LC_MESSAGES/ekiga.mo
installing sr.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sr/LC_MESSAGES/ekiga.mo
installing sr@latin.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sr@latin/LC_MESSAGES/ekiga.mo
installing sv.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/sv/LC_MESSAGES/ekiga.mo
installing ta.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/ta/LC_MESSAGES/ekiga.mo
installing te.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/te/LC_MESSAGES/ekiga.mo
installing th.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/th/LC_MESSAGES/ekiga.mo
installing tr.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/tr/LC_MESSAGES/ekiga.mo
installing uk.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/uk/LC_MESSAGES/ekiga.mo
installing vi.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/vi/LC_MESSAGES/ekiga.mo
installing wa.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/wa/LC_MESSAGES/ekiga.mo
installing xh.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/xh/LC_MESSAGES/ekiga.mo
installing zh_CN.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/zh_CN/LC_MESSAGES/ekiga.mo
installing zh_HK.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/zh_HK/LC_MESSAGES/ekiga.mo
installing zh_TW.gmo as /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/locale/zh_TW/LC_MESSAGES/ekiga.mo
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0/po'
make[1]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0'
make[2]: Entering directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/share/applications" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/applications"
GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults gconftool-2 --makefile-install-rule ekiga.schemas 2>&1 > /dev/null
 /usr/bin/install -c -m 644 'ekiga.desktop' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//usr/share/applications/ekiga.desktop'
test -z "/etc/gconf/schemas" || /bin/mkdir -p "/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//etc/gconf/schemas"
 /usr/bin/install -c -m 644 'ekiga.schemas' '/usr/portage/tmp/portage/net-im/ekiga-3.0.0/image//etc/gconf/schemas/ekiga.schemas'
ACCESS DENIED  open_wr:   /etc/gconf/gconf.xml.defaults/.testing.writeability
ACCESS DENIED  unlink:    /etc/gconf/gconf.xml.defaults/.testing.writeability
None of the resolved addresses are writable; saving configuration settings will not be possible
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/output_device' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/audio/output_device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/input_device' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/audio/input_device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/input_device' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/input_device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/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/ekiga/devices/video/channel' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/channel', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/format' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/format', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/enable_preview' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/enable_preview', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/image' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/image', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/video/max_frame_rate' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/video/max_frame_rate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/lid_output_device_type' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/audio/lid_output_device_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/lid_echo_cancellation_level' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/audio/lid_echo_cancellation_level', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/lid_country_code' locale `C': Unable to store a value at key '/schemas/apps/ekiga/devices/audio/lid_country_code', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/full_name' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/full_name', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/short_status' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/short_status', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/long_status' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/long_status', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/away_custom_status' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/away_custom_status', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/dnd_custom_status' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/dnd_custom_status', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/personal_data/online_custom_status' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/personal_data/online_custom_status', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/audio/media_list' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/audio/media_list', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/audio/enable_silence_detection' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/audio/enable_silence_detection', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/audio/enable_echo_cancelation' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/audio/enable_echo_cancelation', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/output_device' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/output_device', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/incoming_call_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/incoming_call_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/enable_incoming_call_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/enable_incoming_call_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/new_message_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/new_message_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/enable_new_message_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/enable_new_message_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/new_voicemail_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/new_voicemail_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/enable_new_voicemail_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/enable_new_voicemail_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/enable_ring_tone_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/enable_ring_tone_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/ring_tone_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/ring_tone_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/enable_busy_tone_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/enable_busy_tone_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/sound_events/busy_tone_sound' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/sound_events/busy_tone_sound', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/save_prefix' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/save_prefix', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/version' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/version', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/gconf_test_age' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/gconf_test_age', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/accounts_list' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/accounts_list', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/interface' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/interface', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/listen_port' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/listen_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/registrar_registration_timeout' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/registrar_registration_timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/outbound_proxy_host' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/outbound_proxy_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/forward_host' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/forward_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/dtmf_mode' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/dtmf_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/listen_port' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/listen_port', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/ports/tcp_port_range' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/ports/tcp_port_range', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/ports/udp_port_range' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/ports/udp_port_range', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/enable_h245_tunneling' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/enable_h245_tunneling', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/enable_early_h245' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/enable_early_h245', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/enable_fast_start' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/enable_fast_start', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/dtmf_mode' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/dtmf_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/h323/forward_host' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/h323/forward_host', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/call_forwarding/always_forward' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/call_forwarding/always_forward', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/call_forwarding/forward_on_busy' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/call_forwarding/forward_on_busy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/call_forwarding/forward_on_no_answer' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/call_forwarding/forward_on_no_answer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/nat/stun_server' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/nat/stun_server', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/nat/public_ip_detector' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/nat/public_ip_detector', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/protocols/sip/binding_timeout' locale `C': Unable to store a value at key '/schemas/apps/ekiga/protocols/sip/binding_timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/start_hidden' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/start_hidden', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/show_popup' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/show_popup', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/main_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/main_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/main_window/show_call_panel' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/main_window/show_call_panel', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/main_window/panel_section' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/main_window/panel_section', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/main_window/roster_expanded_groups' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/main_window/roster_expanded_groups', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/log_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/log_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/chat_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/chat_window/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/ekiga/general/user_interface/chat_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/chat_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/druid_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/druid_window/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/ekiga/general/user_interface/druid_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/druid_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/calls_history_component/calls_history' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/calls_history_component/calls_history', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/address_book_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/address_book_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/address_book_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/address_book_window/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/ekiga/general/user_interface/audio_settings_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/audio_settings_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/audio_settings_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/audio_settings_window/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/ekiga/general/user_interface/video_settings_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_settings_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_settings_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_settings_window/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/ekiga/general/user_interface/preferences_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/preferences_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/preferences_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/preferences_window/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/ekiga/general/user_interface/accounts_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/accounts_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/accounts_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/accounts_window/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/ekiga/general/user_interface/video_display/disable_hw_accel' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/disable_hw_accel', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/allow_pip_sw_scaling' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/allow_pip_sw_scaling', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/sw_scaling_algorithm' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/sw_scaling_algorithm', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/zoom' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/zoom', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/stay_on_top' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/stay_on_top', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/video_view' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/video_view', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/video_display/video_view_before_fullscreen' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/video_display/video_view_before_fullscreen', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/local_video_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/local_video_window/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/ekiga/general/user_interface/local_video_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/local_video_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/user_interface/remote_video_window/size' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/remote_video_window/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/ekiga/general/user_interface/remote_video_window/position' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/user_interface/remote_video_window/position', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/audio/maximum_jitter_buffer' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/audio/maximum_jitter_buffer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/video/media_list' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/video/media_list', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/video/enable_video' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/video/enable_video', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/video/maximum_video_tx_bitrate' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/video/maximum_video_tx_bitrate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/video/maximum_video_rx_bitrate' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/video/maximum_video_rx_bitrate', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/codecs/video/temporal_spatial_tradeoff' locale `C': Unable to store a value at key '/schemas/apps/ekiga/codecs/video/temporal_spatial_tradeoff', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/contacts/roster_folded_groups' locale `C': Unable to store a value at key '/schemas/apps/ekiga/contacts/roster_folded_groups', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/contacts/show_offline_contacts' locale `C': Unable to store a value at key '/schemas/apps/ekiga/contacts/show_offline_contacts', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/contacts/ldap_servers' locale `C': Unable to store a value at key '/schemas/apps/ekiga/contacts/ldap_servers', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/contacts/call_history' locale `C': Unable to store a value at key '/schemas/apps/ekiga/contacts/call_history', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/contacts/roster' locale `C': Unable to store a value at key '/schemas/apps/ekiga/contacts/roster', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/kind_of_net' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/kind_of_net', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/ekiga/general/call_options/no_answer_timeout' locale `C': Unable to store a value at key '/schemas/apps/ekiga/general/call_options/no_answer_timeout', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
make[2]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0'
make[1]: Leaving directory `/usr/portage/tmp/portage/net-im/ekiga-3.0.0/work/ekiga-3.0.0'
>>> Completed installing ekiga-3.0.0 into /usr/portage/tmp/portage/net-im/ekiga-3.0.0/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-2959.log"

open_wr:   /etc/gconf/gconf.xml.defaults/.testing.writeability
unlink:    /etc/gconf/gconf.xml.defaults/.testing.writeability
--------------------------------------------------------------------------------