Gnome-Shell/GDM not working after update to 3.18

Commod0re · 2015-10-13 00:41:40

I'm having this issue with lightdm (specifically with lightdm-webkit2-greeter and lightdm-webkit-theme-archlinux) after updating, even with glib2 2.46.0-2. lightdm-gtk-greeter works fine.

What's weird is, things show up OK at first, and then when I click my username the whole screen turns white (though login still works blind)

From /var/log/x-0-greeter.log.old:

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'WebKitWebView': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'GtkWindow': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'WebKitWebView': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'GtkWindow': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'WebKitWebView': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'GtkWindow': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'WebKitWebView': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gtk-WARNING **: drawing failure for widget 'GtkWindow': invalid value for an input Visual*

(lightdm-webkit2-greeter:5021): Gdk-WARNING **: lightdm-webkit2-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

EDIT: nevermind; I see that the issue has already been posted on the github issue tracker for lightdm-webkit2-greeter.

Last edited by Commod0re (2015-10-13 00:52:26)

ranjak · 2015-10-13 10:59:41

As an AMD Catalyst user using startx, I get similar problems : black screen, a few white dots, but I can see and move the cursor. Pressing Esc or switching tty doesn't help.
This could very well be our issue : https://bugzilla.gnome.org/show_bug.cgi?id=756306. I get the same message in my journal (shader compilation failed).
I hope this bug isn't on the Catalyst side...

Last edited by ranjak (2015-10-13 11:10:05)

bkuma75 · 2015-10-13 13:56:55

I'm having this same exact issue using gnome, gdm gives have oops message with a grey screen, I then switched to lightdm which did give me a login screen but after I logged in it was only a black screen with the white dots in the upper left corner. I think this is a catalyst issue because I did a fresh install and the system booted up with no issues, gnome and gdm worked as expected but after installing catalyst and black listing radeon and all the other instructions on the wiki after my first reboot I couldn't even get to gnome. I haven't tried the open source drivers because they make my gpu fan too loud so I would rather use catalyst, right now I'm using ubuntu because arch is unusable to me. Has anyone who got the black screen with the dots been able to figure this out yet?

Last edited by bkuma75 (2015-10-13 13:57:57)

ranjak · 2015-10-13 14:18:01

I'd say the bug is on Gnome's end, the issue is likely caused by the failing shader compilation, which is due to the GLSL version being too old for the GL context.

bkuma75 · 2015-10-13 14:36:54

ranjak wrote:

I'd say the bug is on Gnome's end, the issue is likely caused by the failing shader compilation, which is due to the GLSL version being too old for the GL context.

everything was fine before the kernel and gnome update. I know catalyst downgrades the kernel to lts so do you think downgrading gnome back to lets say 3.16 would fix the issue?

BloodyAngel75 · 2015-10-13 15:34:31

bkuma75 wrote:

everything was fine before the kernel and gnome update. I know catalyst downgrades the kernel to lts so do you think downgrading gnome back to lets say 3.16 would fix the issue?

yes downgrading gnome to 3.16 fixed the issue in my case. I also wrote a way to downgrade those packages in this forum post.

bkuma75 · 2015-10-13 16:08:25

BloodyAngel75 wrote:

bkuma75 wrote:
everything was fine before the kernel and gnome update. I know catalyst downgrades the kernel to lts so do you think downgrading gnome back to lets say 3.16 would fix the issue?
yes downgrading gnome to 3.16 fixed the issue in my case. I also wrote a way to downgrade those packages in this forum post.

Thanks for responding, one more question though. is it possible to downgrade gnome and gnome-extra with

pacman -Syy gnome gnome-extra

in its entirety with out without individually choosing what packages I need downgraded like what you did in your post?

BloodyAngel75 · 2015-10-13 17:30:54

bkuma75 wrote:

is it possible to downgrade gnome and gnome-extra with
pacman -Syy gnome gnome-extra
in its entirety with out without individually choosing what packages I need downgraded like what you did in your post?

In my case this wouldn't work since some packages I had to downgrade aren't available in gnome/gnome-extra (for example clutter). However it's a good idea to exchange most of the packages with the gnome/gnome-extra package groups (I haven't thought of that , so thanks).
To list all package within the package group "gnome" use:

pacman -Qg gnome

jasonwryan · 2015-10-13 17:33:53

bkuma75 wrote:

is it possible to downgrade gnome and gnome-extra with
pacman -Syy gnome gnome-extra
in its entirety with out without individually choosing what packages I need downgraded like what you did in your post?

Never do this...

phutchins · 2015-10-14 11:11:45

I'm seeing this issue also. When the login screen comes up, I click on the spash box to see the usernames and as soon as they appear, the screen goes white. I can keep my mouse in the right area and still click on the login if I'm lucky then type my password and hit enter to log in.

What do we need to do to get this fixed? Can we identify the maintainers of the packages with issues here?

tomz · 2015-10-14 21:59:49

phutchins wrote:

What do we need to do to get this fixed? Can we identify the maintainers of the packages with issues here?

I think its not fair to the developers, Archlinux is bleeding edge distro so the packages can often be not working with all variants of hardware or software.

Please find below the list of packages that with these release needs to be blocked to get fully working CINNAMON+GDM, in my case I use FGLRX drivers.

└──> ~ $ >> grep 'Ignore' /etc/pacman.conf
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg = gnome* clutter* cogl* mutter

The list was prepared from 88 packages required to upgrade.

Last edited by tomz (2015-10-14 22:04:20)

almindor · 2015-10-15 02:50:10

phutchins wrote:

I'm seeing this issue also. When the login screen comes up, I click on the spash box to see the usernames and as soon as they appear, the screen goes white. I can keep my mouse in the right area and still click on the login if I'm lucky then type my password and hit enter to log in.
What do we need to do to get this fixed? Can we identify the maintainers of the packages with issues here?

This is not a packager or arch linux issue. It's probably a gnome issue (see bugrep) or maybe even an nvidia issue.

JohnnyDeacon · 2015-10-17 04:15:49

Same problem. I'm using GTX660, Gnome 3.18. What I'm doing while bug is fixed is:

I Had to disable gdm service, but every time I reboot the PC, I have to reinstall glib2, then I do systemctl start gdm.service. If i do not reinstall glib2 and start gdm service after reboot, my PC get stuck without login into gnome...

Mons1990 · 2015-10-17 11:17:55

JohnnyDeacon wrote:

Same problem. I'm using GTX660, Gnome 3.18. What I'm doing while bug is fixed is:
I Had to disable gdm service, but every time I reboot the PC, I have to reinstall glib2, then I do systemctl start gdm.service. If i do not reinstall glib2 and start gdm service after reboot, my PC get stuck without login into gnome...

I think pressing Esc is more comfortable

JohnnyDeacon · 2015-10-17 14:11:48

Mons1990 wrote:

JohnnyDeacon wrote:
Same problem. I'm using GTX660, Gnome 3.18. What I'm doing while bug is fixed is:
I Had to disable gdm service, but every time I reboot the PC, I have to reinstall glib2, then I do systemctl start gdm.service. If i do not reinstall glib2 and start gdm service after reboot, my PC get stuck without login into gnome...
I think pressing Esc is more comfortable

It's not that way, If I do not install GLIB2, the PC get stuck (this means, no ESC, neither other KEYS will resume it...) I have to install GLIB2, then Start gdm service, then put my password, finally press ESC to enter

Mons1990 · 2015-10-17 23:25:26

JohnnyDeacon wrote:

Mons1990 wrote:
JohnnyDeacon wrote:
Same problem. I'm using GTX660, Gnome 3.18. What I'm doing while bug is fixed is:
I Had to disable gdm service, but every time I reboot the PC, I have to reinstall glib2, then I do systemctl start gdm.service. If i do not reinstall glib2 and start gdm service after reboot, my PC get stuck without login into gnome...
I think pressing Esc is more comfortable
It's not that way, If I do not install GLIB2, the PC get stuck (this means, no ESC, neither other KEYS will resume it...) I have to install GLIB2, then Start gdm service, then put my password, finally press ESC to enter

Mmmm, so I think that this is something different from what we are talking about.

ayr-ton · 2015-10-18 03:10:06

Mons1990 wrote:

Hi, sorry for the title, I hope can you help me solving the issue or at least to choose a better title.
After updating GNOME to 3.18 when I put my username and password in GDM and I press enter the screen is stuck at grey GDM background and I can only move the mouse.
If I press Ctrl+Alt+F2 I can reach the shell and use the computer normally.
How can I solve this?
Thanks in advance.

I also figured out this workaround for make this works.

Glad to know that issue is happening to others too.

I will keep digging for solutions and bug reports at the mainstream.

ayr-ton · 2015-10-18 03:33:15

From gnome dev team:

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

If someone with a second machine and could:
1) debuginfo-install gnome-shell (or equivalent for non-fedora distros)
2) ssh into the problem machine
3) gdb attach $(pidof gnome-shell)
4) (gdb) continue
5) reproduce the problem
6) hit control-c on the machine you're ssh'd from
7) (gdb) thread apply all backtrace full
8) (gdb) call gjs_dumpstack()
9) (gdb) continue
10) hit control-c again
11) (gdb) thread apply all backtrace full
12) (gdb) call gjs_dumpstack()
13) (gdb) continue
and then attach the full journal, with debug on in gdm, that would be fantastic.

I will try from my end for providing these log information to Gnome team.

If someone also want to help in this. o/

ayr-ton · 2015-10-18 03:43:19

Seems like Arch Linux doesn't have a debuginfo-install alternative. Could someone confirm this information?
Also, I could not found the debug symbols at the user repos.

There's some place that I could get this debug packages without needing to manual rebuild my gnome? Or should I go through the hard way?

almindor · 2015-10-18 04:38:32

ayr-ton wrote:

Seems like Arch Linux doesn't have a debuginfo-install alternative. Could someone confirm this information?
Also, I could not found the debug symbols at the user repos.
There's some place that I could get this debug packages without needing to manual rebuild my gnome? Or should I go through the hard way?

I'm just working on this right now, trying to get the debug info for gnome devs.

You need to use arch's ABS system and rebuild the pkg with makepkg and options=(debug !strip).

JohnnyDeacon · 2015-10-19 18:31:10

Mons1990 wrote:

JohnnyDeacon wrote:
Mons1990 wrote:
I think pressing Esc is more comfortable
It's not that way, If I do not install GLIB2, the PC get stuck (this means, no ESC, neither other KEYS will resume it...) I have to install GLIB2, then Start gdm service, then put my password, finally press ESC to enter
Mmmm, so I think that this is something different from what we are talking about.

It is no different , It's the same situation. Some users have ATI video cards , the behavior there, is similar to what is described in this forum . Those who use only Nvidia , like me, had the behavior of glib2, after installing GLIB is the same way of ATI users. The people using 3D Nvidia graphics only, does not have this problem, because their primary card is Intel.

Salamandar · 2015-10-20 21:24:24

Cinnamon is also broken after the cogl update (extra/cogl 1.22.0-1 1 -> 1.1)
I just loved the /var/cache/pacman/pkg/cogl-1.22.0-1-x86_64.pkg.tar.xz file that allowed me to downgrade and solve the problem.

numasan · 2015-10-21 18:44:56

Just wanted to chime in and say I have the same problem.

Ropid wrote:

That login bug might only be for NVIDIA driver and that's why it's wasn't noticed by the developers. It seems you can just hit Escape instead of Ctrl-Alt-F2.

I know and respect that this is a Free Software project, but not having tested with Nvidia proprietary driver seems insane to me, as it is so commonly used on Linux.

almindor · 2015-10-21 21:17:19

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>

Last edited by almindor (2015-10-24 02:41:38)

numasan · 2015-10-21 21:28:41

Thanks almindor

I'll just wait for the dust to settle, but good to know that it has been fixed. My surprise was more that supposedly no Gnome developer has access to a machine using the Nvidia driver.

Arch Linux

#26 2015-10-13 00:41:40

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

#27 2015-10-13 10:59:41

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

#28 2015-10-13 13:56:55

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

#29 2015-10-13 14:18:01

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

#30 2015-10-13 14:36:54

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

#31 2015-10-13 15:34:31

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

#32 2015-10-13 16:08:25

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

#33 2015-10-13 17:30:54

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

#34 2015-10-13 17:33:53

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

#35 2015-10-14 11:11:45

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

#36 2015-10-14 21:59:49

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

#37 2015-10-15 02:50:10

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

#38 2015-10-17 04:15:49

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

#39 2015-10-17 11:17:55

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

#40 2015-10-17 14:11:48

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

#41 2015-10-17 23:25:26

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

#42 2015-10-18 03:10:06

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

#43 2015-10-18 03:33:15

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

#44 2015-10-18 03:43:19

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

#45 2015-10-18 04:38:32

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

#46 2015-10-19 18:31:10

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

#47 2015-10-20 21:24:24

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

#48 2015-10-21 18:44:56

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

#49 2015-10-21 21:17:19

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

#50 2015-10-21 21:28:41

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

Board footer