tdesktop
tdesktop copied to clipboard
Published
20 hours ago •
telegramdesktop
telegramdesktop
"Segmentation fault (core dumped)" after auto update to 4.2 (Ubuntu 22.04)
Steps to reproduce
- Press update button on the bottom of the Telegram Desktop window and let it upgrade
Expected behaviour
Telegram window disappear, update then updated Telegram is ready to use. This happened always before this upgrade.
Actual behaviour
Telegram window disappeared and nothing visible happened after that. I started the binary from terminal same way as my Ubuntu Cinnamon shortcut does and I got a "Segmentation fault (core dumped)" message. Nothing more. I still have the older version so I rolled it back but it updated again and I experienced exactly the same. I deleted the data directory as well but still just a seg.fault what I see.
Operating system
Ubuntu 22.04.1 LTS
Version of Telegram Desktop
4.1.1. upgrade to 4.2
Installation source
Static binary from official website
Logs
gabor@gabor1:~/.local/share/TelegramDesktop$ /home/gabor/Apps/Telegram/Telegram -workdir /home/gabor/.local/share/TelegramDesktop/ -- %u
Segmentation fault (core dumped)
gabor@gabor1:~/.local/share/TelegramDesktop$ cat log.txt
[2022.09.17 10:15:38] Launched version: 4002000, install beta: [FALSE], alpha: 0, debug mode: [FALSE]
[2022.09.17 10:15:38] Executable dir: /home/gabor/Apps/Telegram/, name: Telegram
[2022.09.17 10:15:38] Initial working dir: /home/gabor/.local/share/TelegramDesktop/
[2022.09.17 10:15:38] Working dir: /home/gabor/.local/share/TelegramDesktop/
[2022.09.17 10:15:38] Command line: /home/gabor/Apps/Telegram/Telegram -workdir /home/gabor/.local/share/TelegramDesktop/ -- %u
[2022.09.17 10:15:38] Executable path before check: /home/gabor/Apps/Telegram/Telegram
[2022.09.17 10:15:38] Logs started
[2022.09.17 10:15:38] Launcher filename: appimagekit_b8d9d2bc489a088316200b71357b30ad-Telegram_Desktop.desktop
[2022.09.17 10:15:38] Connecting local socket to /run/user/1000/7248a889dc1588d8bcea096c02eecdd0-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2022.09.17 10:15:38] Socket connect error 0, starting server and app...
[2022.09.17 10:15:38] Moved logging from '/home/gabor/.local/share/TelegramDesktop/log_start0.txt' to '/home/gabor/.local/share/TelegramDesktop/log.txt'!
[2022.09.17 10:15:38] Opened '/home/gabor/.local/share/TelegramDesktop/tdata/working' for reading, the previous Telegram Desktop launch was not finished properly :( Crash log size: 393
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansRegular.ttf' loaded 'DAOpenSansRegular'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansRegularItalic.ttf' loaded 'DAOpenSansRegularItalic'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.09.17 10:15:38] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.17 10:15:38] Update Info: MTP is unavailable.
[2022.09.17 10:15:39] App Error: _basePath is empty in writeSettings()
[2022.09.17 10:15:39] Primary screen DPI: 96
[2022.09.17 10:15:39] System tray available: [TRUE]
[2022.09.17 10:15:39] Icon theme: gnome
[2022.09.17 10:15:39] Fallback icon theme:
[2022.09.17 10:15:39] App Info: reading settings...
[2022.09.17 10:15:39] App Info: reading encrypted settings...
[2022.09.17 10:15:39] Lang Info: Loaded cached, keys: 4219
This might help you.
gabor@gabor1:~/Apps/Telegram$ gdb Telegram
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 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-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 Telegram...
(No debugging symbols found in Telegram)
(gdb) run
Starting program: /home/gabor/Apps/Telegram/Telegram
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff67ff640 (LWP 304501)]
[New Thread 0x7ffff57b8640 (LWP 304502)]
[New Thread 0x7ffff49ff640 (LWP 304503)]
[New Thread 0x7ffff0aa2640 (LWP 304504)]
[New Thread 0x7fffefdff640 (LWP 304505)]
[New Thread 0x7fffef5fe640 (LWP 304506)]
[New Thread 0x7fffee7ff640 (LWP 304507)]
[New Thread 0x7fffedcfe640 (LWP 304508)]
[New Thread 0x7fffecfff640 (LWP 304510)]
[New Thread 0x7fffec1ff640 (LWP 304511)]
[New Thread 0x7fffeb3ff640 (LWP 304512)]
[Detaching after vfork from child process 304513]
Thread 1 "Telegram" received signal SIGSEGV, Segmentation fault.
clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:87
87 ../sysdeps/unix/sysv/linux/x86_64/clone.S: No such file or directory.
(gdb)
Yes, I have. You can access it here: https://www.halacs.hu/tdump.dmp I will delete after you downloaded. Thanks!
It's a bad idea to do, it may be accessed by multiple people. You can zip the dump and post it on github.
You mean bad idea to delete or to publish? Am I right there is no any sensitive data in it?
@halacs So, this happens each time you launch a new binary? Can you unpack the new binary to a separate folder, like:
~/TempTest
So you have binaries ~/TempTest/Telegram and ~/TempTest/Updater and then create a folder:
~/TempTest/TelegramForcePortable
And try to launch the binary. Will it start or will it crash the same way?
It seems Qt has a new implementation of starting child processes and this implementation triggers some bug in his system's libc and causes a crash. Apparently, the only thing that could be done is reporting this to Qt, but this should be reproducible and the fact there's only one such report makes me guessing it's not reproducible on other Ubuntu 22.04 installations what makes the situation stuck. The only thing I can suggest is to try to update the system if there are any updates. A full system reinstallation may also help in case there's any kind of mix of libraries from different system versions (due to any third-paty repositories and system upgrades).
I tried it, no luck. There is no available update with apt.
https://www.halacs.hu/c4fb4824-c963-4b14-07263887-87c975aa.dmp
gabor@gabor1:/tmp/TelegramTest$ ll
total 43M
drwxrwxr-x 2 gabor gabor 4.0K szept 16 23:37 Telegram/
-rw-rw-r-- 1 gabor gabor 43M szept 19 08:21 tsetup.4.2.0.tar.xz
gabor@gabor1:/tmp/TelegramTest$ cd Telegram/
gabor@gabor1:/tmp/TelegramTest/Telegram$ ll
total 129M
-rwxr-xr-x 1 gabor gabor 122M szept 16 23:36 Telegram*
-rwxr-xr-x 1 gabor gabor 6.5M szept 16 23:33 Updater*
gabor@gabor1:/tmp/TelegramTest/Telegram$ mkdir TelegramForcePortable
gabor@gabor1:/tmp/TelegramTest/Telegram$ ./Telegram
Segmentation fault (core dumped)
gabor@gabor1:/tmp/TelegramTest/Telegram$ cat TelegramForcePortable/log.txt
[2022.09.19 08:22:17] Launched version: 4002000, install beta: [FALSE], alpha: 0, debug mode: [FALSE]
[2022.09.19 08:22:17] Executable dir: /tmp/TelegramTest/Telegram/, name: Telegram
[2022.09.19 08:22:17] Initial working dir: /tmp/TelegramTest/Telegram/TelegramForcePortable/
[2022.09.19 08:22:17] Working dir: /tmp/TelegramTest/Telegram/TelegramForcePortable/
[2022.09.19 08:22:17] Command line: ./Telegram
[2022.09.19 08:22:17] Executable path before check: /tmp/TelegramTest/Telegram/Telegram
[2022.09.19 08:22:17] Logs started
[2022.09.19 08:22:17] Launcher filename: appimagekit_01eaa4b5dd2577c4102e9d913ef084d9-Telegram_Desktop.desktop
[2022.09.19 08:22:17] Connecting local socket to /run/user/1000/cf1972e43f91f74985f449d359600cc5-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2022.09.19 08:22:17] This is the only instance of Telegram, starting server and app...
[2022.09.19 08:22:17] Moved logging from '/tmp/TelegramTest/Telegram/TelegramForcePortable/log_start0.txt' to '/tmp/TelegramTest/Telegram/TelegramForcePortable/log.txt'!
[2022.09.19 08:22:17] Primary screen DPI: 96
[2022.09.19 08:22:17] System tray available: [TRUE]
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansRegular.ttf' loaded 'DAOpenSansRegular'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansRegularItalic.ttf' loaded 'DAOpenSansRegularItalic'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.09.19 08:22:17] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.09.19 08:22:17] Icon theme: gnome
[2022.09.19 08:22:17] Fallback icon theme:
gabor@gabor1:/tmp/TelegramTest/Telegram$ ll TelegramForcePortable/tdata/dumps/
total 284K
-rw------- 1 gabor gabor 281K szept 19 08:22 c4fb4824-c963-4b14-07263887-87c975aa.dmp
gabor@gabor1:/tmp/TelegramTest/Telegram$ sudo bash -c "apt update && apt upgrade -y && apt dist-upgrade -y && apt autoremove -y --purge"
[sudo] password for gabor:
Hit:1 http://hu.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://hu.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Get:3 http://hu.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Hit:4 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu jammy InRelease
Hit:5 http://repository.spotify.com stable InRelease
Hit:6 https://repo.steampowered.com/steam stable InRelease
Hit:7 https://linux.teamviewer.com/deb stable InRelease
Get:8 https://download.opensuse.org/repositories/home:/npreining:/debian-ubuntu-onedrive/xUbuntu_22.04 ./ InRelease [1,604 B]
Hit:9 https://apt.halacs.hu/apt halacs InRelease
Hit:10 http://ppa.launchpad.net/phoerious/keepassxc/ubuntu jammy InRelease
Hit:11 http://apt.syncthing.net syncthing InRelease
Get:12 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease
Hit:14 http://ppa.launchpad.net/qbittorrent-team/qbittorrent-stable/ubuntu jammy InRelease
Get:15 http://hu.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [92.8 kB]
Get:16 http://hu.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [240 kB]
Get:17 http://hu.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:18 http://hu.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [12.3 kB]
Get:19 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [13.1 kB]
Get:20 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [12.1 kB]
Fetched 697 kB in 5s (135 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
One more thing might help, regarding the libraries:
gabor@gabor1:~/Apps/Telegram$ ldd Telegram
linux-vdso.so.1 (0x00007ffcb7771000)
libesets_pac.so => /lib/x86_64-linux-gnu/libesets_pac.so (0x00007f958c500000)
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f958c328000)
libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f958c2c8000)
libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f958c27e000)
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f958c1b6000)
libEGL.so.1 => /lib/x86_64-linux-gnu/libEGL.so.1 (0x00007f958c66f000)
libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007f958c12f000)
libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f958c105000)
libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007f958bfc5000)
libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f958c66a000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f958be8b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f958c663000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f958bda4000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f958c65e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f958bb7c000)
/lib64/ld-linux-x86-64.so.2 (0x00007f958c6a2000)
libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f958bb75000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f958bb59000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007f958bb15000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f958bae9000)
libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x00007f958badc000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f958baab000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f958baa2000)
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f958ba67000)
libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007f958ba59000)
libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007f958b9a1000)
libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007f958b96d000)
libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007f958b967000)
libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f958b95f000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f958b8e7000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f958b8b0000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f958b819000)
libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007f958b7f6000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f958b7de000)
libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007f958b7d1000)
It might be part of ESET NOD32 Antivirus. It's not a new thing.
gabor@gabor1:~/Apps/Telegram$ cat /etc/ld.so.preload
libesets_pac.so
It takes participation in the crash trace, can you try to comment it out?
Same Telegram binary can run in a VM. I just tested it.
gabor@focal-autoinstall:/tmp/TelegramTest/Telegram$ ldd Telegram
linux-vdso.so.1 (0x00007ffe47964000)
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007fe8b6166000)
libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fe8b6106000)
libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fe8b60bc000)
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fe8b5ff4000)
libEGL.so.1 => /lib/x86_64-linux-gnu/libEGL.so.1 (0x00007fe8b5fe1000)
libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007fe8b5f58000)
libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fe8b5f2e000)
libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007fe8b5dee000)
libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007fe8b5de9000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fe8b5caf000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe8b5caa000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe8b5bc1000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe8b5bbc000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe8b5994000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe8b6353000)
libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007fe8b598d000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fe8b5971000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007fe8b592d000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fe8b58ff000)
libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x00007fe8b58f2000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fe8b58c1000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fe8b58b8000)
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007fe8b587d000)
libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007fe8b586f000)
libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007fe8b57b5000)
libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007fe8b5781000)
libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007fe8b577b000)
libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fe8b5773000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fe8b56fd000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007fe8b56c4000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007fe8b562d000)
libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007fe8b560a000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007fe8b55f2000)
libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007fe8b55e5000)
gabor@focal-autoinstall:/tmp/TelegramTest/Telegram$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
gabor@focal-autoinstall:/tmp/TelegramTest/Telegram$ ll
total 131224
drwxrwxr-x 3 gabor gabor 4096 Sep 19 09:19 ./
drwxrwxr-x 3 gabor gabor 4096 Sep 19 09:19 ../
-rwxr-xr-x 1 gabor gabor 127625584 Sep 19 09:19 Telegram*
drwx------ 3 gabor gabor 4096 Sep 19 09:19 TelegramForcePortable/
-rwxr-xr-x 1 gabor gabor 6727560 Sep 19 09:19 Updater*
It takes participation in the crash trace, can you try to comment it out?
Yes. I guess a system reboot is needed to apply the change. Am I right?
The change should effect immediately, but it's better to reboot so the library is not loaded in any process
I commented that line out with no system restart and it helped. Now Telegram Desktop 4.2 is running on my system.
Do you understand why this helped?
So far as I can see, this step disabled a pre-loading of a dynamic library of ESET NOD32 Antivirus. I guess this is somewhat disabled live antivirus protection but I'm not sure.
gabor@gabor1:~$ cat /etc/ld.so.preload
#libesets_pac.so
Do you understand why this helped?
It seems your antivirus breaks Qt's vforkfd code to spawn new processes
Hmm. Interesting. Can you please report it to Qt's developers? Is it worth to do so?
If I remember correctly ESSET announced end of life their NOD32 Antivirus for Linux in the next months. Bad thing is I have still no good replacement candidate.
Can you please report it to Qt's developers?
I'm not sure when I would do that if will at all. I don't really want to install NOD32.
Just to be clear, they did announce a replacement product with the discontinuation: ESET Endpoint Antivirus for Linux. I haven't switched because my particular license doesn't seem to transfer, but it may behave differently. I'd appreciate knowing if it resolves this issue if your license can indeed transfer.
@Sanaki My university student license is not good for it so far if I'm right, but let's see. I will ping you if I have any news regarding that.
@ilya-fedin thanks for your help!