Hi, maybe just adding "gnomemeeting-config-tool --fix-permissions" to the ebuild is a good idea. It fixes a error message about GConf that might propably occur - here it did. so long, expose Reproducible: Always Steps to Reproduce: 1. emerge gnomemeeting 2. gnomemeeting Actual Results: Config. druid loads, and err-msg about GConf shows up.
I can confirm this bug. Here's the actual error message: Gconf key error GnomeMeeting got an invalid value for the GConf key "/apps/gnomemeeting/general/gconf_test_age". It probably means that your GConf schemas have not been correctly installed or the that permissions are not correct. Please check the FAQ (http://www.gnomemeeting.org/faq.php), the throubleshoot section of the GConf site (http://www.gnome.org/projects/gconf/) or the mailing list archives for more information (http://mail.gnome.org) about this problem.
I don't have the hardware to test gnomemeeting, but this seems like a reasonable request. Sam: does running gnomemeeting-config-tool --fix-permissions reliably fix the problem for you? It probably doesn't hurt to run after every build. Thanks
Mike Gardiner: You don't need a webcam if this is what you referred to with "hardware" since it will not even start if the error i had her shows up - so a simple generic x86 would work to test (Most people have one, that's why i tell this.).
Right, found the error. I've applied the fix to gnomemeeting-1.0.2. Thanks for both your reports and solutions on this bug. Thanks, Mike.
The patch (in the ebuild) did not work for me. I still get the gconf error message when starting Gnomemeeting. I found that running $gconftool-2 --install-schema-file /etc/gconf/schemas/gnomemeeting.schemas as user solves the problem. Moo
Not fixed -- I just got this.
Correct, The pkg_postinst() overrides the base gnome2_pkg_postinst(), which handles installing the gconf schemas, without calling it. Fixed in CVS, see 1.0.2-r1 (adding a revision because people will have 1.0.2 installed but non-usable - the package has changed to the point where people will want to upgrade - so it is usable). Leaving stable on ppc (due to the nature of the fix, and that I've tested it on ppc)
