Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-11 Thread Matteo F. Vescovi
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

Processed (with 2 errors): Re: Processed (with 2 errors): Re: Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 976982 976894 Severity level `976894' is not known. Recognized are: critical, grave, serious, important, normal, minor, wishlist, fixed. > forwarded 976982 https://github.com/telegramdesktop/tdesktop/issues/8506 Bug #976982

Processed (with 2 errors): Re: Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity important Unknown command or malformed arguments to command. > merge 976982 976894 Bug #976982 [telegram-desktop] telegram-desktop: Segmentation fault at start on Wayland GNOME Unable to merge bugs because: forwarded of #976894 is

Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-09 Thread Nicholas Guriev
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

Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-09 Thread Matteo F. Vescovi
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