https://bugs.kde.org/show_bug.cgi?id=416652

--- Comment #12 from hexchain <i...@hexchain.org> ---
(In reply to Konrad Materka from comment #11)
> I'm not so familiar with DBus and StatusNotifierWatcher, but it looks that
> everything is OK on KDE side. It uses QDBusServiceWatcher to watch for
> service unregistration. There is a small possibility that
> QDBusServiceWatcher has a bug (unlikely) but most probably it was a bug in
> Telegram. I quickly checked Telegrams commit log, there was some work
> related to DBus, but for notifications, including
> https://blog.broulik.de/2020/01/venturing-out/ :)
>

If you would like to, you could probably also check out
https://git.archlinux.org/svntogit/community.git/log/trunk?h=packages/telegram-desktop.
 

Telegram desktop client used to require lots of patches to work with system
libraries. After 1.9.4, there are some build options to make it link to the
system libraries so the patches are no longer required. As a result, some large
chunks of code may get disabled/enabled, which may affect its SNI behavior.

> If everything is ok now, I would close it.

I'm not against it. I'll report back if anything new happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to