(29-Jun-2021, 06:48 AM)agent_kith Wrote:(29-Jun-2021, 12:20 AM)Primare11 Wrote: I also notice one thing, have you changed the windows manager to IceVM since Snakeiol 1.1, wasn't another windows manager used then?That means it's not a CPU extension that is causing the issue. Look under graphics and see if you can either:
If yes, can that be the problem?
II did an search on Jriver and segfault and found this: https://yabb.jriver.com/interact/index.p...#msg707248
It's quite old, but they talk about a display driver, has that been updated in Snakeoil 1.2?
I will try to test some more during the week.
1. Pass through your graphics card into this VM (make sure IOMMU is enabled)
2. Enable 3D graphics
See if JRiver will behave properly now in a VM. If all else fails you probably have to run this without virtualisation.
In theory JRiver can do some checks to make sure it has all it's hardware it needs and not seg fault like this. Look for any JRiver log file and see if actually says what the problem is.
Snakeoil always have been using IceVM. It's kind of a bad windows manager, but it's quick to load up and have minimal memory resources, and have a GUI that is more or less usable.
In VMware the following is already set:
- IOMMU
- Accelerated 3D graphics
It is working in VMWare in Ubuntu 20.04 mini, that has the exact same vmware settings, the only difference should be that there is a desktop environment installed right and some package in that desktop environment is what Jriver needs to start, right?
But the next step will to see if it works in real PC.