-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again!
Ok! Anyhow, but i don't know how, i solved it in manipulating the gconf db. So it is solved now. BTW Ekiga Rocks! Impatient to have H263/4 ;) Regards, Didier. Ptitjes a écrit : > Hello! > > I wanted to tried the snapshot version of May 20th to test H.263 and SIP > presence. > > However as this did not work for a library path problem and that i > needed it to communicate, I reemerged the 2.0.9 version. > > Now i've got an gconf error at start. Following the FAQ does not change > anything. I tried gconftool-2 unapply-schema, recursive-unset but > nothing does it. > > "Gconf key error > > Ekiga got an invalid value for the GConf key > "/apps/ekiga/general/gconf_test_age"." > > Could you tell me what number i should put in the gconf_test_age key for > the 2.0.9 version (it is 60 now) and what its type is ? > > Please help. > Didier. _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGUYk3VE1mALQL3JsRAq5bAJ9BH5+CFWK3bGL3ZevpbVi5v/x2rgCgipTO 3/N2Z1A9BV8aG01c1CN87Y4= =XK3Z -----END PGP SIGNATURE----- _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
