Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]

[Ge-org Brohammer]

Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock.

After logging in using wayland, both monitors goes blank and then enters power saving mode. If I replug the dock then the monitors wake up but with display settings reset.

When using x-server, both screen work as normal after login remembering my screen placement etc.

Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode.

Ubuntu 24.04 with latest updtes installed.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-26 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gnome-shell 46.0-0ubuntu5
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
Tags: noble
Uname: Linux 6.8.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-04-26 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gnome-shell 46.0-0ubuntu5
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
Tags: noble wayland-session
Uname: Linux 6.8.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users
_MarkForUpload: True

[lotuspsychje (lotuspsychje)]

Thank you for filing this bug and make Ubuntu better!

In order to pull your logs and system info into this bug

please execute: apport-collect 2064275 from your terminal

so the developers can start debugging your bug a better way.

In the future please use ubuntu-bug yourpackage from a terminal.

Thank you!

[Paul White (paulw2u)]

>Ubuntu 24.04 with latest updtes installed.
but this report has been tagged '22.04'

Please clarify which release of Ubuntu you are using and run the command

  apport-collect 2064275

as requested in comment #1.

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

Sorry about the wrong tag. This running x-server session but not sure if you would like logs with wayland mode? Just let me know what sequence since the screens turn off, I might be able to replug the docking station and collect them again?

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Ge-org Brohammer (gbrohammer)]

apport information

[Paul White (paulw2u)]

Thank your for the clarification.

I'll change the status back to 'New' and no doubt a member of Ubuntu's Desktop Team will review your issue shortly.

[Daniel van Vugt (vanvugt)]

It looks like there are recurring errors "drmModeAtomicCommit: Invalid argument".

Please try adding this to /etc/environment:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and reboot.

[Daniel van Vugt (vanvugt)]

Possibly related:
 * https://gitlab.gnome.org/GNOME/mutter/-/issues/3098
 * https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
 * https://gitlab.gnome.org/GNOME/mutter/-/issues/2254
 * Bug 1968040

[Ge-org Brohammer (gbrohammer)]

Thank you. I have added the option and it seems to be working. If there is anything else I can check or test to solve the bug, let me know.

[Daniel van Vugt (vanvugt)]

If you are interested in debugging then please use:

  MUTTER_DEBUG_FORCE_KMS_MODE=atomic
  MUTTER_DEBUG=kms

Then wait until the problem happens again and run:

  journalctl -b0 /usr/bin/gnome-shell > gslog.txt

and attach the resulting text file here.

[Ge-org Brohammer (gbrohammer)]

I can reproduce it by turning off my computer and then directly logging in using wayland every time.

[Daniel van Vugt (vanvugt)]

Thanks. For each "KMS update failed: drmModeAtomicCommit: Invalid argument", the only unusual things I can see are:

KMS: [atomic] Setting CRTC (83, /dev/dri/card1) gamma, size: 4096
KMS: [atomic] Setting CRTC 83 (/dev/dri/card1) property 'GAMMA_LUT' (28) to 161

which means either Night Light or a custom colour profile is enabled on the AMD GPU.

This is a problem I've seen before in bug 1968040 but the same "Invalid argument" can have multiple causes and "gamma" is just one that I've seen.

Since we can't reproduce the issue in development at the moment, and therefore can't debug it, I suggest sticking to the workaround:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

[Ge-org Brohammer (gbrohammer)]

It's a vanilla install, I haven't setup any custom colour profiles or even enabled night light. I will keep using the setting thank you. Was just hoping to help improve hardware support for new installs. Both screens are 4k HDR capable though. Not sure if that plays a part.

[Daniel van Vugt (vanvugt)]

HDR might be relevant but I'm not sure what the status of HDR support is.