Bug 1463252

Summary: Plasma tray bar does not show GTK application icons
Product: [Fedora] Fedora Reporter: Hynek Mlnarik <hmlnarik>
Component: plasma-desktopAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: jgrulich, kde-sig, kdudka, lukas.marek, me, pierre.juhen, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:30:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1461576    
Bug Blocks:    

Description Hynek Mlnarik 2017-06-20 12:44:47 UTC
Description of problem:
After upgrade from F25 to F26 Beta, all application icons that were present in tray bar in F25 are lost (not even space reserved for the icons).

Version-Release number of selected component (if applicable):
plasma-desktop-5.10.1-1.fc26.x86_64

How reproducible:
always

Steps to Reproduce:
1. run an application that has traybar icon, e.g. pidgin
2. watch traybar carefully

Actual results:
no icon appears even after concentrated watching

Expected results:
icons are shown similarly to plasma from F25

Comment 1 Pavel Raiskup 2017-07-12 16:02:36 UTC
> all application icons that were present in tray bar in F25 are lost 

Seconded.

Not really *all* icons, but the old GTK icons are lost after upgrade to F26.
This used to be long time issue after switching to KF5; and now - after
switching to F26 - the bug regressed.

Comment 2 Pierre Juhen 2017-07-18 05:38:04 UTC
Same bug for me :
Skype, Thunderbird, Nut icons don't show up !

Comment 3 Pavel Raiskup 2017-07-18 06:43:44 UTC
Starting /usr/bin/xembedsniproxy fixes the problem for me.

Comment 4 Hynek Mlnarik 2017-07-18 07:17:50 UTC
Thanks for the workaround - xembedsniproxy fixes the issue for me as well. Hope it would be possible to get this fixed properly

Comment 5 Pavel Raiskup 2017-07-18 07:49:16 UTC
Unfortunately, I think the "proper fix" would only mean running xembedsniproxy
automatically.

Comment 6 Hynek Mlnarik 2017-07-18 10:34:56 UTC
In that case Plasma should run xembedsniproxy automatically upon start (preferred), or at least inform the user to do so to be able to see the program icons. I believe the current behaviour only leads to confusion of users.

There are still legacy GTK applications that have no non-GTK equivalent and use tray icons extensively (e.g. "minimize to tray" functionality). Icons not showing up leads user to false impression that the respective program exited prematurely or even did not start up at all (e.g. when pidgin is started in minimized mode, nothing would visually change).

Comment 7 Pierre Juhen 2017-07-18 17:51:47 UTC
A workaround that works for me is to configure KDE too have xembedsniproxy runing at launch.

System settings -> start / stop

Comment 8 Lukas Marek 2017-07-19 07:56:27 UTC
I believe this can be related: https://retrace.fedoraproject.org/faf/reports/1745795/ It happens to me every time I login into plasma.

Comment 9 Lukas Marek 2017-08-01 07:43:12 UTC
It seems that the latest update to plasma (5.10.4) resolved the issue for me.

Comment 10 Hynek Mlnarik 2017-08-01 09:05:46 UTC
Does not seem to be resolved for me with 5.10.4, I have to run xembedsniproxy manually to see GTK icons in traybar.

Comment 11 Rex Dieter 2017-08-03 15:50:12 UTC
Can any of you post more examples of apps that fail to show (ideally from fedora)?

Of those mentioned, 
pidgin:  recommendation is to use pidgin-indicator
thunderbird: I wasn't aware it supported systray icon?
nut icons: can you give more details?

Comment 12 Hynek Mlnarik 2017-08-04 07:05:53 UTC
@Rex Dieter: I am not keen on using pidgin-indicator as that does not fit my needs as smoothly as the original icon behaviour does. For example, close to tray does not work with it, and I prefer hide/show on click, no walking through a menu.

Another application: hamster time tracker 1.04.

This bug is a regression from F25 and as such should be fixed.

Comment 13 Rex Dieter 2017-08-04 13:58:31 UTC
I don't see any systray icon from hamster... is there some option to turn it on?

Comment 14 Rex Dieter 2017-08-04 14:03:39 UTC
for what it's worth, I found this pygtk demo that works:
https://gist.github.com/pklaus/304963

Comment 15 Rex Dieter 2017-08-04 14:18:35 UTC
per comment #3, I suspect the real problem here is xembedsniproxy crashes on login, and there are some other bugs tracking that already, likely bug #1461576

Comment 16 Hynek Mlnarik 2017-08-04 14:50:11 UTC
FWIW, I can see the icon from the pygtk demo when I manually start xembedsniproxy but not when it is not running. I don't have any reports in abrt on crashing SNI proxy (though I have some unrelated ones on irregular crashes of plasmashell - "Process 17772 (plasmashell) crashed in ??()").

The bug 1461576 might be related but while that one seems to be fixed in 5.10.3, I am experiencing this issue in 5.10.4 (plasma-workspace-5.10.4-1.fc26)

Comment 17 Rex Dieter 2017-08-04 14:53:23 UTC
OK, all the crash traces we have so far is only from 5.10.1, so ideally we'd need a new trace with the latest versions to try to debug this further.

Comment 18 Hynek Mlnarik 2017-08-04 14:59:41 UTC
It seems that SNI proxy is just not started on Plasma start, hence I have no trace to share. Can I confirm this anyhow? Does it use only xembedsniproxy or is it some other way? If the former, I can confirm I don't have xembedsniproxy started after logon. If the letter, how can I do that?

Comment 19 Hynek Mlnarik 2017-08-04 15:00:38 UTC
s/letter/latter/

Comment 20 Rex Dieter 2017-08-04 15:20:48 UTC
It's supposed to autostart with your session, see
/etc/xdg/autostart/xembedsniproxy.desktop

Comment 21 Pavel Raiskup 2017-12-19 07:32:48 UTC
F27 seems to be fine, btw.

Comment 22 Fedora End Of Life 2018-05-03 08:11:40 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 23 Fedora End Of Life 2018-05-29 11:30:53 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.