Description of problem: gimp can't find the xsane plugin unless its placed under /usr/lib{,64}/gimp/2.0/plug-ins/ Version-Release number of selected component (if applicable): xsane-gimp-0.994-3.fc7 How reproducible: always Steps to Reproduce: 1. start gimp as root 2. In the "File"->"Acquire" menu, you find no entries starting with "XSane:" 3. ln /usr/bin/xsane-gimp /usr/lib64/gimp/2.0/plug-ins/ # replace %{_libdir} on 32 bit boxes 4. start gimp as root 5. In the "File"->"Acquire" menu, there's now an entry starting with "XSane:libusb:" Actual results: gimp can't find the xsane plugin Expected results: "XSane" entry under "File"->"Acquire" menu by default. Additional info:
Externally packaged gimp plugins use /usr/sbin/gimp-plugin-mgr to install the symlinks in the (versionized) gimp plugin directory. I presume that some of the scripts weren't executed properly when installing/updating. In order to refresh the symlinks, run the following command as root: /usr/sbin/gimp-plugin-mgr --install '*'
Reopened, because I could reproduce the bug when updating the package. It seems I got the order in which pre/post/un scriptlets are executed mixed up.
gimp-2.2.14-3.fc7 is building right now which should fix this problem.
I've noticed that my fix was still suboptimal and have updated it in gimp-2.2.14-4.fc7 which is building at the moment. Note that when updating from an affected version of the gimp to a fixed one you'll likely still see the problem because the culprit is in the packages %preun script, i.e. the broken script is run. This means that the fix will only help for subsequent updates, use the workaround I described above once again to fix things (hopefully for the last time).
gimp-2.2.14-5.fc7 (building right now) shouldn't fail the %pre/%preun scripts with the symlink missing.
Changing component to gimp (which is where the bug is).
*** Bug 238861 has been marked as a duplicate of this bug. ***
*** Bug 240703 has been marked as a duplicate of this bug. ***