I am seeing some strange behavior with the latest 4.10 client.
If I try and start the usbarbitrator service during init, it will segfault.
A subsequent run will successfully start.
If I don't try during init, and just manually kick off the service after boot finishes, it also works
It only seg faults if I try during init.
This is different behavior than 4.9, which always worked.
What version of linux are you using?
4.14.91
Not the linux kernel version, sorry I meant what distribution?
You may want to open a support ticket directly if you can, that's not on the list of the supported os for 4.10, and you might not get a VMware response directly here. I don't see thin station anywhere, and I've never used with horizon.
Hmmm. Yeah, I doubt the linux version is relevant here or the distribution. This looks like a memory leak in the C.
