Qt svg error while inflating gzip file svg format check failed

TG desktop on linux crashes when trying to join channel over 500 #24975

Steps to reproduce

1. Join 500 channels on a free account
2. Open another channel and click JOIN CHANNEL
3. It shows the Premium offer for a moment
4. Telegram crashes

Expected behaviour

Actual behaviour

Operating system

Linux 20.04.4 LTS (Focal Fossa) x86_64 MATE 1.26.0

Version of Telegram Desktop

Telegram Desktop 4.1.1 stable flathub org.telegram.desktop

Installation source

The text was updated successfully, but these errors were encountered:

plz try downloading official version from https://desktop.telegram.org if it still crashes, enable beta and restart telegram and try to get a new crash and send crash id.

Official version from https://desktop.telegram.org/ still crashes with the same output.

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
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
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

Beta also crashes with the same output.

qt.svg: Error while inflating gzip file: SVG format check failed
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.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.svg: Error while inflating gzip file: SVG format check failed
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
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
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed

enable beta and restart telegram and try to get a new crash and send crash id.

Beta also crashes with the same output.

You missed the key point: send the report tag from the crash reporter

Источник

Arch Linux

You are not logged in.

#1 2022-10-14 22:25:45

[SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Up until about 10 days ago, I had telegram-desktop-bin installed from the AUR.
Issues started when I installed the snap standard package: local/telegram-desktop 4.2.4-1.

Present setup is:
— OS (6.0.1-arch2-1),
— local/telegram-desktop 4.2.4-1 installed
— local/telegram-qt 0.1.0-4 installed
— local/gdm 42.0+r11+g4a52f026-1 (gnome) re-install
— extra/gnome-shell 1:42.5-1 re-install
— extra/gnome-shell-extensions 42.3-1 re-install
— extra/libgdm 42.0+r11+g4a52f026-1 re-install
-> reboot:

. replicated well over 200 times over an 6 hour session (between boot and shut-down).

Full journalctl -b -o short-precise log is at: http://ix.io/4daU
All errors related to Telegram are also related to the failed «SVG format check».

— Thinking It was a Telegram scalable graphic icon issue, I did:

where the output is at: http://ix.io/4da0
where I converted a png Telegram Messenger icon to standard svg format and manually placed it in /usr/share/icons/hicolor/scalable/apps, rebooted . to no avail.

— I installed Qt bindings local/telegram-qt 0.1.0-4 above, although I don’t imagine that the issue is related to absent bindings for the telegram protocol.
— I also went to the home page and to the GNOME project home page to consult the Gnome discourse bbs for any similar looking issue. However telegram-desktop not being a Gnome app, it is out of scope for the Gnome team.

Any pointers are welcome.

Last edited by Cbhihe (2022-11-12 20:36:53)

I like strawberries, therefore I’m not a bot.

#2 2022-10-14 23:41:46

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Any reason why you prefer the AUR package over the community one? telegram-desktop is a community package. I’m just wondering.

#3 2022-10-15 11:07:15

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@matse:
What makes you think so ? I don’t favor one over the other. Standard snap packages from either «local/», «community/» or «extra/» are maybe more straightforward to install/manage. (We should take that debate elsewhere.)

Last edited by Cbhihe (2022-10-15 11:29:58)

I like strawberries, therefore I’m not a bot.

#4 2022-10-15 11:13:08

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

What exactly do you mean by a «snap package»? I don’t think that means what you think it means

#5 2022-10-15 11:33:54

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@arojas: you’re right. I deal with snap packàges a lot in my work but not for Arch hosts. Rectified.

I like strawberries, therefore I’m not a bot.

#6 2022-10-15 11:44:42

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Doe you have any qt.svg icon somewhere? If not, maybe try to add one in

#7 2022-10-15 14:12:31

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@progandy:
Tx. Did that. No qt.svg at those queried locations.
Made a legit svg file file up and placed it at /usr/share/icons/hicolor/scalable/apps/qt.svg. Rebooted. Same behavior. Systemd Journal log still gets spammed as soon as telegram-desktop is launched and everytime the first time the Telegram client sends or receives a message.

Last edited by Cbhihe (2022-10-16 12:00:44)

I like strawberries, therefore I’m not a bot.

#8 2022-10-15 14:34:21

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Something curious and I did not mention is the regularity and predictability of the error entry in the log.
Essentially at boot only 2 identical entries appear, just at the end of the journal log for the current boot and after the login session starts. That’s when the autostarting of telegram-desktop occurs.
Then the first time a message is sent from telegram-desktop the same line, only replicated 158 times (that’s 159 lines in total), are logged. No error entry is logged for received messages

On subsequent message sends and receives, no error entry is logged. So when I mentioned in post#1 that the systemd boot log showed well over 200 messages (in fact well other 600 for certain past sessions during which I spent time making sense of this), it was only because in order to troubleshoot the issue, I was manually killing and restarting the telegram-desktop app within the same OS session, thus generating new journal log entries.

Last edited by Cbhihe (2022-10-16 11:18:25)

I like strawberries, therefore I’m not a bot.

#9 2022-10-16 05:03:31

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

I have this installed

I use lightdm and XFCE. Qt version 5.15.6

Last edited by u666sa (2022-10-16 18:02:57)

#10 2022-10-16 05:05:15

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

There is an issue on github

This error is printed by Qt. The cause is not necessarily the telegram.svg, one has to debug Qt to find the real cause.

#11 2022-10-16 07:40:45

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@u666sa:
That GitHub issue you refer to was opened by me 10 days ago. It garnered this one comment and was subsequently closed.

@u666sa:
Can you share your setup by appending to post #9 ? Of particular interest are whether you use GDM, Xorg or Wayland and your install version of Qt. Tx.

It would suggest that telegram-desktop uses Qt as framework for the app codebase and that Qt in turn tries (unsuccessfully?) to use the SVG icon theme ? I’ve been looking in that general direction, unsuccessfully so far. The curious thing is this only ever happens with telegram-desktop .

On this bbs, one find some references to the exact same logged entry, e.g. here and here, but their appear in slightly different contexts, although in contexts having GDM and Qt in common.
Outside the Arch forum, I found this.

Pointers to continue troubleshooting welcome.

Last edited by Cbhihe (2022-10-16 12:42:50)

I like strawberries, therefore I’m not a bot.

Источник

Telegram doesn’t respect QT_QPA_PLATFORM=wayland anymore #23877

Steps to reproduce

Run telegram with native wayland, e.g:

either from cli or by updating the desktop file.

This worked up until 3.4.3.

Expected behaviour

Telegram should run as a wayland application.

Actual behaviour

Telegram runs as X

Operating system

Version of Telegram Desktop

Installation source

Apt installation from Debian sources.

The text was updated successfully, but these errors were encountered:

Static binary from official website

It seems there’s some confusion since static binary from official website can’t print these lines.

Hey, sorry. It’s installed via apt (debian sources):

Can you fix info in your first post?

I am seeing the same thing on Arch Linux:

This was working on 3.3.0 and lower. Might be that the switch to Qt6 caused this?

Partially yes. Qt 6 started defaulting to Wayland on GNOME what caused a lot of complains and GNOME was blacklisted in tdesktop code.

I suppose you mean this ?

I build telegram-desktop from source, excluding this commit and it seems to work fine for me. What were the issues you encountered on Wayland + Gnome? Or was it a specific Gnome version? Regardless, should we allow to override defaulting back to XWayland? As it seems to work in my situation.

Flickering, another cursor theme & size, troubles with context menu positions (can be out-of-screen or not visible at all if Telegram window is maximized)

Hmm interesting, haven’t noticed any of those issues yet. I’ll keep an eye out for them. Were they incredibly noticeable, or very rare? The only issue I noticed (though that was also present in earlier versions) is that the default interface scaling is set to 200% (possibly because I’m using 150% fractional scaling?), making the cursor twice as big (the rest of the interface seems normally sized to me).

Is there something I can do to help debug these issues?

Would a PR that respects QT_QPA_PLATFORM again, defaulting to XWayland like before, be accepted?

Were they incredibly noticeable, or very rare?

Firstly I thought it’s an old bugged version of GNOME, but then a person with GNOME 41 confirmed it’s still an issue.

making the cursor twice as big (the rest of the interface seems normally sized to me).

Well, it’s not scale, Qt just has another default cursor size and doesn’t respect GNOME settings on Wayland

Would a PR that respects QT_QPA_PLATFORM again, defaulting to XWayland like before, be accepted?

@hgaiser Yes, QT_QPA_PLATFORM should be respected, if set.

@ilya-fedin suggested a to fix it in the code from the mentioned above commit in such way:

if (Platform::DesktopEnvironment::IsGnome() && qEnvironmentVariableIsEmpty(«QT_QPA_PLATFORM»)) .

Источник

error cannot open #16897

The application is unexpectedly terminating when trying to run and displays the following error output on the console

** (process:24503): WARNING **: 17:31:45.266: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
** Message: 17:31:45.266: This can be ignored by setting DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
** Message: 17:31:45.266: GTK integration can be disabled by setting DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to some features being unavailable.

(process:24503): Telegram-WARNING **: 17:31:45.266: Application has been built with foreign rlottie, animated emojis won’t be colored to the selected pack.

(process:24503): Telegram-WARNING **: 17:31:45.266: Application was built without embedded fonts, this may lead to font issues. On Debian-based systems, make sure you have the fonts-open-sans package installed
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
qt.svg: Error while inflating gzip file: SVG format check failed
Aborted

System: Debian Bullseye
Package Version: 2.6.1+ds-1
DE: Xfce 4.16
Theme: WhiteSur-dark-solid [GTK2]
Icons: WhiteSur-dark [GTK2]

The text was updated successfully, but these errors were encountered:

Источник

Arch Linux

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the ‘flag out of date’ link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#71422 — [telegram-desktop] v2.8.4-1 can’t download files

Task Type	Bug Report
Category	Packages
Status	Closed
Assigned To	Jiachen Yang (farseerfc)
Architecture	All
Severity	Low
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	1

Details

Description: Telegram Desktop crashes while trying to download a file

Additional info:
* package version(s): 2.8.4-1

Steps to reproduce:

1. Download a file and see the hang

From what I read from a terminal window, there are some errors related a gzip file. Don’t know if this can help fixing the issue. Below a log:

(telegram-desktop:62118): lib_base-WARNING **: 01:12:03.383: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
lib_base-Message: 01:12:03.384: This can be ignored by setting DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
lib_base-Message: 01:12:03.384: GTK integration can be disabled by setting DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to some features being unavailable.

Источник

Другой курсор в telegram desktop gnome 43.2

После переустановки моей основной ос случилась неприяная вещь- в телеграм у меня не системный курсор.В системе у меня стоит Oreo black cursors,во всех программах и играх курсор тот же что и в системе,но в телеграм он самый обычный,из гном,конечно я нашел некое решение этого поставив kotagram но он уже довольно давно не обновлялся и многие сообщения не отображаются,проблема встречается и с пакетом rpm и flatpak

Я извиняюсь я не опытный пользователь,не могли бы ли вы написать команду?Если вам удобно конечно же

Давай сначала проверим, всё ли работает как надо.

Запусти в терминале телегу, но перед ней напиши это

вместо адвайты свою пиши

сюда скопируй чего написал и чего говорит терминал

после запуска через sudo все заработало

Не надо запускать телегу через sudo, бро!

не знаю что именно помогло при запуске от рута

Но один факт что оно запустилось как надо,плохо то что я уж точно не буду каждый раз запускать телегу от рута

Вот поэтому никто не любит помогать новичкам, ибо они не делают то, что им говорят.

Ещё раз, никаких судо.

Как я понял нужно так,но как я и описывал в удаленном коментарии курсор все так же остается другим

Пробуй менять название темы, например

Скорее всего название неверно пишешь.

Реакция никак не измненилась,название Oreo_black_cursors я взя прямиком из gnome-tweaks

попробуй-ка так, не пиши про тему

Да, выхлоп то был какой по теме в терминал?

Проблема связана с вейландом.

Сработало на xwayland, это такая прокладка иксовая.

Теперь варианта два: либо фиксируем этот вариант, если тебя всё устраивает, либо разбираемся дальше. Как?

Погуглив чють раньше я тоже понял что проблема в wayland и тоже хотел включить XWayland но по тому гайду который был приложен это не получилось.Меня полностью устраивает вариант с фиксацией XWayland

Скопируй из каталога

открой в редакторе тот который теперь в хомяке

в строке Exec добавь как в терминале, типа

Извини за стиль, я с телефона…

/.bashrc сразу, эта же проблема у всех qt приложений.

у меня ничего не поучилось. /usr/share/applications здесь я нашел ярлык и скопировал (не вырезал,переместил и тд. просто скопировал) в

/.local/share/applications Поставил Exec=QT_QPA_PLATFORM=xcb а то что дальше не менял,ничего не поменялось,закинул измененный ярлык в /usr/share/applications и он пропал в меню программ,сейчас могу приложить код из ярлыка который у меня как бэкап,скорее всего вы лучше знаете,если удобно то можете его отредактировать как надо

Источник

error cannot open #16897

Comments

wsalmeida commented Sep 3, 2021

The application is unexpectedly terminating when trying to run and displays the following error output on the console

** (process:24503): WARNING **: 17:31:45.266: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
** Message: 17:31:45.266: This can be ignored by setting DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
** Message: 17:31:45.266: GTK integration can be disabled by setting DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to some features being unavailable.

(process:24503): Telegram-WARNING **: 17:31:45.266: Application has been built with foreign rlottie, animated emojis won’t be colored to the selected pack.

(process:24503): Telegram-WARNING **: 17:31:45.266: Application was built without embedded fonts, this may lead to font issues. On Debian-based systems, make sure you have the fonts-open-sans package installed
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
qt.svg: Error while inflating gzip file: SVG format check failed
Aborted

System: Debian Bullseye
Package Version: 2.6.1+ds-1
DE: Xfce 4.16
Theme: WhiteSur-dark-solid [GTK2]
Icons: WhiteSur-dark [GTK2]

The text was updated successfully, but these errors were encountered:

Источник

Arch Linux

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the ‘flag out of date’ link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#71422 — [telegram-desktop] v2.8.4-1 can’t download files

Task Type	Bug Report
Category	Packages
Status	Closed
Assigned To	Jiachen Yang (farseerfc)
Architecture	All
Severity	Low
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	1

Details

Description: Telegram Desktop crashes while trying to download a file

Additional info:
* package version(s): 2.8.4-1

Steps to reproduce:

1. Download a file and see the hang

From what I read from a terminal window, there are some errors related a gzip file. Don’t know if this can help fixing the issue. Below a log:

(telegram-desktop:62118): lib_base-WARNING **: 01:12:03.383: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
lib_base-Message: 01:12:03.384: This can be ignored by setting DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
lib_base-Message: 01:12:03.384: GTK integration can be disabled by setting DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to some features being unavailable.

Источник

Arch Linux

You are not logged in.

#1 2022-10-14 22:25:45

[SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Up until about 10 days ago, I had telegram-desktop-bin installed from the AUR.
Issues started when I installed the snap standard package: local/telegram-desktop 4.2.4-1.

Present setup is:
— OS (6.0.1-arch2-1),
— local/telegram-desktop 4.2.4-1 installed
— local/telegram-qt 0.1.0-4 installed
— local/gdm 42.0+r11+g4a52f026-1 (gnome) re-install
— extra/gnome-shell 1:42.5-1 re-install
— extra/gnome-shell-extensions 42.3-1 re-install
— extra/libgdm 42.0+r11+g4a52f026-1 re-install
-> reboot:

. replicated well over 200 times over an 6 hour session (between boot and shut-down).

Full journalctl -b -o short-precise log is at: http://ix.io/4daU
All errors related to Telegram are also related to the failed «SVG format check».

— Thinking It was a Telegram scalable graphic icon issue, I did:

where the output is at: http://ix.io/4da0
where I converted a png Telegram Messenger icon to standard svg format and manually placed it in /usr/share/icons/hicolor/scalable/apps, rebooted . to no avail.

— I installed Qt bindings local/telegram-qt 0.1.0-4 above, although I don’t imagine that the issue is related to absent bindings for the telegram protocol.
— I also went to the home page and to the GNOME project home page to consult the Gnome discourse bbs for any similar looking issue. However telegram-desktop not being a Gnome app, it is out of scope for the Gnome team.

Any pointers are welcome.

Last edited by Cbhihe (2022-11-12 20:36:53)

I like strawberries, therefore I’m not a bot.

#2 2022-10-14 23:41:46

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Any reason why you prefer the AUR package over the community one? telegram-desktop is a community package. I’m just wondering.

#3 2022-10-15 11:07:15

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@matse:
What makes you think so ? I don’t favor one over the other. Standard snap packages from either «local/», «community/» or «extra/» are maybe more straightforward to install/manage. (We should take that debate elsewhere.)

Last edited by Cbhihe (2022-10-15 11:29:58)

I like strawberries, therefore I’m not a bot.

#4 2022-10-15 11:13:08

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

What exactly do you mean by a «snap package»? I don’t think that means what you think it means

#5 2022-10-15 11:33:54

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@arojas: you’re right. I deal with snap packàges a lot in my work but not for Arch hosts. Rectified.

I like strawberries, therefore I’m not a bot.

#6 2022-10-15 11:44:42

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Doe you have any qt.svg icon somewhere? If not, maybe try to add one in

#7 2022-10-15 14:12:31

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@progandy:
Tx. Did that. No qt.svg at those queried locations.
Made a legit svg file file up and placed it at /usr/share/icons/hicolor/scalable/apps/qt.svg. Rebooted. Same behavior. Systemd Journal log still gets spammed as soon as telegram-desktop is launched and everytime the first time the Telegram client sends or receives a message.

Last edited by Cbhihe (2022-10-16 12:00:44)

I like strawberries, therefore I’m not a bot.

#8 2022-10-15 14:34:21

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

Something curious and I did not mention is the regularity and predictability of the error entry in the log.
Essentially at boot only 2 identical entries appear, just at the end of the journal log for the current boot and after the login session starts. That’s when the autostarting of telegram-desktop occurs.
Then the first time a message is sent from telegram-desktop the same line, only replicated 158 times (that’s 159 lines in total), are logged. No error entry is logged for received messages

On subsequent message sends and receives, no error entry is logged. So when I mentioned in post#1 that the systemd boot log showed well over 200 messages (in fact well other 600 for certain past sessions during which I spent time making sense of this), it was only because in order to troubleshoot the issue, I was manually killing and restarting the telegram-desktop app within the same OS session, thus generating new journal log entries.

Last edited by Cbhihe (2022-10-16 11:18:25)

I like strawberries, therefore I’m not a bot.

#9 2022-10-16 05:03:31

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

I have this installed

I use lightdm and XFCE. Qt version 5.15.6

Last edited by u666sa (2022-10-16 18:02:57)

#10 2022-10-16 05:05:15

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

There is an issue on github

This error is printed by Qt. The cause is not necessarily the telegram.svg, one has to debug Qt to find the real cause.

#11 2022-10-16 07:40:45

Re: [SOLVED] telegram-desktop package spams systemd log (qt issue ?).

@u666sa:
That GitHub issue you refer to was opened by me 10 days ago. It garnered this one comment and was subsequently closed.

@u666sa:
Can you share your setup by appending to post #9 ? Of particular interest are whether you use GDM, Xorg or Wayland and your install version of Qt. Tx.

It would suggest that telegram-desktop uses Qt as framework for the app codebase and that Qt in turn tries (unsuccessfully?) to use the SVG icon theme ? I’ve been looking in that general direction, unsuccessfully so far. The curious thing is this only ever happens with telegram-desktop .

On this bbs, one find some references to the exact same logged entry, e.g. here and here, but their appear in slightly different contexts, although in contexts having GDM and Qt in common.
Outside the Arch forum, I found this.

Pointers to continue troubleshooting welcome.

Last edited by Cbhihe (2022-10-16 12:42:50)

I like strawberries, therefore I’m not a bot.

Источник

Telegram Desktop can’t play most videos and video messages on a Raspberry Pi 4 #9832

Comments

the-real-cyberpatrol commented Nov 30, 2020

Steps to reproduce

1. Start Telegram Desktop on a Raspberry Pi 4 with 4 GB.
2. Open a channel which includes an uploaded video or a video message.
3. Click onto the video or video message to play it.

Expected behaviour

The video or video message should be played.

Actual behaviour

The video or video message doesn’t get played. Telegram Desktop does nothing.

Configuration

Operating system:
Arch Linux ARM (armv7h) with Xfce on a Raspberry Pi 4.

Version of Telegram Desktop:
2.2.0

Installation source (Linux Only) — the official website / GitHub releases / flatpak / snap / distribution package:
Distribution package: community/telegram-desktop 2.2.0-2

Used theme:
Classic

Console output video: $ telegram-desktop
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
error: : cannot open
error: : cannot open
error: : cannot open
qt.svg: Error while inflating gzip file: SVG format check failed
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
[swscaler @ 0x91f0e740] No accelerated colorspace conversion found from yuv420p to bgra.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0xaca01a10] Packet corrupt (stream = 0, dts = 60030).
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
[swscaler @ 0x91ece7d0] No accelerated colorspace conversion found from yuv420p to bgra.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0xaac2b6b0] Packet corrupt (stream = 0, dts = 100530).
Console output video message: $ telegram-desktop
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
error: : cannot open
error: : cannot open
error: : cannot open
qt.svg: Error while inflating gzip file: SVG format check failed
[swscaler @ 0x9363bdd0] No accelerated colorspace conversion found from yuv420p to bgra.
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
[swscaler @ 0x92a76af0] No accelerated colorspace conversion found from yuv420p to bgra.
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)
[swscaler @ 0x936204d0] No accelerated colorspace conversion found from yuv420p to bgra.
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation is not permitted (1)

The text was updated successfully, but these errors were encountered:

Источник