It segfaults immediately after logging into an account. The welcome screen, that appears when no account is logged in, displays and works just fine, just like the settings panel. Dmesg currently gives the following related info: [ 6125.983559] Thread (pooled)[15754]: segfault at 7ff338c361f8 ip 00007ff3413c780b sp 00007ff338c361f8 error 6 in libQt6Gui.so.6.8.1[7a580b,7ff340e56000+595000] [ 6125.983565] Thread (pooled)[15761]: segfault at 7ff325c881f8 ip 00007ff3413c780b sp 00007ff325c881f8 error 6 [ 6125.983566] Thread (pooled)[15760]: segfault at 7ff329a0e1f8 ip 00007ff3413c780b sp 00007ff329a0e1f8 error 6 [ 6125.983568] likely on CPU 15 (core 7, socket 0) [ 6125.983568] in libQt6Gui.so.6.8.1[7a580b,7ff340e56000+595000] likely on CPU 12 (core 4, socket 0) [ 6125.983572] in libQt6Gui.so.6.8.1[7a580b,7ff340e56000+595000] [ 6125.983573] Code: 0a 01 00 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 49 89 e3 49 81 eb 00 90 01 00 48 81 ec 00 10 00 00 <48> c7 04 24 00 00 00 00 4c 39 dc 75 ec 48 81 ec a8 00 00 00 48 89 [ 6125.983573] Code: 0a 01 00 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 49 89 e3 49 81 eb 00 90 01 00 48 81 ec 00 10 00 00 <48> c7 04 24 00 00 00 00 4c 39 dc 75 ec 48 81 ec a8 00 00 00 48 89 [ 6125.983577] likely on CPU 3 (core 3, socket 0) [ 6125.983581] Code: 0a 01 00 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 49 89 e3 49 81 eb 00 90 01 00 48 81 ec 00 10 00 00 <48> c7 04 24 00 00 00 00 4c 39 dc 75 ec 48 81 ec a8 00 00 00 48 89 Reproducible: Always Steps to Reproduce: 1. Compile telegram-desktop with the ~amd64 keyword and the qt6 USE flag enabled 2. Run telegram-desktop 3. Try to login into your account. Actual Results: I go back to my desktop immediately. Expected Results: Interact with all the highly educated and civilized folk in Telegram, exchanging high quality footage of relevant events and relevant and useful information within public interest. It shouldn't have crashed.
Created attachment 915553 [details] emerge --info
Created attachment 915561 [details] lldb backtrace I haven't really compiled telegram-desktop with debug C*FLAGS, but I believe this can be useful.
I managed to copy Telegram data from my previous install, thus importing active sessions and eliminating the need to sign in. Most features work. It only segfaults when I scroll down the channels list.
Thanks for reporting! I don't think what you posted is a backtrace, and if it is, I cannot interpret it. Can you use GDB and use the "bt" (backtrace) command after it crashes? Also your emerge --info output is lacking the USE and C*FLAGS that telegram-desktop was built with. Make sure to run "emerge --info net-im/telegram-desktop". Info about how tg_owt and any other libraries involved in the crash like Qt6 were built would be useful too. I cannot reproduce this (I've been using USE=qt6 with this package for a while), so I can only assume it's a clang/musl issue. This combination is tested by very few people so things like this can happen. I'd recommend trying to rebuild both tg_owt and telegram-desktop to make sure nothing is lacking a rebuild. If that doesn't work, try with GCC, or an empty CFLAGS, or enable debug info while at it and generate a full backtrace.
