Intermittend black screen - after login on bootup

[Kitsab]

Hello,

I'm experiencing intermittent dekstop environment loading issues with gnome 3.28. After logging in on the Session greeter, it loads for a few seconds and no desktop appears just a grey/black backround, nothings gonna happen.
First I just done Alt-Print-REISUB to recover, but I found out switching console Ctrl-Alt-F3 and back to Ctrl-Alt-F1 brings me back to the login screen and I can do another login which resolved the issue for me everytime it happened.
I think it is going to hapen every 10-20st boot.
I'll attach a few logs.

Additionally I've got to tell I manually installed NVIDIA 390.42 after upgrading to 18.04 beta.

Best regards

Kitsab

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 1 15:55:32 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus-desktop
InstallationDate: Installed on 2015-02-14 (1172 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

[Sebastien Bacher (seb128)]

Could be something similar to https://gitlab.gnome.org/GNOME/gnome-shell/issues/227 , would be worth reporting upstream

[Kitsab (kitsab)]

Hello Sebastien,

it is possible, that this is the same issue, I also entered the password wrong the first time it appeared today, the second login trial with the correct password lead me into the black-screen.

Best regards

Kitsab

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Simon P. (simpre)]

I am experiencing the same problem with 18.04. After a failed login attempt and the subsequent login, the green stays black and only the mouse cursor is shown.

[Simon P. (simpre)]

Seems this bug was fixed. At least I cannot reproduce it any more since the recent updates.