[Bug]: Electron shows duplicate tray icons
lukehmcc opened this issue · comments
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Electron Version
19.0.6
What operating system are you using?
Other Linux
Operating System Version
Fedora 36
What arch are you using?
x64
Last Known Working Electron version
19.0.6
Expected Behavior
When creating a standard electron tray on a platform that both supports libappindicator and GtkStatusIcon, electron should chose one type of indicator to display and put it in the tool bar.
Actual Behavior
Both the native libappindicator and the GtkStatusIcon get added to the toolbar as shown below:
The first one being libappindicator:
The second one being GtkStatusIcon:
Testcase Gist URL
No response
Additional Information
No response
Thanks for reporting this and helping to make Electron better!
Please use Electron Fiddle to create a standalone (no external dependencies) testcase and publish it as a gist, then link to it here.
Even if you have a code snippet or a git repository that show the testcase, please put it in a gist. This lets maintainers triage issues more effectively. It also ensures that we're testing the exact same issue that you're seeing!
Please avoid external dependencies in the test. The Electron team is small and generally doesn't have enough bandwidth to triage third-party code. Also, standalone tests are easier to adapt into regression tests.
If the bug you've found can be tested with a pass / fail test, please make the testcase exit 0 on success or nonzero on failure. This lets Electron's issue bot see what releases are affected by the bug.
I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to the gist in a followup comment.
Thanks in advance! Your help is appreciated.
We haven't gotten a response to our questions in our comment above. With only the information that is currently in the issue, we don't have enough information to take action. In this event, i'm going to go ahead and close this but can reopen should you follow up with more info!