GNOME Bugzilla – Bug 757542
Gnome-shell says something went wrong when I try to log in. But Cinnamon works fine.
Last modified: 2015-11-30 13:05:47 UTC
When I try to log into gnome-shell from MDM (Mint's login manager), it gives me the dreaded message that something went wrong, and the only option is to log out, like in the attached screenshot. I'm not able to use GDM because it gives me the same message, so using MDM works for now. I am able to log into Cinnamon, then I can run gnome-shell --replace in order to esentially get into a gnome environment (although some environment settings are missing, settings that would normally be picked up if logged in properly). I've been using this hack (gnome-shell --replace) for some time now, and have grown tired of it so I thought I'd post here. This is happening on Arch Linux, using the official GNOME packages. I've got the proprietary Nvidia driver working, and acceleration is fast and smooth (in Cinnamon, and after switching to Gnome Shell). I noticed that if I use the Nouveau driver for Nvidia that I can log into Gnome just fine, and I can also use GDM just fine. The only downside to using Nouveau is that the graphics are really slow compared to the proprietary drivers. How can I debug this and what info can I give you guys?
Created attachment 314767 [details] error screen (similar, not necessarily the same Shell/GTK theme)
Is there any useful information in the journal?
Where might I find the journal? Let me try setting starting the GDM systemd unit and see what I find in journalctl.
Alright, here's what `journalctl -u gdm` shows: http://trusktr.io:7777/obanutafik
(In reply to trusktr from comment #4) > Alright, here's what `journalctl -u gdm` shows: > http://trusktr.io:7777/obanutafik Please get us the full 'sudo journalctl -b' output
(In reply to Rui Matos from comment #5) > Please get us the full 'sudo journalctl -b' output That's it.
A small recording of my terminal: http://showterm.io/61cc88dddf43ba0c6680f Let me know if there's any other info I can provide. Thanks!
(In reply to trusktr from comment #6) > (In reply to Rui Matos from comment #5) > > Please get us the full 'sudo journalctl -b' output > > That's it. 'sudo journalctl -b' is not the same as 'sudo journalctl -u gdm'
Oops! Here's that output: http://trusktr.io:7777/etusaticoy Anything useful there? Do you need me to boot to a graphical.target that is using gdm.service?
Well, right now I'm having a different problem starting GDM, some error with PAM, and right now the graphical.targe won't even start in order for GDM to show the "Oh no! Something has gone wrong." message. I'm updating stuff, and trying again.
No luck booting to GDM after updating. Here's more info after trying again: The GDM log: http://trusktr.io:7777/abowolajok And `sudo journalctl -b`: http://trusktr.io:7777/sehebezimu Is there any other info I can provide? /var/log/Xorg.0.log: http://trusktr.io:7777/epijacaruw /var/log/Xorg.0.log.old: http://trusktr.io:7777/xoxayekeve
So, gdm can't use the wayland login screen because the nvidia driver doesn't implement the interfaces that cogl/mutter require. You can edit /etc/gdm/custom.conf and uncomment this line: #WaylandEnable=false That said, gdm should handle the failure and bring up an X backed login screen. Not sure why it's not doing so.
Unfortunately, that didn't work, and I get the same behavior. But, I also noticed an option debug/Enable=false, which I set to true. Here's this morning's GDM-related /var/log/messages.log (I pruned thousands of other lines, hopefully I didn't accidentally prune something useful): http://trusktr.io:7777/gafegajagu I'm getting some lines like this in /var/log/errors.log: ``` Nov 12 09:16:06 starlancer gdm[429]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed Nov 12 09:36:26 starlancer gdm[863]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed Nov 12 09:36:27 starlancer gdm[863]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed ```
Here's some output I get when I run `gnome-shell --replace`: ``` > gnome-shell --replace & Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory) Gjs-Message: JS LOG: Failed to register AuthenticationAgent Gjs-Message: JS LOG: No permission to trigger offline updates: Polkit.Error: GDBus.Error:o rg.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline- update is not registered ``` Is there any other info I can give? I'd really love to be able to log into Gnome on a Macbook.
I'd really prefer to see full logs but I some things stand out for me: Nov 12 09:13:13 starlancer /usr/lib/gdm/gdm-x-session[461]: (EE) systemd-logind: failed to take device /dev/input/event14: No such device Nov 12 09:13:13 starlancer /usr/lib/gdm/gdm-x-session[461]: (EE) evdev: (unnamed): Unable to open evdev device "/dev/input/event14". Nov 12 09:13:13 starlancer /usr/lib/gdm/gdm-x-session[461]: (EE) PreInit returned 2 for "(unnamed)" Nov 12 09:13:13 starlancer kernel: traps: gnome-session-c[642] general protection ip:7f8110a4a7e0 sp:7ffe60644918 error:0 in libpthread-2.22.so[7f8110a38000+18000] Nov 12 09:13:13 starlancer kernel: traps: gnome-session-c[657] general protection ip:7f794de337e0 sp:7ffeee89c798 error:0 in libpthread-2.22.so[7f794de21000+18000] Nov 12 09:13:13 starlancer gnome-session[639]: gnome-session-binary[639]: WARNING: software acceleration check failed: Child process killed by signal 11 Nov 12 09:13:13 starlancer gnome-session-binary[639]: WARNING: software acceleration check failed: Child process killed by signal 11 Can you get the stack traces for these crashes? coredumpctl should allow you to retrieve them. I'm afraid your system is just busted, possibly due to a problem installing the nvidia drivers or manual intervention. Can you try a live system from a USB stick?
The problem was that Intel Microcode needed to be installed. It works perfect now.
On Arch Linux, the relevant package to install was intel-ucode.
ok, thanks for letting us know