Well, what I mean is that the mailing list is not the best place to
report bugs :
- If nobody takes care of it soon, it will be forgotten. And it's not
what we want.
- Bugzilla also provides a lot of tools specific to bug handling, it
really helps their management.
- When a specific file is needed to reproduce the problem, then it's
better to provide a (small) sample showing the bug. Even if it seems
easy to get such a file. The reason is that developpers want to recreate
the "exact" same conditions, e.g. to avoid misunderstanding. The other
reason is that the bug will perhaps be a bit faster to reproduce...
The last point is really not mandatory though, it's more my opinion.
Thanks!
Téo Mazars
Le 2013-04-20 17:52, Partha Bagchi a écrit :
I don't believe this has anything to do with a specific tiff file. So
attaching a tiff does not make sense to me.
Thanks for your response!
Partha
On Sat, Apr 20, 2013 at 4:32 AM, mazarst <mazarst@xxxxxxxxxxxxxxx>
wrote:
I seem to get tiff errors when I am loading a 16-bit tiff say after
opening a couple of images of other formats like png or jpeg. Other
times if I open the tiff first, it seems to open fine.Â
I am stumped. :(
The error is :LibGimp-WARNING (recursed) **: file-tiff-load.exe:
gimp_flush(): error: Invalid argument
Gimp then crashes, that is closes completely. I can provide the
Windows crash message, but I doubt that it will be helpful.
Gimp git updated today on Window 7 64-bit.
Thanks,
Partha
Thanks for reporting this.
Please, fill a bug report in bugzilla and attach a tiff showing the
bug.
Thanks again,
Téo Mazars
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-developer-list [1]
Links:
------
[1] https://mail.gnome.org/mailman/listinfo/gimp-developer-list
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
