Skip to content

VMWare Window Crash: Info on libx11-6 and recent kernel changes with 6.19.11 - fix included #21

Description

@mmattel

Debian 13 (trixie) using Backport (applies to other distros too),
VMWare 17.6.4 (applies also to more recent versions 25h.x)

I updated the kernel from 6.19.10 to 6.19.11 and when starting a VM, shortly after the VMWare window crashed, the VMs continued to run. journalctl -f showed the following:

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 10060 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.)

After searching around, I found that the "culprit" is the current libx11-6 library with installed version 2:1.8.12. A fix has been provided with version 2:1.8.13 which is at the time of writing in testing stage (package forky), see: https://packages.debian.org/forky/libx11-6

After manually downloading the libraries and updating them with:
sudo dpkg -i libx11-6_1.8.13-1_amd64.deb,
sudo dpkg -i libx11-xcb1_1.8.13-1_amd64.deb
I do not have any more issues with crashing VMWare windows.
The filenames depend on your architecture.

If you want to revert, just download the former version (1.8.12-1) and install them as shown above.

@Hyphaed maybe you find a way how this info could be noted in your build output helping desperate users fixing it.
BTW, get back healthy soon, all the best !

For interested readers:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/293
https://lists.x.org/archives/xorg-announce/2026-February/003669.html

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions