[Bug]: Linux X11 to Windows 10 guest clipboard fails – VERR_TIMEOUT (7.2.20 and 7.2.22)

Ouverte
  • Quelque chose ne va pas ?
#957 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
c, linux
Domaine
desktop, operating-systems

Piste de recherche

Start with the shared clipboard implementation for the Linux X11 host and Windows guest, then inspect the VBox.log entries for VERR_TIMEOUT, VERR_SHCLPB_NO_DATA, and VERR_TRY_AGAIN. Use the supplied reproduction steps to trace host-to-guest text transfer while checking that guest-to-host transfer still works. Done means newly copied Linux text reaches Windows reliably under the reported setup.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug
Version

7.2.22

Host OS Type

Linux

Host OS name + version

Linux Mint 22.3 Zena, X11, kernel 7.0.0-42-generic (previously 7.0.0-38-generic)

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 10 22H2 x64, build 19045.6466

Component

Guest Additions/Shared Clipboard

What happened?

Shared clipboard synchronization from a Linux Mint 22.3 X11 host to a Windows 10 guest does not work reliably.

Expected behavior: Text copied on the Linux host should become available in the Windows guest when bidirectional clipboard sharing is enabled.

Actual behavior: Windows retains previously copied Windows clipboard content and does not receive newly copied Linux text. The reverse direction (Windows to Linux) generally works.

The issue occurs with both VirtualBox 7.2.20 and 7.2.22, including matching Guest Additions and Extension Pack versions.

Steps to reproduce:

  1. Start a Windows 10 VM with bidirectional clipboard enabled.
  2. On the Linux host, run:
    printf 'X300_TEST_PRENOSU_12345' | xclip -selection clipboard
  3. Verify that the text is present in the Linux clipboard.
  4. In Windows, run:
    powershell -NoProfile -Command "Get-Clipboard -Raw"

Result: Windows returns old clipboard content instead of X300_TEST_PRENOSU_12345.

The VBox.log file repeatedly contains:

  • VERR_TIMEOUT
  • VERR_SHCLPB_NO_DATA
  • VERR_TRY_AGAIN

Restarting VBoxTray.exe, switching clipboard modes, and restarting the VM have not reliably resolved the issue.

The Linux clipboard itself works normally, with a measured local read time of approximately 7 ms.

A full VBox.log captured during the failure can be provided.

How can we reproduce this?

  1. Start VirtualBox 7.2.22 on Linux Mint 22.3 with an X11 session.

  2. Start a Windows 10 x64 guest with Guest Additions 7.2.22.

  3. Set Shared Clipboard to Bidirectional.

  4. Copy some text inside Windows and verify that it can be pasted into Linux.

  5. On the Linux host, execute:

    printf 'X300_TEST_PRENOSU_12345' | xclip -selection clipboard

  6. Verify the Linux clipboard using:

    xclip -selection clipboard -o

  7. In the Windows guest, execute:

    powershell -NoProfile -Command "Get-Clipboard -Raw"

Expected: Windows returns X300_TEST_PRENOSU_12345.

Actual: Windows returns the previous Windows clipboard content. The new text from Linux is not transferred.

The issue also occurs when copying text from a regular Linux text editor. Restarting VBoxTray.exe does not reliably resolve the problem.

X300_VirtualBox_anonymizovane_logy_20261105.zip

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Langage dominant
C
Étoiles
1.4k
Forks
219
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de VirtualBox/virtualbox

Toutes les issues de VirtualBox/virtualbox

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.