Devices not showing up and out of screen menu

Hello, i have a couple of issues this time.
After having the server running for a while, some of the devices reset their names and 4 of them disconnected.
I dont know if anyone touched the setup, but the names should not just reset out of nowhere. I cant recreate the issue as i dont know what happened. Log files didnt really tell me anything.
The 4 that disconnected are all in the same hub, but they show as connected on the server side.
Second problem: I tried to open the server properties to see if maybe someone ignored them, but when i open the window, i think it opens off screen.
At least i cant see the window, and as its a sub-window of the main program, if i try to show it i just show the main client instead. Meaning i cant use it at all, and i have to force close it if i want to use the client again.

#2

A restart seemed to fix the 4 devices that disconnected, but i would still like to know what might have caused it

#3

Is this a windows or linux server?

#4

Think we found the reason for the disconnect, still curious about the names getting lost.
Are the names bound to the bus or the device id? And why would it change in either case

#5

The names are bound to the serial number of the usb device. (In the VirtualHere client, right click on the device and select Properties and see if there is a SERIAL line)

Do the devices have serial numbers?

#6

Yes, all the devices seem to have serial numbers, so i dont really understand how it just forgot the names of 1/3 of the devices out of nowhere.

The opening property windows outside the screen seems to be when i only run one monitor instead of two. Its an easy workaround, but the main issue is that there is no way to get it back on the screen once its open. If i cascade windows, it just cascades the base window and not the properties window.
Not a real issue, but i thought you should know anyways.

#7

Seems like some hardware issue, virtualhere just wont lose any settings. If it happens next time, just email me the syslog to mail [at] virtualhere.com (mail[at]virtualhere[dot]com) and hopefully that shows some kernel message or error