-
-
Notifications
You must be signed in to change notification settings - Fork 129
Open
Description
The emailproxy GUI seems to have issues in the Wayland environment, as follows:
Failed to dock icon
Traceback (most recent call last):
File "/usr/lib/python3.13/site-packages/pystray/_xorg.py", line 162, in _update_icon
self._assert_docked()
~~~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3.13/site-packages/pystray/_xorg.py", line 395, in _assert_docked
assert self._systray_manager
^^^^^^^^^^^^^^^^^^^^^
AssertionError
Failed to dock icon
Traceback (most recent call last):
File "/usr/lib/python3.13/site-packages/pystray/_xorg.py", line 143, in _show
self._assert_docked()
~~~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3.13/site-packages/pystray/_xorg.py", line 395, in _assert_docked
assert self._systray_manager
^^^^^^^^^^^^^^^^^^^^^
AssertionError
2025-12-09 14:53:23: Initialising Email OAuth 2.0 Proxy (version 2025-10-04) from config file /home/jack/emailproxy.config
2025-12-09 14:53:23: Email OAuth 2.0 Proxy config file not found - see https://github.com/simonrob/email-oauth2-proxy for full documentation and example configurations to help get started
2025-12-09 14:53:23: No server configuration(s) found in /home/jack/emailproxy.config - exiting
2025-12-09 14:53:23: No server configuration(s) found. Please verify your account and server details in /home/jack/emailproxy.config
2025-12-09 14:53:23: Stopping Email OAuth 2.0 Proxy
<emailproxy.App object at 0x7f2c118bfa10>
^C⏎
Why not consider using Qt or other GUI frameworks?
I'm looking forward to the official fix. Additionally, I have a few suggestions: it would be great if you could provide a dedicated command-line parameter to trigger OAuth2 authentication. Are there any plans for this? This would eliminate the need for trigger signals from third-party email clients.
Metadata
Metadata
Assignees
Labels
No labels