Did a round of updates to my Linux host last night. This morning I fire up my daily-use Windows VM guest and the VMware Workstation GUI keeps closing with no warning. From vmware.log:
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="vmx"] VmdbPipeStreamsOvlError Couldn't read: (104) Connection reset by peer.
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] SOCKET 5 (177) recv error 104: Connection reset by peer
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControlMgr: MKSControl Socket Error: (1) Asyncsocket error.
2025-10-24T14:26:49.312Z -WARNING vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControl: Error: (1427)
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControlMgr: MKSControl error
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControlMgr: Dropping MKSControl error due to prior unresolved error.
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="vmx"] VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (-32)
2025-10-24T14:26:49.312Z -WARNING vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControlMgr: MKSControl Error: Disconnecting from UI
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] MKSControlMgr: disconnected
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="vmx"] SOCKET 4 (178) recv detected remote shutdown
2025-10-24T14:26:49.312Z -INFO vmware-vmx 20638 [ws@4413 threadName="vmx"] Vix: [mainDispatch.c:2771]: VMAutomation: Connection Error (4) on connection 0.
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] SWBWindow: Window 0 Destroyed DESTROYED: src screenId=-1, src xywh(0, 0, 1024, 768) dest xywh(0, 0, 1024, 768) pixelScale=1, flags=0x HAS_HOST_ORIGIN ALLOW_MKS_GRAB IS_RENDERING
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="vmx"] VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] SWBWindow: Window 1 Destroyed DESTROYED: src screenId=-1, src xywh(0, 0, 1024, 768) dest xywh(0, 0, 2314, 1736) pixelScale=1, flags=0x HAS_HOST_ORIGIN LIMIT_REFRESH_RATE
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] MKS-HWinMux: Backend Switch Queued
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] XINFO: Disconnecting
2025-10-24T14:26:49.313Z -INFO vmware-vmx 20638 [ws@4413 threadName="mks"] XConnection: Closing console display
From the system journal:
Oct 24 10:35:10 cachyos vmware-tray[20873]: The program 'vmware-tray' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 1648 error_code 2 request_code 135 (XKEYBOARD) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Oct 24 10:35:10 cachyos vmware[21716]: The program 'vmware' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 5879 error_code 2 request_code 135 (XKEYBOARD) minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
This is on a host using Wayland. The VM keeps running; it's just the VMware WS GUI that drops out.
Anyone else seeing this?
-------------------------------------------