Bug 1216256 - telegram-desktop crashes on start
Summary: telegram-desktop crashes on start
Status: RESOLVED DUPLICATE of bug 1216269
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Manfred Hollstein
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-16 07:07 UTC by Arnaud Mez
Modified: 2023-10-16 20:24 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud Mez 2023-10-16 07:07:47 UTC 
Installed telegram-desktop  from official repos and since update to 20231013 the app just crashes at launch.

Terminal output:
** (telegram-desktop:5654): WARNING **: 07:56:28.233: Unable to load patched fonts with Qt workarounds, expect font issues.
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
Segmentation fault (core dumped)

Details about my current session:
SESSION  UID USER        SEAT  TTY  STATE  IDLE SINCE
      2 1000 theunclemez seat0 tty2 active no
Type=wayland

Details about my config:
Static hostname: smartbox
       Icon name: computer-laptop
         Chassis: laptop 💻
Operating System: openSUSE Tumbleweed                
     CPE OS Name: cpe:/o:opensuse:tumbleweed:20231013
          Kernel: Linux 6.5.6-1-default
    Architecture: x86-64
 Hardware Vendor: ASUSTeK Computer Inc.
  Hardware Model: K52F
Firmware Version: K52F.218
   Firmware Date: Tue 2011-07-12
    Firmware Age: 12y 3month 4d
Comment 1 Dmitry Markov 2023-10-16 07:51:13 UTC 
4.10.3-2.2 from OSS repo & 4.10.3-236.2 from server:messaging repo
same problem

blob from github worked (temporary solution)
Comment 2 Andreas Stieger 2023-10-16 20:24:17 UTC 
dup

*** This bug has been marked as a duplicate of bug 1216269 ***