Regression in 3.30.1 (from 3.30.0): gnome-shell process in gdm is spiking at 100% once logged in
Confirmed this didn't happen with gdm 3.30.0 with 70861874 reverted (3.30.0-0ubuntu2) (tested on ubuntu cosmic). Upgraded to gdm 3.30.1.
- Boot up, gnome-shell gdm login -> process behaves normally
- Log in
- While the user session starts, the gnome-shell gdm process is spiking at 100%.
It seems that the login session and display detection is respawning in loop: http://paste.ubuntu.com/p/q6wwXqKbmG/. Remember that we disabled Wayland and so, running on Xorg if that can have an impact triggering the bug.
After some bisecting, I found that (I have a dual intel/nvidia card) this commit was guilty: 5cd78602.
I have tried thus 3.30.0 (working version) and add that commit on top, and indeed, it triggers the same issue, same with WaylandEnable=false
in custom.conf
.
Note that in ubuntu our default user session is using Xorg, but we let the Wayland detection for gdm. So GNOME Shell on xorg on my machine is working for my user (and also for gdm… until logged in).
Here are some logs on 3.30.1. note that to make things clearer, I reached the login screen at 14:00 and waited until 14:01 to start login in, get into the session, and then gdm GNOME Shell respawns indefinitely. This way, we separate from the ureadahead noise.
Note that GdmManager: trying to open new session
is written multiple times in failing.log, confirming this looping behavior and the ice_io_error_handler
error.
More info (with older logs):
I'm attaching 2 journalctl logs:
- one with 3.30.0 + this commit failing.log
- one with 3.30.0 success.log
Note that in failing.log, and that it can't access to my ICC profile (set in GNOME Control Center for my user):
oct. 09 11:52:49 casanier gsd-color[1935]: failed to set screen _ICC_PROFILE: L’ouverture du fichier « /home/didrocks/.local/share/icc/edid-2387fed1096e7df0914900b407c44088.icc » a échoué : Permission non accordée
(permission denied).
-rw-rw-r-- 1 didrocks didrocks 1300 mai 24 19:17 /home/didrocks/.local/share/icc/edid-2387fed1096e7df0914900b407c44088.icc
drwxrwxr-x 2 didrocks didrocks 4096 sept. 3 19:09 /home/didrocks/.local/share/icc/
However, I tried removing the color profile from G-C-C, the CPU spike once logged in is still there, and I don't have ICC* warnings in my logs.
If you need any other debug info, do not hesitate to ask.