[Bug 1971149] Re: Wayland session: Internal display is black after sleep
I'm facing a similar issue. I'm also using Wayland and a Nvidia MX150 card. Let me attach the log once I have the issue again. It seems to happen after long periods of sleep. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
Here you have ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149/+attachment/5586890/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971674] [NEW] Laptop screen black (not powered on) when inactive but NOT in sleep
Public bug reported: I thought this was similar to bug #1971149, but that's not the case at all. Apparently my problem comes from the screen being black but not suspended (while playing some audio). Suspending the laptop (by closing the lid or pressing the POWER buttom) and then waking it up solves the problem. Let me attach you the log. I'm on a Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu May 5 10:51:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1971674/+attachment/5586891/+files/journal.txt ** Description changed: - I thought this was similar to #1971149, but that's not the case at all. - Apparently my problem comes from the screen being black but not + I thought this was similar to bug #1971149, but that's not the case at + all. Apparently my problem comes from the screen being black but not suspended (while playing some audio). Suspending the laptop (by closing the lid or pressing the POWER buttom) and then waking it up solves the problem. Let me attach you the log. I'm on a Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu May 5 10:51:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-30 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Laptop black (not powered on) when inactive but NOT in sleep + Laptop screen black (not powered on) when inactive but NOT in sleep -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1971674 Title: Laptop screen black (not powered on) when inactive but NOT in sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971149] Re: Wayland session: Internal display is black after sleep
Thank you Daniel, I just did (bug #1971674) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1971149 Title: Wayland session: Internal display is black after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I'm facing the same issue (duplicated in reported bug 1971674) with my Mi Notebook Pro 2018 running Ubuntu 22.04, an Intel® Core™ i7-8550U with an NVIDIA GeForce MX150 using Wayland. I thought the issue was with Nvidia, but I can tell that's not the case. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5586937/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hi Daniel! #20 works for me! Thanks! Do you have any explanation for this? How come this was not a problem back when I was running Fedora? Is Ubuntu 22.04 using an older, unfixed version of some package? Was this bug introduced downstream in the Ubuntu release? Are there any plans of fixing this for 22.04.1? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
#23 yes. My laptop is a Nvidia+Intel hybrid laptop. Internal screen now wakes up (although the lockscreen blurred background is shown black, but that's a minor issue for me), and external one works perfectly. I never had performance issues, and once I get past the lockscreen it just works. Again, on Fedora I simply did not have such a problem. I wonder what did Canonical do on Ubuntu for this bug to appear. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Same issue in 22.10. MUTTER_DEBUG_FORCE_KMS_MODE=simple doesn't work (it gets stuck in the login screen, I can't actually login to my session). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] [NEW] Laptop screen can't be turned on after suspension or locking
Public bug reported: My laptop is running a Hybrid Nvidia RTX3060 + Intel i5 11400h graphics. After installing the Nvidia drivers and with Wayland (this doesn't happen with Xorg), once the screen is turned off (for example, by locking the screen or suspending the computer, it cannot be turned on. This is a behavior similarish to the one in bug 1968040 (IDK if that one was also triggered by a screen lock, this one gets triggered inmediately after turning off the screen for whatever reason). In 22.04, I solved it quite easily by setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0. As suggested in that ticket, I set this time MUTTER_DEBUG_FORCE_KMS_MODE=simple. I unfortunately cannot tell whether this would solve my issues because, when I reboot my computer with that variable, I simply cannot log in into my account. I type my password as usual (the login screen works perfectly, though) and then, once submited, the output is a black screen (LCD is on, though) and nothing shows up after. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 08:40:12 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Laptop screen can't be turned on after suspension or locking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello Daniel. Thanks for your help, see bug 1994000. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
Well, I wasn't using that one right now because, as I said, made me unable to use my computer. Will try to do as you suggest. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
From the file, it would seem it actually booted into the session but didn't show anything... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994000] Re: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple
I just switched to the non-atomic KMS (MUTTER_DEBUG_FORCE_KMS_MODE=simple). My computer turned to black and turned unusable. I wasn't able to Crtl+Alt+F3 and switch to the terminal at all. Hopefully, I was able to change the /etc/environment to the default with a live CD and was able to boot again to my computer normally. I can't see any crashes related to this (the last crash was yesterday, and this was a few minutes ago) in /var/crash. I can upload, though, the system log from the previous boot. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+attachment/5626377/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1994000 Title: Can't log in anymore after setting MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] [NEW] Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
Public bug reported: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1994019/+attachment/5626387/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I see I still have the llvm Oibaf package, but that doesn't seem related (and I ppa-purged the PPA, so IDK why that's still there...) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
Removed the llvm oibaf package altogether and still have the same issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I reinstalled Ubuntu 22.10 and I can see no issues. It seems you were right Daniel. Please close this bug, nothing to see here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
