Bug 1463252
Summary: | Plasma tray bar does not show GTK application icons | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hynek Mlnarik <hmlnarik> |
Component: | plasma-desktop | Assignee: | KDE SIG <kde-sig> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | 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
> 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.
Same bug for me : Skype, Thunderbird, Nut icons don't show up ! Starting /usr/bin/xembedsniproxy fixes the problem for me. Thanks for the workaround - xembedsniproxy fixes the issue for me as well. Hope it would be possible to get this fixed properly Unfortunately, I think the "proper fix" would only mean running xembedsniproxy automatically. 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). A workaround that works for me is to configure KDE too have xembedsniproxy runing at launch. System settings -> start / stop I believe this can be related: https://retrace.fedoraproject.org/faf/reports/1745795/ It happens to me every time I login into plasma. It seems that the latest update to plasma (5.10.4) resolved the issue for me. Does not seem to be resolved for me with 5.10.4, I have to run xembedsniproxy manually to see GTK icons in traybar. 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? @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. I don't see any systray icon from hamster... is there some option to turn it on? for what it's worth, I found this pygtk demo that works: https://gist.github.com/pklaus/304963 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 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) 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. 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? s/letter/latter/ It's supposed to autostart with your session, see /etc/xdg/autostart/xembedsniproxy.desktop F27 seems to be fine, btw. 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. 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. |