VNC login, see "Oops, something went wrong." screen
The Xvnc server was enabled on server. Connect to server by VNC, we can see the login screen. Log in as a user(the user was created newly), then we see the "Oops, something went wrong." screen.
This happened on HPE ProLiant DL385 Gen10 server. The CPU is
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 2
Core(s) per socket: 32
Socket(s): 2
NUMA node(s): 2
Vendor ID: AuthenticAMD
CPU family: 23
Model: 49
Model name: AMD EPYC 7452 32-Core Processor
Stepping: 0
CPU MHz: 1497.243
CPU max MHz: 2350.0000
CPU min MHz: 1500.0000
After I mark this line, login becomes successful.
diff --git a/gnome-session/main.c b/gnome-session/main.c
index 7f06dfa..f772514 100644
--- a/gnome-session/main.c
+++ b/gnome-session/main.c
@@ -84,7 +85,7 @@ on_name_lost (GDBusConnection *connection,
{
if (connection == NULL) {
g_warning ("Lost name on bus: %s", name);
- gsm_fail_whale_dialog_we_failed (TRUE, TRUE, NULL);
+ //gsm_fail_whale_dialog_we_failed (TRUE, TRUE, NULL);
} else {
g_debug ("Calling name lost callback function");
I guess on this powerful CPU, the gnome-session-failed has chance to spawn, on other CPU the gnome-session-failed has no chance to spawn, so we didn't meet this issue on other hardware.
For the warning gnome-session-binary[]: WARNING: Lost name on bus: org.gnome.SessionManager
, we can see it always when user log in or log out. I think we need to consider what to do when this warning happens.