On Fri, 2009-09-11 at 17:17 -0500, Leonard Evens wrote:
> For years I have scanned negatives using vuescan, and then opened the
> resulting tiff file in gimp without incident. But now something strange
> has started happening. I scanned a b/w negative, and when I opened it,
> it came up in ufraw and I had to fiddle with it in order to get it into
> gimp. It wwas an noying and took a lot of time, and the image was not
> the same as it appeared in Vuescan, which previously was always the
> case. I don't understand why gimp is doing that.
Sounds like ufraw has installed itself as a loader for TIFF images. To
verify that you could look at your ~/.gimp-2.6/pluginrc and search for
"tiff". You could even edit that file to remove the registration of the
ufraw procedure for TIFF images.
Gimp-user mailing list