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 794989 - Raw Data Import with an Offset and Dimensions Bigger than File Size Creates Blank/White Image
Raw Data Import with an Offset and Dimensions Bigger than File Size Creates B...
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
2.10.0-RC1
Other All
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-04-04 20:43 UTC by Gabriel Miceli
Modified: 2018-05-24 19:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
This is a file containing font data; however, importing it a certain way into GIMP fails. (135.33 KB, application/octet-stream)
2018-04-04 20:43 UTC, Gabriel Miceli 		Details

Description Gabriel Miceli 2018-04-04 20:43:44 UTC 
Created attachment 370533 [details]
This is a file containing font data; however, importing it a certain way into GIMP fails.

It seems to me that whenever I try to import certain raw images (*.data) into GIMP with a non-zero offset, and I set the dimensions to where there are more pixels in the generated image than there are bytes in the file, it generates a white screen and gives "fread failure" in the terminal when run from it. The result varies with different files, but the file I attached to this bug report is what causes it. Image Type: RGB. Offset: Not 0. Width: 16. Height: >3000. This also happens in the stable release 2.8.22.
It could be my computer (Lubuntu 17.10, by the way), but I don't think it is. Correct me if I'm wrong.
Comment 1 GNOME Infrastructure Team 2018-05-24 19:25:56 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1351.