Ask Your Question
1

Fedora 26: Gnome Shell doesn't come up after login from GDM.

asked 2017-11-30 11:44:48 -0500

gobigobi66 gravatar image

updated 2017-12-01 10:02:55 -0500

Hi, I am having a multi-user workstation that runs an up-to-date Fedora26 (x86_64).

The problem is that for my main user the Gnome shell wouldn't come up. I can login but then I see a grey screen and a mouse pointer and nothing else happens. The problem appears no matter if choose a Wayland, an Xorg or even a Gnome Classic session.

I have no problem logging into Gnome with any other user on the system.

Any ideas how to approach this? Is it possible that a bad extensions prevents the Gnome Shell from coming up? Should I try to delete them? It somehow has to be related to user settings since other users can login into Gnome without any problems. How to find out what causes this "crash"?

Thanks!

edit retag flag offensive close merge delete

Comments

I had a similar challenge but was thrown out instead of getting a blank or grey screen. After logging in three times and got thrown out, it logged me in and it worked as usual.

derdoktor gravatar imagederdoktor ( 2017-12-01 04:06:08 -0500 )edit

Q: does the screen remain gray, when you wait 1 or 2 minutes? I had a simular problem, see login takes 40 secondes before it starts

kdg1955 gravatar imagekdg1955 ( 2017-12-02 15:18:32 -0500 )edit

I had a similar idea and thought I just need to wait for some process to time out but I waited as long as 30 minutes and nothing happened - the screen remained grey.

gobigobi66 gravatar imagegobigobi66 ( 2017-12-12 13:52:50 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
3

answered 2017-12-12 13:49:43 -0500

gobigobi66 gravatar image

Answering my own question.

I deleted all extension (located in ~/.local/share/gnome-shell/extensions and that fixed the problem, I could login into Gnome Shell again. All I had to do was to reinstall the extensions but that was a fairly easy task.

edit flag offensive delete link more
0

answered 2017-11-30 19:02:41 -0500

dreua gravatar image

First, switch to a text console: Ctrl+Alt+F4 (Or some other F-Key. F1 and/or F2 should be GDM and Gnome. You can switch back and forth as you desire.)

Login to the text console using your Username and Password. Does that work? Any errors?

If you can login: Try the "startx" command to start Gnome. Does it work? (In case it works you can use this as a temporary workaround. You can go back to the text-only console by logging out of Gnome.)

If you can login in text mode, do this with your account. If you can't, do this logged in with another account: Run "journalctl --follow" to see the system log. Switch back to the Graphical login screen and try logging in. Switch back to the text console running journalctl to see if any errors pop up. (You can do this via SSH too, if you have it set up. Debugging is much more comfortable from another computer via SSH imo.)

If you need further assistance, provide as much information as possible. (Edit your question or comment. You can use the fpaste command to easily upload log files and post the links here.)

edit flag offensive delete link more

Comments

I can login from a console without any problems. I can also startx from there (there is some warnings since X has been started before already). As I stated in my question, Gnome Shell starts fine with other users on that system.

I can run journalctl --follow later to see what that information it reveals. I have looked through the journal before but there is just so much information. Moreover, I have no clue what to look for.

gobigobi66 gravatar imagegobigobi66 ( 2017-12-01 10:01:19 -0500 )edit

Sounds good! I agree, just looking at the journal is too much information, thats why I would recommend running journalctl --follow in a SSH session so you have a live log-view of your failing login attempt. Good luck! (I my case it was an old autostart .desktop file with a missing binary that made the Gnome login fail. I can have a look at the logs if you upload them to but I'm not sure I will find something.)

dreua gravatar imagedreua ( 2017-12-01 10:25:58 -0500 )edit

you can clean your conf directories ~/.local/share/gnome-* or move them somewhere else to test if it's coming from it. Warning , this way you will lose you shell extension and configuration.

baoboa gravatar imagebaoboa ( 2017-12-01 16:33:15 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2017-11-30 11:44:48 -0500

Seen: 1,499 times

Last updated: Dec 12 '17