[bochs_drm] Booting gets stuck with corrupt graphics
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mutter (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When booting on a VPS connected via VNC at first the text messages via boot are displayed. Then the resolution changes several times (VNC size changes) and after a lot of resolution changes it gets stuck in a corrupd graphic design. The cursor is still blinking but alt+Fx does also not work.
Using sudo service gdm3 stop and sudo startx is working. Due to the fact that the VNC console is completely frozen and this is hosted at a provider I have to use a separate putty session to stop gdm and starting a new gui session which is then displayed in the VNC.
This problem does not exist with Ubuntu 18.04 LTS. It does not matter if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04 LTS. On a second VPS the problem is similar but not the same. The second one does not get totally frozen. There is still no GUI when booting but it ends up in a purple uniform screen even the text mode is purple (the first VPS ends up a blueish screen with blue vertical lines).
On the second VPS it is possible to switch to shell (purple style) and executing the abovementioned commands directly without a second putty session. But the behavior is basically similar for both VPS.
When using sudo reboot the second VPS displays text again and the first only some graphic trash. So basically they have both the same behavior but on the first the graphics are totally destroyed even text is not working anymore. The Funny thing is that startx is still working but after clothng the startx session the graphic trash is shown again.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckR
CompizPlugins: No value set for `/apps/
Date: Fri Jun 5 10:39:59 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrations
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Device [1234:1111] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Device [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
Changed in mutter (Ubuntu): | |
status: | Expired → New |
Please try editing /etc/gdm3/ custom. conf and uncomment:
#WaylandEnabl e=false
so it is:
WaylandEnable =false
Then reboot.