[Bug]: VirtualBoxVM crashes in libQt6Widgets.so.6.10.2 after GNOME Wayland lock/unlock, causing VM to become "Aborted"

[abulygin]

Version

7.2.8

Host OS Type

Linux

Host OS name + version

Ubuntu 26.04 (Resolute)

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 11 Home 25H2 Build 26200.8524

Component

Other

What happened?

Summary

When running a Windows 11 guest on VirtualBox 7.2.8 under Ubuntu 26.04 (GNOME/Wayland), the VM occasionally becomes Aborted after the host session is locked and later unlocked.

Investigation shows that the guest itself is not crashing. Instead, the host-side VirtualBoxVM process segfaults in libQt6Widgets.so.6.10.2.

Running the same VM in headless mode completely avoids the issue.

Environment

Host

OS: Ubuntu 26.04 (Resolute)
Desktop: GNOME
Session type: Wayland
NVIDIA Driver: 580.159.03
VirtualBox: 7.2.8 r173730 (Oracle package)

$ loginctl show-session $XDG_SESSION_ID -p Type
Type=wayland

$ dpkg -l | grep virtualbox

ii  virtualbox-7.2  7.2.8-173730~Ubuntu~resolute

Guest

• Windows 11
• UEFI enabled
• TPM enabled
• VMSVGA graphics adapter
• Guest Additions installed

00 00 00 522923 VirtualBox.txt
00 00 00 520120 VirtualBox.txt

Expected Result

The VM continues running normally after the host session is unlocked.

Actual Result

The VM enters the Aborted state.

Kernel logs show that the VirtualBoxVM process segfaulted.

Relevant Log Extracts

Crash 1

Jun 05 11:40:38 kernel: VirtualBoxVM[21870]: segfault at 8 \
ip 00007d8fe51f8024 sp 00007ffd7b3a1038 error 4 \
in libQt6Widgets.so.6.10.2[1f8024,7d8fe5178000+4c8000]

Crash 2

Jun 05 15:03:01 kernel: VirtualBoxVM[22978]: segfault at 8 \
ip 00007dafe85f8024 sp 00007ffe7d822a58 error 4 \
in libQt6Widgets.so.6.10.2[1f8024,7dafe8578000+4c8000]

Crash 3

Jun 05 17:44:56 kernel: VirtualBoxVM[34836]: segfault at 8 \
ip 000077cdb6ff8024 sp 00007fff715bcd48 error 4 \
in libQt6Widgets.so.6.10.2[1f8024,77cdb6f78000+4c8000]

Immediately before/around the crashes, VirtualBox frequently emits Qt-related warnings:

Qt WARNING: QObject::disconnect: wildcard call disconnects
from destroyed signal of UIInvisibleWindow::unnamed

Additional warnings observed:

Qt WARNING: Cannot create accessible child interface for object:
QITreeView(...)

Additional Observations

VirtualBox logs show display geometry changes occurring when the desktop session is locked/unlocked and monitors are reconfigured.

Examples include:

Host-screen available-area changed
Sending guest size-hint to screen 0 as 3440x1325

and resolution change events handled by Guest Additions.

This suggests the crash may be related to GUI/display handling during Wayland session lock/unlock or monitor state transitions.

Workaround

Starting the VM in headless mode completely avoids the issue:

VBoxManage startvm "Windows 11" --type headless
After switching to headless mode, the VM survives repeated host lock/unlock cycles and no further VM aborts have been observed.

This suggests the problem is in the GUI/frontend layer rather than the virtualization core.

Notes

• No guest BSODs observed.
• No storage-related errors observed.
• No VirtualBox kernel module failures observed.
• The VM itself appears stable.
• The crash is consistently in the host-side VirtualBoxVM process inside libQt6Widgets.so.6.10.2.

I'd also attach:

• VBox.log from a session that later aborted.
• The relevant

journalctl_excerpt.txt

containing the segfault.

• A note that headless mode is a reliable workaround, since that's a very strong clue for the VirtualBox developers.

How can we reproduce this?

Steps to Reproduce

1. Start a Windows 11 VM normally from the VirtualBox GUI.
2. Use the VM for some time.
3. Lock the Ubuntu desktop session.
4. Leave the machine locked for a period of time.
5. Unlock the session.
6. Repeat lock/unlock cycles as needed.

Eventually the VM becomes Aborted.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.