Gnome - Oops, something has gone wrong :(

guit4eva · 2015-09-09 12:03:19

Hey guys,

I'm trying out Arch for the first time, and followed this tutorial:

http://www.linuxveda.com/2015/04/20/arc … al-manual/

choosing Gnome as DE. Unfortunately, when booting in (or trying to boot into Gnome), I get the dreaded "Oops, something has gone wrong" screen.

I am installing it on the Dell XPS 15 (l502x) laptop, with GT525M graphics card (with the heinous Optimus!!!)

Highlights of the installation that is the probable cause:

1) "sudo systemctl enable gdm.services" returned a "no file or directory error"

2) I installed nvidia-libgl

Not too sure where to go to from here...can anyone possibly give me some guidance? Really keen to give Arch a spin .

Alad · 2015-09-09 12:21:46

This seems to be the same tutorial from a few months back, which recommends archlinux-fr and pacman -Sy. No wonder it went wrong.

https://wiki.archlinux.org/index.php/Beginners%27_guide

Chazza · 2015-09-09 12:31:08

1) "sudo systemctl enable gdm.services" returned a "no file or directory error"

service, not services.

That guide is just taking the mickey!

Last edited by Chazza (2015-09-09 12:34:00)

guit4eva · 2015-09-09 12:39:21

That "sudo systemctl enable gdm.services" was a typo, it was correct in the actual install:) But good to know that the tutorial sucks - I should have just followed the wiki from the start. The only thing I'm worried about though is my stupid optimus graphics card, it has caused me issues in just about every distro I've tried! My battery is broken, so battery life is not a concern. I just want the best performance possible from my laptop. I'm running CentOS at the moment which is great, but every bit of linux research leads to Arch, so naturally I'm keen to give it a try

Chazza · 2015-09-09 12:45:45

The typo was in the guide as well. Anyway, is your microcode up to date? I remember seeing a thread around here where out of date microcode was causing gnome-settings-daemon to crash which would give you the oops error.

Last edited by Chazza (2015-09-09 12:46:09)

mrunion · 2015-09-09 12:48:53

I followed this and use the nVidia card all the time. I despise that Optimus stuff!

https://wiki.archlinux.org/index.php/NVIDIA_Optimus

guit4eva · 2015-09-09 12:53:25

Oh really? Ha ha flip, will definitely be following the wiki next try!! I get the following output from dmesg | grep microcode

[    0.000000] CPU0 microcode updated early to revision 0x29, date = 2013-06-12
[    0.126534] CPU2 microcode updated early to revision 0x29, date = 2013-06-12
[    0.153712] CPU4 microcode updated early to revision 0x29, date = 2013-06-12
[    0.180889] CPU6 microcode updated early to revision 0x29, date = 2013-06-12
[    1.119311] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x29
[    1.119395] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x29
[    1.119482] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x29
[    1.119568] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x29
[    1.119652] microcode: CPU4 sig=0x206a7, pf=0x10, revision=0x29
[    1.119740] microcode: CPU5 sig=0x206a7, pf=0x10, revision=0x29
[    1.119824] microcode: CPU6 sig=0x206a7, pf=0x10, revision=0x29
[    1.119911] microcode: CPU7 sig=0x206a7, pf=0x10, revision=0x29
[    1.120025] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

Shot for that link mrunion, will definitely have a proper look through it! This Optimus business really is the pits...

Chazza · 2015-09-09 12:57:41

You might want to have at the journal as well by the way. There should be something in there that tells you what caused the GNOME session to fail.

# journalctl -b

should suffice.

Then have a look towards the end for the GNOME related entries.

guit4eva · 2015-09-09 14:41:06

Before I try again, I ran a gpg check on the ISO and it returned the following, is it a problem?

$ gpg --verify archlinux-2015.09.01-dual.iso.sig
gpg: Signature made Tue 01 Sep 2015 07:51:25 PM SAST using RSA key ID 9741E8AC
gpg: Good signature from "Pierre Schmitz <pierre@archlinux.de>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 4AA4 767B BC9C 4B1D 18AE  28B7 7F2D 434B 9741 E8AC

Arch Linux

#1 2015-09-09 12:03:19

Gnome - Oops, something has gone wrong :(

#2 2015-09-09 12:21:46

Re: Gnome - Oops, something has gone wrong :(

#3 2015-09-09 12:31:08

Re: Gnome - Oops, something has gone wrong :(

#4 2015-09-09 12:39:21

Re: Gnome - Oops, something has gone wrong :(

#5 2015-09-09 12:45:45

Re: Gnome - Oops, something has gone wrong :(

#6 2015-09-09 12:48:53

Re: Gnome - Oops, something has gone wrong :(

#7 2015-09-09 12:53:25

Re: Gnome - Oops, something has gone wrong :(

#8 2015-09-09 12:57:41

Re: Gnome - Oops, something has gone wrong :(

#9 2015-09-09 14:41:06

Re: Gnome - Oops, something has gone wrong :(

Board footer