After a short time of seemingly proper operation, gnome-shell crashes and I end up back in VT1 This is what the logs show. It appears that cogl is broken by the upgrades. org.gnome.Shell.desktop[1802]: (gnome-shell:1802): Cogl-ERROR **: Failed to create an OpenGL framebuffer object kernel: traps: gnome-shell[1802] trap int3 ip:7f68841e173b sp:7ffcd55b6050 error:0 polkitd[1115]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.16, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disco gnome-session[1776]: gnome-session-binary[1776]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 gnome-session-binary[1776]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 org.gnome.Shell.desktop[7716]: X Error of failed request: BadMatch (invalid parameter attributes) org.gnome.Shell.desktop[7716]: Major opcode of failed request: 139 (RANDR) org.gnome.Shell.desktop[7716]: Minor opcode of failed request: 7 (RRSetScreenSize) org.gnome.Shell.desktop[7716]: Serial number of failed request: 241 org.gnome.Shell.desktop[7716]: Current serial number in output stream: 242 gnome-session[1776]: gnome-session-binary[1776]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 gnome-session[1776]: gnome-session-binary[1776]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly gnome-session-binary[1776]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 gnome-session-binary[1776]: Unrecoverable failure in required component org.gnome.Shell.desktop gnome-session-binary[1776]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly gnome-session[1776]: ** (gnome-session-failed:7721): WARNING **: Cannot open display: gnome-session[1776]: gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session[1776]: gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session[1776]: gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-session[1776]: gnome-session-binary[1776]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gnome-settings-daemon.desktop[2282]: (gnome-settings-daemon:2282): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Thanks for reporting the bug. I am not really sure I how to approach this. I have never seen this. Does it happen randomly or after performing some kind of action? Can You see any pattern? Are you using anything special? What's your version of mesa? Can you try to update mesa to 11.1.2 if you didn't already?
It doesn`t matter if you perform an action or let the System idle. The first time it does happen, when I got to the kitchen and my Xorg.0.log does show that systemd-logind does pause, and the 2nd time it crashes right after I was moving the mouse. But I`m on mesa 11.0.6 so updating could be an option for me. Does the same bug did happen to you Ole Reifschneider?
I downgraded to gnome-3.18 to get running again. Then verified all was working as I had also enabled nvidia-drm modeset=1 on the new 364.12 driver and I wanted to make sure that was not the issue. After I ran under 3.18 for a while I reinstalled all the 3.20 stuff from the overlay. Then I rebuild every dependency of cogl. I closed all programs running and then restarted gnome-shell. 3.20 came up and I have be running for over a day with no issue. I have not rebooted yet so I am not sure if the rebuild of cogl and dependencies fixed anything for sure. If someone else could give this a try and let me know.
Updating mesa to 11.1.2-r1 doesn`t fix the problem. http://pastebin.com/vsccpGm1
so far without rebooting I can verify that the problem if it was not fixed by rebuilding cogl dependencies in not in gnome-shell-3.20 nautilus or gnome-control-center. I am still running under gdm-3.18 and gnome-session-3.18
After rebooting the crash is back. I get a consistent crash 5:10 min after login to gdm. All shell extensions are disabled. I tried with a clean user. Does not matter what I am doing. I can login and do nothing for 5:10 and it crashes
I stopped the crashes. After a few hours of experimenting gnome continued to crash 5:10 minutes after login. I tried setting opengl to xorg and the crashing stopped. It seems like there could be an incompatibility between gnome-3.20 and nvidias opengl at least in the latest driver. I am using nvidia-drivers-364.12 with X acpi -compat driver gtk3 kms multilib -pax_kernel -static-libs tools uvm -wayland build_options: symbols=split -dwarf_compress -optional_tests -trace work=tidyup
After getting past the 5:10m crash and running with eselect opengl xorg-x11 for a few hours. I decided to rebuild nvidia-drivers and switch back to eselect opengl nvidia I did that and am still running with no issues a day later. I have not rebooted but it is possible nvidia-drivers just needed a rebuild after all the 3.20 stuff was installed.
Reboot and I`m really sure, that you encounter the same issue as before. Did it help to downgrade the Nvidia-driver or maybe it helps to compile wayland support in? I would test it myself, but I rebuild my Gnome now alot of times and I need a working system. And I couldn`t switch to xorg-x11 on opengl cause I can`t live without Victor Vran at the moment :D
As I am running now, I booted with opengl set to nvidia but switch to to xorg-x11 before the 5:00m mark. After that I think you can switch back to nvidia with no issues as I am running now I have restarted gnome-shell a few times too with extension updates
So I don`t know if it`s really useful, but the error doesn`t exist on Opensuse Tumbleweed, with Nvidia-364.12 and it uses the same cogl package-version as we do on Gentoo.
There are a lot of variables unfortunately. In my case the gnome-desktop crash happens 5:10 after signing into gdm. I can leave gdm up indefinitely with no crash. If after I sign in, I switch opengl to xorg-x11 I can get past the 5:10 crash mark and then switch opengl back to nvidia. I tried turning on the wayland use flag globally and rebuilding the effected packages. My first attempt had GDM fail in a bad way. I was able to fix that by uncommenting the use_wayland=false entry in /etc/gdm/custom. Interestingly, after login gnome-control-center would not run and the switch opengl to xorg-x11 trick did not work and after 5:10 I was back to VT1 So I am back to which I was. -wayland globally and the opengl switch after login. Interestingly, if I leave opengl set to xorg-x11 and reboot it is automatically switched to nvidia when I next login. Any ideas of what could be happening exacting 5:10 after I finish signing in at the GDM prompt?
So today I tested Fedora rawhide with Nvidia-358.16 and Nvidia-361.42. With both drivers I got the same crash I experienced with Gentoo and Gnome-3.20. So this is not a Gentoo specific overlay bug and has to be fixed upstream I think ;-)
https://bbs.archlinux.org/viewtopic.php?id=211100 I already discovered, that you could switch back to tty2 and get back to your gnome-session(with a corrupt wallpaper). On gnomes-bugzilla there is also a user that had the same problem. A real workaround is to switch to lightdm, instead of using gdm as a login-manager, according to the archlinux-thread
Created attachment 430140 [details, diff] patch from arch to gnome-shell which is reported to fix issue This a a patch from the arch bug equiv that is reported the fix the issue. I will test later.
I can now report that this issue is resolved by the patch I posted from arch. They have already updated gnome-shell-3.20. I recommend we do the same.
Arch has issued a new revision of gnome-shell-3.20 with the patch I posted. I suggest we do the same. This issue is resolved from my testing. Can someone confirm.
I can confirm that the patch does work on my end aswell :-) Do you fix the bug in the patch? [quote] Shouldn't the second `priv->old_offscreen = COGL_INVALID_HANDLE;` use `priv->new_offscreen` instead? [/quote]
I did not write the patch. It comes from arch. I could not tell if they changed what they applied to their new version of gnome-shell.
I just pushed gnome-shell-3.20.1 into the overlay with the patch from arch applied. So it should be fixed.
