Yes I believe 22.04 is the only supported release that has/had this bug.
But we'd like to know what caused it there (and if it's still
happening).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Follow up to #92 and #98. For reasons unrelated to this bug I upgraded
my system to mantic and removed the workaround. It's been a week and so
far I haven't hit this bug again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
For those using mirror mode, bug 2051074 might finally provide an
explanation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
[i915] Blanked screen doesn't wake up
Actually the issue I'm thinking of might be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2620 coming in
mutter 46... If not already fixed in the kernel because it looks like
this bug only affects jammy?
--
You received this bug notification because you are a member of Desktop
Thinking about the most common cause of this error I've seen, can anyone
with multiple monitors confirm that it happens more on monitors that the
mouse pointer isn't on?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5708896/+files/journalctl.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I am also able to reproduce this bug. I logged in via ssh and collected
journal logs and drm_info while the screen was blank and unrecoverable.
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 does in fact solve the issue for me.
** Attachment added: "drm_info.txt"
There you go, attached is the journal of the boot when I removed the
workaround and got the screen stuck in the off state. I assume this is
what you really wanted and not the journal of my current boot. I have
since rebooted many times.
The messages start at 21:45 which is when I managed to get
Please provide a system log showing the errors:
journalctl -b0 > journal.txt
and attach the resulting text file here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Hello.
I seem to be hitting the same bug and I have attached the drm_info
output while the screen is stuck in the off state.
I see the the same Failed to post KMS update: drmModeAtomicCommit:
Invalid argument and Page flip discarded: drmModeAtomicCommit: Invalid
argument in my logs while the the
I'm not sure why the mode would be limited to 60Hz but you should know
that Xorg's multi-monitor support is very limited. It can only update
all monitors at the same time at the same rate. So if you have a 60Hz
monitor connected then it's possible Xorg will limit all monitors to
60Hz.
Even if all
Hey Daniel. Your comment made me look closer at what was happening and I
found the culprit in my case.
I have 2x 1440p screens connected through the dock, that support up to
165hz, and the dock supports enough bandwidth to run them at 1440px60hz.
But when it wakes up from suspend it for some
If anyone would like to help more, please reproduce the bug and while
the screen is stuck in the off state, log in by ssh and run:
sudo apt install drm-info
sudo drm_info > drminfo.txt
Then attach the resulting text file here.
--
You received this bug notification because you are a member
Thanks Tolga. It looks like the root cause of the issue on your machine
is a lack of display bandwidth when trying to drive 2 screens through
the same cable:
May 11 21:08:51 messier32 kernel: i915 :00:02.0:
[drm:intel_dp_mst_compute_config [i915]] Trying to find VCPI slots in DSC mode
May 11
Comment #86 does not appear to be related to this bug so doesn't need to
be discussed here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
[i915] Blanked screen doesn't
An issue with the same symptoms (still valid in Ubuntu 23.04) is also
reported against GNOME Shell at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/3135.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3135
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3135
--
I'm reporting this same issue from another distro (Arch in my case).
I've added the journal file with the drm.debug parameter. Hope it helps.
A summary of my issues just in case:
- Lenovo T480 Laptop
- Using in combination with Lenovo USB-C thunderbolt 3 dock to drive 2 screens
(That are
** Description changed:
[ Workaround ]
Add to /etc/environment (in Ubuntu 22.04):
- MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
+ MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
or in Ubuntu 22.10 and later:
- MUTTER_DEBUG_FORCE_KMS_MODE=simple
+ MUTTER_DEBUG_FORCE_KMS_MODE=simple
and then
I think we might have multiple different bugs here. The log in comment
#80 sounds like this kernel bug which might occur on HDMI connections
that are not 16:9 aspect:
https://gitlab.freedesktop.org/drm/intel/-/issues/6153
But not everyone here seems to have an unusual aspect ratio, or even
Next please:
* More people follow the steps in comment #75.
* Some people try newer kernel versions to see if/where the problem was fixed:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
--
You received this bug notification because you are a member of Desktop
Packages, which is
20 matches
Mail list logo
