[ISSUE] telegram-desktop crashes on Sway Wayland

[ISSUE] telegram-desktop crashes on Sway Wayland

[shnaps]

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

New issue by shnaps on void-packages repository

https://github.com/void-linux/void-packages/issues/51180

Description:
### Is this a new report?

Yes

### System Info

Void 6.9.8_1 x86_64 GenuineIntel uptodate rrmFFFFFFFFFFFF

### Package(s) Affected

telegram-desktop-5.1.7_2 

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Telegram doesn't crash time from time

### Actual behaviour

Telegram crashes for no reason. It takes somewhere from 2 to 10 minutes to reproduce it. 

>telegram-desktop
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.svg: Error while inflating gzip file: SVG format check failed
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
[libvpx-vp9 @ 0x7fdfa02e7800] v1.13.1
[libvpx-vp9 @ 0x7fdfa02e7800] v1.13.1
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
[libvpx-vp9 @ 0x7fdfa02e8200] v1.13.1
[libvpx-vp9 @ 0x7fdfa02e8200] v1.13.1
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
  OpenType support missing for "Open Sans", script 11
  OpenType support missing for "vazirmatn ui nl", script 11
xdg_surface@118: error 1: xdg_popup has no parent
The Wayland connection experienced a fatal error: Protocol error

### Steps to reproduce

1. Open telegram-desktop
2. Browse some channel
3. Telegram will crash in 2-10 minutes

Re: telegram-desktop crashes on Sway Wayland

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 226 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/51180#issuecomment-2218694482

Comment:
does `xbps-pkgdb -a` show any errors? if so `xbps-install -f` those packages 

Re: telegram-desktop crashes on Sway Wayland

[shnaps]

[-- Attachment #1: Type: text/plain, Size: 317 bytes --]

New comment by shnaps on void-packages repository

https://github.com/void-linux/void-packages/issues/51180#issuecomment-2218749049

Comment:
> does `xbps-pkgdb -a` show any errors? if so `xbps-install -f` those packages

Nope, nothing related. Missing config in cups-browsed and some symlink troubles with neovim.

Re: telegram-desktop crashes on Sway Wayland

[pedrocorral]

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

New comment by pedrocorral on void-packages repository

https://github.com/void-linux/void-packages/issues/51180#issuecomment-2226991113

Comment:
Same problem here with Telegram on Debian (no special configuration at all, just out-of-the-box installation).

@classabbyamp, if you want a channel that systematically breaks down the App this is: "Tech & Leaks Zone". They have posted something recently that I cannot see at all. The rest of the channels do not break it.

I hope that helps. Best regards.