You are not logged in.
Hello
With the last upgrade from 1.2.6-2 to 1.2.6-3 (see this commit), the packager seems to have intended to remove GTK+ dependencies, and thus removed libappindicator-gtk3 from the dependencies.
That is fine, but they also added the GYP option TDESKTOP_DISABLE_GTK_INTEGRATION, which—according to this code—prevents telegram-desktop from using libnotify (it is currently unknown to me why using libnotify would require "GTK+ integration"; discussed here), and understandably I no longer have the option to use native notifications.
I was a bit confused, so I rebuilt telegram-desktop without TDESKTOP_DISABLE_GTK_INTEGRATION, but also without the libappindicator-gtk3 dependency (and I made sure that latter is not installed), and surprise!: It still works (and I got my native notifications back)!
Unfortunately I don't properly understand the interactions between libappindicator-gtk3, Telegram and libnotify, and although it appears to me that it is perfectly possible to build the package the way I have, there may be other things that play into this, so here my questions:
Are there any GNOME+Telegram users here? Do native notifications still work for you with 1.2.6-3 (w.r.t. FS#56803)?
Could anyone confirm that building telegram-desktop the way I have makes native notifications work again?
If the second question is answered with "yes", would it be acceptable to open a bug report on the Arch Linux bug tracker to ask for the removal of the GYP option?
--edit: Or am I completely on the wrong track here, and native notifications still work with 1.2.6-3 from the repos, and just not for me? (sorry for jumping to the conclusion that this is a bug).
Last edited by ayekat (2018-01-10 21:04:48)
Offline
If it causes libnotify to work again without pulling gtk back in, then this is absolutely something that you can and should report as a bug, however you should probably hold back until you get a response from upstream about why they require gtk integration to be enabled before turning on the libnotify code.
(From a quick perusal, I agree with your assessment about the code.)
Last edited by eschwartz (2018-01-10 16:13:36)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I just say that I'm a GNOME and Telegram user and I confirm that there isn't any "Use native notifications" option in settings, therefore built-in notification system is used.
Offline
Offline
Great, they just reverted the change from -2 to -3: https://git.archlinux.org/svntogit/comm … 18d2c11763
I don't know if I should tell them that libappindicator-gtk3 is actually not necessary... -.-
--edit Then again, that would touch the "Arch Linux package dependencies" topic/discussion...
I'll mark this issue as "solved". Thank you for your replies!
Last edited by ayekat (2018-01-11 07:25:08)
Offline
Has this issue been resolved for any of you?
It's been many years now and for me the issue is still present in the Telegram Desktop Clients I use frequently (Official, 64Gram).
Notifications are working fine in Kotatogram ~ which is still Version 1.4.9 beta (TD. 3.5.2) ~ so I assume the real cause for this misbehaviour might be someone changing mechanics or messing something up back then without ever fixing it.
This is clearly not an issue related to packaging!
You can pull any Binary ~ either official or forks ~ from the devs website and notifications just won't work.
It also doesn't matter which Distribution. I don't know of any where it works.
Any help would be greatly appreciated.
Kotatogram Screenshot: https://i.ibb.co/dGT1wV9/Screenshot-fro … -24-40.png
Last edited by NA0341 (2024-05-19 15:51:38)
Offline
Has this issue been resolved for any of you?
Yes, with the change I linked in post #5 from six years ago, the issue had been resolved.
(TD. 3.5.2)
I assume "TD" here means "Telegram Desktop"? If so, the current version in [extra] is 5.0.1-1. And native notifications work still fine with this version, at least for me.
But since you mention older versions and/or pulling binaries from upstream: Have you tried simply installing telegram-desktop from [extra]?
--edit Ah, sorry, it seems all the cgit links stopped working, here's the updated one: https://gitlab.archlinux.org/archlinux/ … 2890dbba23
Last edited by ayekat (2024-05-19 17:23:59)
Offline
Okay first I'm sorry for necro-bumping this thread.
I don't use forums very often and so I did not think about this rule.
Yes that's right.
TD is short for Telegram Desktop in this context.
I use the newest Official Version which I downloaded directly from https://desktop.telegram.org (it's an Archive containing the Application & Updater in AppImage format).
I did install the latest telegram-desktop-5.0.2-2 package from extra, it did not start however:
~ telegram-desktop
telegram-desktop: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by telegram-desktop)
Considering the fact that every version of every client I use works fine (including newer versions) ~ the version from the repos must have been modified by the package maintainers.
My guess is that either my system is missing a component for the inbuilt notifications to work. Or the binaries have been compiled without theese notifications (which is very unlikely since this is still an official feature).
There is some output when I start the Official Client via the commandline:
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
Maybe those errors are an issue because it cannot "draw" or render the custom notifications?
But 64Gram doesn't output any errors when started from Terminal and doesn't have the inbuilt notifications in settings either.
The only errors I could find in the logfiles were related to one API error and two RPC Error types:
API Warning: not loaded minimal channel applied.
RPC Error: request 45 got fail with code 400, error FILE_REFERENCE_EXPIRED
RPC Error: request 97 got fail with code 400, error WEBFILE_NOT_AVAILABLE
Thank you very much in advance.
If you have an idea or tips on how to find out the cause - I'd highly appreciate to hear from you.
--
PS:
I use the developers versions directly for two main reasons:
1. Installing a very universally compatible, self - updating AppImage via a Package Manager doesn't make sense to me.
2. I get faster updates and can decide to update the application when I want the update ~ and not when I'm updating the system as a whole (updates aren't always a good thing…).
Offline
~ telegram-desktop telegram-desktop: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.15' not found (required by telegram-desktop)
Please post the output of
pacman -Q gcc-libs
2. I get faster updates and can decide to update the application when I want the update ~ and not when I'm updating the system as a whole (updates aren't always a good thing…).
You will likely not enjoy Arch very much if you want to only update individual software/packages. See also https://wiki.archlinux.org/title/System … nsupported
Errors such as the one above are expected if you do so anyway.
Offline