Hi, Not sure which mail list it should address this report, so I'm posting it here.
About a couple of weeks since gdm started to expose "Oh no! Something has gone wrong." message on my amd64 current. I suspect the reason is the gnome-session-binary killed by SIGILL, as I see in my /var/log/messages: Jul 19 01:20:31 wurger gnome-session-binary[28233]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 4 Jul 19 01:20:31 wurger gnome-session-binary[28233]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 4 Jul 19 01:20:31 wurger gnome-session-binary[28233]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Jul 19 01:20:45 wurger gnome-session-binary[28233]: WARNING: GsmConsoleKit: Calling GetSessionClass failed. Jul 19 01:20:45 wurger gnome-session-binary[28233]: WARNING: Could not get session class: Operation not permitted Jul 19 01:20:45 wurger gdm[99524]: Gdm: Child process -11483 was already dead. Jul 19 01:20:45 wurger gdm[99524]: Gdm: GdmDisplay: Session never registered, failing Jul 19 01:20:45 wurger gdm[99524]: GLib: Source ID 8 was not found when attempting to remove it The problem exists on my "cpu0: 12th Gen Intel(R) Core(TM) i7-1255U", on older Intel CPUs gnome works fine.
