TL;DR: If I open Chrome or Edge with GPU acceleration enabled inside a Winboat Windows instance, the Winboat app crashes, and permanently breaks resizing for certain windows outside of Winboat (freerdp, the Winboat app itself and Discord) until I log out or reboot, including after re-launching Winboat and Discord.
Layout:
- Laptop with Intel 255HX CPU/RTX 5070 GPU
- Kernel 7.0.5-2
- Plasma 6.6.4
- KWin/Wayland with xwayland
- winboat 0.9.0-9
- discord 1:1.0.137-1
- freerdp 2:3.26.0-1
- 2560x1600 with fractional scaling at 135% (tested with standard resolution too, same issue)
Steps:
- log in to Plasma desktop
- (optional) launch Discord
- launch Winboat
- (optional) launch the Windows desktop
- launch Chrome or Edge without disabling GPU acceleration first (enabled by default on first install)
The freerdp instance should crash, and take the Winboat desktop app with it - the container will continue to run, and if you use btop or another process checker, you might see Winboat still running in the background. If Discord is running, it may also crash at the same time as Winboat.
The really weird part is, if you re-launch either the Winboat app or Discord, you can no longer maximize or resize either window. If you can re-launch Winboat, attempting to open another desktop session may result in either freerdp not being full screen, or if Edge/Chrome is still running, it’ll just crash Winboat (and Discord) again.
The only resolution is to stop the Winboat container either from the app or command line, then logging out or rebooting.
Anyone else see this issue? Any idea where I can look for diagnosing it?