LDprg
commented
4 months ago @b1rkenwald are you using wayland? Wayland isn't compatible with winapps (will change in future).
Open b1rkenwald opened 4 months ago
LDprg
commented
4 months ago @b1rkenwald are you using wayland? Wayland isn't compatible with winapps (will change in future).
b1rkenwald
commented
4 months ago The issue persists on x11/x-org. It might be an issue with Fedora, since both of my devices run on F40.
LDprg
commented
4 months ago @b1rkenwald Is the error log with x11 the same? Because the log you posted is about the window creation failure (which would be a typical wayland problem).
Can you also post a neofetch of you system for basic info.
Also try connecting to the vm by using the freerdp command directly.
MrTumnis
commented
4 months ago I use Fedora 40 and have run into the same issue. I noticed that the black screen happens when logged into the VM. I had to make sure I was not signed in from using a rdesktop or even xfreerdp in the command line.
b1rkenwald
commented
4 months ago The error log was the same, however, I have now got it to work using Wayland! Fedora users (especially those using Wayland) have to make sure to install the freerdp version that I mentioned above and change the winapps.conf. This version automatically uses xfreerdp instead of the normal freerdp. I also had to remove any trace of the normal freerdp. I can elaborate, if needed. I could also sum it into a guide, if you'd like. But now, everything works as it should!
Is there any way to enable copying from the clipboard between host and guest? Installing the virtio-guest-tools bricked the whole installation.
MrTumnis
commented
4 months ago Are you using workstation or atomic? I am curious what you mean by "remove all traces of freerdp." Also, I looked at their script and the clipboard setting is already integrated. I have not had issue using the clipboard myself.
SmileYik
commented
4 months ago The black full window appears to be generated because the login user specified by winapps has already logged in to the session through other means (such as virt-manager, other rdp clients), causing Windows to ask the user to choose whether to continue logging in to Windows with the current user after the user logs in normally.
I am using xfreerdp3 command, and when I encounter a black window, I will change command to wlfreerdp3, and run bin/winapps check to click the yes button to ensure i can login Windows. then change command back to xfreerdp3, and all things as normal. (by the way, when i using wlfreerdp3 command, it will freeze my computer, and i need to login other tty to killall wlfreerdp3 process)
I don't know the details but this way seems work for me.
KernelGhost
commented
3 months ago I use Fedora 40 (XFCE) with the X11 window system and have experienced this issue before. To resolve it, I had to run kill -9 $(pgrep xfreerdp). This problem reliably occurs when trying to use WinApps while the Windows user is logged in, and it can be avoided by ensuring the Windows user is not logged in during usage.
0verEngineer
commented
1 month ago Maybe the docker/podman setup readme has to be changes because i was logged in on the web novnc console and this was the issue for the blacksceen
FYI: I had to use a normal win11 img because the tiny11 download kept failing.
My compose.yaml looked like this:
The docker vm is fully operational. My winapps.conf is this:
I'm using the "freerdp-3.5.1-1.fc40.x86_64.rpm" package from the Fedora repo.
Whenever I use bin/winapps check, it opens a black screen on both monitors. After this, the terminal has to be force-closed in order to restore functionality. This is the bin/winapps check ouput:
Edit: I already tried deleting the certificate and creating it again. Output is the following: