GNOME Bugzilla – Bug 313096
Plugin collision prevention too aggressive in the junk hook
Last modified: 2013-09-13 00:48:44 UTC
In the emjh_construct function in em-junk-hook.c, the 'loaded' static variable is used to prevent multiple plugins from being attached to the same hook. The problem is, when the first available plugin candidate is disabled in the plugin manager, its processing still sets 'loaded' to TRUE and prevents another available plugin from being attached. It takes removing the conflicting .eplug manifesto from the plugin directory to enable the second plugin. On a more general note, shouldn't resolution of hook conflicts be handled in some generic way in the EPlugin system?
does it work if you enable/disable the right plugin, then restart? the plugin manager does say that changes may not take effect till restart. and no, the eplugin system cannot resolve hook conflicts. it is up to the hooks themselves to do it since they know what they're dealing with.
No, the problem is persistent. sa-junk-plugin is disabled, and my bogofilter junk plugin is enabled, but as the first one comes first in the eplugin initialization list, it prevents the enabled one from being considered for the hook.
something to look into vivek?
vivek: ping? mikhail got a bogofilter plugin and this prevents a proper implentation of any other antispam plugin. raising priority.
This is fixed on HEAD in the 2.4 cycle itself. find it here http://cvs.gnome.org/viewcvs/evolution/mail/em-junk-hook.c?r1=1.2&r2=1.3 closing bug.