FS#63102 - [telegram-desktop] Crash at login

Attached to Project: Community Packages
Opened by Mosè Giordano (giordano) - Thursday, 04 July 2019, 22:28 GMT
Last edited by Jiachen Yang (farseerfc) - Wednesday, 10 July 2019, 04:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jiachen Yang (farseerfc)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

telegram-desktop crashes after login. This is exactly the same as https://bugs.archlinux.org/task/62953, but I've installed telegram-desktop 1.7.10-6:

% telegram-desktop
QApplication: invalid style override passed, ignoring it.
Available styles: Breeze, Oxygen, Windows, Fusion
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = telegram-desktop path = /usr/bin pid = 9683
KCrash: Arguments: /usr/bin/telegram-desktop
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
zsh: suspended (signal) telegram-desktop

% pacman -Ss telegram-desktop
community/telegram-desktop 1.7.10-6 [installed]
Official Telegram Desktop client

Steps to reproduce: Start Telegram Desktop, crashes when it tries to login (i.e., no crash if there is no Internet connection).
This task depends upon

Closed by  Jiachen Yang (farseerfc)
Wednesday, 10 July 2019, 04:04 GMT
Reason for closing:  Works for me
Additional comments about closing:  Reporter says it is working now.
Comment by Jiachen Yang (farseerfc) - Tuesday, 09 July 2019, 02:01 GMT
Can you please get a backtrace from the crash? You can usually get it from `coredumpctl debug` command.
Also does the crash happens on newer versions of telegram-desktop?
The 1.7.10-6 release was built against qt5 5.13 which was in testing at the releasing time, so if it is mixed with stable qt5 5.12.x the crash would happen.
For stable(core/extra/community) repos 1.7.10-5 was the right one to use.
Comment by Mosè Giordano (giordano) - Tuesday, 09 July 2019, 23:12 GMT
I just tried again and now it works, without having upgraded any package since I opened the ticket. No idea of what might have changed. Thanks anyway!
Comment by Jiachen Yang (farseerfc) - Wednesday, 10 July 2019, 04:03 GMT
Great that it is working now. Will close this bug for now. If it crashes on newer versions please open a new bug.

Loading...