winapps-org / winapps

The winapps main project, forked from https://github.com/Fmstrat/winapps/
544 stars 26 forks source link

Main install script fails while manual run with exe path works fine. #106

Open Xarishark opened 1 month ago

Xarishark commented 1 month ago

I am having the same problems. Here is the check results: image

Here is the installer results: image

Reg is working and I can rdp fine with remmina and novnc. Check is also working as you can see. I will be happy to try anything you tell me to make it work. office 365 is already activated and installed and I have a full win11 install from your yaml

running the "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE" manually works but I have the top bar cut(minimize close etc)

Edit: Another bug I have is the window is freaking out when maximized or I try to resize it but I count that as an nvidia wayland weirdness with KDE

EDIT2: Removing the quotes on sudo and forcing the user flag returns this error for line 50: image

Originally posted by @Xarishark in https://github.com/winapps-org/winapps/issues/103#issuecomment-2137720226

DesNZ commented 1 month ago

Edit: Another bug I have is the window is freaking out when maximized or I try to resize it but I count that as an nvidia wayland weirdness with KDE

@Xarishark I've had issues like that before, have a play with some xfreerdp flags relating to graphics.

LDprg commented 1 month ago

I just want to note that wayland isn't currently supported until the sdl version of freerdp3 supports app streaming. So you expect weird bugs (especially related to window rendering).

LDprg commented 1 month ago

Is this maybe related to #104 ?

oskardotglobal commented 1 month ago

107 should fix the error, but not the jankiness; that's probably due to wayland

Alchemi1963 commented 1 month ago

I found that the installer.sh script was to blame; printf works differently than echo (as used by Fmstrat).

Explained this in #104 as well.

Wrote a fix for it (at least, it worked for me). Pull request is pending. @Xarishark I forked the repo on my profile (to create aforementioned pull request), you can probably try that to see if it fixes your problem