[SOLVED] System won't boot into Gnome

NarcoticNoble · 2017-10-26 17:45:27

So I have Arch Linux installed on my laptop and an old desktop, but since I have just purchased a new desktop I thought I would reinstall it on there too. I had been trying to install it for ages and after every install the system would freeze at

"Reached Graphical Interface"

I have been trying to figure out what it is, found out that the

"startx"

command would freeze too - so I removed gnome as everything seemed fine before then and luckily I was able to boot into my system and even run "startx". So installed KDE to see if that would work and KDE is working fine!

I still prefer Gnome personally and would prefer to install it on this desktop but for some reason my system freezes up when it's installed.

I have a GeForce GT 610 installed with the nouveau drivers (I thought the drivers may be an issue)

Does anyone have any idea of what is going on or how I can even begin to fix this? Is this a motherboard issue or something?

Last edited by NarcoticNoble (2017-11-02 19:15:33)

jasonwryan · 2017-10-26 17:59:17

Read your Xorg log and your journal. Also, Gnome uses wayland, not X, by default.

NarcoticNoble · 2017-10-26 19:27:17

I realised it was gdm which was the problem, gnome works fine with sddm.

jasonwryan · 2017-10-26 19:32:44

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

seth · 2017-10-26 19:57:49

Gnome on wayland or on xorg? ("loginctl session-status")
Seen https://wiki.archlinux.org/index.php/GD … rg_backend ?

NarcoticNoble · 2017-10-27 12:02:36

When I run

loginctl  session-status

I get:

c3 - noble (1000)
           Since: Fri 2017-10-27 12:52:11 BST; 1min 45s ago
          Leader: 727 (sddm-helper)
            Seat: seat0; vc1
         Display: :0
         Service: sddm; type x11; class user
         Desktop: GNOME
           State: active
            Unit: session-c3.scope
                  ├─ 727 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth7772b5b2-b5eb-4e60-8181-c04558c92df8 --id 1 --start gnome-session --user noble
                  ├─ 737 /usr/bin/gnome-keyring-daemon --daemonize --login
                  ├─ 740 /usr/lib/gnome-session/gnome-session-binary
                  ├─ 795 /usr/bin/gnome-shell
                  ├─ 923 /usr/lib/gnome-settings-daemon/gsd-media-keys
                  ├─ 924 /usr/lib/gnome-settings-daemon/gsd-mouse
                  ├─ 926 /usr/lib/gnome-settings-daemon/gsd-power
                  ├─ 929 /usr/lib/gnome-settings-daemon/gsd-print-notifications
                  ├─ 932 /usr/lib/gnome-settings-daemon/gsd-rfkill
                  ├─ 938 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
                  ├─ 939 /usr/lib/gnome-settings-daemon/gsd-sharing
                  ├─ 949 /usr/lib/gnome-settings-daemon/gsd-wacom
                  ├─ 951 /usr/lib/gnome-settings-daemon/gsd-xsettings
                  ├─ 952 /usr/lib/gnome-settings-daemon/gsd-smartcard
                  ├─ 953 /usr/lib/gnome-settings-daemon/gsd-sound
                  ├─ 963 /usr/lib/gnome-settings-daemon/gsd-a11y-keyboard
                  ├─ 965 /usr/lib/gnome-settings-daemon/gsd-clipboard
                  ├─ 966 /usr/lib/gnome-settings-daemon/gsd-color
                  ├─ 967 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
                  ├─ 972 /usr/lib/gnome-settings-daemon/gsd-housekeeping
                  ├─ 973 /usr/lib/gnome-settings-daemon/gsd-keyboard
                  ├─ 975 /usr/lib/gnome-settings-daemon/gsd-datetime
                  ├─1013 /usr/lib/gnome-settings-daemon/gsd-printer
                  ├─1014 /usr/lib/tracker-miners/tracker-extract
                  ├─1022 /usr/lib/tracker-miners/tracker-miner-fs
                  ├─1025 /usr/lib/gsd-disk-utility-notify
                  └─1026 /usr/lib/tracker-miners/tracker-miner-apps

Oct 27 12:52:22 nexus gnome-shell[795]: No permission to trigger offline updates: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is no
Oct 27 12:52:23 nexus gsd-xsettings[951]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Oct 27 12:52:23 nexus gsd-sharing[939]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Oct 27 12:52:23 nexus gsd-sharing[939]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
Oct 27 12:52:24 nexus gnome-shell[795]: JS WARNING: [resource:///org/gnome/shell/ui/workspaceThumbnail.js 892]: reference to undefined property "_switchWorkspaceNotifyId"
Oct 27 12:52:24 nexus gnome-session-binary[740]: Entering running state
Oct 27 12:52:24 nexus gsd-rfkill[932]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Oct 27 12:52:25 nexus gnome-shell[795]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service f
Oct 27 12:52:26 nexus gnome-shell[795]: GNOME Shell started at Fri Oct 27 2017 12:52:22 GMT+0100 (BST)
Oct 27 12:52:54 nexus gnome-shell[795]: Received error from DBus search provider org.gnome.Epiphany.desktop: Gio.IOErrorEnum: Timeout was reached

So I am guessing gnome is running in xorg and not wayland.

Omar007 · 2017-10-27 12:23:09

The Gnome session type is normally selected by you yourself in GDM/SDDM/whichever; Gnome = Wayland, Gnome on Xorg = Xorg.
GDM defaults to starting on Wayland and as far as I'm aware will not fall back to Xorg unless Wayland outright crashes completely at initialization (I've had it crash after initialization and at that point no fallback ever happened for me) or KMS is unavailable.
If Gnome on Xorg works, it's quite likely that you have problems with Wayland, not necessarily GDM.

Last edited by Omar007 (2017-10-27 12:24:21)

NarcoticNoble · 2017-10-27 12:29:32

Well when I boot into sddm I choose "Gnome" and not "Gnome Xorg" so surely I should be in Wayland at this point - then if I can run in wayland why isn't GDM working? Could it be something else?

seth · 2017-10-27 12:40:42

You're *not* running gnome on wayland (as your session status reports).
What likely happens is that gnome/wayland fails and resorts to gnome/xorg.

Try gdm/xorg (link in my last post) and see whether gdm works (again).
In case your trouble is with wayland and you should investigate your actual hardware setup, notably around the nvidia GPU (eg. whether there's an nvidia installation in parallel to nouveau or whatever)

NarcoticNoble · 2017-10-27 13:06:18

I ran gdm/xorg and it boots - must be an issue with wayland then - before I installed a display manager I messed around with weston which worked, I have just bought an RX 560 as I need an upgrade and I plan on doing a fresh install when I get it. I will look into the drivers I have installed for my nvidia graphics card. Thanks!

Arch Linux

#1 2017-10-26 17:45:27

[SOLVED] System won't boot into Gnome

#2 2017-10-26 17:59:17

Re: [SOLVED] System won't boot into Gnome

#3 2017-10-26 19:27:17

Re: [SOLVED] System won't boot into Gnome

#4 2017-10-26 19:32:44

Re: [SOLVED] System won't boot into Gnome

#5 2017-10-26 19:57:49

Re: [SOLVED] System won't boot into Gnome

#6 2017-10-27 12:02:36

Re: [SOLVED] System won't boot into Gnome

#7 2017-10-27 12:23:09

Re: [SOLVED] System won't boot into Gnome

#8 2017-10-27 12:29:32

Re: [SOLVED] System won't boot into Gnome

#9 2017-10-27 12:40:42

Re: [SOLVED] System won't boot into Gnome

#10 2017-10-27 13:06:18

Re: [SOLVED] System won't boot into Gnome

Board footer