[Bug 275350] net-im/telegram-desktop: qt6 flavor dumping core on startup after qt6 update

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275350

            Bug ID: 275350
           Summary: net-im/telegram-desktop: qt6 flavor dumping core on
                    startup after qt6 update
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: madpilot at FreeBSD.org
                CC: kde at FreeBSD.org

Hi!

First of all thanks to all people working on this port and keeping qt libraries
up to date.

Unluckily, after the update to qt 6.6.0 in ports commit
1d76bdf62dffad91834699701f41d3374dfb6a3a the qt6 flavor of telegram desktop
fails to start.

I don't have debug enabled binaries available, and have not investigated mush,
but I got this using lldb:

```
(lldb) run
Process 4360 launched: '/usr/local/bin/telegram-desktop' (x86_64)
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not
permitted (1)
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
Process 4360 stopped
* thread #10, name = 'telegram-desktop', stop reason = signal SIGSEGV: invalid
address (fault address: 0x0)
    frame #0: 0x0000000843ed9376 libQt6Svg.so.6`___lldb_unnamed_symbol1597 + 38
libQt6Svg.so.6`___lldb_unnamed_symbol1597:
->  0x843ed9376 <+38>: movq   (%rdi), %rax
    0x843ed9379 <+41>: callq  *0x18(%rax)
    0x843ed937c <+44>: cmpl   $0x2, %eax
    0x843ed937f <+47>: jae    0x843ed93e0               ; <+144>
(lldb) 
```

Looks like this affects linux too and has already been reported upstream:

https://github.com/telegramdesktop/tdesktop/issues/27134


The issue could be in qt6svg but I was unable to find a bug report about this
in qt6 bug reporting system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.