Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix master issue 1306 (system-tray icon) and releated "missing icons" issues #1480

Merged
merged 11 commits into from
Jul 17, 2023
Merged

Fix master issue 1306 (system-tray icon) and releated "missing icons" issues #1480

merged 11 commits into from
Jul 17, 2023

Conversation

aryoda
Copy link
Contributor

@aryoda aryoda commented Jul 17, 2023

Candidate to fix all major sys-tray icon and missing app icon issues (#1159, #1236, #1306, #1364).
Refactor qtsystrayiconplugin.py

@buhtz After merging this you can refactor icon.py (thanks for waiting for my PR to avoid merge conflicts :-)

* Fix bug: Unit test fails on some machines due to warning "Ignoring XDG_SESSION_TYPE=wayland on Gnome..." (#1429)
* Fix bug: Generation of config-manpage caused an error with Debian's Lintian (#1398).
* Fix bug: Return empty list in smartRemove (#1392, Debian Bug Report 973760)
* Breaking change: Minimal Python version 3.8 required (#1358).
* Feature: Exclude /swapfile by default (#1053)
* Documentation: Removed outdated docbook (#1345).
* Build: Introduced .readthedocs.yaml as asked by ReadTheDocs.org (#1443).
* Dependency: The oxygen icons should be installed with the BiT Qt GUI since they are used as fallback in case of missing icons
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This info should be added to the README.md. There it is where distro maintainers pick up this information.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I forgot that :-)

I will add this ASAP

I would also like to keep it in the CHANGES since this is what pkg maintainers do read first I guess (not the diff of the README)

common/tools.py Outdated

logger.debug(f"Qt5 probing result: exit code {proc.returncode}")

if proc.returncode != 23: # if some Qt5 parts are missing: Show details
Copy link
Contributor Author

@aryoda aryoda Jul 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Damn, I forgot to remove my testing code. Will follow up on this with a new commit...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it has to be this way. Some more verbose logging in such a complex situation isn't bad.

# TODO Is this really required? If the client is not configured for X11
# it may use Wayland or something else...
# Or is this just required when run as root (where GUIs are not
# configured normally)?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know, sorry. ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I keep this comment for the future

@@ -56,7 +60,7 @@ def __init__(self):
self.qapp.setQuitOnLastWindowClosed(False)

import icon
self.icon = icon
self.icon = icon # What does this code do? Make the import accessible?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.
It is the same in app.py's MainWindow.
Let's keep it that way until next refactor session.

Copy link
Member

@buhtz buhtz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice. Well done. High quality docu.

@buhtz
Copy link
Member

buhtz commented Jul 17, 2023

(#1159, #1236, #1306, #1364)

I assume the merge will close all this issues because of your commit messages. It is OK for me.

But maybe we should re-open the issues immediately and ask the reports for feedback?

@aryoda
Copy link
Contributor Author

aryoda commented Jul 17, 2023

I assume the merge will close all this issues because of your commit messages. It is OK for me.
But maybe we should re-open the issues immediately and ask the reports for feedback?

Yes, I will re-open them if auto-closed, but I tried to avoid this by not directly using the "fix"... keyword followed by the issue numbers. Let's see what github does here...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants