Re: [Ekiga-devel-list] Various Bugs

[hohyeis eml cc]

Using the current repository versions, ALSA works for input and output.


I found out that the 'make install' of ekiga gives the gconf errors due to a fault which is circumvented by running as root. Even when everything is owned by another user, it is still necessary to run as root, at least as set up in Debian. If we don't find out more about how to fix this, it would be good to describe in the build documentation.

The error messages are like this:

 /usr/bin/install -c -m 644 ekiga.schemas '/usr/local/etc/gconf/schemas'
WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/output_device', locale `lv': 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 proble
m: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gco
nfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machi
ne crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two 
at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, rem
ove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default conf
iguration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on p
roblems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in 
individual storage locations such as ~/.gconf

-- 
http://www.fastmail.fm - The professional email service