Gnome Crashing after install [SOLVED]

mornindew · 2016-01-12 05:13:49

Hi all,
I am doing my first arch linux install and I have an issue.

I am installing on a Lenovo X1 carbon and everything was going pretty well. After installing gnome, gdm, and other libraries gnome will crash on startup and then I am "stuck".

I get a screen that says "oh no! something has gone wrong" and I am asked to logout. After I logout it will just try to relog in and the same thing happens again.

I don't know how to force it to the command line (CTRL --> ALT --> F1 didn't work) so that I can try to get some logging to diagnose the issue. I guess I really have two main issues:

1) How can I get out of the login loop and try to diagnose the issue?
2) Has anyone seen this before and have any idea on what might have caused it?

Thank you in advance.

Craig

Last edited by mornindew (2016-01-14 17:45:16)

Docbroke · 2016-01-12 06:21:43

to answer your first question, try to login from alternative tty with below command,

ctrl+alt+F2

(F2 is function key 2, you can use any other tty with F3/4/5 etc.)

this will bring new login console, enter your id & password, next you can disable gnome login manager with

sudo systemctl disable gdm
sudo systemctl stop gdm

try to start gnome from console without using gdm

startx /usr/bin/gnome-session

mornindew · 2016-01-12 13:59:52

Thank you for the reply. Unfortunately Ctrl+alt+F2 (or F3, F4, F5) didn't seem to work. I tried it at time of boot and once the error occurred. It doesn't take me to the console.

Any other thoughts?

Last edited by mornindew (2016-01-12 14:00:11)

Docbroke · 2016-01-12 16:11:37

Probably system hangs with gnome, in that case you will need to chroot into the system with arch live cd. After that you can disable gdm with above posted command. https://wiki.archlinux.org/index.php/Change_root

loqs · 2016-01-12 16:27:28

Assuming gdm is being started by the gdm.service Change_default_target_to_boot_into should also work.
Still need to disable the service as previously noted but the above should stop it from being started.
As to diagnosis would suggest starting by examining the journal.

mornindew · 2016-01-13 04:18:23

Thank you all. I am now out of the boot loop...

I was able to chroot over and disable gdm. This now will only start gnome when I explicitly request it.

I looked at the journalctl logs and I see a "extension "GLX" missing on display ":0" error and that seems to be predicating the crash.

In my googling it seems correlated with the microcode and how that is installed (https://wiki.archlinux.org/index.php/Mi … de_Updates). I believe that I did install the intel-ucode libraries and I updated "/boot/loader/entries/arch.conf" with relevant entries:

My FILE:

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=/dev/sda3 rw

I will keep googling around to see what I can find but I am a little hesitant to just hack away with my limited knowledge. Any help would be appreciated.

Thanks

V1del · 2016-01-13 08:38:33

Missing GLX means your graphics driver isn't installed properly, what's your graphics card, and the driver for it? Also post the output you get.

Last edited by V1del (2016-01-13 08:40:00)

mornindew · 2016-01-13 14:28:21

Thank you very much. Sorry for the limited into. Hopefully this will help.

Output: Journalclt
https://ptpb.pw/8p72

Graphics Card Output
https://ptpb.pw/i_JH

Commands I used to install drivers:
sudo pacman -S nvidia nvidia-libgl lib32-nvidia-libgl lib32-nvidia-utils
sudo pacman -S mesa
sudo pacman -S xorg-server xorg-server-utils xorg-xinit xorg-twm xorg-xclock xterm

ran this command (took from website):

lspci -nnk | grep -i vga -A3 | grep 'in use'

Kernel driver in use: i915

Thank you

loqs · 2016-01-13 14:41:33

Jan 12 15:52:47 craigslaptop systemd-coredump[813]: Process 803 (gnome-shell) of user 120 dumped core.
                                                    
                                                    Stack trace of thread 803:
                                                    #0  0x00007fe78cdac7e0 __lll_unlock_elision (libpthread.so.0)
                                                    #1  0x00007fe77946cccc n/a (libEGL_nvidia.so.0)
                                                    #2  0x00007fe7793fa252 n/a (libEGL_nvidia.so.0)

Is https://bugs.archlinux.org/task/46064

V1del · 2016-01-13 14:58:59

While what loqs mentioned is technically true it is irrelevant in your case. You don't have an Nvidia card, why did you install nvidia drivers? You have Intel graphics so remove all those nvidia packages and install what is mentioned in the article I linked and try again

mornindew · 2016-01-13 15:30:52

Thank you very much. I guess because I am a dumb arse . I will give this a shot today. I was trying to do it last night but was in dependency nightmare. Is there a recommended way to remove the nvidia packages (and dependencies)?

V1del · 2016-01-13 15:44:17

You will want to ignore dependencies on uninstall since there are a few that will require a libgl implementation so use

pacman -Rdd nvidia lib32-nvidia-utils nvidia-utils lib32-nvidia-libgl nvidia-libgl

and install Intel drivers afterwards (and while you are at it read https://wiki.archlinux.org/index.php/Pa … g_packages and generally that whole page because it contains a few neat tricks like that)

Last edited by V1del (2016-01-13 21:44:48)

mornindew · 2016-01-14 02:14:53

And what do you know!?!?!? When you install the right driver it just works great!!

Feel silly, got lost in an Arch tutorial and wan't critically thinking about what I was doing.

Thank you to all.

severach · 2016-01-14 04:24:02

pacman -Rdd is not necessary. Just upgrade to the other libgl. The reason it doesn't appear to work is because pacman has a bug and it requires libgl to be first on the command line.

pacman -S foobar foobar-util foobar-libgl # works on new install, fails on upgrade
pacman -S foobar-libgl foobar foobar-util # works on upgrade

I figured this out when I was duel booting (not dual booting) between Intel, nVidia, and Nouveau to see which worked the best.

According to Wikipedia the proper term for a 3 way duel is a truel.

Last edited by severach (2016-01-14 04:30:53)

ewaller · 2016-01-14 04:33:52

If everything is working, don't forget to edit your first post and add [SOLVED] to the thread title.

Last edited by ewaller (2016-01-14 04:34:09)

V1del · 2016-01-14 07:52:44

I assumed you were using some random tutorial, but refrained from making a quip against that. For closure's sake, don't follow random blog posts they will very likely tell you outdated and often blatantly wrong information. You should've followed the Beginner's guide actually you should still read through it and follow the links on topics, they will help you out in the long run. But yeah, if the current topic is solved for you, follow ewaller's advice

Last edited by V1del (2016-01-14 07:53:38)

Arch Linux

#1 2016-01-12 05:13:49

Gnome Crashing after install [SOLVED]

#2 2016-01-12 06:21:43

Re: Gnome Crashing after install [SOLVED]

#3 2016-01-12 13:59:52

Re: Gnome Crashing after install [SOLVED]

#4 2016-01-12 16:11:37

Re: Gnome Crashing after install [SOLVED]

#5 2016-01-12 16:27:28

Re: Gnome Crashing after install [SOLVED]

#6 2016-01-13 04:18:23

Re: Gnome Crashing after install [SOLVED]

#7 2016-01-13 08:38:33

Re: Gnome Crashing after install [SOLVED]

#8 2016-01-13 14:28:21

Re: Gnome Crashing after install [SOLVED]

#9 2016-01-13 14:41:33

Re: Gnome Crashing after install [SOLVED]

#10 2016-01-13 14:58:59

Re: Gnome Crashing after install [SOLVED]

#11 2016-01-13 15:30:52

Re: Gnome Crashing after install [SOLVED]

#12 2016-01-13 15:44:17

Re: Gnome Crashing after install [SOLVED]

#13 2016-01-14 02:14:53

Re: Gnome Crashing after install [SOLVED]

#14 2016-01-14 04:24:02

Re: Gnome Crashing after install [SOLVED]

#15 2016-01-14 04:33:52

Re: Gnome Crashing after install [SOLVED]

#16 2016-01-14 07:52:44

Re: Gnome Crashing after install [SOLVED]

Board footer