Description of problem: When you install a 64-bit plugin, it gets installed to /usr/lib64/mozilla/plugins. However, the about:plugins page does not show the plugin (and the plugin is not used). Version-Release number of selected component (if applicable): galeon-2.0.3-4.fc6.1 How reproducible: Deterministic. Steps to Reproduce: 1. Have 64-bit galeon installed. 2. Install 64-bit plugin, for example nspluginwrapper. 3. Check that the plugin got installed to /usr/lib64's subdirectory, not to /usr/lib, which seems like a sensible thing to do. 4. Go to about:plugins. Actual results: The plugin is not shown. Expected results: The plugin should be shown. Additional info: Creating symlinks from /usr/lib/mozilla/plugins/* to those appropriate 64-bit files in /usr/lib64/mozilla/plugins makes them to work, however, this should work out of box and not search (32-bit) /usr/lib.
The problem is in file mozilla/mozilla-embed-shell.cpp (function mozilla_init_plugin_path) where the search path for plugins is created. Quick and dirty solution I am using for codeblocks: - patch the file to use @libdir@/mozilla/plugins instead of /usr/lib/mozilla/plugins - in the prep section run "sed -i s|@libdir@|%{_libdir}|g mozilla/mozilla-embed-shell.cpp"
Created attachment 146747 [details] fix for correct loading of plugins on 64-bit platforms
Created attachment 146748 [details] new spec file for FC6
Created attachment 146751 [details] x86_64 mozilla plugin path fix Dan, Your patch is not correct: @foo@-type substitutions are done by automake. To make this work, you'd need a AC_SUBST() statement as well as a mozilla-embed-shell.cpp.in file. There's a simpler way to do this, as galeon already passes down configuration paths through -D compiler flags. Could you verify that the attached patch works on your x86_64 system ? many thanks!
The @foo@ substitutions are usually done when running configure (they are contained in the foo.in files) and I am doing it manually with sed called from the %prep section of the spec file which could be a bit confusing. But your solution is much better and it works too.
Ah ok sorry, I missed the spec file sed. Will build and close.