Bug 1154112 - Package Telegram with native notifications turned on
Summary: Package Telegram with native notifications turned on
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: 64bit Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Marcel Kuehlhorn
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on: 1149986
Blocks:
  Show dependency tree / graph
 
Reported: 2019-10-15 18:38 UTC by Nathaniel Graham
Modified: 2019-12-09 21:39 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nathaniel Graham 2019-10-15 18:38:26 UTC 
Apparently native notifications (i.e notifications provided by your DE, rather than drawn by the app) for Telegram need to be turned on by compiling against libappindicator3-1 and making sure that TDESKTOP_DISABLE_GTK_INTEGRATION is not set in the packaging.

See how Arch fixed this here: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/telegram-desktop&id=3f47bddefd3b06f0c816c1f88ad78318d2c11763

I just migrated from an Arch-based distro, where the native notifications are used and they're much nicer than the app-drawn notifications. I did not notice any bugs after more than a year of use. openSUSE should consider enabling Telegram's native notifications, too.

For more information, see https://github.com/telegramdesktop/tdesktop/issues/3831
Comment 1 Marcel Kuehlhorn 2019-10-16 09:42:03 UTC 
We can't enable this feature globally at the moment due to an issue libqt5-qtbase.

For details see bug 1149986

Currently as a workaround I set up a home repo with modified libqt5-qtbase and telegram with enabled gtk integration here:
https://build.opensuse.org/project/show/home:tux93:tdesktop

For me a more urgent issue at the moment is that recent updates of telegram upstream moved around files in the buildsystem and I fail to get it to build again. Any help there would be appreciated.
Comment 2 Nathaniel Graham 2019-10-16 15:57:34 UTC 
Thanks, I've marked that bug as a blocker.
Comment 3 Nathaniel Graham 2019-11-14 20:41:25 UTC 
Bug 1149986 is marked as resolved; are we just waiting for the fix to get packaged now?
Comment 4 Nathaniel Graham 2019-12-09 20:25:08 UTC 
Ping. Is something blocking this?
Comment 5 Marcel Kuehlhorn 2019-12-09 21:36:32 UTC 
(In reply to Nathaniel Graham from comment #4)
> Ping. Is something blocking this?

The SR for Telegram 1.8.15 was held up by legal review for some time and finally accepted 2 weeks ago.

With that update Telegram on Tumbleweed (and Leap 15.2 as that was accepted today) now allows using native notifications.
Comment 6 Nathaniel Graham 2019-12-09 21:39:30 UTC 
So it does! Many thanks. I didn't notice because the option is off by default and needs to be turned on, as it's not this way in other distros I've used. Is there a reason why it isn't on by default?