You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in version: 2.0.5 Reported for operating system, platform: Windows 7, x86
Comments on the original bug report:
On 2020-01-11 02:44:38 +0000, Austin Hurst wrote:
I'm one of the maintainers of the pysdl2 project, and have spent a good chunk of the past week updating the test/CI suite to support the current set of SDL2 libraries. In the process, I think I've found a regression in SDL2_image from 2.0.4 to 2.0.5: loading XCF images (well, our test XCF image) no longer works with the official 32-bit Windows runtime DLLs (returns a null pointer instead of a surface).
You can see that the tests for IMG_LoadXCF_RW (and other image-loading functions with the .xcf test image) fail with the 32-bit SDL2_image 2.0.5, but pass with the 64-bit SDL2_image 2.0.5 and with the 32-bit SDL2_image 2.0.4 & 2.0.2.
While trying to figure out if it was a pysdl2 or SDL2_image problem, I dug into the source history and found this commit between 2.0.4 and 2.0.5 that looks like a likely culprit, a commit that adds support for 64-bit offsets in XCF files: https://hg.libsdl.org/SDL_image/rev/6536f264b1eb
Not sure how common XCF loading in SDL2 actually is, but I figured you'd want the heads-up!
OK, I think I understand what's going on.
XCF files normally have the version in their header, just like
00000000 67 69 6d 70 20 78 63 66 20 76 30 31 31 00 00 00 |gimp xcf v011...|
but this one has
00000000 67 69 6d 70 20 78 63 66 20 66 69 6c 65 00 00 00 |gimp xcf file...|
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: 2.0.5
Reported for operating system, platform: Windows 7, x86
Comments on the original bug report:
On 2020-01-11 02:44:38 +0000, Austin Hurst wrote:
On 2020-10-26 16:22:28 +0000, Ozkan Sezer wrote:
On 2020-10-26 22:19:23 +0000, miniupnp@free.fr wrote:
On 2020-10-26 22:33:59 +0000, miniupnp@free.fr wrote:
On 2020-10-26 22:34:32 +0000, miniupnp@free.fr wrote:
On 2020-10-26 23:05:40 +0000, Ozkan Sezer wrote:
On 2020-10-31 17:24:13 +0000, Ozkan Sezer wrote:
The text was updated successfully, but these errors were encountered: