This is looking like a kernel bug (comment #81) and increasingly unlike
mutter has done anything wrong. Sounds like it is specifically about
i915 HDMI handling.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirme
Thanks!
It looks like most of the errors are in fact caused by previous errors:
i915 :00:02.0: [drm:drm_atomic_crtc_check [drm]] [CRTC:45:pipe A]
requesting event but off
i915 :00:02.0: [drm:drm_atomic_check_only [drm]] [CRTC:45:pipe A] atomic
core check failed
...
KMS: [atomic] KMS upd
Hi, Daniel
I performed next changes:
1. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0xff"
2. Add to /etc/environment: MUTTER_DEBUG=kms
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5664106/+files/journal.txt
--
You rece
Note to self:
One possible explanation here is that we're setting this twice in the
same commit, which some drivers might reject(?):
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79
(/dev/dri/card0) property 'CRTC_ID' (20) to 0
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [
Thanks but we do need drm.debug=0xff to make any progress here. You add
it in /etc/default/grub as part of GRUB_CMDLINE_LINUX_DEFAULT and then
run:
sudo update-grub
and reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
Hi team and all.
I'm stuck with a similar issue.
The solution with MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 helped me! Thanks guys!
I created logs for you (without kernel parameter: drm.debug=0xff, can't find
how do it).
If somebody wants to help collect logs it easy perform without working screen:
1. D
Hi team and all.
I'm stuck with the similar issue.
The solution with MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 helped me! Thanks guys!
I created logs for you (I removed MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
before).
If somebody wants to help collect logs it easy perform without working screen:
1. Desable auth
** Information type changed from Public Security to Public
--
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 [drmModeAtomicC
** Information type changed from Public to Public Security
--
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 [drmModeAtomicC
Someone please help us to find the cause of this bug by:
1. Remove all workarounds.
2. Add kernel parameter: drm.debug=0xff
3. Add to /etc/environment: MUTTER_DEBUG=kms
4. Reboot.
5. Reproduce the bug.
6. Run: journalctl -b0 > journal.txt
7. Attach the resulting text file here.
--
You received t
I run Ubuntu 22.04.02 on a Lenovo Legion 5i pro.
There was a bug when I switched on Wayland session.
I followed instructions that are described above and deleted gnome extention
aplication.
And I've got no issues any more with lock my laptop and black screen. It's
fantastic!
My conclusion is, set
I run Ubuntu 22.04 on a Dell Optiplex 7010.
This issue started suddenly a couple of weeks back - I run updates several
times weekly so not exactly sure when it started.
Just tried adding
MUTTER_DEBUG_FORCE_KMS_MODE=simple
to environment file and after reboot, problem seems to have been resolved.
Is anyone able to try putting both the kernel and mutter into debug
modes at the same time?
For the kernel add parameter: drm.debug=0x4
For mutter add to /etc/environment: MUTTER_DEBUG=kms
Then reboot and your journal *should* tell us the cause of the bug.
--
You received this bug notification
That's not this bug then, so please open a new one by running:
ubuntu-bug gnome-shell
--
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
The workaround doesn't fix the problem for me.
It's not only doesn't wake up the screen, it freezes the whole system and I
have to hard reset!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.ne
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
--
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 [drm
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
--
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 [drm
Josef, did you try the workaround in the original post? The workaround
fixed the problem for me on Ubuntu 22.10.
[ Workaround ]
Add to /etc/environment (in Ubuntu 22.04):
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
or in Ubuntu 22.10 and later:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and t
Hello guys. Is this being worked on? I am experiencing this issue using
Wayland on Lenovo ThinkPad P14s Gen 3 on Ubuntu 22.04.2 LTS. Would be
nice to not have to restart my PC every damn time :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
Thanks Michal. The diff looks perfectly clean and exactly what I would
expect in that no part of the system has changed that would fool mutter
into doing the wrong thing. So it's just that mutter's done the wrong
thing... somehow. And that wrong thing is not visible in the above text
files.
--
Yo
** Attachment added: "after.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650348/+files/after.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/1
This may be a better one, no reboots or kernel changes between.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650347/+files/before.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
** Attachment added: "after.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650276/+files/after.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/1
I believe I just had this happen, though there was a reboot and kernel
switch (bug #1988989...) in between before and after.
gnome-shell was also topping out CPU.
Maybe this helps.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/565
To anyone who can reproduce this bug, please help me to debug it by:
1. Remove the workaround.
2. Reboot.
3. Log in by ssh from another machine.
4. Run: drm_info > before.txt
5. Reproduce the bug by locking and trying to resume.
6. Run: drm_info > after.txt
7. Attach the two resulting text
Unfortunately I still can't reproduce the bug (on 23.04) using those
steps.
--
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 lockin
I found an easier way to reproduce this issue by the following steps:
1. Log out and select xorg
2. Log in and log out again to select wayland session
3. super + L to make screen blank.
I can reproduce this issue easily. I tried the latest drm-tip/linux-next
then I can't reproduce this issue.
Th
Answer from email to comment #57:
It appears your CPU/GPU (i7-1280P) is too new for that old kernel
(5.14.0-1055-oem). And so you are hitting this bug:
https://launchpad.net/bugs/1991777
But the solution is simple: Just install 22.10 and don't downgrade the
kernel. It should be kernel version 5.1
Please collect a log from the previous boot where it froze:
journalctl -b-1 > prevboot.txt
and create a new bug with that file attached.
Also check for /var/crash files and create new bugs for each using
'ubuntu-bug'.
--
You received this bug notification because you are a member of Ubuntu
D
I have the same or similar bug. I tried the workaround to
Add to /etc/environmen in Ubuntu 22.10 and later:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
And my computer froze on startup on the Ubuntu screen. When I deleted
the line, my computer again booted up fine.
I have a Thinkpad X1 with Ubuntu 2
Actually the bug just happened to me and now I can see
"drmModeAtomicCommit: Invalid argument" in my logs now. So it turns out
I am experiencing this bug.
I will try the work around posted at the top of the first post:
[ Workaround ]
Add to /etc/environment (in Ubuntu 22.04):
MUTTER_DEBUG_ENA
Bug 1971149 is definitely a duplicate of this one.
Please open your own bug by running:
ubuntu-bug gnome-shell
--
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:
Blan
Ah sorry I can't find "drmModeAtomicCommit: Invalid argument" in my
system log. I think my problem is more like this one here:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
To check if this is the bug you are experiencing, look for this
repeating in your system log:
drmModeAtomicCommit: Invalid argument
If it's not mentioned in the log then you should create a new bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
I have a similar problem using an external HDMI monitor connected to a
laptop.
Not sure if this is related because it happens with the blank screen
after a period of inactivity (without using the screen lock).
After the screen has gone blank due to a period of inactivity, I move
the mouse or pres
Comment #50 is a kernel bug in the nouveau driver that is not relevant
here.
--
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 locki
MUTTER_DEBUG_FORCE_KMS_MODE=simple
Didn't solve the issue for me.
This problem happens only while using the nouveau driver and I have filed a bug
here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/2002314
--
You received this bug notification because you are a membe
** Tags added: dt-962
--
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] [drmModeA
Any news on this?
--
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] [drmModeAtomi
** Changed in: mutter
Status: Unknown => New
--
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:
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
Jorge,
Please open a new bug to discuss that, by running:
ubuntu-bug gnome-shell
--
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 aft
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.ne
ok, I was not aware of : « Wayland sessions (which might include the
login screen) ».
--
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 af
The error message "Failed to post KMS update: drmModeAtomicCommit:
Argument invalide" can only occur in Wayland sessions (which might
include the login screen), and it does occur in the above log from bug
1983175 too.
If you would like to discuss a Xorg problem then please open a new bug
from the
It seems NOT exclusive to Wayland, as seen here →
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983175/comments/5
--
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
** Description changed:
+ [ Workaround ]
+
+ Add to /etc/environment (in Ubuntu 22.04):
+
+ MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
+
+ or in Ubuntu 22.10 and later:
+
+ MUTTER_DEBUG_FORCE_KMS_MODE=simple
+
+ and then reboot.
+
+ [ Original report ]
+
(initially reported as a comment on bug
I don't think this bug relates to mirror mode. It happens on single
display systems.
--
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 aft
@vanvugt actually my issue must have been different, I'm not using
mirror mode and it was happening to me without an external display (as
well as with). The workaround did work though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to m
@vanvugt actually my issue must have been different, I'm not using
mirror mode and it was happening to me without an external display (as
well as with). The workaround did work though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to m
Unassigning myself just because I won't get to this any time soon. I
investigated the logs, couldn't explain it and couldn't reproduce it.
Anyone is free to work on this but I suggest discussing any findings in
the upstream bugs:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
https://git
In mutter 43 (Ubuntu 22.10) the workaround has changed to:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
--
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
Thanks Daniel for the solution, this fixes both night-light bug as well
as suspend screen bug, hope this will be included in the main files in
the coming updates. I m on dell g3 which has both intel and nvidia
graphics, looks like this is only affecting the ones who has graphics
processor.
--
You
greenmandd, please report your bug separately by running:
ubuntu-bug gnome-shell
--
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 afte
Blanked screen doesn't wake up after locking (dual monitors pc desktop
config) when i use new AMD Radeon video card as RX6500XT for example. I
was able to reproduce this issue in Ubuntu 20.04.4, Ubuntu 22.04 and
Fedora 36. First I thought there was a problem with the video driver.
Make some test wi
I added this option:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
to
/etc/environment
Now both screens don't turn off on a Intel/Nividia hybrid laptop similar
to this:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1973467
The screens just get blank.
--
You received this bug notification because
** Changed in: gnome-shell
Status: Unknown => New
--
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 [drmModeAtomicCom
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5098
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098
Importance: Unknown
Status: Unknown
--
You received this bug no
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2216
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2254
https://gitlab.gnome.org/GNOME/mutter/-/issues/2254
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/i
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 also works for me (XPS 9500).
Furthermore, it fixes also the Night Light feature.
Thank you Daniel!
--
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/
Seems MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 solves the issue, hope it gets
real fix soon without workarounds.
--
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
Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then
reboot. If that doesn't fix your problem then please open a new bug.
--
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/bu
** Attachment added: "gnome"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5596972/+files/gnome
--
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
This happens to when connecting HDMI monitor to the laptop.
The laptop's screen doesn't wake up while the external monitor turns on.
Unplugging the HDMI cable, makes internal monitor works again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
If MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 doesn't work for you then you are
commenting on the wrong bug.
--
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
The "Unblank lock screen" extenions
(https://extensions.gnome.org/extension/1414/unblank/) works for me as a
workaround until this issue gets fixed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchp
> Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 doesn't help.
> Is there any way to disable the screen blanking?
Yes it does solve this bug. If it doesn't solve your issue then you need
to report a NEW bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I'm away from Ubuntu for now, so can anyone check if the following
command solves this issue:
xset -dpms
--
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 s
#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,
Hi Jorge, do you have an external monitor connected via HDMI and an
internal display (a laptop with hybrid graphics Intel + NVIDIA) too? I
can't test this right now.
My original bug report is a big messy. It is more like three separate issue
into one.
1. Internal monitor doesn't wake up after sle
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
Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 doesn't help. Is there any way
to disable the screen blanking?
--
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 d
Just add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment and then
reboot.
--
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 loc
I ran into the same issue, any progress on this? Can I somehow disable
the screen blanking?
--
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
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2268
https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2268
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
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"
htt
Potentially related: https://gitlab.gnome.org/GNOME/mutter/-/issues/2254
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2254
https://gitlab.gnome.org/GNOME/mutter/-/issues/2254
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Alright let's mention both translations to help with text searches.
** Summary changed:
- Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument
invalide]
+ Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument
invalide] [drmModeAtomicCommit: Invalid a
I'm also seeing this problem exactly as per bug description.
Apr 17 14:26:01 n1687 gnome-shell[845778]: Page flip discarded:
drmModeAtomicCommit: Invalid argument
Apr 17 14:26:01 n1687 gnome-shell[845778]: Failed to post KMS update:
drmModeAtomicCommit: Invalid argument
Apr 17 14:26:01 n1687 gno
Thanks. Yes MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 will reliably avoid any
failures in drmModeAtomicCommit.
This seems like a very simple setup (Intel graphics and one monitor) so
hopefully I will be able to reproduce the problem at some stage.
** Summary changed:
- Blanked screen doesn't wake up afte
I can confirm MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 reliably makes the
problem go away for me.
--
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 u
Attaching the requested output of drm_info.
** Attachment added: "drminfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5580371/+files/drminfo.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because y
Now testing MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0, and it seems to fix my
problem. I'll continue experimenting with it some more to confirm.
--
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/1
Just tested MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1, and I can still
observe the problem.
--
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 u
In case the 'rotation' and 'GAMMA_LUT' properties are relevant, please
try:
* Regular landscape orientation for a while
* Disabling night light for a while
Please also run:
sudo drm_info > drminfo.txt
and attach the resulting text file here.
--
You received this bug notification because
Thanks. Unfortunately MUTTER_DEBUG=kms can't tell us which is the
invalid argument and I can't see a consistent pattern in the log.
Please try these in /etc/environment in separate sessions:
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
** Changed in: mutter (Ubun
I reverted to stock mutter (42.0-1ubuntu1), enabled KMS debug in mutter,
and observed that the problem persists. Attaching the corresponding
journal.
** Attachment added: "journal-with-kms-debug.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5579395/+files/journ
mutter 42.0-1ubuntu2~ppa1 is a locally-patched version with a work-
around for https://gitlab.gnome.org/GNOME/mutter/-/issues/2216, as not
being able to re-order my tabs in firefox was bothering me.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
https://gitlab.gnome.org/GNOME/
Also what is mutter 42.0-1ubuntu2~ppa1 ? Does reverting to the archive
version work?
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launch
Not a crash, apparently. The screen is failing to update in Wayland
sessions:
abr 06 13:55:43 dantian gnome-shell[37489]: Failed to post KMS update:
drmModeAtomicCommit: Argument invalide
abr 06 13:55:43 dantian gnome-shell[37489]: Page flip discarded:
drmModeAtomicCommit: Argument invalide
To
Crash report for gnome-session-binary:
https://errors.ubuntu.com/oops/d5e2d4b2-b62f-11ec-a2f0-fa163ef35206
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blank
Attaching my journal for the current boot, where I have observed the
issue a few times already.
I'm seeing some critical error messages for gnome-session-binary and one
segfault, unsure whether this is related to the problem though.
** Attachment added: "journal.log"
https://bugs.launchpad.ne
92 matches
Mail list logo
