Summary: | mail-client/evolution-2.26.3 ; setting URL via gconftool-2 --set NOT working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joseph <syscon780> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | markus, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 263083 | ||
Attachments: | emerge --info |
Description
Joseph
2009-10-13 00:33:28 UTC
Created attachment 207959 [details]
emerge --info
Same thing on amd64 (attached `emerge --info`) and x86.
I believe the bug is actually with libgnome and/or gvfs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519263 The last message mentions a fix, but the note in the changelog only indicates they added gvfs as a dependency. I have both installed, and I see gvfs is a PDEPEND of libgnome. Anyway, when I run either `gnome-open URL` or `gvfs-open URL` I get the same error. Here are my USE flags if it matters: gvfs-1.2.3 USE="bash-completion cdda hal samba -archive -avahi -bluetooth -debug -doc -fuse -gnome -gnome-keyring -gphoto2" libgnome-2.26.0 USE="branding esd -debug -doc" I got it to work. I switched on the 'gnome' USE flag, added a dependency for GConf and switched the configure flag from --disable-gconf to --enable-gconf. Then restarted evolution. I recommend removing the 'gnome' USE flag from gvfs' ebuild and force dependency on GConf. Unless you have a VERY good reason. I don't think gvfs should even have the option of disabling GConf support. Whoops. That first paragraph should read (change in CAPS): I got it to work. I switched on the 'gnome' USE flag, WHICH added a dependency for GConf and switched the configure flag from --disable-gconf to --enable-gconf. Then restarted evolution. + 26 Oct 2009; Gilles Dartiguelongue <eva@gentoo.org> + libgnome-2.26.0.ebuild: + Depend on gvfs[gnome] otherwise gnome-open does nothing, bug #288794. + Thanks for reporting and investigating the issue. |