[Bug]: Shared clipboard fails on RHEL 10 GNOME (XWayland) guest – X11 backend chosen but libXt/libXmu not installed

Abierto
  • ¿Algo no está bien?
#914 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux
Área
desktop

Línea de trabajo

The failure comes from the X11 clipboard backend (shclx11) when VBoxClient --clipboard -f -vvv runs under XWayland and fails to dlopen libXt.so.6. Start with the clipboard service code that selects the X11 backend and the dlopen call that logs the error, and check how the RHEL guest-additions package declares its X11 dependencies. Done means either a clean fallback or an actionable error when libXt/libXmu are missing, confirmed by the reproduction steps on a RHEL 10 GNOME guest.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Version

7.2.20

Host OS Type

Windows

Host OS name + version

Windows 11 Build 26100

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Red Hat Enterprise Linux 10.2

Component

Guest Additions/Shared Clipboard

What happened?

Shared clipboard does not work in a RHEL 10 guest with a default GNOME (Wayland) desktop, although Guest Additions install successfully and Shared Clipboard is set to Bidirectional.

VBoxClient --clipboard -f -vvv fails with:

shclx11 rtldrNativeLoad: dlopen('libXt.so.6', RTLD_NOW | RTLD_LOCAL) failed: libXt.so.6: cannot open shared object file: No such file or directory
How can we reproduce this?
  1. Install RHEL 10.x with the default "Server with GUI" or "Workstation" environment (GNOME, Wayland only).
  2. Install Guest Additions 7.2.20 (with kernel-devel, gcc, make, perl etc. so the modules build).
  3. Set Devices → Shared Clipboard → Bidirectional, then reboot and log in to GNOME.
  4. Confirm rpm -q libXt libXmu reports both as not installed.
  5. Copy text on the Windows host and try to paste in the guest (and the reverse): nothing is transferred.
  6. Run VBoxClient --clipboard -f -vvv: session type is detected as XWayland, the X11 backend is chosen and fails to dlopen libXt.so.6.
Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Lenguaje dominante
C
Estrellas
1.4k
Forks
219
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VirtualBox/virtualbox

Todos los issues de VirtualBox/virtualbox

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.