There's a hardware connection problem which seems to come first in some
cases:
cze 23 15:35:36 jarek-Inspiron kernel: [drm]
perform_link_training_with_retries: Link(2) training attempt 1 of 4 failed @
rate(10) x lane(2) : fail reason:(1)
...
cze 23 15:35:36 jarek-Inspiron kernel: [drm]
My optimism was to early. Journal dump attached. Took it after
unplugging one of the monitors and waiting few flickers for desktop to
stabilize.
Btw, were should I report that Slack crashes when I right click inside?
:D
** Attachment added: "journal_wayland.txt"
It looks like a kernel update was released a few days ago so maybe that
fixed it?
--
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/2023647
Title:
Screens go into flicker cycle after
I don't know what changed but I switched back to Wayland a few days ago
and cannot repoduce any glitches I suffered. Is this the week I stop
regretting buying a laptop on AMD chipset?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
That's also interesting to me. Please report that crash when you can...
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I'll try to find some time during the weekend to reproduce it with
Wayland. I am using this PC for work during the week and Wayland keeps
crashing with entire session whenever I am in a videocall. :)
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: mutter
Status: Unknown => New
--
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/2023647
Title:
Screens go into flicker cycle after going blank with external
Thanks. Can you repeat that in a Wayland session?
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2604
https://gitlab.gnome.org/GNOME/mutter/-/issues/2604
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2604
Importance: Unknown
Status:
As requested attaching a result of a journalctl -b0 command.
This happened after renaming monitor.xml and monitor.xml~ so
unfortunaltely that does not help.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023647/+attachment/5679605/+files/journal.txt
I wonder if it matters that some of your configs in
~/.config/monitors.xml don't intersect with the origin 0,0. If you
rename that file and then log in again, does the bug stop happening?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
And next time the flicker occurs, please run:
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/2023647
Title:
Thanks for the bug report. These log messages look relevant:
[118317.782940] jarek-Inspiron gnome-shell[3471]: Window manager warning:
Configuring CRTC 79 with mode 1881 (1920 x 1200 @ 59,950172) at position 0, 0
and transform 0 failed
[118319.278873] jarek-Inspiron gnome-shell[3471]:
12 matches
Mail list logo
