You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Third party (AUR, Docker, Chocolatey, etc. Specify in comments)
Install and OS comments
Using the official Docker release
Bug description and reproduction
The official Docker release uses FVWM which does not have a system tray. However, options > system tray > "Close the main window to system tray" is enabled by default, with no way to change the option because the options are disabled when there is no system tray. This means that closing the window results in being completely unable to bring the window back up until the Docker is restarted.
This also means if you replace the database with one that has "Start minimized to system tray" enabled there will be no way to bring up the client window.
Log output
No response
The text was updated successfully, but these errors were encountered:
That setting defaults to false so I think it's because the db you loaded in has it set but it is still an issue if you move the db to a machine without a system tray without turning it off first.
Hydrus version
v580
Qt major version
Qt 6
Operating system
Linux (specify distro and version in comments)
Install method
Third party (AUR, Docker, Chocolatey, etc. Specify in comments)
Install and OS comments
Using the official Docker release
Bug description and reproduction
The official Docker release uses FVWM which does not have a system tray. However, options > system tray > "Close the main window to system tray" is enabled by default, with no way to change the option because the options are disabled when there is no system tray. This means that closing the window results in being completely unable to bring the window back up until the Docker is restarted.
This also means if you replace the database with one that has "Start minimized to system tray" enabled there will be no way to bring up the client window.
Log output
No response
The text was updated successfully, but these errors were encountered: