After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 721948 - This file can't be exported to PNG
This file can't be exported to PNG
Status: RESOLVED DUPLICATE of bug 721135
Product: GIMP
Classification: Other
Component: General
2.8.10
Other Mac OS
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-01-10 17:32 UTC by Anders
Modified: 2014-01-10 18:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The file that i can't export (3.05 KB, image/png)
2014-01-10 17:32 UTC, Anders 		Details

Description Anders 2014-01-10 17:32:52 UTC 
Created attachment 265954 [details]
The file that i can't export

When I try to open a PNG file and export it to PNG I receive an error message and export fails.


How to reproduce this bug:
1. Open the attached file named ic_action_search.png in GIMP.
2. File -> Export as..
3. Press Export button.
4. Press Export button in next window.
5. You will see the error message.
6. If you look in the directory where you exported it to its file size 0 byte.


I have no problem exporting other PNG files. I can open ic_action_search.png and it look like it should.
I am running OS X mavericks.
Comment 1 Michael Natterer 2014-01-10 17:45:23 UTC 
Is this a duplicate of 721135 ?
Comment 2 Anders 2014-01-10 18:04:54 UTC 
Yes it is a duplicate of 721135. You can close this issue.

If it helps the png file i have problem with have colorsync-profile set to sRGB IEC61966-2.1.
The other png file that i can export without any problems do not have any colorsync-profile set.
Comment 3 Michael Schumacher 2014-01-10 18:07:58 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 721135 ***