When trying to enable/change settings for/use Evolution's EAddress gnome-pilot conduit, the following error appears: libgpilotdcm-WARNING **: unable to g_module_open (/usr/lib/gnome-pilot/conduits/libeaddress_conduit.so), reason /usr/lib/gnome-pilot/conduits/libeaddress_conduit.so: undefined symbol: g_unichar_isalpha I suspect this might be a problem with unicode and glib, but this is only a guess.
The above error was encountered with evolution 1.0.1-r1. I downgraded to evolution-1.0-r5, which seems to work better. I'm not sure about the differences between Evolution 1.0 and Evolution 1.0.1.
I have the same problem. I'm running an emerge --world update, and then I'll rebuild evo and see if that fixes the problem.
I finished emerge --world update && emerge net-mail/evolution; the problem has not been resolved.
Grant: can you test this with evo 1.0.2?
Still a problem w/ 1.0.2. There's an entry on Ximian's bugzilla, but neither a work-around nor a solution.
I've restored the 1.0-r5 ebuild, which does have a working conduit. The current work-around is to downgrade to 1.0-r5.
The evo folks don't seem to be in any hurry to close this bug. I'm moving it to "later", since it's not our fault.
*** Bug 1513 has been marked as a duplicate of this bug. ***
I've fixed this by removing the line "libtoolize --copy --force" from the appropriate .ebuild. (using gentoo 1.1). I've seen suggestions that this is an issue with libtool rather than Evolution. That might explain why Ximian hasn't responded. Also, since it's working for me, I wonder under what circumstances the libtools invocation is necessary, and if those could be tested for in the .ebuild.
Even with 1.0.3-r5, I'm still getting the conduit error.
I also get the bug if I compile with the 1.0.3-r5 ebuild. And again, removing the call to libtoolize seems to fix the problem.
I'm pretty sure we finally have this problem fixed.
