When logging into gnome the gnome shell sometimes looks like the attached screenshots. Using Alt-F2 "r" to restart the shell fixes the corruption. Reproducible: Always
Created attachment 371456 [details] Bottom left corner in the activities overlay
Created attachment 371460 [details] Top centre in the activities overlay
Created attachment 371462 [details] Top right corner
Created attachment 371464 [details] Shutdown message window After pressing ctrl+alt+del, the top right menu is unusable.
Are you able to reproduce on a newly created user account?
(In reply to Pacho Ramos from comment #5) > Are you able to reproduce on a newly created user account? I have been unable reproduce with new user account, reloging between users worked ok even for my regular account. The corruption usually appears on the first login after startup. I have been hit by #503082, so it might be a result of fs corruption (but how could restarting shell fix this?). If I see the corruption again on clean boot, I'll try logging to the new account first to see if it can be reproduced.
I have managed to reproduce this after a shell restart in the middle of the session. (kill -SUGUSR1 $PID_OF_SHELL) This time it was not fixable by additional shell restarts, however I noticed this in kernel log: traps: gdbus[5417] trap int3 ip:7f8e223fa779 sp:7f8e1983d940 error:0 gdbus[6052]: segfault at 8 ip 00007f2022705f98 sp 00007f2019b60ae0 error 4 in libglib-2.0.so.0.3800.2[7f20226cc000+126000] Restarting gnome (systemctl restart gdm) helped. Is there a daemon that needs to be running for gnome-shell to get proper styles? I tried diffing the list of processes when this happened just after login but saw no difference in running processes. I also tried sending SIGSEGV to random dbus related processes run by local user, but I could not reproduce the behavior. either nothing happened or I was logged out immediately after sending the segv signal. I have no idea how dbus things work, so if you can point me to a process that matches the description I can test whether killing it reproduces the behavior.
please retry with 3.14.4