Arch Linux User Repository

New package version released: 25H2-4

Changelog:

• Thanks for the feedback as usual. This version fixes the DKMS old/new kernel detection. While i was doing bit of cleanup to onboard the new 25H2 version by mistake I lost one patch which was vital for allowing new kernels to be build on top of new headers. Issue was that the default Makefiles from vmware always considered the running kernel the one used to build modules, while if you're in the middle of an upgrade you want to build it for the new version ( a custom flow however introduced by pacman and libalpm ). Anyway, long story short this behavior is back again and starting this version you should be able to upgrade without trouble ( and probably this fixes as well the other reports I've seen around CachyOS ).

Enjoy!

After the first installation, please:

1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...

2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)

3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :

• vmware-networks: to have network access inside VMs

• vmware-usbarbitrator: to connect USB devices inside VMs

Dev of libxkbcommon here. Could you help debugging the issue at https://github.com/xkbcommon/libxkbcommon/issues/888?

@manywolves I can confirm, downgrade and re-login fix this error.Well I used test repositories and the first version 1.12.0-1 was for me 10 days ago. Then I didn’t have time to find the source of the problem and I assumed that the cause was in Plasma 6.5 Beta, which I also tested.

[2025-10-11T18:27:59] [ALPM] upgraded libxkbcommon-x11 (1.11.0-1 -> 1.12.0-1)
[2025-10-11T18:27:59] [ALPM] upgraded libxkbcommon (1.11.0-1 -> 1.12.0-1)

good find @manywolves downgrading these two did solve the problem for me as well!

I have bisected the XKEYBOARD crash (when grabbing or ungrabbing input) issue over time down to the package. The problem appears to be introduced in extra/libxkbcommon version 1.12.2-1 released on October 20th (@indigokeriann and others, this should fix your issue).

Downgrading extra/libxkbcommon and extra/libxkbcommon-x11 to 1.11.0-1 resolved the problem for me. You may only need to downgrade one, but cautiously I downgraded both. So this doesn't seem to be a problem with this package itself.

Some bugs in KDE-Wayland ( 6.17.4-arch2-1 )

Crash the vmware app, but he VM is stay live.

systemctl -f

oct 22 16:07:11 DualXeon vmware[5669]: 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 1985 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.)

@JulianXhokaxhiu 4th revision builds perfectly, thanks, saves me fixing it :D

EDIT: seems that downgrading extra/libxkbcommon and extra/libxkbcommon-x11 to 1.11.0-1 solves the below issue. Thanks @manywolves

not sure if others experiencing, moving mouse in and out of any VM (that I tested) causes vmware window to crash. Atleast the VMs stay running... Here is the crash message from terminal:

Gdk-WARNING **: 17:33:45.793: 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 4334 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.)

I already wrote about this 10 days ago, some problem with xwayland and gtk3. just run vmware in console, to see error.

(vmware:417490): Gdk-WARNING **: 00:29:37.439: 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 23821 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.)

In Arch, since kernel 6.17, Wayland, Vmware GUI crashes if i click or move the mouse inside the running VM.

@investigato: yes, i have the same issue since updating kernel to 6.17.4-4. Uninstall and reinstall of vmware workstation doesn't help. Vmware GUI crashes if i click or move the mouse inside the running VM. I am using CachyOS.