-
-
Notifications
You must be signed in to change notification settings - Fork 433
Description
What version of WinBoat are you running?
0.9.0
Your Environment
Linux Mint 22.2 Cinnamon
RDP (last from Flatpack)
Podman, Podman Compose
Deb Package
Steps to Reproduce / Context
-
When selecting a local disk image, the installation went through the Cloud anyway, and it was no longer possible to select the installation language (it is worth correcting the installation from the local image, and everything should be OK).
-
The container settings are available even when the container is active (it is worth making them unavailable when the container is active). If you try to change something, everything breaks down and the system cannot start the container, even if you reset the settings back. A complete reinstall of Winboat and Podman did not work. With the complete removal and new installation, I noticed that the amount of resources for the new container has decreased... and then I realized that there was an old container that reserves resources for itself. I found on the Internet: how to list containers and how to delete them. I deleted the inactive container, and everything started working as it should.
- When I finally launched Winboat and did not change the settings while the container was running, everything worked as it should. Logically, the first application I launched was "Windows Desktop". Everything was fine, and I installed all the apps I needed, and I was very happy because they were running and it was all working. After a couple of days, I wanted to launch the application through the "applications" section and, after trying to do this, I realized that they would not launch (a new window would not appear), I tried to launch other applications — the result is the same. So I tried running "Windows Desktop" again to check that the system was working at all. "Windows Desktop" started, but reported that another user was already connected to the system. I had an idea that the application in the container still started, but the remote session in the window did not open (HDD — showed that the download was underway, but the application did not open in the window). It is possible that the remote session opens only "Windows Desktop", and does not open other applications (I think this can be corrected).
- One more little thing: I have Linux Mint (if it's important) and a dark theme, so when I right-click on the application, I see a white menu with white text, when I hover over the menu items, I can make out the text, but it's visually unreadable.
- As an improvement, I would add a "Favorites" filter to the applications section, and the ability to add applications to this category, for example, through the context menu (we use only individual applications, we do not need a full list of applications and installers — it only hinders; this will improve navigation among "our" applications when the container is fully formed).
Logs
Expected Behavior
Current Behavior
Possible Solution
Quality Notice
- I have checked the issue tracker and verified that this bug is a unique case.