feat: Cleanup Qt-based tray implementation

[Kishi85]

Description

This reworks the Qt-based tray with an adapted version of QtTrayMenu.h/cpp from upstream as suggested in LizardByte/Sunshine#4907.

This version restores libnotify for notifications due to potential problems caused by DBus interface limitations when running with elevated privileges (e.g. as used by Sunshine). The new libnotify integration also tries to separate the used codepaths as best as possible to keep the implementation clean and easily understandable (with a fallback to basic notifications using QtTrayMenu::showMessage).

There is still an issue with left clicking the tray icon on Wayland (also present in the current AI based implementation) which caused by https://qt-project.atlassian.net/browse/QTBUG-139921 that can unfortunately not be worked around.

This version is platform-neutral for QtTrayMenu.h/cpp code with Linux platform-specific parts (and libnotify integration) restricted to tray_linux.cpp. Qt-provided features are used as much as possible to keep this platform-independent.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[codecov]

Codecov Report

❌ Patch coverage is 59.23345% with 117 lines in your changes missing coverage. Please review.
✅ Project coverage is 63.90%. Comparing base (fc343dc) to head (6f718bc).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/QtTrayMenu.cpp	53.53%	59 Missing and 33 partials ⚠️
src/tray_linux.cpp	71.91%	10 Missing and 15 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
+ Coverage   63.51%   63.90%   +0.38%     
==========================================
  Files           4        5       +1     
  Lines         858      615     -243     
  Branches      313      199     -114     
==========================================
- Hits          545      393     -152     
+ Misses        207      150      -57     
+ Partials      106       72      -34     

Flag	Coverage Δ
Linux-qt5	52.94% <59.23%> (-4.18%)	⬇️
Linux-qt6	52.94% <59.23%> (-4.18%)	⬇️
Windows	70.67% <ø> (ø)
macOS	58.40% <ø> (+0.88%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/tray_linux.cpp	62.18% <71.91%> (+2.72%)	⬆️
src/QtTrayMenu.cpp	53.53% <53.53%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc343dc...6f718bc. Read the comment docs.

[Kishi85]

I've fixed most of the issues I've found so far (added all the necessary pointer valid checks/etc. and moved the exit() order around so everything gets cleaned up in reverse order (clearing references as necessary on the go). But no matter what I do the CI pipeline segfaults at this one specific test:

[ RUN      ] TrayTest.TestCheckboxStates
/home/runner/work/_temp/d5b937f4-9556-4df2-8f27-571e2cb10ca8.sh: line 1:  8581 Segmentation fault      (core dumped) ./test_tray --gtest_color=yes --gtest_output=xml:test_results.xml
Error: Process completed with exit code 139.

I can run all the tests fine locally after I've added support for spectacle screenshots due to using KDE, tests running both with clang and gcc compiled project. It just wont complete when run on the CI-container with ubuntu-latest. I'm a bit out of ideas here and it looks like I have to test this on a native Ubuntu-latest install at some point to continue this further.

[ReenigneArcher]

@Kishi85 have a look at #123

[Kishi85]

@Kishi85 have a look at #123

I'll pick that test change if you dont mind as it IMHO makes more sense logically

[Kishi85]

Also the change you did for showing the menu on wayland in #123 does not work. Same issue as with show() due to that bug in Qt:
qt.qpa.wayland: Failed to create grabbing popup. Ensure popup QWidgetWindow(0x55c3cc28b8c0, name="QMenuClassWindow") has a transientParent set and that parent window has received input.

Looks like the only way to get left-click to work on Linux/Wayland is for Qt to fix the bug, every other workaround either fails silently or yields above message unfortunately.

[Kishi85]

One main deficit of the QSystemTray::showMessage notification is that it does not hide immediately when you click it even if it triggers the callback. Neither can you programmatically close the message via the trayIcon object hence the screenshots showing multiple balloons due to tests firing in rapid succession.

After looking around for a bit the best thing (in terms of interoperability and functionality) seems to be using libnotify just for the notifications (as the XDG desktop notification path is not really viable due to the process privilege constraints).

Good thing here is that now that most of the Qt Tray Menu stuff is now isolated, it should be easy to do something similar for notifications and have a clean implementation.

[ReenigneArcher]

I think 1500 is fine. I'm guessing the windows runner is pretty resource constrained, because the 500ms was enough for me locally. If we make the delay too high, I think the notification will fade away before the screenshot is taken.

[ReenigneArcher]

Somehow that change reverts it 🤔

[Kishi85]

Curious. I did a test run with 1500ms and it worked: https://github.com/Kishi85/tray/actions/runs/26105012151/artifacts/7086987459

So that might just be the spot where it turns around. Guess I'll bump it to 2000ms then and try again.

EDIT: Still working with 2000ms for me: https://github.com/Kishi85/tray/actions/runs/26114068759/artifacts/7090855706

[ReenigneArcher]

[Kishi85]

That is a weird timing issue? or is something acknowledging the notification by accident from the windows side? Would be interesting to have a screencapture of the whole CI run to see what is really happening but that's a bit out of scope for this PR.

[ReenigneArcher]

Agreed. At least I not know it's possible to show it in the GitHub runner.

[ReenigneArcher]

This is pretty close I think. After this iteration, I think it would be good to make a PR into Sunshine as well. Either into LizardByte/Sunshine#4907 or replacing it with the updated tray commit (can be a temporary commit until this PR is merged). This way it will be easier for testers to give it a try using Sunshine.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Kishi85]

This is pretty close I think. After this iteration, I think it would be good to make a PR into Sunshine as well. Either into LizardByte/Sunshine#4907 or replacing it with the updated tray commit (can be a temporary commit until this PR is merged). This way it will be easier for testers to give it a try using Sunshine.

Not sure the temporary commit on third-party/tray will work as you'd have to explicitly request the pull (git fetch origin refs/pull/121/head) to have access to it in the submodule (since it's otherwise just in my fork). I'll test it anyway, just a heads up that this might be an issue.

[ReenigneArcher]

You can just point the submodule to this commit. I'm fairly certain it will work