Upgrading from 20190823, that is.

Problem: telegram-desktop-1.8.2-1.1.x86_64 conflicts with libqt5-qtstyleplugins-platformtheme-gtk2 provided by libqt5-qtstyleplugins-platformtheme-gtk2-5.0.0+git20170311-6.11.x86_64
 Solution 1: Following actions will be done:
  deinstallation of telegram-desktop-1.8.1-1.1.x86_64
  deinstallation of telegram-theme-plata-0.8.9-1.1.noarch
  deinstallation of telegram-theme-adapta-3.95.0.11-2.1.x86_64
 Solution 2: deinstallation of libqt5-qtstyleplugins-platformtheme-gtk2-5.0.0+git20170311-6.11.x86_64
 Solution 3: keep obsolete telegram-desktop-1.8.1-1.1.x86_64
 
The problem is the same

I see that the bug has been assigned to telegram-desktop bugowner, but it's been a week without response. Any clue on what's wrong?

Since the bugowner is inherited, I've added telegram-desktop maintainers to CC, maybe they can help.

(In reply to Ave Milia from comment #4)
> Since the bugowner is inherited, I've added telegram-desktop maintainers to
> CC, maybe they can help.

Thanks, up until now I was not notified of this.

As for the Bug: the Conflict was introduced intentionally to be able to use Telegrams GTK integration for native notifications.
After enabling this, Telegram would refuse to start as long as libqt5-qtstyleplugins-platformtheme-gtk2 is present on the system.

(In reply to Marcel Kuehlhorn from comment #5)
> As for the Bug: the Conflict was introduced intentionally to be able to use
> Telegrams GTK integration for native notifications.
> After enabling this, Telegram would refuse to start as long as
> libqt5-qtstyleplugins-platformtheme-gtk2 is present on the system.

Thank you for the information. So the resolution is to uninstall libqt5-qtstyleplugins-platformtheme-gtk2?

I remember there was some problem with GTK themes when moving to Qt 5.7[0], is this package related to that? The issue I refer to has caused weird problems like

> GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion
> 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

as a runtime error on already compiled applications.

[0]: <https://bbs.archlinux.org/viewtopic.php?id=214147>

(In reply to Ave Milia from comment #6)
> Thank you for the information. So the resolution is to uninstall
> libqt5-qtstyleplugins-platformtheme-gtk2?
> 
For now, yes.

> I remember there was some problem with GTK themes when moving to Qt 5.7[0],
> is this package related to that? The issue I refer to has caused weird
> problems like
> 
> > GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion
> > 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> 
> as a runtime error on already compiled applications.
> 
> [0]: <https://bbs.archlinux.org/viewtopic.php?id=214147>

That looks indeed similar to the errors Telegram gives:
> ~>telegram-desktop 
> (telegram-desktop:4205): GLib-GObject-WARNING **: 17:15:44.346: cannot register existing type 'GdkDisplayManager'
> (telegram-desktop:4205): GLib-CRITICAL **: 17:15:44.346: g_once_init_leave: assertion 'result != 0' failed
> (telegram-desktop:4205): GLib-GObject-CRITICAL **: 17:15:44.346: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(In reply to Marcel Kuehlhorn from comment #7)
> (In reply to Ave Milia from comment #6)
> > Thank you for the information. So the resolution is to uninstall
> > libqt5-qtstyleplugins-platformtheme-gtk2?
> > 
> For now, yes.
> 
> > I remember there was some problem with GTK themes when moving to Qt 5.7[0],
> > is this package related to that? The issue I refer to has caused weird
> > problems like
> > 
> > > GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion
> > > 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> > 
> > as a runtime error on already compiled applications.
> > 
> > [0]: <https://bbs.archlinux.org/viewtopic.php?id=214147>
> 
> That looks indeed similar to the errors Telegram gives:
> > ~>telegram-desktop 
> > (telegram-desktop:4205): GLib-GObject-WARNING **: 17:15:44.346: cannot register existing type 'GdkDisplayManager'
> > (telegram-desktop:4205): GLib-CRITICAL **: 17:15:44.346: g_once_init_leave: assertion 'result != 0' failed
> > (telegram-desktop:4205): GLib-GObject-CRITICAL **: 17:15:44.346: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

Is there a tracking bug for this particular issue of tg? For example, ckb-next was haunted by it[0] (if that's the same cause) seemingly due to appindicator, and it only happened for KDE users, or something like that. But for some people installing qt5ct resolved the issues. That was a mess that I never figured out.

[0]: <https://github.com/ckb-next/ckb-next/issues/139>

(In reply to Ave Milia from comment #8)
> Is there a tracking bug for this particular issue of tg? For example,
> ckb-next was haunted by it[0] (if that's the same cause) seemingly due to
> appindicator, and it only happened for KDE users, or something like that.
> But for some people installing qt5ct resolved the issues. That was a mess
> that I never figured out.
> 
> [0]: <https://github.com/ckb-next/ckb-next/issues/139>

Not an open one at least, the one I could find [1] was closed with (paraphrasing): "Use our binary blob, we don't care about errors with distro packages"

[1] https://github.com/telegramdesktop/tdesktop/issues/4301

(In reply to Marcel Kuehlhorn from comment #9)
> (In reply to Ave Milia from comment #8)
> > Is there a tracking bug for this particular issue of tg? For example,
> > ckb-next was haunted by it[0] (if that's the same cause) seemingly due to
> > appindicator, and it only happened for KDE users, or something like that.
> > But for some people installing qt5ct resolved the issues. That was a mess
> > that I never figured out.
> > 
> > [0]: <https://github.com/ckb-next/ckb-next/issues/139>
> 
> Not an open one at least, the one I could find [1] was closed with
> (paraphrasing): "Use our binary blob, we don't care about errors with distro
> packages"

Fair enough :) As a developer, I 100% understand their decision.

> 
> [1] https://github.com/telegramdesktop/tdesktop/issues/4301

So, do you have any documented issues on your side? Or where did you pull the #7 error messages from? If you have any recorded information and can reproduce it, it's probably a good idea to create a new bug for it. I feel like this issue is triggered by some edge case in a mishmash of Qt versions, now-additional Qt packages (like platform themes), desktop environments and tray icon libraries.

Regarding current issue, if you (or any other knowledgeable people) think that current resolution of package removal is a correct one and is not a temporary workaround, feel free to close.

*** Bug 1149130 has been marked as a duplicate of this bug. ***

(In reply to Ave Milia from comment #10)
> 
> So, do you have any documented issues on your side? Or where did you pull
> the #7 error messages from? If you have any recorded information and can
> reproduce it, it's probably a good idea to create a new bug for it. I feel
> like this issue is triggered by some edge case in a mishmash of Qt versions,
> now-additional Qt packages (like platform themes), desktop environments and
> tray icon libraries.
> 
I did not have one yet, created bug 1149986 now.
The error messages are from building telegram-desktop without the Conflicts and installing it together with libqt5-qtstyleplugins-platformtheme-gtk2

> Regarding current issue, if you (or any other knowledgeable people) think
> that current resolution of package removal is a correct one and is not a
> temporary workaround, feel free to close.
>
I'll keep this Issue open to discussion seeing as you're not the first one to bring it up and I get the feeling quite a few people would prefer disabled GTK integration / no native notifications as it was before.

cinnamon-session required libqt5-qtstyleplugins-platformtheme-gtk2 as hard dependency, therefore user with cinnamon desktop cannot install telegram from the repo.

(In reply to andy great from comment #13)
> cinnamon-session required libqt5-qtstyleplugins-platformtheme-gtk2 as hard
> dependency, therefore user with cinnamon desktop cannot install telegram
> from the repo.

I guess I'll have to disable GTK integration on the main package again with the next version update...

A branch with it enabled will be kept at
https://build.opensuse.org/project/show/home:tux93:tdesktop

SR#730197 with the update to 1.8.8 was just accepted to Factory, it removes GTK integration and the Conflict again.