FS#80091 - [prusa-slicer] CRASH: Wrong JPEG library version: library is 80, caller expects 62

Attached to Project: Arch Linux
Opened by Tomas Mudrunka (harvie) - Thursday, 26 October 2023, 21:41 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 November 2023, 22:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Bruno Pagani (ArchangeGabriel)
freswa (frederik)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Crash when slicing g-code with JPEG thumbnail says:
Wrong JPEG library version: library is 80, caller expects 62

Upstream says it's a packaging problem, because it works in their AppImage.

Additional info:
* package version(s)
prusa-slicer 2.6.1-1
* link to upstream bug report, if any
https://github.com/prusa3d/PrusaSlicer/issues/11239

Steps to reproduce:

Go to printer settings
switch to expert mode
set following:
g-code flavor: marlin2
g-code thumbnails: 230x180
Format of g-code thumbnails: JPG
Slice STL model as usual
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 23 November 2023, 22:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  prusa-slicer-2.7.0-1
Comment by Toolybird (Toolybird) - Friday, 27 October 2023, 01:01 GMT
The build log [1] shows a vendored version (2.0.6) of libjpeg-turbo being downloaded as part of the build. This is not good...because there now appears to be some kind of mismatch linking against the system libjpeg.

[1] https://reproducible.archlinux.org/api/v0/builds/510383/log
Comment by Tomas Mudrunka (harvie) - Tuesday, 21 November 2023, 14:26 GMT
Just tried the AppImage version on ArchLinux, i can confirm it works there. So it has to be issue with packaging.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 23 November 2023, 22:15 GMT
I think I've found a working fix for v2.7.0. Could you check whether 2.7.0-1 works for you?
Comment by loqs (loqs) - Thursday, 23 November 2023, 22:38 GMT
@Svenstaro now that Arch is no longer using all upstream's vendored dependencies will that not mean upstream will reject Arch bug reports again? Upstream rejected this bug report anyway. If upstream only supports their AppImage why keep the other vendored dependencies?

Loading...