Crashes instantly on launch with Pentium J5005 Processor

[milvi]

* Impact
djvulibre segfaults on older i386 CPU

* Test case
try to open a djvu file in evince on an atom based machine

* Regression potential
check that djvu files are open fine on newer machines

---------------------------------

[PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel Atom based processors. (I got a J5005 pentium ).
Doesn't crash on a Intel® Core™ i7-7567U.

Due to this bug https://sourceforge.net/p/djvu/bugs/293/ ,

and fixed in commit 8407dd, on the 7th of October 2018.

From git tags, it is included in 3.5.27.1-11 (probably version xxx -10, though I cannot see this tag in git history)

I notice that no dependency change affects any of the versions to the build process up to Disco (3.5.27.1-10)

For intel J5005 (or N5000 on other popular machines ) this bug renders the package useless.

Indeed, it crashes immediately at application startup. Note that this affects rdependencies such as evince, djview4.

I suggest upgrading the version available for Bionic LTS as part of the development hardware stack long term support to 3.5.27.1-11.

Yours sincerly,

Milvi

[Sebastien Bacher (seb128)]

It looks like it was fixed upstream with that commit
https://sourceforge.net/p/djvu/djvulibre-git/ci/8407dd34

[Robie Basak (racb)]

Hello milvi, or anyone else affected,

Accepted djvulibre into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/djvulibre/3.5.27.1-8ubuntu0.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[milvi (milvi)]

Hello Robie,

testing djvulibre-bin :
testing command : djvups, djview4
hardware : atom based processor (Pentium J5005)

- 3.5.27.1-8ubuntu0.1

$ Segfault (core dumped)
(as expected)

then with version,

- 3.5.27.1-8ubuntu0.2

It works ! It now returns and produces a valid postscript file.

djview4 (version 4.10.6-3) works only when the patch is applied (3.5.27.1-8ubuntu0.1 -> 3.5.27.1-8ubuntu0.2).
To check this, I ran djview4 before and after upgrade.

Regression on an Intel® Core™ i7-7567U doesn't trigger any failure.
- djvups, djview4 run like a charm as before.

Thanks a bunch,

There is a community out there reading old research material, digitized papers, and books, the likes of which are often found in DJVU format. You have opened access again to half my disk's content !

[Sebastien Bacher (seb128)]

Great, thanks for testing the update and for the nice comment!

[Launchpad Janitor (janitor)]

This bug was fixed in the package djvulibre - 3.5.27.1-8ubuntu0.2

---------------
djvulibre (3.5.27.1-8ubuntu0.2) bionic; urgency=medium

  * debian/patches/git_cpu_fix.patch:
    - don't segfault when trying to open document on an atom based config
      (lp: #1846785)

 -- Sebastien Bacher <email address hidden> Wed, 20 May 2020 23:32:10 +0200

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for djvulibre has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.