Problem on Ubuntu 13.10

[paul womack]

(short version; the attached image was generated by Hugin
on Ubuntu 13.10 but isn't readable by Eye of Gnome on Ubuntu 13.10)

I first encountered this with files made by Hugin 2011.4.0 but the version
that (actually) ships with Ubuntu 13.10 (Hugin 2013.0.0)
shows the same incompatibility.

Again, I first hit this using a self compiled
viewer (viewnior) but eog (Eye of Gnome) shows
the same error, which I suspect to be in a core
library.

The first files that showed the error were quite large (20,000 pixels)
but some work has led to the attached, small, file, a simple
2-up shot.

The error is "Error Interpreting JPEG image file(Suspension not allowed here)"

Gimp reads the file just fine, imagemagick is OK, netpbm is OK.

The message is from the JPEG library

./jerror.h:JMESSAGE(JERR_CANT_SUSPEND, "Suspension not allowed here")

./djpeg.c: ERREXIT(cinfo, JERR_CANT_SUSPEND);
./jcmarker.c: ERREXIT(cinfo, JERR_CANT_SUSPEND);
./jcapimin.c: ERREXIT(cinfo, JERR_CANT_SUSPEND);
./jerror.h:JMESSAGE(JERR_CANT_SUSPEND, "Suspension not allowed here")
./jchuff.c: ERREXIT(cinfo, JERR_CANT_SUSPEND);
./jcphuff.c: ERREXIT(entropy->cinfo, JERR_CANT_SUSPEND);

I am not yet sure wether hugin is spawing an invalid file, or wether
there's a weakness in the viewers.

BugBear

[Bruno Postle]

On 18 November 2013 11:00, paul womack <pwo...@papermule.co.uk> wrote:

(short version; the attached image was generated by Hugin
on Ubuntu 13.10 but isn't readable by Eye of Gnome on Ubuntu 13.10)

I first encountered this with files made by Hugin 2011.4.0 but the version
that (actually) ships with Ubuntu 13.10 (Hugin 2013.0.0)
shows the same incompatibility.

Again, I first hit this using a self compiled
viewer (viewnior) but eog (Eye of Gnome) shows
the same error, which I suspect to be in a core
library.

The  JPEG you attached is 'arithmetic coded', this is a problem caused by the switching to libjeg-turbo. Your distribution needs to apply a one-line patch to enblend or upgrade to enblend 4.1, see this bug report: https://bugs.launchpad.net/enblend/+bug/798952

--

Bruno

[paul womack]

Bruno Postle wrote:
> The JPEG you attached is 'arithmetic coded', this is a problem caused by the switching to libjeg-turbo. Your distribution needs to apply a one-line patch to enblend or upgrade to enblend 4.1, see this bug report: https://bugs.launchpad.net/enblend/+bug/798952

Thanks for that; I can confirm that man enblend shows:

enblend 4.0-753b534c819d

BugBear

[paul womack]

Yowza. I just followed this page

http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Shortcut

for "stable" and still get

enblend 4.0-753b534c819d

even though the bug report you linked to is from 2011.

That's one hell of a release lag :-(

BugBear

[paul womack]

paul womack wrote:
> http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Shortcut
>
> for "stable" and still get
>
> enblend 4.0-753b534c819d
>
> even though the bug report you linked to is from 2011.
>
> That's one hell of a release lag :-(

Since I prefer to stay on distributed binaries, I'll simply export as TIFF
and post-convert to JPEG to work round this fault.

BugBear

[Bruno Postle]

On 20 November 2013 09:42, paul womack <pwo...@papermule.co.uk> wrote:

Since I prefer to stay on distributed binaries, I'll simply export as TIFF
and post-convert to JPEG to work round this fault.

 

You could ask Ubuntu to fix the bug, the workaround is a simple one-line patch for enblend. Usually you can get a fast response from a distribution with this sort of thing, and the fix benefits all the other users too.

--

Bruno

[paul womack]

Bruno Postle wrote:

>
> You could ask Ubuntu to fix the bug, the workaround is a simple one-line patch for enblend. Usually you can get a fast response from a distribution with this sort of thing, and the fix benefits all the other users too.

I'd assumed it would be fixed (along with all the new features) as part of the
ongoing new version pipeline.

BugBear

[Bruno Postle]

The new enblend isn't likely to make it into a version of a distribution that is already released, but these do get simple bug fixes, and often. Lots of people use older distribution releases, they shouldn't have to upgrade to the latest beta to fix a critical bug.

--

Bruno