search

winapps-org / winapps

The winapps main project, forked from https://github.com/Fmstrat/winapps/
Other
998 stars 45 forks source link

Applications cannot be opened from Application menu on KDE #89

Closed kaanchinar closed 4 months ago

kaanchinar commented 5 months ago

I freshly installed and configured my win10 VM with winapps. All programs work fine via terminal.

winapps word-o365-x86

Hovewer, when I attempt to start same program from Application menu, I appears on my taskbar for a second, then disappears without any screen and error.

How can I solve that issue?

Using Arch Linux with FreeRDP 2 and KDE Plasma 6

oskardotglobal commented 4 months ago

Did you try manually checking what command the desktop files attempt to run? Maybe it's an issue with the path to the executable?

kaanchinar commented 4 months ago

Did you try manually checking what command the desktop files attempt to run? Maybe it's an issue with the path to the executable?

I did. Changed chmod, edited .desktop entries with different combinations (with sudo command, direct path etc.) but no success.

oskardotglobal commented 4 months ago

Can you try this again with the latest commit?

oskardotglobal commented 4 months ago

Also, please upgrade to freerdp3

oskardotglobal commented 4 months ago

Moving this to #104

Sithuk commented 2 months ago

I am experiencing the same issue with a fresh install from the master. I'm on Arch. The Exec command line works perfectly from the terminal. The menu item fails silently.

Journalctl reports "ERROR: WINDOWS NOT RUNNING." and "Exiting with status '4'."

Sithuk commented 2 months ago

I've tracked the issue down to the waCheckVMRunning function by uncommenting "set -x" in the winapps script and checking journalctl.

The waThrowExit function is triggered. I have logged "virsh list" output to a text file from within the script and can see that "virsh list" isn't outputting the name of the running VM. I'm not sure why. I added a "whoami" check just before the virsh list command and it reported my user. So I'm not sure what the issue is.

! virsh list --state-running --name | grep -q "^${VM_NAME}$" && waThrowExit "$EC_NOT_RUNNING"

I have freeRDP3. I am on plasma 6 but am not using Wayland.

Sithuk commented 2 months ago

@oskardotglobal : Please can you re-open this issue? I'm experiencing the issue and I've provided some new debugging info above.