Re: [Gimp-developer] 2.3.18 deletes exif data from images
* El 24/06/07 a las 14:57, Sven Neumann chamullaba: Bug GIMP is the only application, graphic or not, that showed this problem, in several years of daily use. The mouse works on every other application perfectly, and always did. Did you actually try it with another GTK+ application that has support for XInput devices? I don't know of another one but GIMP. Could you please point me such an application for testing? It is not surprising that applications that don't enable input devices are not affected. Yes, perhaps... Observe that what is affected is the mouse, not the tablet, though. And only in GIMP canvas, not in any other GIMP window. And through 3 fresh and complete OS upgrades (Fedora 4,5 and 6) the mouse is still broken in GIMP canvas. Gimp worked fine in Fedora 3 and below. For a long time, nothing has changed in GIMP with respect to XInput devices. So the fact that an upgrade introduced this problem seems to be a strong indication that the problem is elsewhere. Perhaps in the X server or, more likely, in the wacom driver. Of course there might also be something that GIMP does wrong. But the vast majority of GIMP users with a tablet doesn't seem to be affected by this problem. As I said already, someone who is affected by this problem will have to track it down. It is not reproducible for me and, as it seems, for no other GIMP developer. Yes, I understand the difficulty with this. Thanks, L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
On Sat, 23 Jun 2007 03:36:01 +0200, Luis A. Florit [EMAIL PROTECTED] wrote: Look at this for example: So: 1) Is the EXIF source in the all the 3 cameras (of 3 different brands) broken? 2) Why all the other graphic programs that I use (showfoto, gqview, gthumb, exiftool) always showed the EXIF data with no problem, and still show? 3) Why the Save EXIF data option in the Save as... dialog is no longer present? 4) Why GIMP deletes the EXIF data now? 5) If broken, why previous versions of GIMP preserve the EXIF data? GIMP 2.3.16 2.3.17 and 2.2.14 still work perfectly for me (in this respect; I had to stop using 2.3.17 because it crashed consistently, probably because of its known bug). Is this tone in any way helpful? The only thing you can achieve by putting it this way is to demotivate the developer working on this. Sorry, but I see no aggression in the above quote. I just tried to point to Mukund that this had nothing to do with broken EXIF, giving several arguments for that. To be precise. BTW, it is interesting to notice that you cut the paragraph that was right before the one you quoted, where I wrote: : Please excuse me, Mukund, but I will be very surprised : if this has something to do with broken EXIF data. Do you also think that an argument that begins with Please excuse me... is aggressive? Probably not, but for some reason you cut that sentence and took the next out of context. And still, it is not aggressive. My apologies to Mukund if he felt that. As I have just pointed out in another thread I think it would be helpful to avoid sort of noise if contributers were not so touchy and frequently get rather irrate for no reason. Sure everyone puts their time in for free, including those who take the time to report bugs and make suggestions. Sometimes reports may communicate an aire of frustration. Though I really dont think that was the intention here. Often if a bug or interface defect is minor no-one bothers reporting. Only when it becomes a major pain and time waster may it get reported. But dont expect to be molly coddled either. If someone takes the time to report it's because they think Gimp is a good tool, that is worth having and wish to contribute to it being better. That in itself is a complement to the work that has already been done. Please dont expect a preamble of thank you everso much for your free work on this great project , you are really clever by the way, but I have one little issue I'd like to bring up if I may. It would greatly accelerate development and reduce noise if we could be a bit more down to Earth and in some cases a bit more humble. We all know emails and posts are a clumbsy for of communication, so let's all try to take things with a pinch of salt and concentrate on improving Gimp. Now I have a lanczos filter to debug, so good day to all. En avant! /gg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Hi Mukund, Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Ah good. So there lies your problem :-) Yes. Thanks for your time, and sorry for the mess. Btw I use Fedora 7 (RPM based) and we have 0.6.15 in it. I still use Fedora 6 (too much work to find time for upgrading...) with 11 repositories, and the most recent is 0.6.13. But this is not unusual with Fedora. After many years with Red Hat/Fedora, am planing to migrate to Debian because things like this. Anyway, I'll download the 0.6.15 tarball and compile it. Thanks again, L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Sven, So, yes, I state, publicly, again: this bug has been ignored for months (in fact, for years, since Fedora 4, and we are now in Fedora 7). No matter if you let me 'get away' or not. These bug reports have not been ignored. They are not GIMP bugs and have been reassigned accordingly. Most likely the bug is not even in GTK+ but on a lower level. The fact that it works for most people makes it likely that it is perhaps even just a misconfigured X server. Of course, yes, I can be wrong. Bug GIMP is the only application, graphic or not, that showed this problem, in several years of daily use. The mouse works on every other application perfectly, and always did. And through 3 fresh and complete OS upgrades (Fedora 4,5 and 6) the mouse is still broken in GIMP canvas. Gimp worked fine in Fedora 3 and below. Disabling the eraser (?!) in GIMP make the mouse work. X config (in particular, xorg.conf) was never changed. I know no X config could make all this happen. But I can be wrong. I am no expert on this (in anything, in fact). Someone who if affected by the problem will have to track it down. There is no chance that a core GIMP or GTK+ developer will find the time to debug a problem that he/she cannot reproduce. Indeed, this is a problem. The same problem that appears with intermittent bugs (the above is not intermittent, though). : Pals, : : I reported this bug in this list some time ago, and got no : answer (I think), and the 2.3.16 version still has the same bug: : The despeckle plugin shifts the image one pixel to the right, : and one to the bottom. Consequently, it is essentially useless. : If you draw in the middle of a white background a black cross : like this: : : x : xxx : x : : and run the despeckle plugin with radius 1, you get this : asymmetric output: : : x : xxx : xx : : Thanks, : : Luis. I hope you don't think the 'tone' was aggressive in this mail also... Yes, I do think that the tone of this mail was aggressive. You complain that you don't get an answer and you complain that the bug is still there. Not only there was no complain (but a remark where I even added 'I think'), but I also took the time to resend the same bug in a friendly way, and you call that aggressive! Clearly, you're going to say the first thing that comes to your mind just to maintain your position. Discussions under these terms are useless. Interestingly, yesterday someone suggested me in this list to read the page http://www.catb.org/~esr/faqs/smart-questions.html (quite interesting, BTW), where it says: - Much of what looks like rudeness in hacker circles is not - intended to give offense. Rather, it's the product of the direct, - cut-through-the-bullshit communications style that is natural to - people who are more concerned about solving problems than making - others feel warm and fuzzy. You simply can not demand that a bug is fixed. Again you insist on changing the words that I wrote. I never demanded anything to be fixed. In fact I never demanded anything. Just asked for the bug reports not to be ignored. Please, try to see the point on what I am trying to say... I do believe that GIMP is a great program, in fact the best OS image editor. Easily. And by using it I know that you all do a great job with it. As you know, I installed the trunk version, so I follow closely its development, and don't mind using devel versions with some sacrifices. Therefore, I know how fast it changes, and that means that there is a lot of work being done to it right now. So, it was never my intention to criticize any of you as developers. However, GIMP (as well as many other OS projects) is not the sole result of the developers. Of course you have the biggest part, but GIMP is also the result of the people that makes plugins, or the community that says something about its usability, or... the people that bother reporting bugs. It is very bad for a reporter to see 'his' bug unanswered and present in several versions after he reported it. What he must do then? He just stops reporting (as I did with Fedora). And the project and the community loose with that. And, unfortunately, this happens with GIMP. At least this happened with me. Three times. Perhaps, as you said, with good reasons: because maintainers are no longer around, or some other reasons. And perhaps you're right, and I am just too impatient (but not aggressive) reporting bugs... Or perhaps gimpdevel is overloaded with bug reports and you are very few to handle all of them. But I read posts like these before in gimpdevel, and never in the other mailing lists that I've participated. Even the ones with only 1 developer (Cartes du Ciel, Xephem). The fact is that this is bad for the project. This is bad for YOUR project. Perhaps, there is no way to improve this...? I only hope you don't think that everything is just fine as it is. L.
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Luis Luis A. Florit wrote: Please excuse me, Mukund, but I will be very surprised if this has something to do with broken EXIF data. As I'm yet to see the actual original image in question, speculating about what is wrong with it is pointless. Please attach the image to the bug and we'll have a look at it and find out what is going on. There is (well was) only one place where EXIF info was discarded in GIMP, and hence I suggested what the problem be, but we may not know until you attach your image first to a bug and show it to us. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Hi Luis Luis A. Florit wrote: Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Ah good. So there lies your problem :-) Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Luis A. Florit wrote: Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Observe that version libexif 0.6.15 has a delicate security bug that was only fixed in the last version 0.6.16 (2007-06-12). Btw I use Fedora 7 (RPM based) and we have 0.6.15 in it. Kind regards, Mukund signature.asc Description: OpenPGP digital signature ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi, On Fri, 2007-06-22 at 00:18 -0300, Luis A. Florit wrote: From aggressive answers, to unanswered mails (not that bad), It would help a lot if you could try to be more precise in your mails. That would avoid the need to ask for details. If a dialog is titled Save as JPEG, then why do you call it Save as ... several times? Your message was so imprecise that even experienced GIMP developers could not tell what exactly you are talking about. Several plug-in can save EXIF data and without the information which plug-in you are using, there is not much we can do. Also, your questions are rather aggressive. It would help a lot if you could try to understand that people are working on this project in their free time. If something breaks in the development version, then this does not happen with the intent of breaking something. It is also not a personal offense, but your mails make it look like one. Look at this for example: So: 1) Is the EXIF source in the all the 3 cameras (of 3 different brands) broken? 2) Why all the other graphic programs that I use (showfoto, gqview, gthumb, exiftool) always showed the EXIF data with no problem, and still show? 3) Why the Save EXIF data option in the Save as... dialog is no longer present? 4) Why GIMP deletes the EXIF data now? 5) If broken, why previous versions of GIMP preserve the EXIF data? GIMP 2.3.16 2.3.17 and 2.2.14 still work perfectly for me (in this respect; I had to stop using 2.3.17 because it crashed consistently, probably because of its known bug). Is this tone in any way helpful? The only thing you can achieve by putting it this way is to demotivate the developer working on this. to ignored bug reports in bugzilla (VERY bad). Please point me to any ignored bug reports. We take bug reports very seriously and I will not let you get away stating in public that we would ignore bug reports. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
* El 22/06/07 a las 8:53, Sven Neumann chamullaba: Hi, On Fri, 2007-06-22 at 00:18 -0300, Luis A. Florit wrote: From aggressive answers, to unanswered mails (not that bad), It would help a lot if you could try to be more precise in your mails. That would avoid the need to ask for details. If a dialog is titled Save as JPEG, then why do you call it Save as ... several times? Only you seemed not to know, or didn't want to know, where the Save EXIF data option is in GIMP. Alex Pounds knew exactly what I was talking about, and understand the same as me by Save as ... dialog. Your message was so imprecise that even experienced GIMP developers could not tell what exactly you are talking about. Several plug-in can save EXIF data and without the information which plug-in you are using, there is not much we can do. You answered as if no such option never existed, and not as if there were many. Also, your questions are rather aggressive. It would help a lot if you could try to understand that people are working on this project in their free time. Of course. If something breaks in the development version, then this does not happen with the intent of breaking something. I never said that. We are all here in our free time, we are all here to try to make GIMP better for others and for us. Not only the developers, but also the ones that bother reporting bugs. It is also not a personal offense, but your mails make it look like one. I don't understand where you read that. Look at this for example: So: 1) Is the EXIF source in the all the 3 cameras (of 3 different brands) broken? 2) Why all the other graphic programs that I use (showfoto, gqview, gthumb, exiftool) always showed the EXIF data with no problem, and still show? 3) Why the Save EXIF data option in the Save as... dialog is no longer present? 4) Why GIMP deletes the EXIF data now? 5) If broken, why previous versions of GIMP preserve the EXIF data? GIMP 2.3.16 2.3.17 and 2.2.14 still work perfectly for me (in this respect; I had to stop using 2.3.17 because it crashed consistently, probably because of its known bug). Is this tone in any way helpful? The only thing you can achieve by putting it this way is to demotivate the developer working on this. Sorry, but I see no aggression in the above quote. I just tried to point to Mukund that this had nothing to do with broken EXIF, giving several arguments for that. To be precise. BTW, it is interesting to notice that you cut the paragraph that was right before the one you quoted, where I wrote: : Please excuse me, Mukund, but I will be very surprised : if this has something to do with broken EXIF data. Do you also think that an argument that begins with Please excuse me... is aggressive? Probably not, but for some reason you cut that sentence and took the next out of context. And still, it is not aggressive. My apologies to Mukund if he felt that. to ignored bug reports in bugzilla (VERY bad). Please point me to any ignored bug reports. We take bug reports very seriously and I will not let you get away stating in public that we would ignore bug reports. My bug report was sent to bugzilla.redhat when Fedora 4 was out. bugzilla.redhat is dead now. But I sent this email, with subject still the same bug on April 30 to this list (Gimp-developer Digest, Vol 56, Issue 1, to be precise): : However, about a year or two ago, I reported a bug in Bugzilla: : the mouse buttons in GIMP main image window do nothing when I have : attached a my Wacom tablet. ONLY in GIMP. This happened with Fedora : 4,5,6 (fresh installs), with GIMP stable and devel versions. It is : the only program that I have this problem, and the bug is still alive. And just a quick search in http://bugzilla.gnome.org/ in this precise minute returned this: http://bugzilla.gnome.org/show_bug.cgi?id=406440 (2007-02-10) http://bugzilla.gnome.org/show_bug.cgi?id=449590 (2007-06-20) So, 3 bugzilla reports of the same bug. 4 months and not a single answer. And still stated as unconfirmed! And still we cannot use the mouse in GIMP. So, yes, I state, publicly, again: this bug has been ignored for months (in fact, for years, since Fedora 4, and we are now in Fedora 7). No matter if you let me 'get away' or not. BTW, the thread of April 30 mentioned above was because a bug report I made in this list about a shift in the despeckle plugin was unanswered! I sent a second report (also included in the same Digest above): : Pals, : : I reported this bug in this list some time ago, and got no : answer (I think), and the 2.3.16 version still has the same bug: : The despeckle plugin shifts the image one pixel to the right, : and one to the bottom. Consequently, it is essentially useless. : If you draw in the middle of a white background a black cross : like this: : : x : xxx : x : : and run the despeckle plugin with radius 1, you get this asymmetric : output: : : x :
Re: [Gimp-developer] 2.3.18 deletes exif data from images
On Thu, Jun 21, 2007 at 07:59:08AM +0200, Sven Neumann wrote: On Wed, 2007-06-20 at 21:01 -0300, Luis A. Florit wrote: Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. There has never been such an option in the Save as... dialog. My copy of the Gimp disagrees with you on this point: http://www.ethicsgirls.com/stuff/exifshot.jpg -- Alex Pounds (Creature) .~. http://www.alexpounds.com/ /V\http://www.ethicsgirls.com/ // \\ Variables won't; Constants aren't /( )\ ^`~'^ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi, On Thu, 2007-06-21 at 07:58 +0100, Alex Pounds wrote: There has never been such an option in the Save as... dialog. My copy of the Gimp disagrees with you on this point: http://www.ethicsgirls.com/stuff/exifshot.jpg That's not the Save As dialog which would be the file-chooser you get earlier in the process of saving an image. This is the dialog created by the JPEG plug-in. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. There has never been such an option in the Save as... dialog. That's probably the reason why no one understood your mail and cared to answer. Sven On Thu, 2007-06-21 at 07:58 +0100, Alex Pounds wrote: There has never been such an option in the Save as... dialog. My copy of the Gimp disagrees with you on this point: http://www.ethicsgirls.com/stuff/exifshot.jpg That's not the Save As dialog which would be the file-chooser you get earlier in the process of saving an image. This is the dialog created by the JPEG plug-in. Sven Thanks for (yet another) (double) stupid answer, Sven. L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
On 6/22/07, Luis A. Florit wrote: Thanks for (yet another) (double) stupid answer, Sven. offtopic We are not going to compensate loss of Carol by become rude ourselves are we? Could we possibly take a deep breath, count to 10 and smile friendlier to each other? /offtopic Alexandre ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Mukund, On Wed, Jun 20, 2007 at 09:01:16PM -0300, Luis A. Florit wrote: Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. Yes, it's not limited to Bibble. That's a title stated by the reporter, but the bug encompasses the class of bugs where EXIF info is not saved when the EXIF info in the source image is broken (missing required tags). Various cameras/applications can make such images with faulty EXIF info. Please excuse me, Mukund, but I will be very surprised if this has something to do with broken EXIF data. I have 3 cameras: a Canon SD500, a Nikon Coolpix 4500, and a Panasonic FZ50. For the 3, I never have any problem with GIMP (or any other program). Now, for the 3, the Save as... dialog (yes, Sven, the Save as... dialog) show no Save EXIF data option, and for the 3 the EXIF data is now removed. So: 1) Is the EXIF source in the all the 3 cameras (of 3 different brands) broken? 2) Why all the other graphic programs that I use (showfoto, gqview, gthumb, exiftool) always showed the EXIF data with no problem, and still show? 3) Why the Save EXIF data option in the Save as... dialog is no longer present? 4) Why GIMP deletes the EXIF data now? 5) If broken, why previous versions of GIMP preserve the EXIF data? GIMP 2.3.16 2.3.17 and 2.2.14 still work perfectly for me (in this respect; I had to stop using 2.3.17 because it crashed consistently, probably because of its known bug). I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. First, do a check with GIMP trunk and see if the issue has been fixed. If not, please report your image (the original source image) at the same bug too. We'll take a look at it and if it's a different bug, then we'll file another one for it. Please mark the bug as reopened too when you attach the image. Ok. Thanks the time you took to answer, Mukund. Cheers, Luis. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
Hi Mukund, On Wed, Jun 20, 2007 at 09:01:16PM -0300, Luis A. Florit wrote: Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. Yes, it's not limited to Bibble. That's a title stated by the reporter, but the bug encompasses the class of bugs where EXIF info is not saved when the EXIF info in the source image is broken (missing required tags). Various cameras/applications can make such images with faulty EXIF info. Please excuse me, Mukund, but I will be very surprised if this has something to do with broken EXIF data. I have 3 cameras: a Canon SD500, a Nikon Coolpix 4500, and a Panasonic FZ50. For the 3, I never have any problem with GIMP (or any other program). Now, for the 3, the Save as... dialog (yes, Sven, the Save as... dialog) show no Save EXIF data option, and for the 3 the EXIF data is now removed. So: 1) Is the EXIF source in the all the 3 cameras (of 3 different brands) broken? 2) Why all the other graphic programs that I use (showfoto, gqview, gthumb, exiftool) always showed the EXIF data with no problem, and still show? 3) Why the Save EXIF data option in the Save as... dialog is no longer present? 4) Why GIMP deletes the EXIF data now? 5) If broken, why previous versions of GIMP preserve the EXIF data? GIMP 2.3.16 2.3.17 and 2.2.14 still work perfectly for me (in this respect; I had to stop using 2.3.17 because it crashed consistently, probably because of its known bug). I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. First, do a check with GIMP trunk and see if the issue has been fixed. If not, please report your image (the original source image) at the same bug too. We'll take a look at it and if it's a different bug, then we'll file another one for it. Please mark the bug as reopened too when you attach the image. Ok. I realized what happens. Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). Observe that version libexif 0.6.15 has a delicate security bug that was only fixed in the last version 0.6.16 (2007-06-12). My fault, I should have checked better the config log. Sorry. Thanks again, Mukund. L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images (2)
On Thu, 2007-06-21 at 23:25 -0300, Luis A. Florit wrote: Compiling the trunk, I saw that GIMP (also version = 2.3.18) needs libexif = 0.6.15, while there is no RPM repository with libexif version bigger than 0.6.13. (Probably most RPM based distros have the libexif outdated). [...] Same happened to me. I asked in #mandriva-cooker and got, Ankh well, I need a newer libexif Ankh we are 2 releases behind, and unfortunately gimp seems to need one newer than we have mrl32 Ankh: okay mrl32 Ankh: I'll update it :) so we should have a new one soon. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org www.advogato.org ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] 2.3.18 deletes exif data from images
Haven't found in bugs and SVN changelog. GIMP 2.3.18 (Windows) deletes exif data from images. -- With respect Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
On Wed, Jun 20, 2007 at 12:52:50PM +0530, Mukund wrote: On Wed, Jun 20, 2007 at 10:06:53AM +0300, Alexander Rabtchevich wrote: Haven't found in bugs and SVN changelog. GIMP 2.3.18 (Windows) deletes exif data from images. There is a similar bug on bugzilla.gnome.org filed against the GIMP component (it may have been closed recently). Please find the bug and attach your source image (original) to it. It may be that your image's EXIF data is invalid and missing tags required in various IFDs. Raphael has put a patch into GIMP trunk recently to work around this issue and you can try that and see if the EXIF data is still deleted. If you can't find the bug, please file a new bug with the image in question and reply to this thread with the bug number. Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Mukund, Hi Alexander On Wed, Jun 20, 2007 at 10:06:53AM +0300, Alexander Rabtchevich wrote: Haven't found in bugs and SVN changelog. GIMP 2.3.18 (Windows) deletes exif data from images. There is a similar bug on bugzilla.gnome.org filed against the GIMP component (it may have been closed recently). Please find the bug and attach your source image (original) to it. It may be that your image's EXIF data is invalid and missing tags required in various IFDs. Raphael has put a patch into GIMP trunk recently to work around this issue and you can try that and see if the EXIF data is still deleted. If you can't find the bug, please file a new bug with the image in question and reply to this thread with the bug number. Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. Thanks, L. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
I can prove this for RAWs from UFRaw CVS as plug-in (exiv2 2.14 SVN) with Minolta G500 and Minolta 7D and jpg from Sony alpha RAW (Photoshop CS2). Luis A. Florit wrote: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. Thanks, L. -- With respect Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi Luis On Wed, Jun 20, 2007 at 09:01:16PM -0300, Luis A. Florit wrote: Here is the bug in question: http://bugzilla.gnome.org/show_bug.cgi?id=446809 In fact, this bug in 2.3.18 is not related (only) to Bibble. Yes, it's not limited to Bibble. That's a title stated by the reporter, but the bug encompasses the class of bugs where EXIF info is not saved when the EXIF info in the source image is broken (missing required tags). Various cameras/applications can make such images with faulty EXIF info. Raphael: Btw, even if we accept broken EXIF data, the EXIF data we write back should be fixed and valid. I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. I reported this issue a week ago to this list, but got no answer. First, do a check with GIMP trunk and see if the issue has been fixed. If not, please report your image (the original source image) at the same bug too. We'll take a look at it and if it's a different bug, then we'll file another one for it. Please mark the bug as reopened too when you attach the image. Kind regards, Mukund ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2.3.18 deletes exif data from images
Hi, On Wed, 2007-06-20 at 21:01 -0300, Luis A. Florit wrote: I have a Panasonic FZ50 whose EXIF data was always preserved by GIMP. Now, opening a file straight from the camera with GIMP and immediately saving it deletes the EXIF. And in the Save as... dialog, there is no option to save (or not) the EXIF, as it always was. Not evey a grey unavailable option. There has never been such an option in the Save as... dialog. That's probably the reason why no one understood your mail and cared to answer. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
