FS#79575 - [telegram-desktop] crashes randomly

Attached to Project: Arch Linux
Opened by Mr.Smith1974 (Mr.Smith1974) - Tuesday, 05 September 2023, 13:51 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 06 September 2023, 04:41 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

telegram crashes randomly

Version:
extra/telegram-desktop 4.9.4-1

```
Sep 05 08:04:59 home-desktop systemd-coredump[11521]: [🡕] Process 11411 (telegram-deskto) of user 1000 dump>
Module libBlocksRuntime.so without build-id.
Module libdispatch.so without build-id.
Stack trace of thread 11411:
#0 0x00007f1a30660ee1 n/a (libjemalloc.so.2 + 0x60ee>
#1 0x00007f1a30619fe7 n/a (libjemalloc.so.2 + 0x19fe>
#2 0x00007f1a3173eec6 _ZN10QImageDataD1Ev (libQt6Gui>
#3 0x00007f1a31744e99 _ZN6QImageD2Ev (libQt6Gui.so.6>
#4 0x0000555eebd7c628 n/a (telegram-desktop + 0xf826>
#5 0x00007f1a2fe40cc6 n/a (libc.so.6 + 0x40cc6)
#6 0x00007f1a2fe40e10 exit (libc.so.6 + 0x40e10)
#7 0x00007f1a2fe27cd7 n/a (libc.so.6 + 0x27cd7)
#8 0x00007f1a2fe27d8a __libc_start_main (libc.so.6 +>
#9 0x0000555eeb84efc5 n/a (telegram-desktop + 0xa54f>

Stack trace of thread 11420:
#0 0x00007f1a2ff0ed6d syscall (libc.so.6 + 0x10ed6d)
#1 0x00007f1a362e1c07 g_cond_wait (libglib-2.0.so.0 >
#2 0x00007f1a36257154 n/a (libglib-2.0.so.0 + 0x2515>
#3 0x00007f1a362c125e n/a (libglib-2.0.so.0 + 0x8f25>
#4 0x00007f1a362becd5 n/a (libglib-2.0.so.0 + 0x8ccd>
#5 0x00007f1a2fe8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007f1a2ff10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 11421:
#0 0x00007f1a2ff0359f __poll (libc.so.6 + 0x10359f)
#1 0x00007f1a362e9b8f n/a (libglib-2.0.so.0 + 0xb7b8>
#2 0x00007f1a3628a112 g_main_context_iteration (libg>
...skipping...
#3 0x00007f1a35906387 n/a (libdispatch.so + 0x36387)
#4 0x00007f1a2fe8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f1a2ff10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 11427:
#0 0x00007f1a2fe894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f1a2fe9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007f1a3590799f n/a (libdispatch.so + 0x3799f)
#3 0x00007f1a35906387 n/a (libdispatch.so + 0x36387)
#4 0x00007f1a2fe8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f1a2ff10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 11431:
#0 0x00007f1a2ff0359f __poll (libc.so.6 + 0x10359f)
#1 0x00007f1a1d1ac8c7 n/a (libpulse.so.0 + 0x338c7)
#2 0x00007f1a1d19646c pa_mainloop_poll (libpulse.so.>
#3 0x00007f1a1d1a042c pa_mainloop_iterate (libpulse.>
#4 0x00007f1a1d1a04e1 pa_mainloop_run (libpulse.so.0>
#5 0x00007f1a1d1b0c02 n/a (libpulse.so.0 + 0x37c02)
#6 0x00007f1a1d14dc67 n/a (libpulsecommon-16.1.so + >
#7 0x00007f1a2fe8c9eb n/a (libc.so.6 + 0x8c9eb)
#8 0x00007f1a2ff10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 11440:
#0 0x00007f1a2fe894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f1a2fe9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007f1a3590799f n/a (libdispatch.so + 0x3799f)
#3 0x00007f1a35906387 n/a (libdispatch.so + 0x36387)
#4 0x00007f1a2fe8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f1a2ff10dfc n/a (libc.so.6 + 0x110dfc)
ELF object binary architecture: AMD x86-64

```


```
% telegram-desktop
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
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
```
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 06 September 2023, 04:41 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Tuesday, 05 September 2023, 21:40 GMT
When reporting crashes, you *must* post stacktraces that include debug symbols [1], because what is posted above is essentially useless. It's usually as simple as this (after the crash, with gdb installed):

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by Mr.Smith1974 (Mr.Smith1974) - Wednesday, 06 September 2023, 04:23 GMT
root@home-desktop /home/admin # coredumpctl gdb
PID: 43762 (telegram-deskto)
UID: 1000 (admin)
GID: 1000 (admin)
Signal: 11 (SEGV)
Timestamp: Tue 2023-09-05 13:52:15 MSK (17h ago)
Command Line: /usr/bin/telegram-desktop --
Executable: /usr/bin/telegram-desktop
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.telegram.desktop-60336a92fdda4001b65ff3a2bcb7c1ca.scope
Unit: user@1000.service
User Unit: app-org.telegram.desktop-60336a92fdda4001b65ff3a2bcb7c1ca.scope
Slice: user-1000.slice
Owner UID: 1000 (admin)
Boot ID: 64069b8ff2614d3886035b6b102b706a
Machine ID: 8f61f012c3c1458d8ee14ed948c1497a
Hostname: home-desktop
Storage: /var/lib/systemd/coredump/core.telegram-deskto.1000.64069b8ff2614d3886035b6b102b706a.43762.1693911135000000.zst (present)
Size on Disk: 29.2M
Message: Process 43762 (telegram-deskto) of user 1000 dumped core.

Module libBlocksRuntime.so without build-id.
Module libdispatch.so without build-id.
Stack trace of thread 43762:
#0 0x00007fc837660ee1 n/a (libjemalloc.so.2 + 0x60ee1)
#1 0x00007fc837619fe7 n/a (libjemalloc.so.2 + 0x19fe7)
#2 0x00007fc837b78b26 n/a (libQt6Core.so.6 + 0x178b26)
#3 0x00007fc836e40731 __cxa_finalize (libc.so.6 + 0x40731)
#4 0x00007fc837adcec8 n/a (libQt6Core.so.6 + 0xdcec8)
#5 0x00007fc83d6ac0e2 n/a (ld-linux-x86-64.so.2 + 0x10e2)
#6 0x00007fc83d6aff4e n/a (ld-linux-x86-64.so.2 + 0x4f4e)
#7 0x00007fc836e40cc6 n/a (libc.so.6 + 0x40cc6)
#8 0x00007fc836e40e10 exit (libc.so.6 + 0x40e10)
#9 0x00007fc836e27cd7 n/a (libc.so.6 + 0x27cd7)
#10 0x00007fc836e27d8a __libc_start_main (libc.so.6 + 0x27d8a)
#11 0x00005630e2e78fc5 n/a (telegram-desktop + 0xa54fc5)

Stack trace of thread 43768:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e8c055 pthread_cond_timedwait (libc.so.6 + 0x8c055)
#2 0x00007fc83762c643 n/a (libjemalloc.so.2 + 0x2c643)
#3 0x00007fc83762bf43 n/a (libjemalloc.so.2 + 0x2bf43)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43774:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43764:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e8c055 pthread_cond_timedwait (libc.so.6 + 0x8c055)
#2 0x00007fc83762c643 n/a (libjemalloc.so.2 + 0x2c643)
#3 0x00007fc83762c132 n/a (libjemalloc.so.2 + 0x2c132)
#4 0x00007fc83762bff5 n/a (libjemalloc.so.2 + 0x2bff5)
#5 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43770:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e8c055 pthread_cond_timedwait (libc.so.6 + 0x8c055)
#2 0x00007fc83762c643 n/a (libjemalloc.so.2 + 0x2c643)
#3 0x00007fc83762bf43 n/a (libjemalloc.so.2 + 0x2bf43)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43766:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e8c055 pthread_cond_timedwait (libc.so.6 + 0x8c055)
#2 0x00007fc83762c643 n/a (libjemalloc.so.2 + 0x2c643)
#3 0x00007fc83762bf43 n/a (libjemalloc.so.2 + 0x2bf43)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43778:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43793:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43771:
#0 0x00007fc836f0ed6d syscall (libc.so.6 + 0x10ed6d)
#1 0x00007fc83d1e3c07 g_cond_wait (libglib-2.0.so.0 + 0xafc07)
#2 0x00007fc83d159154 n/a (libglib-2.0.so.0 + 0x25154)
#3 0x00007fc83d1c325e n/a (libglib-2.0.so.0 + 0x8f25e)
#4 0x00007fc83d1c0cd5 n/a (libglib-2.0.so.0 + 0x8ccd5)
#5 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43772:
#0 0x00007fc836f0359f __poll (libc.so.6 + 0x10359f)
#1 0x00007fc83d1ebb8f n/a (libglib-2.0.so.0 + 0xb7b8f)
#2 0x00007fc83d18c112 g_main_context_iteration (libglib-2.0.so.0 + 0x58112)
#3 0x00007fc83d18c162 n/a (libglib-2.0.so.0 + 0x58162)
#4 0x00007fc83d1c0cd5 n/a (libglib-2.0.so.0 + 0x8ccd5)
#5 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43775:
#0 0x00007fc836f11226 epoll_wait (libc.so.6 + 0x111226)
#1 0x00007fc83bd499b8 n/a (libdispatch.so + 0x3e9b8)
#2 0x00007fc83bd40ab5 n/a (libdispatch.so + 0x35ab5)
#3 0x00007fc83bd40a0b n/a (libdispatch.so + 0x35a0b)
#4 0x00007fc83bd410b3 n/a (libdispatch.so + 0x360b3)
#5 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43776:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43777:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43773:
#0 0x00007fc836f0359f __poll (libc.so.6 + 0x10359f)
#1 0x00007fc83d1ebb8f n/a (libglib-2.0.so.0 + 0xb7b8f)
#2 0x00007fc83d18e01f g_main_loop_run (libglib-2.0.so.0 + 0x5a01f)
#3 0x00007fc83d3f045c n/a (libgio-2.0.so.0 + 0x11045c)
#4 0x00007fc83d1c0cd5 n/a (libglib-2.0.so.0 + 0x8ccd5)
#5 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)

Stack trace of thread 43779:
#0 0x00007fc836e894ae n/a (libc.so.6 + 0x894ae)
#1 0x00007fc836e9476b n/a (libc.so.6 + 0x9476b)
#2 0x00007fc83bd4299f n/a (libdispatch.so + 0x3799f)
#3 0x00007fc83bd41387 n/a (libdispatch.so + 0x36387)
#4 0x00007fc836e8c9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007fc836f10dfc n/a (libc.so.6 + 0x110dfc)
ELF object binary architecture: AMD x86-64

GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/telegram-desktop...
(No debugging symbols found in /usr/bin/telegram-desktop)

warning: Can't open file /memfd:/.nvidia_drv.XXXXXX (deleted) during file-backed mapping note processing

warning: Can't open file /usr/lib/libnghttp2.so.14.24.3 during file-backed mapping note processing

warning: core file may not match specified executable file.
[New LWP 43762]
[New LWP 43768]
[New LWP 43774]
[New LWP 43764]
[New LWP 43770]
[New LWP 43766]
[New LWP 43778]
[New LWP 43793]
[New LWP 43771]
[New LWP 43772]
[New LWP 43775]
[New LWP 43776]
--Type <RET> for more, q to quit, c to continue without paging--c
[New LWP 43777]
[New LWP 43773]
[New LWP 43779]
Core was generated by `/usr/bin/telegram-desktop --'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc837660ee1 in ?? ()
[Current thread is 1 (LWP 43762)]
(gdb) bt
#0 0x00007fc837660ee1 in ?? ()
#1 0x00007ffdcd0a9e08 in ?? ()
#2 0xe8fa1b32b752a600 in ?? ()
#3 0x00007fc8274cbe30 in ?? ()
#4 0x00007fc826d1e498 in ?? ()
#5 0x00007fc8274cbfe0 in ?? ()
#6 0x00007fc837619fe7 in ?? ()
#7 0x0000000000000000 in ?? ()
(gdb) bt full
#0 0x00007fc837660ee1 in ?? ()
No symbol table info available.
#1 0x00007ffdcd0a9e08 in ?? ()
No symbol table info available.
#2 0xe8fa1b32b752a600 in ?? ()
No symbol table info available.
#3 0x00007fc8274cbe30 in ?? ()
No symbol table info available.
#4 0x00007fc826d1e498 in ?? ()
No symbol table info available.
#5 0x00007fc8274cbfe0 in ?? ()
No symbol table info available.
#6 0x00007fc837619fe7 in ?? ()
No symbol table info available.
#7 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb) pwd
Working directory /home/admin.
(gdb) thread apply all bt
Comment by Toolybird (Toolybird) - Wednesday, 06 September 2023, 04:29 GMT
Still no debugging information. Please review [1] and ensure the env var DEBUGINFOD_URLS is set correctly.

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod
Comment by Toolybird (Toolybird) - Wednesday, 06 September 2023, 04:33 GMT
PS: telegram-desktop 4.9.5-1 is now in the repos. Could you please update to that version and see if the crashes still happen?
Comment by Mr.Smith1974 (Mr.Smith1974) - Wednesday, 06 September 2023, 04:36 GMT
@Toolybird
I've had this crash consistently in Archlinux for the past 3-5 years.
I'm sure nothing has changed with the new version.
Comment by Toolybird (Toolybird) - Wednesday, 06 September 2023, 04:41 GMT
> I've had this crash consistently in Archlinux for the past 3-5 years.

Well if that's the case, I'm sorry but we cannot help you here. You'll need to take it to the proper Arch support channels (Forum/IRC/Mailing Lists/Reddit/etc) to see if anyone can assist troubleshoot what is wrong with your system...or you can always try reporting it upstream.

Loading...