Arch Linux

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#79905 - [qt6-svg] telegram-desktop will SIGSEGV in 4.10.3-2

Attached to Project: Arch Linux
Opened by Celeste (Coelacanthus) - Tuesday, 10 October 2023, 17:26 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 10 October 2023, 20:01 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

telegram-desktop will SIGSEGV when upgraded to 4.10.3-2

Additional info:
* package version(s): 4.10.3-2

Steps to reproduce:
Just run it.

You got
qt.svg: Error while inflating gzip file: SVG format check failed
zsh: segmentation fault (core dumped) telegram-desktop

if use gdb bt, you got
#0 0x00007a389dd4c5b2 in detectCycles(QSvgNode const*, QList<QSvgUse const*>) (node=0x0, active=QList<const QSvgUse *> (size = 0)) at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/svg/qsvghandler.cpp:3609
#1 0x00007a389dd541ef in QSvgHandler::parse() (this=0x7a38377f5a40) at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/svg/qsvghandler.cpp:3690
#2 0x00007a389dd5f5d8 in QSvgTinyDocument::load(QByteArray const&) (contents="") at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/svg/qsvgtinydocument.cpp:199
#3 0x00007a389dd5f752 in loadDocument<QByteArray>(QSvgRenderer*, QSvgRendererPrivate*, QByteArray const&) (q=q@entry=0x7a3826a344d8, d=0x7a3826a0a780, in="") at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/svg/qsvgrenderer.cpp:316
#4 0x00007a389dd5f990 in QSvgRenderer::load(QByteArray const&) (this=this@entry=0x7a3826a344d8, contents="") at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/svg/qsvgrenderer.cpp:356
#5 0x00007a38864d963b in QSvgIOHandlerPrivate::load(QIODevice*) (this=this@entry=0x7a3826a344d0, device=<optimized out>) at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/plugins/imageformats/svg/qsvgiohandler.cpp:53
#6 0x00007a38864d9a33 in QSvgIOHandlerPrivate::load(QIODevice*) (device=<optimized out>, this=0x7a3826a344d0) at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/plugins/imageformats/svg/qsvgiohandler.cpp:146
#7 QSvgIOHandler::read(QImage*) (this=0x7a38223f33e0, image=0x7a38377f5f40) at /usr/src/debug/qt6-svg/qtsvg-everywhere-src-6.6.0/src/plugins/imageformats/svg/qsvgiohandler.cpp:121
#8 0x00007a389a370e90 in QImageReader::read(QImage*) (this=0x7a38377f5e98, image=0x7a38377f5f40) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/gui/image/qimagereader.cpp:1221
#9 0x00006249eb4de736 in ()
#10 0x00006249eb005d32 in ()
#11 0x00007a389e3e713f in () at /usr/lib/libdispatch.so
#12 0x00007a3898aaa9eb in start_thread (arg=<optimized out>) at pthread_create.c:444
#13 0x00007a3898b2e7cc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 10 October 2023, 20:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt6-svg 6.6.0-2
Comment by Celeste (Coelacanthus) - Tuesday, 10 October 2023, 17:32 GMT
Someone told me that there is a bug in libstdc++ that will lead software using microsoft-gsl SIGSEGV, but will have a different backtrace.
https://src.fedoraproject.org/rpms/guidelines-support-library/pull-request/1
https://github.com/desktop-app/GSL/commit/09938e870420b69a01f55c755207c871bc20b4e5
May be unrelated, but provided as information.
Comment by Celeste (Coelacanthus) - Tuesday, 10 October 2023, 17:37 GMT
Ok, upstream has a fix in QtSVG, please include it.
https://github.com/qt/qtsvg/commit/edc8ca7f1e45302223b4b7962a57a30918f84c8d
Comment by Devin Cofer (Ranguvar) - Tuesday, 10 October 2023, 19:52 GMT
I am also affected.
Confirmed patched qt6-svg 6.6.0-1 allows telegram 4.10.3-2 to start and run normally
Comment by Toolybird (Toolybird) - Tuesday, 10 October 2023, 19:57 GMT
> Just run it.

Launches fine here i.e. cannot repro. So it's not across the board.

Loading...