Just FYI, happened about two weeks ago and yet again today. This time I tried to turn off the screen and on again (vis settings -> display). But turning on again is blocked by the UI saying "Changes can not be Applied" "This could be due to hardware limitations". Was worth a try for a mitigation, back to reboot for now :-/
The Journal has the following (I still have MUTTER_DEBUG=kms enabled) 1. what feels like millions of the following Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Committing update flags: ATOMIC_NONBLOCK|TEST_ONLY Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: Assigning buffer to primary plane update on CRTC (72) with src rect 0,000000,0,000000 1920,000000x1080,000000 and dst rect 0,0 1920x1080 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: Posting direct scanout update for CRTC 72 (/dev/dri/card5) Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Processing update Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Assigning primary plane (52, /dev/dri/card5) to 138, 1920x1080+0+0 -> 1920x1080+0+0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'FB_ID' (17) to 138 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'CRTC_ID' (20) to 72 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'SRC_X' (9) to 0,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'SRC_Y' (10) to 0,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'SRC_W' (11) to 1920,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'SRC_H' (12) to 1080,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'CRTC_X' (13) to 0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'CRTC_Y' (14) to 0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'CRTC_W' (15) to 1920 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'CRTC_H' (16) to 1080 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'IN_FENCE_FD' (18) to 170 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane (52, /dev/dri/card5) rotation to 1 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 52 (/dev/dri/card5) property 'rotation' (54) to 1 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Committing update flags: ATOMIC_NONBLOCK|PAGE_FLIP_EVENT Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Adding page flip data for (72, /dev/dri/card5): 0x72e968086090 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Page flip callback for CRTC (72, /dev/dri/card5), data: 0x72e968086090 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: Setting page flip timings for CRTC (72, /dev/dri/card5), sequence: 7682755, sec: 536321, usec: 106496 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: Assigning buffer to primary plane update on CRTC (93) with src rect 0,000000,0,000000 1920,000000x1080,000000 and dst rect 0,0 1920x1080 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: Posting direct scanout test update for CRTC 93 (/dev/dri/card5) synchronously Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Processing update Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Assigning primary plane (73, /dev/dri/card5) to 136, 1920x1080+0+0 -> 1920x1080+0+0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'FB_ID' (17) to 136 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'CRTC_ID' (20) to 93 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'SRC_X' (9) to 0,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'SRC_Y' (10) to 0,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'SRC_W' (11) to 1920,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'SRC_H' (12) to 1080,00 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'CRTC_X' (13) to 0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'CRTC_Y' (14) to 0 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'CRTC_W' (15) to 1920 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'CRTC_H' (16) to 1080 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'IN_FENCE_FD' (18) to 170 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane (73, /dev/dri/card5) rotation to 1 Nov 20 18:14:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting plane 73 (/dev/dri/card5) property 'rotation' (75) to 1 And I really mean many of these: $ journalctl --since "2024-11-21 10:25:00" --until "2024-11-21 10:30:00" | grep -c "Assigning buffer to primary plane update on CRTC" 5182 => 1k / minute is that supposed to be normal due to the debug or is that a problem by itself? I was looking for anything different around the time it happened today. Messages that I found by excluding those I got thousands of time per minute where these Nov 21 10:31:16 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:16 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 1 damage clips on 31 Nov 21 10:31:18 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:18 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 1 damage clips on 31 Nov 21 10:31:56 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:56 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 1 damage clips on 31 Nov 21 10:31:59 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:59 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:59 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:31:59 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:00 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:01 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:01 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:01 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:02 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:04 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:04 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 1 damage clips on 31 Nov 21 10:32:18 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:18 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:18 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 2 frames pending (triple-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 2 frames pending (triple-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 2 frames pending (triple-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 5 damage clips on 31 Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 5 damage clips on 31 Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 5 damage clips on 31 Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: [atomic] Setting 5 damage clips on 31 Nov 21 10:32:20 Keschdeichel gnome-shell[6793]: KMS: Swap buffers: 1 frames pending (double-buffering) Not sure if that is any help, but I hope it is. I'll stop the massive debug and go for MUTTER_DEBUG_FORCE_KMS_MODE=simple now trying to check if it is no more happening then over long periods of time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2083479 Title: 24.04: single screen gets stuck and no more updates (5 monitor setup with i915 and DisplayLink) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, I considered it a one off, but it now happened a second time so I thought it might be worth to report so you can match against anything else you might get reported. ## Setup - Ubuntu 24.04 with mostly defaults (I config a few things but e.g. do not install a massive amount of extensions or such) - Lenovo T580 - GPU UHD Graphics 620 - DisplayLink Plugable USBC-6950 Dual HDMI Adapter - 5 Screens left to right - top row: 1: laptop display, 2: full HD on displaylink, 3: full HD on displaylink - bottom row: 4: full HD on DP of the docking station, 5: full HD on DP of the docking station - 1: is the primary screen (e.g. with the dock) - 4: is the screen with issues at least the 2/2 times it happened so far - In xrand terms it is DP-4 connected 1920x1080+514+1920 (normal left inverted right x axis y axis) 600mm x 340mm DP-5 connected 1920x1080+2434+1920 (normal left inverted right x axis y axis) 600mm x 340mm eDP-1 connected primary 1920x1080+0+840 (normal left inverted right x axis y axis) 340mm x 190mm DVI-I-1 connected 1920x1080+3000+840 (normal left inverted right x axis y axis) 600mm x 340mm DVI-I-2 connected 1080x1920+1920+0 left (normal left inverted right x axis y axis) 600mm x 340mm - $ echo $XDG_SESSION_TYPE wayland ## Situation: #1 first time 24. Sept - Right at the moment when I tried to screen share through meets the screen (4) froze up - froze to me means the content froze, not going black but no more doing updates e.g. no mouse moves are seen, no video update, nothing - The system otherwise was happy and responsive I could continue to work on the other screens - The content stayed frozen even when e.g. changing workspaces - I had a look, but nothing interesting came up to my non-GUI-trained eyes - I've set up my system to power down screens on lock, so I thought maybe lock/unlock would re-set the screen. But what happened was that all screens successfully powered down - yet nothing ever woke up again The messages (interesting to me) that I spot around there are: Sep 24 17:31:34 Keschdeichel xdg-desktop-por[952454]: Failed to associate portal window with parent window ... Sep 24 17:33:52 Keschdeichel gnome-shell[5030]: Can't update stage views actor Window drag helper [ClutterActor] is on because it needs an allocation. Sep 24 17:34:02 Keschdeichel gnome-shell[5030]: Can't update stage views actor unnamed [Gjs_ui_altTab_WindowSwitcherPopup] is on because it needs an allocation. #2 second time 1. Oct ~18:00 +- 25 min (The meeting was important and hence I failed to spot the exact time) - I was in a screen sharing session (coincidence or am I just having too many meetings?) - Then suddenly I found the same screen (4) frozen - My counterpart told me they could still see me move and even the active sharing of screen 5 still was updating - I was again looking into the logs, but again found nothing obvious to me - I reached out to #desktop what I should look out for but didn't catch the reply before auto-screen save kicked in. That in turn again made the system fully unresponsive so I had to reboot. Again I found the same messages, Okt 01 17:46:02 Keschdeichel xdg-desktop-por[6150]: Failed to associate portal window with parent window Okt 01 17:46:04 Keschdeichel wireplumber[4976]: <WpPortalPermissionStorePlugin:0x5814964a3840> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera But in hindsight I consider these red herring, as I see them more often. $ journalctl -b -1 | grep "associate portal window with parent window" -c 14 I asked in Desktop what to look out for and got the good hint to look for "drm" ot "atomic". I found this one: Sep 24 15:49:28 Keschdeichel kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=338711 end=338712) time 137 us, min 1073, max 1079, scanline start 1072, end 1081 But that is only in one of the logs and hours before the issue happened the second time. I'll attach the full journals of those two cases and run apport-bug to collect the usual-suspect information. I hope that this makes this good enough to be somewhat helpful, if you end up having some theories let me know what I should check next time as I keep control of the other screens that should be well debuggable if only I'd know what to look for. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 GsettingsChanges: InstallationDate: Installed on 2023-09-26 (372 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) NonfreeKernelModules: zfs Package: gnome-shell 46.0-0ubuntu6~24.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.1 Tags: noble Uname: Linux 6.8.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083479/+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
