Re: [Gimp-developer] EXIF data missing after jpg save
Omari Stephens wrote: Sven Neumann wrote: Hi, On Thu, 2008-06-05 at 07:25 -0400, Paka wrote: the opensuse team that is maintaining gimp/ufraw does not believe that exif data is important to the project and do not include support for exif. Easy enough to copy the plug-in binary from a compatible distribution that compiles GIMP with Exif support enabled. Are you all following a red herring? I think Jim said, in his response to my email, that the EXIF data always exists after the JPEG has been saved from the GIMP. --xsdg I always compile gimp myself to be sure I get everything I want in it. It's almost the only opensuse program I do that with. And yes, I did find that the exif data were there after saving to jpg; the problem must be with the pbase site. What confused me and made me think it was gimp was that it started immediately after compiling/installing gimp 2.4.7. Just an unlucky coincidence I suppose. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] EXIF data missing after jpg save
Bill Skaggs wrote: Jim Sabatke [EMAIL PROTECTED] wrote: It seems that in 2.4.6 that exif data are missing when saving as a compressed jpg. They are not missing on jpgs with no compression. There is no such thing as a jpg with no compression, so it is pretty much impossible to make sense of what you are saying. It would be helpful if you would describe the actions you took and the error messages you received in a more concrete way. What were the settings you used when saving as jpg? What were the messages that told you whether or not exif data is present? -- Bill OK, I'm processing Nikon D200 NEF (RAW) photos with gimp and ufraw. ufraw shows the exif data properly. When I edit the photo in gimp and go to save with the standard settings, the exif data do not show up on my pbase website. This is a new behavior as exif data have always shown up before. I looked at the help on the pbase site and it said most of the problems saving exif data come from high compression. So, I re-edited a photo and saved it. On the the Save as JPEG screen Save EXEF data was checked. On the Subsampling: drop box, I selected 1x1,1x1,1x1 (best quality). Then I saved and the exif data showed on my pbase photo. I was mistaken that I changed the compression. It was still at 85. Hope this helps, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] EXIF data missing after jpg save
Omari Stephens wrote: Jim Sabatke wrote: Bill Skaggs wrote: Jim Sabatke [EMAIL PROTECTED] wrote: It seems that in 2.4.6 that exif data are missing when saving as a compressed jpg. They are not missing on jpgs with no compression. There is no such thing as a jpg with no compression, so it is pretty much impossible to make sense of what you are saying. It would be helpful if you would describe the actions you took and the error messages you received in a more concrete way. What were the settings you used when saving as jpg? What were the messages that told you whether or not exif data is present? -- Bill OK, I'm processing Nikon D200 NEF (RAW) photos with gimp and ufraw. ufraw shows the exif data properly. When I edit the photo in gimp and go to save with the standard settings, the exif data do not show up on my pbase website. This is a new behavior as exif data have always shown up before. I looked at the help on the pbase site and it said most of the problems saving exif data come from high compression. So, I re-edited a photo and saved it. On the the Save as JPEG screen Save EXEF data was checked. On the Subsampling: drop box, I selected 1x1,1x1,1x1 (best quality). Then I saved and the exif data showed on my pbase photo. I was mistaken that I changed the compression. It was still at 85. Is the EXIF data not visible in the first case with a tool designed specifically for that purpose, such as metacam? --xsdg I couldn't find metacam anywhere, but a search through freshmeat.net showed the program jhead. Jhead did indeed find the exif data in the photo that did NOT display exif data in my album. Since the timing on this issue coincided exactly with compiling and installing gimp 2.4.6, I assumed too quickly that a bug had been introduced. That is not the case. Apparently the gallery program has changed in some way that requires a different setting on saving jpegs. Sorry for the confusion cause and thanks for your help. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Merged Image not able to be drawn on...
Brendan wrote: More on the bug I am running into. It very well may be that this is not a bug and just a feature or whatever that I am running into, but it's not very well explained anywhere, seemingly. I have an image that I have worked on, had multiple layers, then when merged down, it cannot be drawn on directly, even though only one layer is shown and no error message pops up. 2.2 didn't seem to feature this, as I have done it countless times. Seems to be intermittent, but it's hard to figure out when I don't have much time to debug. More info...when I am saving the image as a jpeg, it shows the message about transparency...so is there a hidden layer or something that isn't allowing me to draw on...oh hell, I am running out of words. I can send out a screenshot of the issue. Didn't want to send it to the list and waste bandwidth. BTW, this is a compiled-from-source version of 2.4.4. ___ I suspect that sending the XCF file, as suggested earlier by I don't remember who, might be the best way to start. That should contain everything, hidden or not, in your picture. Good luck, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Compiling denoise plug-in
I downloaded and tried to compile Roland Simmen's DeNoise plug-in. It only comes with source files, no Makefile, no configure to make the Makefile. gimptool-2.0 doesn't seem to like multiple *.c source files. Would someone please point me in the right direction to get this plug-in compiled and working? TIA, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Preview Windows in Python-Fu - Do they exist?
David Gowers wrote: Hi Jim, On Dec 8, 2007 10:22 AM, Jim Sabatke [EMAIL PROTECTED] wrote: I've been searching the net for a couple days to see if Python-Fu supports Preview Windows in plug-ins. Depending on the search strings I No, it doesn't. PyGimp does, though. This means that if you want a preview window, you need to construct the GUI yourself -- you cannot rely on PythonFu to construct it automatically for you. In the 'gimpui' module, look up the help -- see 'GimpPreview','GimpAspectPreview', and associates. Thank you David. Next question ... is there any GUI generator, like Glade that does a decent job of building interfaces like that? TIA, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Preview Windows in Python-Fu - Do they exist?
I've been searching the net for a couple days to see if Python-Fu supports Preview Windows in plug-ins. Depending on the search strings I use in Google, I get thousands of hits, far too many to find anything useful. I haven't found anything useful in the the hits I did read. So, if someone could point me to a useful link, I would be very grateful. TIA, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Still need a home for my plug-ins
Kevin Cozens wrote: Jim Sabatke wrote: My free time on the file hosting site I've been using is almost up. I had several suggestions before that I should upload the files to the plug-in registry site. I may be missing something, but it looks like I need some sort of special privileges to do that. Look at the right hand side of the page under Coders Corner. It has a link for you to register as a plug-in author. The link below that let's you change plug-in information once you have registered. I *finally* got past the login prompt to get to the file upload area. Thanks for your help. Apologies for the *noise* of the extra entries in the latest modification area. Hopefully their will be more added and the extras will fall off the screen. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Still need a home for my plug-ins
This is a second posting. I think I sent the first from a different address than the one I signed up with. Apologies if this shows up twice. My free time on the file hosting site I've been using is almost up. I had several suggestions before that I should upload the files to the plug-in registry site. I may be missing something, but it looks like I need some sort of special privileges to do that. Any help would be welcome. TIA Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Help!!! I need a home for my plug-ins
Michael Schumacher wrote: Jim Sabatke wrote: I've got a couple of plug-ins in the gimp plug-in registry that I need a home for. If you are searching for a home, then they are not in the registry. You're just linking to them. Why don't you upload them there? HTH, Michael Yes, I'm aware of the distinction between being there and linked there, and you are quite correct that they are linked. I looked all over for an upload area in the registry and didn't see one. Since you say there is one, I'll go back and take another look. Thanks, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Help!!! I need a home for my plug-ins
I've got a couple of plug-ins in the gimp plug-in registry that I need a home for. Right now they live at a site that begins charging after trying them for a month. I've tried putting them in my Yahoo briefcase, but like Yahoo pictures, some people can see them and some can't, even though I made everything accessible to the public. I'm not going to pay $10/month to host a couple of small files. Does anyone have a good idea about where I can put those files? I'm really finding writing plug-ins (and learning Python, which I've wanted an excuse to do for a long time) gives me something I really feel good about doing. TIA Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] scheme changes
I have a lot of scripts that no longer work under 2.3.x. I understand that gimp has migrated to tiny scheme and variables need to be declared with let or let*. I have tried and tried to modify some of the scripts and can't get them to work. I've looked at examples of scripts that do work and I've gone over (and over) the syntax for 'let' in my Lisp books, all to no avail. I have also searched the archives for this email list for clues. Has anyone produced a simple to understand document on how to use those functions on misbehaving scripts? The documents on the let and let* functions make it seem like I shouldn't be having this much trouble. TIA Jim ___ Gimp-developer mailing list [EMAIL PROTECTED] https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Is there any thought of layer blending in the future?
Raphaël Quinet wrote: On Thu, 12 Apr 2007 21:42:28 -0500, Jim Sabatke [EMAIL PROTECTED] wrote: There is an excellent tutorial on using PS to do this at: http://www.luminous-landscape.com/tutorials/glow.shtml This would be VERY useful in gimp. Has here been any consideration of this functionality? If you are looking for a quick soft glow effect, you can use Filters - Artistic - Soft glow (in GIMP 2.3.x). But if you want to follow the tutorial step-by-step and if you really want something like adjustment layers, then you should look at this bug report: http://bugzilla.gnome.org/show_bug.cgi?id=79025 -Raphaël Actually, I can do a soft glow manually. The kind of glow I'm looking for would have glow applied to some colors and not others. The enhancement request you noted looks like it would meet that need. Thanks, Jim ___ Gimp-developer mailing list [EMAIL PROTECTED] https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Is there any thought of layer blending in the future?
There is an excellent tutorial on using PS to do this at: http://www.luminous-landscape.com/tutorials/glow.shtml This would be VERY useful in gimp. Has here been any consideration of this functionality? Jim ___ Gimp-developer mailing list [EMAIL PROTECTED] https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Denoising Plugin
[EMAIL PROTECTED] wrote: On Thu, 29 Mar 2007 22:31:50 +0200, Jim Sabatke [EMAIL PROTECTED] wrote: I've just compiled a plugin based on a denoising program that attracted slashdot's attention a short while ago. http://rss.slashdot.org/~r/Slashdot/slashdot/~3/99611463/article.pl It gets very good reviews compared to Noise Ninja and other commercial products. I was wondering if it is good enough that you might be willing to include it in the standard distro? The only holdback I can see is that it is written in C++. I've got it running on SuSE 10.0 and there is a windows version available online. The author has no objections to including it. Jim _ very interesting filter. I just did a quick comparison rescaling some of thier sample images with lanczos interpolation in gimp. Generally, lanczos was inbetween cubic and the denoising filter. The latter usually produces images that are easier on the eye than both cubic and lanczos but on closer inspection this is not without a price. Denoising grossly simplifies the image in cleaning it up. The girl in hat image, res_lana.png becomes badly distorted and the result is worse than both lanczos and cubic. (This is going by thier images on the demo page). Ringing, while present, is less than gimp lanczos. However, quite a bit of detail is lost and the biggest defect seems to be constast takes a bit hit. The overall effect is pleasing and probably would be good for a lot of applications. Like any image processing it's a case of horses for courses and what defects in the result are acceptable in a specific application with a specific image. Thanks for bringing this up. A useful filter to have. gg. Thanks for the analysis. This code is still undergoing active development, with students scheduled to keep it up. I'm passing your comments to the development team. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Denoising Plugin
I've just compiled a plugin based on a denoising program that attracted slashdot's attention a short while ago. http://rss.slashdot.org/~r/Slashdot/slashdot/~3/99611463/article.pl It gets very good reviews compared to Noise Ninja and other commercial products. I was wondering if it is good enough that you might be willing to include it in the standard distro? The only holdback I can see is that it is written in C++. I've got it running on SuSE 10.0 and there is a windows version available online. The author has no objections to including it. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Denoising Plugin
Robert L Krawitz wrote: Date: Thu, 29 Mar 2007 13:50:02 -0700 From: William Skaggs [EMAIL PROTECTED] Jim Sabatke wrote: I've just compiled a plugin based on a denoising program that attracted slashdot's attention a short while ago. [...] Jim, there is already a GREYCstoration gimp plugin, which you can find out about by googling greycstoration gimp plugin. Is yours better? In any case, the main gimp distribution doesn't currently include anything written in C++. Greycstoration is extremely slow. If there's a faster one that does a good job (and at least with the settings I tried, greycstoration didn't do that great of a job), I'd be very interested in seeing it. The new version is MUCH faster and does a much better job than the old plugin. The Greycstoration's original author and the gimp plugin's original author never did see eye to eye on the plugin. You can try out the new plugin, source at: http://sound.eti.pg.gda.pl/~greg/gimp/ It's basically a windows version, but if you put CC=g++ and LDFLAGS=-lpthread in the ENV, then gimptool does it's job on my version of linux just fine (SuSE 10.0). It shows up under Filters-Enhance Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Denoising Plugin
William Skaggs wrote: Jim Sabatke wrote: I've just compiled a plugin based on a denoising program that attracted slashdot's attention a short while ago. [...] Jim, there is already a GREYCstoration gimp plugin, which you can find out about by googling greycstoration gimp plugin. Is yours better? In any case, the main gimp distribution doesn't currently include anything written in C++. Best wishes, -- Bill Bill, The current gimp site Greycstoration plugin has been abandoned and wasn't that good to begin with. There has been a lot of work on the source code, plus a better gimp interface. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] healing the healing tool
GSR - FR wrote: Hi, [EMAIL PROTECTED] (2007-02-21 at 0837.29 -0800): snip http://video.about.com/graphicssoft/How-to-fix-blemishes-.htm Notice the clock cursor, that is the extra processing, with old computer and big area you clearly see it does clone and secs later it blends. - patch tool, behaves like a reversed order copy paste (first select area to fix, then source). Allows knowing both areas perfectly thus avoiding one typical problem of clone: a big stroke covers all you want... but starts to get pixels from source you do not want. The extra processing is done at the end of the motion, too. http://video.about.com/graphicssoft/The-Patch-Tool.htm Notice how it looks like copy and then blends. - spot healing brush, behaves like paint tool. A drop down decides what the program uses as inspiration for the fix. Simpler than clone but prone to not doing what you want if used in really big areas or complex images (thus the name spot, best used for dust in sky of a photo, ie). http://www.totaltraining.com/videos/mov/TPSE3_Healing_Brush.mov Notice some undo and redos until the guessing is correct. Looking at the paper without looking at the tools is a bit strange, you already accepted looking at the inner part, better look at the full picture then. Or at least set the context of what is going to be copied, what not, what is going to be completly new or what is going to be improved. GSR The resynthesizer plugin http://registry.gimp.org/plugin?id=457 can do a lot of the healing functionality (and more). I've used it for everything from removing small areas and filling with a good likeness to major reconstruction of parts of photos. It's biggest downfall is that the documentation for it isn't very good; especially for replacing large sections. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] segfault problem
Carol Spears wrote: On Thu, May 04, 2006 at 06:45:32PM -0500, Jim Sabatke wrote: I have been updating all my machines to gimp 2.2.10. It works fine on all of them except for my HP ZD 7000 laptop. 2.2.0 worked fine on this box. I'm getting the infamous wire_read error whenever I try to open a file. I've googled for some time and there seem to be countless solutions, none of which work for me. The error I get is: Segmentation fault [EMAIL PROTECTED]:~/programs/media/gimp-2.2.10 (script-fu:8117): LibGimpBase-WARNING **: script-fu: wire_read(): error that is a message that is sent by a healthy script-fu server when gimp crashes. i wonder if your gimp is using the old gimp libraries. did you build this gimp yourself or did your distribution install it? one quick way to check to see if it is using the wrong library is to: [EMAIL PROTECTED]:~ whereis gimp and [EMAIL PROTECTED]:~ whereis libgimp if you have some gimp stuff in /usr/lib and also in /usr/local/lib that would be what is making the crash. if you still have the gimp-2.2.0 sources around, as root, make uninstall and then in the new gimp-2.2.10 sources, make install again. let me know how this goes carol Here's some more info. I ran gcc on it and here is the debug info after trying to open a file: [Switching to Thread 16384 (LWP 14365)] 0x401f6595 in error_message_with_parent (parent=0x0, msg=0x8bfcdb8 Could not retrieve information about the file, detail=0x8bfce20 error accessing 'file:///home/jim': Invalid URI) at gtkfilechooserdefault.c:962 962 if (parent-group) Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] segfault problem
I have been updating all my machines to gimp 2.2.10. It works fine on all of them except for my HP ZD 7000 laptop. 2.2.0 worked fine on this box. I'm getting the infamous wire_read error whenever I try to open a file. I've googled for some time and there seem to be countless solutions, none of which work for me. The error I get is: Segmentation fault [EMAIL PROTECTED]:~/programs/media/gimp-2.2.10 (script-fu:8117): LibGimpBase-WARNING **: script-fu: wire_read(): error Any help here? TIA, Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] segfault problem
Carol Spears wrote: On Thu, May 04, 2006 at 06:45:32PM -0500, Jim Sabatke wrote: I have been updating all my machines to gimp 2.2.10. It works fine on all of them except for my HP ZD 7000 laptop. 2.2.0 worked fine on this box. I'm getting the infamous wire_read error whenever I try to open a file. I've googled for some time and there seem to be countless solutions, none of which work for me. The error I get is: Segmentation fault [EMAIL PROTECTED]:~/programs/media/gimp-2.2.10 (script-fu:8117): LibGimpBase-WARNING **: script-fu: wire_read(): error that is a message that is sent by a healthy script-fu server when gimp crashes. i wonder if your gimp is using the old gimp libraries. I don't think so. Here is a ldd dump: [EMAIL PROTECTED]:~/programs/media/gimp-2.2.10 ldd /opt/gnome/bin/gimp2 libgimpwidgets-2.0.so.0 = /opt/gnome/lib/libgimpwidgets-2.0.so.0 (0x4003c000) libgimpmodule-2.0.so.0 = /opt/gnome/lib/libgimpmodule-2.0.so.0 (0x40117000) libgimpcolor-2.0.so.0 = /opt/gnome/lib/libgimpcolor-2.0.so.0 (0x4011c000) libgimpthumb-2.0.so.0 = /opt/gnome/lib/libgimpthumb-2.0.so.0 (0x40125000) libgimpmath-2.0.so.0 = /opt/gnome/lib/libgimpmath-2.0.so.0 (0x4012e000)libgimpbase-2.0.so.0 = /opt/gnome/lib/libgimpbase-2.0.so.0 (0x40133000) libgtk-x11-2.0.so.0 = /opt/gnome/lib/libgtk-x11-2.0.so.0 (0x4014) libgdk-x11-2.0.so.0 = /opt/gnome/lib/libgdk-x11-2.0.so.0 (0x403fc000) libatk-1.0.so.0 = /opt/gnome/lib/libatk-1.0.so.0 (0x40475000) libgdk_pixbuf-2.0.so.0 = /opt/gnome/lib/libgdk_pixbuf-2.0.so.0 (0x4048d000) libm.so.6 = /lib/i686/libm.so.6 (0x404a2000) libpangoxft-1.0.so.0 = /opt/gnome/lib/libpangoxft-1.0.so.0 (0x404c6000)libpangox-1.0.so.0 = /opt/gnome/lib/libpangox-1.0.so.0 (0x404cd000) libart_lgpl_2.so.2 = /opt/gnome/lib/libart_lgpl_2.so.2 (0x404d8000) libpangoft2-1.0.so.0 = /opt/gnome/lib/libpangoft2-1.0.so.0 (0x404ee000)libpango-1.0.so.0 = /opt/gnome/lib/libpango-1.0.so.0 (0x40514000) libgobject-2.0.so.0 = /opt/gnome/lib/libgobject-2.0.so.0 (0x4054d000) libgmodule-2.0.so.0 = /opt/gnome/lib/libgmodule-2.0.so.0 (0x40584000) libdl.so.2 = /lib/libdl.so.2 (0x40588000) libglib-2.0.so.0 = /opt/gnome/lib/libglib-2.0.so.0 (0x4058b000) libfontconfig.so.1 = /usr/local/lib/libfontconfig.so.1 (0x4060f000) libfreetype.so.6 = /usr/local/lib/libfreetype.so.6 (0x4063d000) libc.so.6 = /lib/i686/libc.so.6 (0x406a6000) libpangocairo-1.0.so.0 = /opt/gnome/lib/libpangocairo-1.0.so.0 (0x407da000) libz.so.1 = /lib/libz.so.1 (0x407e2000) libcairo.so.2 = /opt/gnome/lib/libcairo.so.2 (0x407f1000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x4083) libXrender.so.1 = /usr/X11R6/lib/libXrender.so.1 (0x4092c000) libXrandr.so.2 = /usr/X11R6/lib/libXrandr.so.2 (0x40935000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x40939000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) libXft.so.2 = /usr/X11R6/lib/libXft.so.2 (0x40947000) libexpat.so.0 = /opt/gnome/lib/libexpat.so.0 (0x40959000) [EMAIL PROTECTED]:~/programs/media/gimp-2.2.10 did you build this gimp yourself or did your distribution install it? I built it myself, which I am accustomed to doing. I am on SuSE 9.0 boxes, so everything basically goes into /opt/gnome. one quick way to check to see if it is using the wrong library is to: [EMAIL PROTECTED]:~ whereis gimp and [EMAIL PROTECTED]:~ whereis libgimp They are both correct. if you have some gimp stuff in /usr/lib and also in /usr/local/lib that would be what is making the crash. if you still have the gimp-2.2.0 sources around, as root, make uninstall and then in the new gimp-2.2.10 sources, make install again. I also had already done this. I don't like stray stuff laying around. let me know how this goes carol Thanks for you help. Jim ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
