Summary: | net-im/telegram-desktop: error when starting in KDE Plasma "Launching Telegram Desktop (Failed)" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Hirte <johannes.hirte> |
Component: | Current packages | Assignee: | Esteve Varela Colominas <esteve.varela> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | dlan, esteve.varela, hugegameartgd, joe, kripton, lg3dx6fd, neb.semqen.ramesses, proxy-maint, sarnex, silvio.gerli |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Segmentation fault with -02 and -ggdb flags
disable-raster_fp.patch disable-raster_64bit.patch |
Description
Johannes Hirte
2023-11-14 17:05:41 UTC
Thanks for the report! Please include the version number in the bug report title. That said, if it can be reproduced with the binary, then it may be reported upstream as well. I have the same problem both with source and binary packages. Error was detected on versions 4.10.3 and 4.11.7. Versions 4.11.5 both binary and source are OK. I think it's worth reporting upstream, then. Telegram crashes on KDE Plasma 6 (Wayland session, Clang/musl) after user authorization, the setup wizard works fine for me. Reproducible with Gentoo ebuilds and overlays (e. g. https://gitlab.com/reagentoo/gentoo-overlay/-/blob/master/net-im/telegram-desktop/telegram-desktop-9999.ebuild) ~ $ gdb --args telegram-desktop [...] Thread 36 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to LWP 26778] 0x00007fffe8ddf0ab in ?? () from /lib/libQt6Gui.so.6 (gdb) Can you try the official binary? Created attachment 888013 [details]
Segmentation fault with -02 and -ggdb flags
> Can you try the official binary?
The official binary linked against glibc segfaults with gcompat (might be expected I think), previous telegram-desktop Gentoo ebuilds worked fine on musl libc.
(gdb) run
Starting program: /home/user/Telegram
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Program received signal SIGSEGV, Segmentation fault.
0x00007fffefa10df4 in memcpy () from /lib64/ld-linux-x86-64.so.2
(gdb) exit
Sorry, I missed your mention of musl. In that case I'll have to check it out myself. I can't promise that'll be soon. If you want to help out, please build the program and relevant libraries with debug symbols and use the "bt" command in gdb. Created attachment 888014 [details, diff]
disable-raster_fp.patch
Created attachment 888015 [details, diff]
disable-raster_64bit.patch
Might be a qt6 bug, telegram runs fine after patching qtbase-6.7, disabling raster_fp and raster_64bit. Hello. I've got it too after update . I'm on stable. It seems after update to Qt6, plasma6 and telegram-desktop[qt6] I've got it too. Same problem here. Very old problem. I've two PCs, one presents the problem (amd CPU) the other no (intel CPU) Using bin version seems to fix the issue. I figured out what was going on with my end. I don't know *how* this happened but it appears an old version of telegram dropped a launch shortcut in /home/joecool/.local/share/applications . This one would always launch telegram but it would crash soon after. The main /usr/share/applications one works just fine every time. Thanks for letting me know! That makes a lot of sense, as it could be due to telegram-bin, or a different binary build of telegram. It's really unpredictable when it does this, and I can imagine it being the cause of problems. Closing this ticket since it's really old. Please let me know if anything similar pops up. |