Version
7.2.12
Host OS Type
Windows
Host OS name + version
Windows 11 PRO 25H2
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Debian GNU/Linux 13 (trixie)
Component
Guest Additions/Shared Clipboard
What happened?
Behavior observed also with previous VBox versions and with other Debian based Linux guests (e.g. Ubuntu 22.04, Ubuntu 24.04).
Sometimes typing ctrl+c (to copy some text, or in a terminal to terminate a command) causes a guest UI crash, that results in a sudden closure of all graphics applications too.
After this crash, sometimes the shared clipboard continues to work (in both directions), sometimes it stops to work until a guest reboot is issued.
Attached also the journalctl (seems there is nothing strange). No kernel panics/oopses reported.
I use always the VM in full screen mode, if it could be helpful.
How can we reproduce this?
Not simple to reproduce. Probably the bug happens only after some automatic UI lock and user unlock, and probably only if the host did some suspends with the VM running. I tried to pause the VM just before the host goes to suspend (attaching to Windows events) but it does not resolve the issue
VBox.log
journalctl.log
Did you upload all of your necessary log files, screenshots, etc.?
Version
7.2.12
Host OS Type
Windows
Host OS name + version
Windows 11 PRO 25H2
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Debian GNU/Linux 13 (trixie)
Component
Guest Additions/Shared Clipboard
What happened?
Behavior observed also with previous VBox versions and with other Debian based Linux guests (e.g. Ubuntu 22.04, Ubuntu 24.04).
Sometimes typing ctrl+c (to copy some text, or in a terminal to terminate a command) causes a guest UI crash, that results in a sudden closure of all graphics applications too.
After this crash, sometimes the shared clipboard continues to work (in both directions), sometimes it stops to work until a guest reboot is issued.
Attached also the journalctl (seems there is nothing strange). No kernel panics/oopses reported.
I use always the VM in full screen mode, if it could be helpful.
How can we reproduce this?
Not simple to reproduce. Probably the bug happens only after some automatic UI lock and user unlock, and probably only if the host did some suspends with the VM running. I tried to pause the VM just before the host goes to suspend (attaching to Windows events) but it does not resolve the issue
VBox.log
journalctl.log
Did you upload all of your necessary log files, screenshots, etc.?