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]
perform_link_training_with_retries: Link(2) training attempt 2 of 4 failed @
rate(10) x lane(2) : fail reason:(1)
cze 23 15:35:37 jarek-Inspiron kernel: [drm]
perform_link_training_with_retries: Link(2) training attempt 3 of 4 failed @
rate(10) x lane(2) : fail reason:(1)
...
cze 23 15:35:37 jarek-Inspiron kernel: [drm] enabling link 2 failed: 15
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int)
number < g_list_length (manager->logical_monitors)' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]:
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL'
failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int)
number < g_list_length (manager->logical_monitors)' failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]:
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL'
failed
cze 23 15:35:38 jarek-Inspiron gnome-shell[3512]:
meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor <
n_logical_monitors' failed
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned
frame counter but no frame drawn time
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned
frame counter but no frame drawn time
cze 23 15:35:39 jarek-Inspiron gnome-shell[3512]: 0x3800080: Frame has assigned
frame counter but no frame drawn time
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Screens go into flicker cycle after going blank with external monitor(s)
+ [amdgpu] Screens go into flicker cycle after going blank with external
monitor(s)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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:
[amdgpu] Screens go into flicker cycle after going blank with external
monitor(s)
Status in Mutter:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
This happens whenever screen goes blank after inactivity with external
monitors.
When there is only one external monitor after few cycles the system
recovers from the bug.
When there are more than one monitors the system almost never recovers
until unplugging extra monitor, as shown in video:
https://photos.app.goo.gl/td6coEKFQd3DKe9C7
Happens on desktop and login screen. The same result with Wayland and
X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or
is it connected via USB-C hub or directly.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 13 12:36:44 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-04-13 (60 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
RelatedPackageVersions: mutter-common 44.1-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2023647/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
