Impact correction: reported high CPU usage and whole-system unresponsiveness
The reporter clarified on 2026-10-08 that the impact was more severe than stated in the original report: they observed high CPU usage and the whole system becoming blocked/unresponsive during the RDP-related problem, not merely a failed remote login. This impact was omitted from the initial report and should be considered during triage. This is a user-observed symptom. An exact CPU percentage, responsible process/thread, onset time, duration, and a contemporaneous process- level trace have not been captured, so no confirmed attribution to GNOME Remote Desktop, Mutter, or another component is claimed. Nor is a shared cause with the separately reported graphical-corruption screenshot established. Retained historical measurements provide limits, not proof or disproof of that observation: - The machine has 32 logical CPUs. Ten-minute aggregate sar samples on October 7 remain mostly idle before the last pre-reboot CPU sample at 23:20 (93.78% aggregate idle); there is no CPU sample covering the directly recorded 23:21:18 handover failure through the subsequent 23:28 service stop. These coarse, all-CPU averages cannot exclude a later spike or an individual saturated process/core causing desktop unresponsiveness. - Samples around the October 8 screenshot also show low aggregate load; they do not identify the time of the reported CPU/unresponsiveness incident or establish that the screenshot and CPU symptom occurred together. - Systemd recorded only 21.398 seconds of total CPU for the SYSTEM remote-login service over its 4-day lifetime. That accounting does not cover every user-session/handover/compositor process and cannot diagnose a host-wide freeze. Please treat whole-system unresponsiveness as reported severity/impact, while keeping the causal link and process-level CPU attribution unconfirmed. A per-process/thread CPU snapshot and exact incident timing would be useful during a recurrence; no disruptive reproduction or service restart was performed to obtain this correction. ** Attachment added: "Historical aggregate CPU/load; high-CPU and whole-system unresponsiveness impact correction" https://bugs.launchpad.net/bugs/2170125/+attachment/6007240/+files/historical-cpu-load.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170125 Title: RDP reconnect to long-lived GNOME session fails during handover (UnknownObject) on Ubuntu 26.04.1, gnome-remote-desktop 50.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2170125/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
