Arch Linux

totokaka

Member

Registered: 2012-12-03

Posts: 26

Gnome shell won't start

After I updated my system on Friday (24th), Gnome shell won't start.

Whether I open it with `startx` or GDM, it crashes with the "Oh, no! Something has gone wrong" message. With GDM, it seems the whole of GDM crashes, as it happens before I see anything of the UI, and I don't have auto login enabled. For `startx`, I don't see any UI there either.

Here is my Xorg.0.log: http://sprunge.us/hhZj
Here is my .xinitrc: http://sprunge.us/VjSJ
Here is the stderr from startx: http://sprunge.us/UCHj

I tried cleaning all gnome extensions, to no avail. I tried creating a new user, and run gnome with startx from there, and that worked. I tried cleaning my ~, and launching gnome with startx, but that didn't work.

Any ideas on what might be wrong, or how to further debug this?

Last edited by totokaka (2015-04-26 18:32:04)

Thorsten Reinbold

Member

From: Germany

Registered: 2011-12-06

Posts: 353

Re: Gnome shell won't start

You want to install the intel ucode updater (package: intel-ucode).

https://bbs.archlinux.org/viewtopic.php … 6#p1522996

Last edited by Thorsten Reinbold (2015-04-26 21:29:52)

totokaka

Member

Registered: 2012-12-03

Posts: 26

Re: Gnome shell won't start

You want to install the intel ucode updater (package: intel-ucode).

https://bbs.archlinux.org/viewtopic.php … 6#p1522996

Intel ucode didn't help, sadly. But thanks, still.

Here is the output if I try to launch gnome from within another WM:

[tobias@archie ~]$ gnome-session --failsafe --debug --whale | curl -F 'sprunge=<-' [url]http://sprunge.us[/url]
gnome-session[1518]: DEBUG(+): Enabling debugging
gnome-session[1518]: DEBUG(+): hardware acceleration check failed: Child process killed by signal 11
gnome-session[1518]: WARNING: software acceleration check failed: Child process killed by signal 11

(gnome-session-failed:1527): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed

(gnome-session-failed:1527): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed

[Here I click the logout button on the "Oh, no! Something has gone wrong" message]

** (gnome-session-quit:1532): WARNING **: Failed to call logout: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Terminated
[tobias@archie ~]$

Last edited by totokaka (2015-04-27 18:50:34)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: Gnome shell won't start

What is the output of:

lspci -knn|grep -A2 VGA
glxinfo|grep rendering

---

Jin, Jîyan, Azadî

~osc~

Member

Registered: 2013-03-15

Posts: 13

Re: Gnome shell won't start

here is my gdm log

Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7664 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7664 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7690 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7679 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7679 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7705 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7694 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7694 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Could not start command '/usr/lib/gdm/gdm-session-worker': Muitos arquivos abertos
Abr 27 15:02:38 al-khowarizmi gdm[490]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process -7720 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7709 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:38 al-khowarizmi gdm[490]: Child process 7709 was already dead.
Abr 27 15:02:38 al-khowarizmi gdm[490]: Unable to kill session worker process
Abr 27 15:02:46 al-khowarizmi systemd[1]: Stopping GNOME Display Manager...
Abr 27 15:02:46 al-khowarizmi gdm[490]: Failed to contact accountsservice: Erro ao chamar StartServiceByName para org.freedesktop.Accounts: A conexão está fechada
Abr 27 15:02:46 al-khowarizmi gdm[490]: Tried to look up non-existent conversation gdm-launch-environment
Abr 27 15:02:46 al-khowarizmi gdm[490]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Abr 27 15:02:46 al-khowarizmi gdm[490]: (gdm-display.c:1141):gdm_display_dispose: runtime check failed: (self->priv->status != GDM_DISPLAY_PREPARED)
Abr 27 15:02:46 al-khowarizmi systemd[1]: Stopped GNOME Display Manager.

~osc~

Member

Registered: 2013-03-15

Posts: 13

Re: Gnome shell won't start

What is the output of:

lspci -knn|grep -A2 VGA

here is mine

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1)
	Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1280]
	Kernel driver in use: nvidia

totokaka

Member

Registered: 2012-12-03

Posts: 26

Re: Gnome shell won't start

What is the output of:

lspci -knn|grep -A2 VGA
glxinfo|grep rendering

Output of the first command:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8520]
	Kernel driver in use: nvidia

And the second:

direct rendering: Yes
    GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
    GL_NV_path_rendering_shared_edge, GL_NV_pixel_data_range, 
    GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
    GL_NV_path_rendering_shared_edge, GL_NV_pixel_data_range, 
    GL_NV_packed_float_linear, GL_NV_path_rendering, 
    GL_NV_path_rendering_shared_edge, GL_NV_pixel_buffer_object, 

I had to start x to run the last command, just used xterm in twm.

Also to see if it would help I did a reinstall. Gnome started fine until I inserted my graphics card and installed the Nvidia drivers. I will try with the nouveau drivers now.

totokaka

Member

Registered: 2012-12-03

Posts: 26

Re: Gnome shell won't start

I ran journalctl -a -b and uploaded the result to sprunge: http://sprunge.us/YhJA
I guess that should contain most relevant logging.

To recap the issue, here is what I have figured so far:
Gdm and gnome shell won't start properly on my system, probably because of the same problem.
The issue is likely related to my driver: nvidia, (nouveau won't function on my card, so that's a no go.)
Neither x nor the driver is completely broken, as for example awesome or twm works fine, and the error message gnome gives me is graphical within x

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: Gnome shell won't start

Sorry, that output request was nonsense (I was very tired)...

I tried creating a new user, and run gnome with startx from there, and that worked.

There must be something in $HOME stopping GNOME from working.

---

Jin, Jîyan, Azadî

totokaka

Member

Registered: 2012-12-03

Posts: 26

Re: Gnome shell won't start

Sorry, that output request was nonsense (I was very tired)...

I tried creating a new user, and run gnome with startx from there, and that worked.

There must be something in $HOME stopping GNOME from working.

Thanks for trying, anyways. I also believed that there was something in $HOME, but after my latest tests, that doesn't seem to be the case.
I tried creating another user after I had got it working, but that user failed to run gnome.

Now, I fixed the problem by downgrading the nvidia drivers (to 346.59), so the problem is most likely there.

totokaka

Member

Registered: 2012-12-03

Posts: 26

Re: Gnome shell won't start

You want to install the intel ucode updater (package: intel-ucode).

https://bbs.archlinux.org/viewtopic.php … 6#p1522996

Turns out this was actually the issue. By installing the microcode updates properly (chainloading the ucode.img before vmlinuz) I was able to install the newest drivers.
The wiki explains how to do it