Telegram-desktop won't start after last Manjaro update

I don’t know, but it would help to know the system you are running it on.

Output of which command you would like to see?

inxi -Fxz would be a good start.

Output of sudo inxi -Fxz command:

System:
  Kernel: 5.15.71-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: GNOME v: 42.5 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook 15_ASUS Laptop X540UBR
    v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: X540UBR v: 1.0 serial: <filter>
    UEFI-[Legacy]: American Megatrends v: X540UBR.301 date: 08/13/2018
Battery:
  ID-1: BAT0 charge: 22.2 Wh (92.1%) condition: 24.1/33.3 Wh (72.3%)
    volts: 11.1 min: 11.1 model: ASUSTeK ASUS Battery status: discharging
CPU:
  Info: dual core model: Intel Core i3-7020U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 3 MiB
  Speed (MHz): avg: 700 min/max: 400/2300 cores: 1: 700 2: 700 3: 700
    4: 700 bogomips: 18406
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: NVIDIA GM108M [GeForce MX110] vendor: ASUSTeK driver: nvidia
    v: 515.76 arch: Maxwell bus-ID: 01:00.0
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:3
  Display: server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver: X:
    loaded: modesetting,nvidia gpu: i915 resolution: 1920x1080
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2F) v: 4.6 Mesa
    22.1.7 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.15.71-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    vendor: AzureWave driver: rtw_8821ce v: N/A port: d000 bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 1-8:4
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 931.51 GiB used: 239.91 GiB (25.8%)
  ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
Partition:
  ID-1: / size: 425.12 GiB used: 239.91 GiB (56.4%) fs: ext4 dev: /dev/sda6
Swap:
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sda7
Sensors:
  System Temperatures: cpu: 35.0 C pch: 31.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 1900
Info:
  Processes: 265 Uptime: 2h 34m Memory: 7.64 GiB used: 4.26 GiB (55.7%)
  Init: systemd Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1825
  Shell: Zsh v: 5.9 inxi: 3.3.21

It’s probably the particular Telegram package you are running. There is at least one that shortly after certain Plasma updates that will just not run. It gets fixed with in a couple of days but yes is annoying in the mean time. I typically just remove and install one of the other Telegram Packages and it’s fine again.

Same Issue here since the latest updates, which I ran the updates today. Telegram doesn’t open. When trying to launch from terminal I get:
zsh: segmentation fault (core dumped) telegram-desktop

I am also using Gnome DE.

Same thing for me, also with Gnome. Several people, including me, described the problem on the topic of 2022-10-05 stable update (no answer for now).

Output of inxi -Fxz:

System:
  Kernel: 5.15.71-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: GNOME v: 42.5 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Latitude 5490 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 08NJ82 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.8.2 date: 04/03/2019
Battery:
  ID-1: BAT0 charge: 21.2 Wh (33.5%) condition: 63.3/68.0 Wh (93.2%)
    volts: 7.3 min: 7.6 model: LGC-LGC8.820 DELL FPT1C95 status: discharging
CPU:
  Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 1706 high: 2092 min/max: 400/3400 cores: 1: 2000
    2: 2000 3: 2000 4: 1993 5: 700 6: 1001 7: 2092 8: 1866 bogomips: 28808
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: Realtek Integrated Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:2
  Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver:
    X: loaded: modesetting gpu: i915 resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa
    22.1.7 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Sound Server-1: ALSA v: k5.15.71-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
    bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 238.47 GiB used: 175.08 GiB (73.4%)
  ID-1: /dev/sda vendor: Micron model: 1100 SATA 256GB size: 238.47 GiB
Partition:
  ID-1: / size: 216.57 GiB used: 175.08 GiB (80.8%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 299.4 MiB used: 280 KiB (0.1%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 17.08 GiB used: 0 KiB (0.0%)
    dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 54.0 C pch: 47.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 3001
Info:
  Processes: 290 Uptime: 1h 31m Memory: 15.49 GiB used: 5.89 GiB (38.0%)
  Init: systemd Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 2322
  Shell: Bash v: 5.1.16 inxi: 3.3.21

Hi, i have solved with downgrade qt6ct from 0.6-2 to 0.5-4

1 Like

maybe the solution is add one line on the config file /etc/environment

With sudo edit de config file :
sudo nano /etc/environment
and add this
QT_QPA_PLATFORMTHEME=qt6ct

and finally reboot the pc.
:3

I would not downgrade the qt6 file since other things rely on it and aren’t having issues with it. If what @FedericoRaika works I’d do that, but wait til one of the devs weighs in on that solution before doing it.

1 Like

I have try again qt6ct ver 0.6-2 and resolved recreating config qt6ct.conf by copy from
/etc/skel/.config/qt6ct/qt6ct.conf to /home/$USER/.config/qt6ct/qt6ct.conf

qt6ct.conf from etc skel

[Appearance]
color_scheme_path=/usr/share/qt6ct/colors/Adwaita-maia-dark.conf
custom_palette=true
icon_theme=Papirus-Dark-Maia
standard_dialogs=gtk3
style=Adwaita-Dark

[Fonts]
fixed=@Variant(\0\0\0@\0\0\0\x1c\0N\0o\0t\0o\0 \0S\0\x61\0n\0s\0 \0M\0o\0n\0o@$\0\0\0\0\0\0\xff\xff\xff\xff\x5\x1\0\x32\x10)
general=@Variant(\0\0\0@\0\0\0\x12\0N\0o\0t\0o\0 \0S\0\x61\0n\0s@$\0\0\0\0\0\0\xff\xff\xff\xff\x5\x1\0\x32\x10)

[Interface]
activate_item_on_single_click=1
buttonbox_layout=3
cursor_flash_time=1200
dialog_buttons_have_icons=1
double_click_interval=400
gui_effects=@Invalid()
keyboard_scheme=4
menus_have_icons=true
show_shortcuts_in_context_menus=true
stylesheets=@Invalid()
toolbutton_style=4
underline_shortcut=1
wheel_scroll_lines=3

[PaletteEditor]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x4\x15\0\0\x1\x11\0\0\x6\x8b\0\0\x3\x42\0\0\x4\x15\0\0\x1\x32\0\0\x6\x8b\0\0\x3\x42\0\0\0\0\0\0\0\0\a\x80\0\0\x4\x15\0\0\x1\x32\0\0\x6\x8b\0\0\x3\x42)

[SettingsWindow]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x5\xa0\0\0\0 \0\0\a\xa7\0\0\x3\x12\0\0\x5\xa0\0\0\0\x41\0\0\a\xa7\0\0\x3\x12\0\0\0\0\0\0\0\0\a\x80\0\0\x5\xa0\0\0\0\x41\0\0\a\xa7\0\0\x3\x12)

my old config qt6ct.conf

[QSSEditor]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0\xb8\0\0\0\xa8\0\0\x3:\0\0\x2\xb4\0\0\0\xb8\0\0\0\xc2\0\0\x3:\0\0\x2\xb4\0\0\0\0\0\0\0\0\x5\xa0\0\0\0\xb8\0\0\0\xc2\0\0\x3:\0\0\x2\xb4)

[SettingsWindow]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0\x84\0\0\0\x62\0\0\x3m\0\0\x2\xfa\0\0\0\x84\0\0\0|\0\0\x3m\0\0\x2\xfa\0\0\0\0\0\0\0\0\x5\xa0\0\0\0\x84\0\0\0|\0\0\x3m\0\0\x2\xfa)
3 Likes

This works for me, too. I believe there’s a serious bug in the current Manjaro packaging of qt6ctl: I do not have it even in the /ec/skel/ directory. The bug seems to affect most, if not all applications based on qt6 - I’ve tried texstudio and qtcreator. Neither works if /home/$USER/.config/qt6ct/qt6ct.conf can’t be found.

3 Likes

Hi, I don’t use desktop apps each time I see a web app.
I group them on a specific Firefox instance:

This applies to telegram and empovers me to use whichever control or improvement I can.
ublock origin, firefox translation, localcdn…

And no software version issue.

Thanks. This worked for me :tada:

In particular, I went for this one liner if anyone wants a go:

rsync /etc/skel/.config/qt6ct ~/.config/

Note though this isn’t just web apps - things like OBS, qjackctl, Jamulus and all the other QT desktop apps were affected.

My point on this thread was that it’s more secure & simpler to use Firefox for network stuff, the other issue is obviously a qt one.

Two threads in one !

Hello all,

First, I tried:

but it hasn’t worked.

Then I tried:

it hasn’t worked either.

Do you have any other suggestions?

Best,
Orkut

I succeded with “copy from
/etc/skel/.config/qt6ct/qt6ct.conf to /home/$USER/.config/qt6ct/qt6ct.conf”, /home/$USER/.config/qt6ct/ didn’t exists before.

1 Like

This worked, thank you:)

I’ve copied qt6ct.conf under qt5ct directory first, because qt6ct directory is not there.

And then, I did mkdir qt6ct, copied the conf file under that one too.

Thanks for your support:)

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.