Your message dated Mon, 2 May 2022 22:51:57 +0200
with message-id <[email protected]>
and subject line Re: virtualbox: 6.1.34-dfsg-2 broken, guest VM display window
stays black with blinking cursor
has caused the Debian Bug report #1010112,
regarding virtualbox: 6.1.34-dfsg-2 broken, guest VM display window stays black
with blinking cursor
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1010112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010112
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: virtualbox
Version: 6.1.34-dfsg-2
Severity: serious
This version is completely unusable as the guest OS never starts - the VM
display stays black with a blinking cursor. It is not guest OS dependent as
this is 100% reproducible with any guest OS. The VM log does not show any
errors. Last working version was 6.1.32.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.5 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages virtualbox depends on:
ii adduser 3.121
ii iproute2 5.17.0-1
ii libc6 2.33-7
ii libcurl3-gnutls 7.82.0-2
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgcc-s1 12-20220319-1
ii libgl1 1.4.0-1
ii libgsoap-2.8.117 2.8.117-2
ii liblzf1 3.6-3
ii libopus0 1.3.1-0.1
ii libpng16-16 1.6.37-3
ii libsdl1.2debian 1.2.15+dfsg2-6
ii libssl1.1 1.1.1n-1
ii libstdc++6 12-20220319-1
ii libvncserver1 0.9.13+dfsg-3
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.5-1
ii libxcursor1 1:1.2.0-2
ii libxml2 2.9.13+dfsg-1
ii libxt6 1:1.2.1-1
ii procps 2:3.3.17-7+b1
ii python3 3.10.4-1
ii python3.10 3.10.4-1
ii virtualbox-dkms [virtualbox-modules] 6.1.34-dfsg-2
ii virtualbox-source 6.1.34-dfsg-2
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages virtualbox recommends:
ii libqt5core5a 5.15.2+dfsg-16
ii libqt5gui5 5.15.2+dfsg-16
ii libqt5opengl5 5.15.2+dfsg-16
ii libqt5widgets5 5.15.2+dfsg-16
ii libxcb1 1.14-3
ii libxext6 2:1.3.4-1
ii virtualbox-qt 6.1.34-dfsg-2
Versions of packages virtualbox suggests:
pn vde2 <none>
ii virtualbox-guest-additions-iso 6.1.34-1
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 30 Apr 2022 11:13:29 -0700 nbi <[email protected]> wrote:
False alarm. The answer is given here:
https://forums.virtualbox.org/viewtopic.php?f=7&t=105468
In my case after exiting QEMU-KVM virt-manager the qemu-system-x86 and
kvm-nx-lpage-re processes remain live. Since only one hypervisor is
active at a time the fix is to simply kill these processes when QEMU-KVM
is not in use - and the VirtualBox VMs start just fine. Hope this helps
someone else who might get tripped up by this.
On Fri, 29 Apr 2022 11:57:02 -0700 nbi <[email protected]> wrote:
> You upgraded to 6.1.34-dfsg-2 from what? 6.1.32 or an earlier version?
> How did you upgrade? dpkg, apt, or Synaptic?
>
> On Tue, 26 Apr 2022 03:24:46 +0300 Alexander Kernozhitsky
> <[email protected]> wrote:
> > Hello,
> >
> > I just upgraded to 6.1.34-dfsg-2, and for me everything worked fine,
> guest
> > systems start normally.
> >
> > Did you try to downgrade the package and ensure that the bug is done
> after
> > downgrade?
> >
> > --
> > Alexander Kernozhitsky
> >
> >
> >
> >
>
>
>
closing.
G.
--- End Message ---
