Gnome-Shell/GDM not working after update to 3.18

axfelix · 2015-10-22 22:01:46

Is it possible that a new issue has been created? I never had any problems immediately after the Gnome 3.18 release, but I just rebooted my machine for a first time in a while and when I get to GDM all I have is a cursor, no input being recognized (can't even switch to tty) and no login box. Going to mount a live USB and do some pacman updates as a first resort, but not sure how this would've gotten through if it's a widespread issue, so I'm a little worried...

axfelix · 2015-10-22 22:45:38

I was able to fix it by uncommenting #WaylandEnable=false in /etc/gdm/custom.conf after mounting the disk and chrooting via a live USB, though my efforts to revert to slightly earlier GDM and wayland versions didn't seem to solve anything, so I wonder if it's some dependency that's bugged out on me. Anyhow, back in business for now.

axfelix · 2015-10-22 23:39:59

Seems like this might somehow be geoclue (or, more likely, networkmanager) related? https://bugzilla.gnome.org/show_bug.cgi?id=756994

Last edited by axfelix (2015-10-22 23:43:34)

ayr-ton · 2015-10-23 02:15:23

The fix was committed:

https://bugzilla.gnome.org/show_bug.cgi?id=754814

It will be present at version 3.19.

saivert · 2015-10-23 18:28:53

At 3.19? This not being a new feature certainly warrants a 3.18 update release.
I'm not going to be running on unstable Gnome branch just to fix this.

Last edited by saivert (2015-10-23 18:29:30)

tomer007007 · 2015-10-23 19:01:03

I'm having the exact same issue as the OP, I tried uncommenting the WaylandEnable=false, does'nt work, any ideas?

Mons1990 · 2015-10-23 19:46:53

saivert wrote:

At 3.19? This not being a new feature certainly warrants a 3.18 update release.
I'm not going to be running on unstable Gnome branch just to fix this.

+1

htfy96 · 2015-10-24 03:09:37

ayr-ton wrote:

The fix was committed:
https://bugzilla.gnome.org/show_bug.cgi?id=754814
It will be present at version 3.19.

That's horrible. "Login - black screen - switch to tty3 - sudo killall gnome-session - login again" takes me much time.

JohnnyDeacon · 2015-10-25 01:46:53

saivert wrote:

At 3.19? This not being a new feature certainly warrants a 3.18 update release.
I'm not going to be running on unstable Gnome branch just to fix this.

+2

ThePlague · 2015-10-27 16:14:28

I've been looking on the forum and so far nothing has helped me.
I have a clean installation of Arch with GNOME. When I try to start GDM it just sits at a black screen.

I've tried install nvidia, all xorg packages, everything I've seen recommended.

I have an nVidia 760 in this PC and in my laptop I have Intel onboard which it will also not display on.
I did a test run on vmware and it worked perfectly. Any ideas? What error logs should I provide?

Trilby · 2015-10-27 16:50:29

Welcome to the forums ThePlague. I'm not sure how you missed the thread on this exact issue. I'll merge your post into it. (edit: merged)

ThePlague · 2015-10-27 18:09:26

Trilby wrote:

Welcome to the forums ThePlague. I'm not sure how you missed the thread on this exact issue. I'll merge your post into it. (edit: merged)

I didn't miss it. Nothing here worked.

costil · 2015-10-27 18:26:04

This bug doesn't affect only Nvidia. I also had the problem with grey screen and just the cursor with fglrx, but not with OSS drivers. The problem got solved for me from Vi0l0, maintainer of the catalyst driver. There is cogl 1.22.0-2 in [catalyst] repo that you can try:
enable [catalyst] repo
add key
# pacman -Syy
# pacman -S cogl
comment/remove repo
reboot

Last edited by costil (2015-10-28 08:35:13)

almindor · 2015-10-28 15:32:20

ThePlague wrote:

I've been looking on the forum and so far nothing has helped me.
I have a clean installation of Arch with GNOME. When I try to start GDM it just sits at a black screen.
I've tried install nvidia, all xorg packages, everything I've seen recommended.
I have an nVidia 760 in this PC and in my laptop I have Intel onboard which it will also not display on.
I did a test run on vmware and it worked perfectly. Any ideas? What error logs should I provide?

If my patched version of gdm/gnome-shell (see page 2 on this thread) didn't fix it for you then your issue is a separate one.

Given what the patch changes it might be a not-only-nvidia issue however. There is nothing nvidia-only in this bug. It just only happened on nvidia due to it being so damn fast

WorLord · 2015-10-29 13:03:36

almindor wrote:

If my patched version of gdm/gnome-shell (see page 2 on this thread) didn't fix it for you then your issue is a separate one.

FYI: Patched version working great here. Thanks, Almindor! Our long national nightmare is over.

JohnnyDeacon · 2015-10-29 20:52:25

Well. It seems I have to jump to KDE again, at least till 3.19 release

phoenixkc · 2015-10-30 14:02:09

The gnome-shell git repo had a commit 23 hours ago bumping the version to 3.19.1.

Question about protocol: The version on the master branch got bumped. Is this considered stable? Should I flag the package as out of date?

Last edited by phoenixkc (2015-10-30 14:03:39)

Trilby · 2015-10-30 14:50:30

phoenixkc wrote:

Should I flag the package as out of date?

No.

https://www.gnome.org/getting-gnome/ wrote:

Try the latest release
GNOME 3.18 is the latest version, released in September 2015.

So even flags for 3.18 being out of date are inappropriate.

You can build from git and/or the AUR and/or ABS if you want the newest development version. But the current stable version is 3.18.

phoenixkc · 2015-10-30 15:39:44

Got it. Thanks for clarifying.

Nilangshu · 2015-11-06 11:23:04

almindor wrote:

The gdm/nvidia issue has been fixed in latest gnome-shell/gdm. If you can't wait for upstream to land you can use my modified PKGCONFIG/patches and rebuild the package yourself using makepkg. I kept the version so that the new ones will override when they land.
Get the modified/patch included pkgbuilds at http://filebin.ca/2JqhF7yesNEY
Checksum: SHA256 09adfc8b2c8642c099b485a5eb4b5606903172420e3644a6df19aa61541934a7
Just extract, go to gdm and gnome-shell each and execute pkgbuild and then pacman -U <package>

-This has worked for me. Thanks almindor.

danfly09 · 2015-11-12 17:45:58

Same problem here, tired to try everything. The problem is in Gnome and Cinnamon and GDM, lightdm and mate works fine. I'm using an ATI HD6770. The problem is present using linux and linux-lts kernels. Open Source drivers are worse, they totally freeze the machine, using catalyst drivers the problem is as described here, black screen, couple of ramdom white pixels and able to watch and move the mouse pointer.

PS: After updating cogl from Vi0lo repo, finally I was able to launch cinnamon. Next step, try gdm and gnome.

Last edited by danfly09 (2015-11-12 17:56:37)

Mons1990 · 2015-11-13 08:06:35

Fixed with last updates!

ayr-ton · 2015-11-26 23:14:18

Could you please verify if it is working after the last updates and mark the topic as resolved? o/

ayr-ton · 2015-11-26 23:14:50

Could you please verify if it is working after the last updates and mark the topic as resolved? o/

htfy96 · 2015-11-27 03:00:16

ayr-ton wrote:

Could you please verify if it is working after the last updates and mark the topic as resolved? o/

The latest gdm(3.18.2-1) and gnome-shell(3.18.3-1) only reduced the frequency of this bug for me(dual monitors). (50% => 20%)

Nov 27 10:13:29 lz gnome-session[1253]: (gnome-shell:3679): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to open display ':0'
Nov 27 10:13:29 lz gnome-session[1253]: (gnome-shell:3679): mutter-WARNING **: Unable to initialize Clutter.
Nov 27 10:13:29 lz gnome-session[1253]: ** (gnome-settings-daemon:3673): WARNING **: Unable to initialize GTK+
Nov 27 10:13:29 lz gnome-session[1253]: gnome-session-binary[1253]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Nov 27 10:13:29 lz gnome-session-binary[1253]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Nov 27 10:13:29 lz gnome-session[1253]: gnome-session-binary[1253]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Nov 27 10:13:29 lz gnome-session-binary[1253]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Nov 27 10:13:29 lz gnome-session[1253]: gnome-session-binary[1253]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Nov 27 10:13:29 lz gnome-session-binary[1253]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Nov 27 10:13:29 lz systemd[3274]: Started Sound Service.
Nov 27 10:13:29 lz /usr/lib/gdm/gdm-x-session[3299]: (II) Server terminated successfully (0). Closing log file.
Nov 27 10:13:29 lz gnome-session[3310]: ** (gnome-settings-daemon:3674): WARNING **: Unable to initialize GTK+
Nov 27 10:13:29 lz gnome-session-binary[3310]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Nov 27 10:13:29 lz gnome-session-binary[3310]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
Nov 27 10:13:29 lz gnome-session-binary[3310]: Unrecoverable failure in required component gnome-settings-daemon.desktop
Nov 27 10:13:29 lz gdm[435]: Child process -1236 was already dead.
Nov 27 10:13:29 lz gnome-session[3310]: gnome-session-binary[3310]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
Nov 27 10:13:29 lz gnome-session[3310]: gnome-session-binary[3310]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
Nov 27 10:13:29 lz systemd-logind[416]: Removed session c1.
Nov 27 10:13:29 lz systemd[1]: Stopping User Manager for UID 120...

Arch Linux

#51 2015-10-22 22:01:46

Re: Gnome-Shell/GDM not working after update to 3.18

#52 2015-10-22 22:45:38

Re: Gnome-Shell/GDM not working after update to 3.18

#53 2015-10-22 23:39:59

Re: Gnome-Shell/GDM not working after update to 3.18

#54 2015-10-23 02:15:23

Re: Gnome-Shell/GDM not working after update to 3.18

#55 2015-10-23 18:28:53

Re: Gnome-Shell/GDM not working after update to 3.18

#56 2015-10-23 19:01:03

Re: Gnome-Shell/GDM not working after update to 3.18

#57 2015-10-23 19:46:53

Re: Gnome-Shell/GDM not working after update to 3.18

#58 2015-10-24 03:09:37

Re: Gnome-Shell/GDM not working after update to 3.18

#59 2015-10-25 01:46:53

Re: Gnome-Shell/GDM not working after update to 3.18

#60 2015-10-27 16:14:28

Re: Gnome-Shell/GDM not working after update to 3.18

#61 2015-10-27 16:50:29

Re: Gnome-Shell/GDM not working after update to 3.18

#62 2015-10-27 18:09:26

Re: Gnome-Shell/GDM not working after update to 3.18

#63 2015-10-27 18:26:04

Re: Gnome-Shell/GDM not working after update to 3.18

#64 2015-10-28 15:32:20

Re: Gnome-Shell/GDM not working after update to 3.18

#65 2015-10-29 13:03:36

Re: Gnome-Shell/GDM not working after update to 3.18

#66 2015-10-29 20:52:25

Re: Gnome-Shell/GDM not working after update to 3.18

#67 2015-10-30 14:02:09

Re: Gnome-Shell/GDM not working after update to 3.18

#68 2015-10-30 14:50:30

Re: Gnome-Shell/GDM not working after update to 3.18

#69 2015-10-30 15:39:44

Re: Gnome-Shell/GDM not working after update to 3.18

#70 2015-11-06 11:23:04

Re: Gnome-Shell/GDM not working after update to 3.18

#71 2015-11-12 17:45:58

Re: Gnome-Shell/GDM not working after update to 3.18

#72 2015-11-13 08:06:35

Re: Gnome-Shell/GDM not working after update to 3.18

#73 2015-11-26 23:14:18

Re: Gnome-Shell/GDM not working after update to 3.18

#74 2015-11-26 23:14:50

Re: Gnome-Shell/GDM not working after update to 3.18

#75 2015-11-27 03:00:16

Re: Gnome-Shell/GDM not working after update to 3.18

Board footer