FS#67725 - [telegram-desktop] v2.3.2 crashes with cordump on startup

Attached to Project: Community Packages
Opened by Gunnar Bretthauer (Taijian) - Wednesday, 26 August 2020, 10:43 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 02 September 2020, 16:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

Trying to start telegram-desktop v2.3.2 I get an immediate coredump.

Additional info:
* package version(s): 2.3.2-1
* Core dump here: https://gist.github.com/Taijian/45beb7adb28ceed834725bfa9cba075a

Steps to reproduce:

Start telegram-desktop
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 02 September 2020, 16:32 GMT
Reason for closing:  Fixed
Comment by crashbit (crashbit) - Wednesday, 26 August 2020, 14:07 GMT
Same problem here.

I'm using nouveau with xwayland and gnome-shell

crashbit@gt62vr-6re ~]$ telegram-desktop

(process:4054): Telegram-WARNING **: 16:07:01.475: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
Telegram-Message: 16:07:01.477: This can be ignored by setting TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
Telegram-Message: 16:07:01.477: GTK integration can be disabled by setting TDESKTOP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to clipboard issues and tdesktop will be unable to get settings from GTK (such as decoration layout, dark mode & more).

(process:4054): Telegram-WARNING **: 16:07:01.477: Application was built without embedded fonts, this may lead to font issues.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Telegram-Message: 16:07:01.605: You can disable tray icon counter with TDESKTOP_DISABLE_TRAY_COUNTER and make it look better if it is monochrome.
error: : cannot open
error: : cannot open
error: : cannot open
qt.qpa.xcb: xcb_shm_create_segment() failed for size 3346112
The X11 connection broke (error 2). Did the X11 server die?
Violació de segment (s'ha bolcat la memòria)
Comment by somody (somody) - Wednesday, 26 August 2020, 14:55 GMT
Same problem.

These are my relevant .bashrc lines:
export QT_QPA_PLATFORM=wayland-egl
export QT_WAYLAND_FORCE_DPI=physical
export QT_STYLE_OVERRIDE=gtk2
export WAYLAND_DISPLAY=wayland-0
Comment by Svyatoslav Gryaznov (nightuser) - Wednesday, 26 August 2020, 19:30 GMT
It broke for me on Gnome (Wayland session, works on X11) after updating `xorg-server-wayland` to 1.20.9-1. If I downgrade to 1.20.8-3 then it works.

somody: Telegram runs on X11 and ignores QT_QPA_PLATFORM unless you specify TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY (you can actually see the information about this variable in the crashbit's message above).
Comment by Nick Novikov (novns) - Thursday, 27 August 2020, 03:51 GMT
I confirm. Telegram runs with Gnome X session, and fails with Wayland session.

The problem arrived after after today update of xorg-server-* packages.

It starts normally when I clean `~/.local/share/TelegramDesktop`, but fails again after the successful login process.

The only error messages are three "error: : cannot open"
Comment by Nick Novikov (novns) - Thursday, 27 August 2020, 04:08 GMT Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 27 August 2020, 04:12 GMT
So hang on, I'm a little confused. We know that 2.3.2 always works on X11 and always fails on Wayland and it appears to be a problem of xorg-server-wayland?

Does any combination of compile flags or env vars make it work for any of you guys on Wayland?
Comment by Nick Novikov (novns) - Thursday, 27 August 2020, 12:26 GMT
Svenstaro, It works with environment variables QT_QPA_PLATFORM=wayland and XCURSOR_SIZE=24
Comment by Vitali Malyshkin (vitalyam13gmail.com) - Thursday, 27 August 2020, 17:55 GMT
I confirm a bug. Also on telegram 2.3 I have a bug with cracking sound on all system when the call starts. Does anyone have the same?
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 28 August 2020, 02:08 GMT
Let's not conflate bugs, please! Make a new bug in our tracker in case you have reasonable cause to assume this new bug to be a packaging issue.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 28 August 2020, 02:10 GMT
For the actual issue: This also seems like an upstream bug to me as I don't see any reasonable option for us to set. We could do some downstream patching but it seems to me we should rather make sure this is properly handled upstream.
Comment by freswa (frederik) - Friday, 28 August 2020, 02:19 GMT
This is the corresponding upstream bug:
https://github.com/telegramdesktop/tdesktop/issues/8506
Comment by freswa (frederik) - Friday, 28 August 2020, 02:25 GMT
And this is the bug report for the xserver:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1072
Comment by Kasei Wang (kasei) - Friday, 28 August 2020, 02:48 GMT
Same issue here. I revert https://github.com/freedesktop/xorg-xserver/commit/5c20e4b834145f590c68dbc98e33c7d3d710001a and telegram works again.
The "QT_QPA_PLATFORM=wayland" workaround only works with "Client-Side Decorations Initiative"(Turn off Telgram setting->Advanced->System integration->Use system window frame).
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 28 August 2020, 03:13 GMT
I think we're going to wait this one out and see which upstream wants to fix this.
Comment by Jean-Louis Dupond (dupondje) - Sunday, 30 August 2020, 17:50 GMT Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 02 September 2020, 15:56 GMT
2.3.2-2 should be good, please test.
Comment by Nick Novikov (novns) - Wednesday, 02 September 2020, 16:06 GMT
2.3.2-2 works. The issue is fixed.

Thank you!

Loading...