Your message dated Fri, 6 Feb 2026 14:24:52 -0500 with message-id <caaajcmzeurnzuo0tnwoqma_-gww_fmu5a+s-n3mgsndfvdw...@mail.gmail.com> and subject line Re: io-jasper invalid operation has caused the Debian Bug report #774712, regarding io-jasper invalid operation to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 774712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774712 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gdk-pixbuf Version: 2.31.1-2 Tags: upstream patch The following code in io-jasper.c looks suspicious: [...] if (jas_stream_write (context->stream, buf, size) < 0) { g_set_error_literal (error, GDK_PIXBUF_ERROR, GDK_PIXBUF_ERROR_INSUFFICIENT_MEMORY, [...] here size is usually a small size (4096...). However in jasper we have: [...] /* Write characters from a buffer to a stream. */ int jas_stream_write(jas_stream_t *stream, const void *buf, int cnt); [...] Where implementation is: int jas_stream_write(jas_stream_t *stream, const void *buf, int cnt) { int n; const char *bufptr; bufptr = buf; n = 0; while (n < cnt) { if (jas_stream_putc(stream, *bufptr) == EOF) { return n; } ++bufptr; ++n; } return n; } therefore the return value can never be below zero. I suggest changing the code to: if (jas_stream_write (context->stream, buf, size) != size ) {
--- End Message ---
--- Begin Message ---gdk-pixbuf hasn't used jasper in Debian for a decade so I'm closing this bug. Thank you, Jeremy Bícha
--- End Message ---
