Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15568 - Gimp can't load mng files

Attached to Project: Arch Linux
Opened by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 22:01 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 19 July 2009, 00:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Gimp can't load mng files. When trying so, Gimp complains: "Opening '/path/to/file.mng' failed: Unknown file type"

Additional info:
Gimp version: 2.6.6-2
libmng version: 1.0.10-2
This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 19 July 2009, 00:30 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 18 July 2009, 22:30 GMT
Probably this is more related to libmng than gimp. Previuos (before libjpeg-7 upgrade) versions works OK?

All .mng fails? Others programs loading the same mng fail?

Please attach the .mng if small <= 2MB
Comment by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 22:32 GMT
Yes it worked sometime ago, before updating libjpeg and libmng. And it fails for all mng files I've tried, which were created with gimp when it worked.
Comment by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 22:38 GMT
Now, I'm trying to remember, and I don't know if it worked before the update... Because I still can create mng files. But Gimp should be able to open them, right?
Thanks
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 18 July 2009, 22:47 GMT
Hi, I rebuilded the libmng here, and I see two warnings of strict aliasing, this is bad in many cases. Can you recompile libmng with this PKGBUILD?

This only add this line at top of the build function: export CFLAGS="$CFLAGS -fno-strict-aliasing"

Test and report if the problem is solved, Thanks.
   PKGBUILD (0.8 KiB)
Comment by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 22:59 GMT
I'm sorry, but this didn't solve the problem :(
I have exactly the same complain from Gimp...
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 18 July 2009, 23:03 GMT
mmm ok, please attach the .mng here.

when you upgraded the libmng pkg (to your build with the pkgbuild), you have closed all apps that uses libmng? This can be important.
Comment by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 23:05 GMT
Here you are! (I'm designing an animated version of the KMess logo as you will see :))
   kmess.mng (186.3 KiB)
Comment by Adria Arrufat (swiftscythe) - Saturday, 18 July 2009, 23:05 GMT
Yes I closed all mng-related apps ;)
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 18 July 2009, 23:36 GMT
mmm seems that gimp by default don't open .mng files (is not listed in the know extensions) This is why this msg appears. "File -> open". But appears in "File->save".

I don't use gimp, you need a plugin to work with mng?
Comment by Adria Arrufat (swiftscythe) - Sunday, 19 July 2009, 00:03 GMT
No, i don't need any plugins :) I have always a gimp format file before exporting to mng, so i can edit and export again.

So there's no bug, it's just gimp that doesn't support opening mng files. It's VERY strange, as it can create them...
Anyway, GwenView from KDE 4.3 will be able to open them correctly, although they won't be editable...

Thanks for your replies :D
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 19 July 2009, 00:12 GMT
No problem, closing this...

Loading...