Copying/Paste from AlmaLinux 9 to Windows Host Broken

[agilis]

This issue/bug concerns AlmaLinux 9 using Standard (Wayland display server) AlmaLinux: ​https://almalinux.org is based off of RHEL.

The issue occurs when you copy text from GNOME Terminal or TextEditor (gedit) which are native applications in AlmaLinux. When the text is copied from these 2 applications (There may be others) and then pasted into a host running Windows, in my case Windows 10 Enterprise, the text has extra lines inserted between each line of text.

Screenshots of the behavior mentioned above as well as the thread discussing this issue can be found here:

​https://forums.virtualbox.org/viewtopic.php?t=109447&start=45

When AlmaLinux is set to run with Standard (Wayland display server), VirtualBox does not detect that Wayland is being used.

18:32:08.121654 main Package type: LINUX_64BITS_GENERIC 18:32:08.121659 main VBoxClient 7.0.8 r156879 started. Verbose level = 0. Wayland environment detected: no

When AlmaLinux is set to run with Standard (X11 display server), this issue regarding the copying and pasting of text is not present.

I will attach VirtualBox logs of both with and without Wayland being used.

I am unable to install test builds of VirtualBox due to the environment I work in. I can help troubleshoot if needed.

Thank you!

[agilis]

VBox Log with Wayland active.

[agilis]

VBox.log with X11 active.

[agilis]

I was unsure of the component for this issue. Please update the component as you see fit.

[fth0]

FWIW, the resulting EOLs on the Windows host are "<CR><LF><CR><LF>" (from the forum thread).

[galitsyn]

Hi guys,

The latest "Development snapshots" build from Test Builds page has now experimental support for clipboard sharing with Wayland guest. Guests which are running Gnome on Wayland should now be able to exchange text, html and image clipboard content. Implementation for Plasma on Wayland is still in progress and is not stable now.

To make it work, both parts -- host package and Guest Additions -- need to be updated. If you wold like to give it a try and leave a feedback, that would be much appreciated.

Please note that Wayland host is not yet supported. DnD into Wayland guest is not yet supported either.

[agilis]

This is still an issue.

I have been using X11 as the display server ever since but now I'm being forced into Wayland because an update was carried out, AlmaLinux 9.4, and this caused Xorg to spike the CPU until I switched to 3D Acceleration. However, switching to 3D acceleration causes Window glitches such as screen redraws, consistently.

Here's a URL where someone had the same issue with Gnome Terminal, Debian, and VirtualBox: ​https://groups.google.com/g/linux.debian.user/c/DUZF2viqd9g?pli=1

Here's a mention of the issue being experienced by a comunity member of Synergy which was fixed: ​https://github.com/symless/synergy-core/issues/7145

Here's a indepth discussion of the issue being experienced by a comunity member of Alacritty which was fixed: ​https://github.com/alacritty/alacritty/issues/2844

[galitsyn]

Hi agilis,

Thank you for pointing out. I will try to reproduce the issue (as time permits) and see what we can do. In addition to the GTK, we also do text buffers processing. Maybe we can work it out on our side.

[galitsyn]

Btw, which VBox build are you using and which Guest Additions build is installed into he guest?

[agilis]

Hi galitsyn,

Thank you so much for your reply! This is the information your requested:

VirtualBox: Version 7.0.14 r161095
Guest Additions Version: 7.0.14 r11095

[agilis]

The original issue is not distribution specific. This is an issue with GNOME and is present in Ubuntu 22.04 LTS as well. Upgrading to Ubuntu 23.10 fixes this issue because 23.10 is packaged with GNOME 45 as well as a Kernel upgrade.

[galitsyn]

Hi agilis,

We have a fix for the issue for both "Latest 7.0.x test builds" (r163426+) and "Development snapshots" (r163445+) on this page. Both host and Guest Additions part are needed to be updated. Thank you for reporting the issue.

[Klaus Espenlaub]

Fixed with VirtualBox 7.0.20.