Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME
Hello, Am Fri, Dec 11, 2020 at 10:48:42PM +0100 schrieb Matteo F. Vescovi: > Hi again! > > On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote: > > I daresay the bug you reported relates to screensaver integration that > > revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does > > not work for you, it could be something else. Can you please describe > > the crash more comprehensive and attach logs and terminal output of > > telegram-desktop to identify the issue? > > > > [1]: https://bugs.debian.org/976894 > > Actually, installing the qtwayland5 package (as stated in #976894) and > setting the reported variable did the trick. > > I've just set severity and merging accordingly. from a user point of view the behavior the package isn't working, or in other words, the package isn't usable that makes this issue grave by definition of severities. In my eyes it's not useful to keep this broken package in testing because using an uncomfortable work around make the binary "work". Doing so makes the usage of severities quite obsolete. For me it doesn't look like the binary is segfaulting, at least there is no message about that. This happen even if I update to the most recent version of telegram-desktop from unstable (2.2.0+ds-4+b1) which pulls in some newer rdeps due the QT updates some days ago. > carsten@i5:~ $ telegram-desktop > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > error: : cannot open > error: : cannot open > error: : cannot open > qt.svg: Error while inflating gzip file: SVG format check failed > qt.svg: Error while inflating gzip file: SVG format check failed > The X11 connection broke (error 2). Did the X11 server die? > carsten@i5:~ $ A doable compromise could be to extend the Exec entries in the desktop file. It should not harm non Gnome + Wayland users. https://github.com/telegramdesktop/tdesktop/issues/8506#issuecomment-683176286 So I hereby suggest to set the severity back to grave and add a tag help if needed, that would be a clear statement that the package has a problem. The world isn't going down if the package is kicked out of testing. If a newer upstream version is fixing the whole problem than the package should get an update in Debian too. Regards Carsten
Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME
Hi again! On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote: > I daresay the bug you reported relates to screensaver integration that > revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does > not work for you, it could be something else. Can you please describe > the crash more comprehensive and attach logs and terminal output of > telegram-desktop to identify the issue? > > [1]: https://bugs.debian.org/976894 Actually, installing the qtwayland5 package (as stated in #976894) and setting the reported variable did the trick. I've just set severity and merging accordingly. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A signature.asc Description: PGP signature
Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME
Hi Nicholas! Sorry for the late reply. On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote: > I daresay the bug you reported relates to screensaver integration that > revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does > not work for you, it could be something else. Can you please describe > the crash more comprehensive and attach logs and terminal output of > telegram-desktop to identify the issue? > > [1]: https://bugs.debian.org/976894 My first test is about launching simply telegram-desktop on a terminal; this is what I get: = = = = = >8 = = = = = $ telegram-desktop Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. error: : cannot open error: : cannot open error: : cannot open The X11 connection broke (error 2). Did the X11 server die? Segmentation fault (core dumped) = = = = = >8 = = = = = If I try to export the variable you referred in your reply, I get: = = = = = >8 = = = = = $ QT_QPA_PLATFORM=wayland telegram-desktop Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) = = = = = >8 = = = = = Feel free to ping me to gather more information about this behavior while running on Wayland. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A signature.asc Description: PGP signature
Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME
severity important merge 976982 976894 stop I daresay the bug you reported relates to screensaver integration that revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does not work for you, it could be something else. Can you please describe the crash more comprehensive and attach logs and terminal output of telegram-desktop to identify the issue? [1]: https://bugs.debian.org/976894 signature.asc Description: This is a digitally signed message part
Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME
Package: telegram-desktop Version: 2.2.0+ds-4 Severity: grave Justification: renders package unusable Dear Maintainer, since last update (-4 revision), the package fails to start on Wayland GNOME. However, the package works as expected while on Xorg GNOME. The fix to #975992 seems to be reason of the problem, or maybe related somehow. Cheers. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libavcodec58 7:4.3.1-5 ii libavformat58 7:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc6 2.31-5 ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1 ii libgcc-s1 10.2.1-1 ii libgdk-pixbuf-2.0-0 2.40.0+dfsg-10 ii libglib2.0-0 2.66.3-2 ii libgtk-3-03.24.23-3 ii libhunspell-1.7-0 1.7.0-3 ii liblz4-1 1.9.2-2 ii liblzma5 5.2.4-1+b1 ii libminizip1 1.1-8+b1 ii libopenal11:1.19.1-2 ii libopus0 1.3.1-0.1 ii libqrcodegencpp1 1.5.0-2 ii libqt5core5a [qtbase-abi-5-15-1] 5.15.1+dfsg-4 ii libqt5dbus5 5.15.1+dfsg-4 ii libqt5gui55.15.1+dfsg-4 ii libqt5network55.15.1+dfsg-4 ii libqt5waylandclient5 [qtwayland-client-abi-5-15- 5.15.1-3 ii libqt5widgets55.15.1+dfsg-4 ii librlottie0-1 0.1+dfsg-1 ii libssl1.1 1.1.1i-1 ii libstdc++610.2.1-1 ii libswresample37:4.3.1-5 ii libswscale5 7:4.3.1-5 ii libx11-6 2:1.6.12-1 ii libxcb-screensaver0 1.14-2 ii libxcb1 1.14-2 ii libxxhash00.8.0-1 ii qt5-image-formats-plugins 5.15.1-2 ii zlib1g1:1.2.11.dfsg-2 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-1 telegram-desktop suggests no packages. -- no debconf information signature.asc Description: PGP signature
