Ubuntu
linux-oem-5.17 package

Blank screen when using GDM

Bug #2028096 reported by Mahyar Mirrashed on 2023-07-18

This bug report is a duplicate of: Bug #2026887: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gdm	Unknown	Unknown	auto-gitlab.gnome.org-gnome-gdm-- #860
	linux-oem-5.17 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Refer to this issue that I created for the GDM developers: https://gitlab.gnome.org/GNOME/gdm/-/issues/860

They have indicated that they will not fix this bug.

Description: Ubuntu 22.04.2 LTS
Release: 22.04

gnome-shell:
  Installed: 42.9-0ubuntu2
  Candidate: 42.9-0ubuntu2
  Version table:
*** 42.9-0ubuntu2 500
        500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     42.0-2ubuntu1 500
        500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

I am expecting not to have pipe errors between my integrated graphics card and GDM and for the login screen to appear.

I got a pixelated screen and then a blank, black screen.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 5.17.0-1034.35-oem 5.17.15
Uname: Linux 5.17.0-1034-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Jul 18 18:12:57 2023
DisplayManager: sddm
InstallationDate: Installed on 2023-06-14 (34 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 42.9-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Mahyar Mirrashed (mahyarmirrashedjca) wrote on 2023-07-18:

Dependencies.txt Edit (24.5 KiB, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (107 bytes, text/plain; charset="utf-8")
monitors.xml.txt Edit (6.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2023-07-19:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2026887, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

affects:

gnome-shell (Ubuntu) → linux-oem-5.17 (Ubuntu)

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2023-07-19:

Actually I'm just assuming it's that bug. I can't see enough of your logs to confirm. But you might like to try one of the workarounds:

* Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment

* Upgrade to a newer kernel:
sudo apt install linux-generic-hwe-22.04

Revision history for this message

Mahyar Mirrashed (mahyarmirrashedjca) wrote on 2023-07-19:

What kind of logs can I provide to assist? I was thinking of maybe sharing the pipe errors but, that was literally the only thing out of the ordinary that I was seeing in the system journal.

For your workarounds. For the first option, how do I add the environment variable to `/etc/environment`? All that I see in the file so far is my PATH declaration in BaSH syntax in there. For the second option, if I update the kernel, is that a reversible change?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2023-07-20:

When the bug is happening just switch to a VT (like Ctrl+Alt+F4) and run:

journalctl -b0 > journal.txt

then attach the resulting text file here.

To add to /etc/environment you need to edit the file as super user and add a new line.

If you update the kernel, yes that is reversible. You probably wouldn't need to reverse it since that's the stable kernel for our long term stable release in use by probably most Ubuntu users.

Revision history for this message

Mahyar Mirrashed (mahyarmirrashedjca) wrote on 2023-07-21:

journal.txt Edit (37.1 MiB, text/plain)

I got the same problem unexpectedly on Kubuntu with X11. That suggests that the problem is beyond the desktop and window managers.

The additional line in /etc/environment has temporarily fixed this for me. I have attached the journal logs with the pipe errors inside.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2023-07-24:

No that seems to be a different kernel issue if the flood of log messages is anything to go by:

Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x00000080
Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe A: 0x00000080
Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x00000080
Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe B: 0x00000080
Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe C: 0x00000080
Jul 21 10:21:09 jcapc196 kernel: i915 0000:00:02.0: [drm] *ERROR* Fault errors on pipe C: 0x00000080

You could open a new bug report about that but generally it's the same theme as this bug: The kernel version is really too old for your new hardware, so please try:

sudo apt install linux-generic-hwe-22.04