Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#73313 - [scribus] Segfault when starting

Attached to Project: Community Packages
Opened by Danilo (danilo) - Sunday, 09 January 2022, 18:09 GMT
Last edited by Caleb Maclennan (alerque) - Monday, 10 January 2022, 11:24 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Caleb Maclennan (alerque)
Bruno Pagani (ArchangeGabriel)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When starting scribus (even when calling just --version or --help), it immediately segfaults.

System is up to date, Scribus 1.5.7-10 is installed.

I'm using Sway and Wayland. QT_QPA_PLATFORM is set to "wayland".

Stack trace:

Stack trace of thread 69944:
#0 0x00007f4dbd443214 _ZN7QStringaSERKS_ (libQt5Core.so.5 + 0x159214)
#1 0x000056141c01138d n/a (scribus + 0x35138d)
#2 0x000056141c0139c8 n/a (scribus + 0x3539c8)
#3 0x000056141ca952ad __libc_csu_init (scribus + 0xdd52ad)
#4 0x00007f4dbcdceab1 __libc_start_main (libc.so.6 + 0x27ab1)
#5 0x000056141c01526e _start (scribus + 0x35526e)
This task depends upon

Closed by  Caleb Maclennan (alerque)
Monday, 10 January 2022, 11:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  Temporary workaround posted as scribus-1.5.7-11-x86_64.pkg.tar.zst
Comment by Danilo (danilo) - Sunday, 09 January 2022, 18:17 GMT
The segfault doesn't happen if I rebuild the package from PKGBUILD, so maybe a rebuild is needed?
Comment by Caleb Maclennan (alerque) - Monday, 10 January 2022, 09:57 GMT
I'm not on wayland at all and see the same thing. I'll look into a rebuild (and hopefully see what we're linking against that caused this).
Comment by Caleb Maclennan (alerque) - Monday, 10 January 2022, 10:07 GMT
I bumped the pkgrel and rebuilt from the current [community] PKGBUILD and — segfault. No improvement on my end. I rebuilt using the official `extra-x86_64-build` script, did you? Or did you build against what was on your current system?
Comment by Danilo (danilo) - Monday, 10 January 2022, 10:12 GMT
Caleb: I got the PKGBUILD and patch from https://github.com/archlinux/svntogit-community/tree/packages/scribus/trunk and built it using "makepkg -sfi", so yeah, it was built against my current system...
Comment by Caleb Maclennan (alerque) - Monday, 10 January 2022, 10:15 GMT
Can you try building the same PKGBUILD using `extra-x86_64-build` (in the *devtools* package if you don't have it)? This is the required way to build anything that goes into official repositories, but there may actually be an issue with new compiler options in there. It would be really interesting if somehow you building it produced a working version, but it's also pretty strange that we're both getting segfaults with the official package on fully up to date systems. Something is cross wired...
Comment by Caleb Maclennan (alerque) - Monday, 10 January 2022, 10:28 GMT
I just confirmed building this using `makepkg` with no chroot also produces a working package on my system. The chrooted builds still segfault for me, even fresh ones.

Also notable is the locally built version is some 2.73 MB bigger (installed) than the chroot build. I'll try to figure out what is different under the hood.
Comment by Caleb Maclennan (alerque) - Monday, 10 January 2022, 11:14 GMT
The difference appears to be Arch's disttools enabling LTO by default. I'll post a build with that disabled for now and we need to figure out what options to pass or how to patch Scribus to work with LTO enabled.

Loading...