Telegram Desktop 0.9.18
Chrystal Dueno
- 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.
@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.
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.
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 .
Sorry, qt.svg is not a filename, but the logging category. qt.svg means it comes from the qtsvg package. The specific error message results from the function qt_inflateSvgzDataFrom. That function is called from QSvgTinyDocument::load, so I'd guess telegram might contain some compressed svg file that cannot be decompressed by qt.
@progandy:
Yes, most probably cannot read that svg file, but I had to try it.
Yes, telegram-desktop use themes and is customizable in that sense, but I just use the package from Arch local/ repo as is. No tweak whatsoever.
If you don't want the blue icon to be visible on this group, but you want to go to this view, then you can first go to the Telegram channel. This is the channel that tells you an update is ready. In this channel, you DO get notifications for your other chats even if you don't mark the telegram chat as unread and just stay in that chat. That is basically what I do. But marking it unread to get to the default screen looks better for sure.
After updating the looks of GNOME installation as described here, telegram-desktop (installed from Official repos, not from AUR) got some borders.If I use Style: kvantum or kvantum-dark I get borders, if I switch to anything else - borders are gone.
a workaround would be to copy /var/lib/flatpak/app/org.telegram.desktop/current/active/export/share/applications/org.telegram.desktop.desktop to /.local/share/applications/. and removing the line DBusActivatable=true from it
I saw there are various UDF libs for Telegram already (to my pleasure, I must say), but looks like they're for direct interaction with telegram API, so kinda to use them with a bot.
Unfortunately bot file management is severely limited in size of files (20mb compared to 4gb on premium normal user) and other aspects.
Therefore my last choice was to automate in some way telegram desktop in a way that directly interacts with the window (WinGetHandle, WinExists, etc etc.).
Unfortunately, probably due to the fact that as I understood telegram is packed with electron, and electron AFAIK just displays a webapp into an exe,, trying to use Window Info tool doesn't give any result beside a main window, which has the current chat name and a random number.
The only way to grab it is by classname like this:
But I'm unable to catch any other button/UI element info with the telegram application. They all give the same handle info of the main page.
I tried to disable/enable Spy++ detection logic but nothing changed.
This leaves me to 3 roads:
1) Maybe there is another way to detect the handles and I don't know?
2) Trying some injector ( -injector for example) to inject html/js directly and interact with it
@debendraoli Wouldn't that affect all applications started via DBus? The only reason this fix works for telegram is, ironically, because it has its own UI scaling settings. If it didn't, then you would be depending on that variable to scale its UI correctly. Doing so globally for all apps started via DBus might break other applications that depends on it.
This package behavior is different from the official static binaries downloaded from the telegram website when it comes to HiDPI support. Telegram has its own UI scaling which conflict with KDE scaling and mangles every picture in the app. The official binaries seems to ignore the QT_SCREEN_SCALE_FACTORS environement variable which fixes the issue, but this package doesn't making it unusable when a fractional scaling (eg. 125%) setting is applied in KDE's display settings.
Polls are available on Android, iOS, and desktop applications. Polls have the option to be anonymous or visible. A user can enter multiple options into the poll. Quiz mode can also be enabled where a user can select the right answer for their poll and leave it to the group to guess. Quiz bots can also be added to track correct answers and even provide a global leaderboard.[123]
The desktop clients (excluding the macOS client) do not feature options for end-to-end encrypted messages. When the user assigns a local password in the desktop application, data is locally encrypted also. Telegram has defended the lack of ubiquitous end-to-end encryption by claiming the online-backups that do not use client-side encryption are "the most secure solution currently possible".[288]
In March 2014, Telegram promised that "all code will be released eventually", including all the various client applications (Android, iOS, desktop, etc.) and the server-side code.[305] As of May 2021, Telegram had not published their server-side source code.[306] In January 2021, Durov explained his rationale for not releasing server-side code, citing reasons such as inability for end-users to verify that the released code is the same code run on servers, and a government that wanted to acquire the server code and make a messaging app that would end competitors.[307]
Telegram version 3.7.1 does not allow to select the web camera to use in video conference. If you want to force telegram to use a different camera, as a workaround you can disable the unwanted camera device as described in [1].
Telegram-desktop is built against Qt 6 since 3.4.2-2. Users upgrading from an older version might notice Fcitx stop working for this application. To make it work again, install fcitx-qt6 or the fcitx-im group. If using Fcitx5, install fcitx5-im.
Fiddler Everywhere and Fiddler Classic are HTTPS proxies, and as such they can capture application traffic that utilizes HTTP, HTTPS, WebSocket, or gRPC protocols. While some basic operations in the Telegram desktop application use HTTP (pre-handshake requests), all communication is end-to-end encrypted. The encryption is not using the TLS protocol that is widely used with HTTP, but instead, Telegram created its encryption protocol called MTProto. The creators of Telegram started this protocol with the sole idea of preventing traffic decryption from the intermediate.
Then open /.local/share/applications/telegram-desktop.desktop in your text editor of choice and edit the Exec line to include -scale 80 (or whatever scale works better for you). It should look something like this:
Then open /.local/share/applications/telegram-desktop.desktop in your text editor of choice and edit the Exec line to start Telegram with the env command which allows running a program with a modified environment. It should look something like this:
The search service can find package by either name (apache),provides(webserver), absolute file names (/usr/bin/apache),binaries (gprof) or shared libraries (libXm.so.2) instandard path. It does not support multiple arguments yet... The System and Arch are optional added filters, for exampleSystem could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system. System Arch RPM resource telegram-desktopTelegram is a non-profit cloud-based instant messaging service.Users can send messages and exchange photos, videos, stickers, audio and files of any type.Its client-side code is open-source software but the source code for recent versions is notalways immediately published, whereas its server-side code is closed-source and proprietary.The service also provides APIs to independent developers.
Telegram is very reliable so you can be sure that your opponent will receive your message. Its client software is relatively lightweight and useful. For example, you don't have to keep your mobile Telegram client running when you need to use the desktop version of the app unlike WhatsApp Desktop app which connects via WiFi to your phone or tablet running WhatsApp. Telegram also consumes notably less resources than competing apps like WhatsApp and Viber.
e2b47a7662