Thanks. Indeed it seems the workaround is to just avoid selecting the
third party software option during install.
** Package changed: linux (Ubuntu) => ubuntu-restricted-extras (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
A screenshot of my settings in Virtualbox are in the attachment. If
needed I can also send the vbox file. Note that the first thing I do, if
I run into display/video issues, is switching off 3D acceleration, but
that did not help this time.
** Attachment added: "Screenshot"
Hi Daniel, I played around with VirtualBox settings and Ubuntu installer
settings: The problem seems to occur only when "Install third-party
software for graphics and Wi-Fi hardware and additional media formats"
is selected in the Ubuntu installer.
If the option is _not_ selected, the installed
I've just installed 22.10 in VirtualBox and still can't reproduce this
bug. What changes from the default VirtualBox settings might be causing
it?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
I can confirm the behavior as reported by BertN45:
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment does not help, but disabling Wayland in
/etc/gdm3/custom.conf does help.
I also tried both Ctrl-Alt-F1 and chvt 1 when the screen is frozen,
I both cases I get the login screen of the Host and not the one of the
VM :)
Even Right-Ctrl followed by Ctrl+Alt+F1 gives the Host screen.
I've tried in Xorg the following command:
bertadmin@VM-Ubuntu-2210:~$ ps $(pgrep Xorg)
PID TTY STAT TIME COMMAND
1749 tty2 Sl+0:16
The log in comment #13 suggests Wayland was working before those error
messages from the vmwgfx kernel driver... Can you check the VM isn't
just booting into the wrong virtual terminal? I've seen that happen
occasionally.
Try Ctrl+Alt+F1 in the VM or running: sudo chvt 1
--
You received this
I did the command in the xorg session, since in the Wayland session I
have no display.
bertadmin@VM-Ubuntu-2210:~$ find /lib/modules -name vmwgfx.ko
/lib/modules/5.15.0-27-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
/lib/modules/5.19.0-15-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko
In the guest VM, what output do you get from:
find /lib/modules -name vmwgfx.ko
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988488
Title:
Screen freeze at the moment of login
In the guest VM, what output do you get from:
find /lib/modules -name vmwgfx.ko
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988488
Title:
Screen freeze at the moment of login on
That change did not help, the display still did freeze.
The content of /etc/environment was:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
The host OS is a minimal
OK, if the problem is just Wayland then please try adding to
/etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and re-enable Wayland then reboot the VM. Does it work after that?
P.S. What OS is the host?
--
You received this bug notification because you
Well a summary: The Ubuntu 22.04 LTS VM works file and it also works fine with
the Ubuntu 22.10 VM on Xorg after disabling Wayland.
If I use Wayland it freezes and does not display the login screen. The last
message, I see flashing by during the start-up, is about starting the gnome
display
gdm3 launches the login screen app but does not do any graphics itself.
So if the display or input are frozen on the login screen then it's
either gnome-shell, mutter, or the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I did read that gdm3 did take care of the login screen, maybe it is
wrong or incomplete, but whatever I have news:
I changed /etc/gdm3/custom.conf and disabled wayland. Both systems
Ubuntu 22.10 and Ubuntu Unity 22.10 work now with Xorg without any
issues.
--
You received this bug notification
Although your Lspci.txt suggests it's not relevant here, if you have any
VMs set to use a non-default virtual graphics adapter then you will hit
bug 1990256 which sounds similar. But while your 'lspci -k' is showing
'vmwgfx' that won't be the issue here.
--
You received this bug notification
gdm3 does not do any graphics so that's unlikely to be related. Even the
login screen is done by gnome-shell/mutter, which accesses the virtual
screen through the vmwgfx kernel driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I don't expect it is a problem in Virtualbox as you assume, since I use
exactly the same VBox release in Ubuntu 22.04 LTS; Ubuntu 20.04 LTS and
Fedora 36. I only have a problem with the 22.10 systems using the latest
gdm3. I've tried Ubuntu Mate 22.10 and that one worked fine with
Virtualbox
Thanks. I'm going to keep assuming this is the problem:
sep 21 16:08:34 VM-Ubuntu-2210 kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR*
Failed to open channel.
sep 21 16:08:34 VM-Ubuntu-2210 kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR*
Failed to open channel.
which would be either a bug in the
Another try to send the journalctl file, using Email.
On Tue, 2022-09-20 at 10:30 +, Daniel van Vugt wrote:
> Please use one of these commands to provide a full log.
>
> If you have not rebooted since the freeze:
>
> journalctl -b0 > journal.txt
>
> Or after you have rebooted:
>
>
Again the program crashes, if I add the text file. So I attach the last
lines:
sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]:
snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled
restart job, restart counter is at 4.
sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Starting
Please use one of these commands to provide a full log.
If you have not rebooted since the freeze:
journalctl -b0 > journal.txt
Or after you have rebooted:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Changed in: linux (Ubuntu)
Status: Confirmed =>
22 matches
Mail list logo
