You are not logged in.
I upgraded last night to Gnome 3.24. Initially I couldn't get any display at all, but I fixed that by removing the patched gnome-settings-daemon-redshift and installing instead gnome-settings-daemon.
Now I'm able to get a display, but I'm only presented with a blank grey screen and a mouse cursor instead of GDM login. Trying to go straight to Gnome with startx results in the same thing.
I reinstalled both gnome and gdm but it hasn't helped. I also haven't been able to find much useful information in the logs:
The most interesting line is -
Gnome-session-binary[547]: Unrecoverable error in required component org.gnome.Shell.desktop
I'm fully up to date and using the latest Nvidia drivers. I did try booting with Nouveau but didn't get any display at all.
Any ideas?
Thanks.
Last edited by themusicalduck (2017-04-25 21:19:13)
Offline
Managed to get lxde working at least.
I've also seen errors like this:
Apr 25 19:41:03 rikka systemd[1]: Starting GNOME Display Manager...
Apr 25 19:41:03 rikka systemd[1]: Started GNOME Display Manager.
Apr 25 19:41:04 rikka gdm[528]: GdmDisplay: display lasted 0.390469 seconds
Apr 25 19:41:04 rikka gdm[528]: Child process -562 was already dead.
Apr 25 19:41:04 rikka gdm[528]: Child process 551 was already dead.
Apr 25 19:41:04 rikka gdm[528]: Unable to kill session worker process
Apr 25 19:41:42 rikka systemd[1]: Stopping GNOME Display Manager...
Apr 25 19:41:42 rikka gdm[528]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Apr 25 19:41:42 rikka systemd[1]: Stopped GNOME Display Manager.
Apr 25 19:44:51 rikka systemd[1]: Starting GNOME Display Manager...
Apr 25 19:44:51 rikka systemd[1]: Started GNOME Display Manager.
Apr 25 19:44:52 rikka gdm[3457]: GdmDisplay: display lasted 0.155367 seconds
Apr 25 19:44:52 rikka gdm[3457]: Child process -3475 was already dead.
Apr 25 19:44:52 rikka gdm[3457]: Child process 3463 was already dead.
Apr 25 19:44:52 rikka gdm[3457]: Unable to kill session worker process
Apr 25 19:45:06 rikka systemd[1]: Stopping GNOME Display Manager...
Apr 25 19:45:06 rikka gdm[3457]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Apr 25 19:45:06 rikka systemd[1]: Stopped GNOME Display Manager.
Apr 25 19:47:42 rikka systemd[1]: Starting GNOME Display Manager...
Apr 25 19:47:42 rikka systemd[1]: Started GNOME Display Manager.
Apr 25 19:48:04 rikka systemd[1]: Stopping GNOME Display Manager...
Apr 25 19:48:04 rikka gdm[5240]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Apr 25 19:48:04 rikka systemd[1]: Stopped GNOME Display Manager.
I did reinstall glibc, but it didn't help.
I also uncommented WaylandEnable=false in /etc/gdm/custom.conf, but that hasn't helped either.
Last edited by themusicalduck (2017-04-25 18:53:32)
Offline
I remember there were issues with NVIDIA drivers in older Gnome 3 versions that could be fixed by setting certain environment variables. Do you maybe still have those set in a shell script somewhere?
When I experimented earlier today with an environment variable "CLUTTER_VBLANK=none", I also got that gray screen with just mouse pointer. Removing the environment variable made things work again.
Offline
That did it! Thanks so much!
Offline
When I experimented earlier today with an environment variable "CLUTTER_VBLANK=none", I also got that gray screen with just mouse pointer. Removing the environment variable made things work again.
Thanks, Ropid! I forgot that I had exactly that environment variable set. GDM would appear, but logging in just leads me to a grey textured screen with the Adwaita-themed cursor.
I was using it to play Counter-Strike: Global Offensive and Team Fortress 2 in windowed mode under GNOME 3.22, because I didn't want Clutter limiting my framerates to 60 fps (interestingly, this only happens when playing those two games mentioned above).
Removing the environment variable (I had it in /etc/profile.d/custom.sh) allowed me to log into GNOME once again! Unfortunately, this means I might not be able to enjoy >60 fps (on average) when playing those two games in windowed mode. I guess I'll have to play with a different desktop environment or window manager (or in full-screen mode), but thanks again!
Last edited by jlsantos (2017-04-26 22:12:21)
Offline
I have the exact same problem.
I removed the line from /etc/environment.
I also re-installed the gnome packages.
I also removed any kernel parameters.
Still no luck
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
[...] I guess I'll have to play with a different desktop environment or window manager (or in full-screen mode), but thanks again!
I had a setup for a while where I had a hotkey in Gnome to run "openbox --replace", and then in Openbox I ran "gnome-shell --replace" to load Gnome's window manager again. That's how I turned off Gnome's compositing for gaming.
Offline