Gnome 3.16 "Oh no! Something has gone wrong."

jstapels · 2015-04-13 19:05:35

nOvoid wrote:

Well that very segfault is probably what's causing the gnome crash. Doesn't it give any hints to what the cause might be?

Not really... journalctl says the following...

Apr 13 11:59:29 bahamut kernel: gnome-settings-[3941]: segfault at 20 ip 00007fae986eef78 sp 00007ffdb3196e30 error 6 in libglib-2.0.so.0.4400.0[7fae986cf000+10c000]

The last 20-30 lines of my strace is...

futex(0x21351d8, FUTEX_WAKE_PRIVATE, 1) = 1
write(8, "\1\0\0\0\0\0\0\0", 8)         = 8
futex(0x7fbc8400a7a0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fbc8400a7a0, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7fbc8400a7a0, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x21b3690, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x21351d8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fbc8400cb10, FUTEX_WAKE_PRIVATE, 1) = 0
write(8, "\1\0\0\0\0\0\0\0", 8)         = 8
futex(0x7fbc8400a7a0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x21b3690, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x21351d8, FUTEX_WAKE_PRIVATE, 1) = 1
write(8, "\1\0\0\0\0\0\0\0", 8)         = 8
futex(0x21351d8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=11, events=0}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17, events=POLLIN}, {fd=19, events=POLLIN}], 8, 0) = 2 ([{fd=5, revents=POLLIN}, {fd=16, revents=POLLIN}])
read(5, "\n\0\0\0\0\0\0\0", 16)         = 8
futex(0x20eb500, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
recvmsg(16, {msg_name(0)=NULL, msg_iov(1)=[{"L\0\0\0\2L\0\0\0\5L\0\0\0\0tLogin Session c4"..., 4354}], msg_controllen=32, [{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, {pid=1217, uid=1000, gid=100}}], msg_flags=0}, 0) = 4354
write(1, "(gnome-settings-daemon:5900): Gv"..., 90(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=0 name='Login Session c4'
) = 90
write(1, "(gnome-settings-daemon:5900): Gv"..., 155(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=3 name='XSMP Session on gnome-session as 10fecf3f13ea9bc748142893148846832400000011700024'
) = 155
write(1, "(gnome-settings-daemon:5900): Gv"..., 85(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=5 name='GNOME Shell'
) = 85
write(1, "(gnome-settings-daemon:5900): Gv"..., 100(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=6 name='GNOME Shell Volume Control'
) = 100
write(1, "(gnome-settings-daemon:5900): Gv"..., 86(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=9 name='Chrome input'
) = 86
write(1, "(gnome-settings-daemon:5900): Gv"..., 83(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=23 name='Terminal'
) = 83
write(1, "(gnome-settings-daemon:5900): Gv"..., 82(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=27 name='Eclipse'
) = 82
write(1, "(gnome-settings-daemon:5900): Gv"..., 106(gnome-settings-daemon:5900): Gvc-DEBUG: Updating client: index=49 name='GNOME Volume Control Media Keys'
) = 106
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
eventfd2(0, O_NONBLOCK|O_CLOEXEC)       = 22
write(22, "\1\0\0\0\0\0\0\0", 8)        = 8
write(8, "\1\0\0\0\0\0\0\0", 8)         = 8
futex(0x7fbc8400a7a0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7fbc8400bfb0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x21350d8, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=22, events=POLLIN}], 1, 25000) = 1 ([{fd=22, revents=POLLIN}])
poll([{fd=22, events=POLLIN}], 1, 25000) = 1 ([{fd=22, revents=POLLIN}])
read(22, "\1\0\0\0\0\0\0\0", 16)        = 8
poll([{fd=22, events=POLLIN}], 1, 25000) = 1 ([{fd=22, revents=POLLIN}])
read(22, "\1\0\0\0\0\0\0\0", 16)        = 8
write(22, "\1\0\0\0\0\0\0\0", 8)        = 8
futex(0x28afef0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
close(22)                               = 0
write(13, "\1\0\0\0\0\0\0\0", 8)        = 8
futex(0x2185f40, FUTEX_WAKE_PRIVATE, 1) = 1
write(1, "(gnome-settings-daemon:5900): co"..., 130(gnome-settings-daemon:5900): common-plugin-DEBUG: Checking for match between ['','',''] and ['DEL','DELL U2412M','M2GCR212408L']
) = 130
write(1, "(gnome-settings-daemon:5900): co"..., 130(gnome-settings-daemon:5900): common-plugin-DEBUG: Checking for match between ['','',''] and ['DEL','DELL U2412M','M2GCR2123WJL']
) = 130
write(1, "(gnome-settings-daemon:5900): co"..., 96(gnome-settings-daemon:5900): common-plugin-DEBUG: Did not find a matching output for EDID ',,'
) = 96
write(1, "(gnome-settings-daemon:5900): co"..., 83(gnome-settings-daemon:5900): common-plugin-DEBUG: Did not find a built-in monitor
) = 83
write(2, "\n(gnome-settings-daemon:5900): G"..., 105
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
) = 105
write(2, "\n(gnome-settings-daemon:5900): G"..., 102
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
) = 102
write(2, "\n(gnome-settings-daemon:5900): G"..., 105
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
) = 105
write(2, "\n(gnome-settings-daemon:5900): G"..., 102
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
) = 102
write(2, "\n(gnome-settings-daemon:5900): G"..., 105
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
) = 105
write(2, "\n(gnome-settings-daemon:5900): G"..., 102
(gnome-settings-daemon:5900): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
) = 102
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x20} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)

numasan · 2015-04-13 21:58:37

I had the same problem after updating to Gnome 3.16.

Tried updating/reinstalling nvidia-libgl as someone suggested but it didn't help. Then I unplugged my Wacom tablet like others suggested, and that "fixed" it. Not really happy with this solution, but at least the "Oh no! Something has gone wrong." message is gone.

Error message in journald is:

Apr 13 23:28:49 uranus gnome-shell[1028]: GNOME Shell started at Mon Apr 13 2015 23:28:48 GMT+0200 (CEST)
Apr 13 23:25:54 uranus gnome-session[655]: (gnome-settings-daemon:681): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
Apr 13 23:25:54 uranus gnome-session[655]: (gnome-settings-daemon:681): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
Apr 13 23:25:54 uranus gnome-session[655]: (gnome-settings-daemon:681): GLib-CRITICAL **: g_variant_new_string: assertion 'string != NULL' failed
Apr 13 23:25:54 uranus gnome-session[655]: (gnome-settings-daemon:681): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value != NULL' failed
Apr 13 23:25:54 uranus kernel: gnome-settings-[681]: segfault at 20 ip 00007f4718ea5f78 sp 00007ffe5acc83a0 error 6 in libglib-2.0.so.0.4400.0[7f4718e86000+10c000]
Apr 13 23:25:54 uranus gnome-session[655]: gnome-session[655]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
Apr 13 23:25:54 uranus gnome-session[655]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11

Gatto · 2015-04-14 15:23:13

I just received a xorg update that fixed the problem. Remember to use Gnome and not "Gnome on Wayland" since it seems pretty unstable. Maybe, with the next updates it will be usable even in a office pc.

jstapels · 2015-04-14 15:42:16

A quick update for those that haven't been following the bug report. There's three different issues that have been identified, although they may be related.

Unplugging your Wacom tablet can solve the issue.
Unplugging a USB headset/audio adapter can solve the issue.
Unplugging any extra monitors can solve the issue.

numasan · 2015-04-14 16:55:16

I can confirm that starting Gnome 3.16 with only one monitor, then restart/shutdown, plug in the second monitor and starting Gnome again, fixes the problem permanently (for me).

BTW, my Wacom was plugged in during this, and it worked with one monitor right away - and now works with both of them.

EDIT:
Ok, there is still an issue with the Wacom tablet. It was mapped to a single monitor, so I changed it via gnome-control-center to span both monitors, and then the "Oh no.." message came up again.

Last edited by numasan (2015-04-14 17:18:27)

Bubbel · 2015-04-16 08:00:51

Solved it (For me anyway):
ICC Profiles are corrupted when switching from/to Wayland/X
Do: 'rm ~/.local/share/icc/*', logout/in and Gnome functions again.
At least for me anyway...

phreekbird · 2015-04-16 21:54:38

I can confirm that unplugging my second monitor, logging in w/gnome, and then plugging the second monitor back in, worked. I have since rebooted and logged back in with no ill effects.

haafoo · 2015-04-26 03:30:45

Downgrading the nvidia related packages listed below from 349.16-1 to 346.59-1 allowed gdm to start normally. After reading through the comments here, a scan through the recently upgraded packages in /var/log/pacman.log pointed to these as the likely cause.

nvidia-utils
nvidia
lib32-nvidia-utils
lib32-nvidia-libgl
nvidia-libgl

Note that I have a GTX 760 driving dual monitors but unplugging one didn't work for me (gdm 3.16.1.1-1; linux 3.19.3-3).

Scimmia · 2015-04-26 03:40:42

The cause is your CPU microcode. Update it.

brrbrrbruno · 2015-04-26 04:07:22

i can confirm Scimmia ... this: https://wiki.archlinux.org/index.php/Microcode -> fixed it ...

haafoo · 2015-04-26 17:52:30

Scimmia wrote:

The cause is your CPU microcode. Update it.

Thanks Scimmia. This did the trick for me too. Back to running with the latest nvidia packages. Good to learn something new too.

Last edited by haafoo (2015-04-26 17:52:56)

whoop · 2015-04-27 21:53:11

This microcode stuff is new to me...
So is this microcode update permanent or is it an update aplied every time the os boots with an initrd?
Can I remove the updating procedure by uninstalling intel-ucode and removing the initrd?

ewaller · 2015-04-27 22:44:02

Thus spake the Arch Linux News: https://www.archlinux.org/news/changes- … deupdates/

dmp1ce · 2015-04-29 03:29:02

The microcode update fixed this for me as well.

I installed intell-ucode with "pacman -S intel-ucode". Then I changed my "/boot/grub/grub.cfg" file with an edit to the initrd line. The initrd line now shows "initrd /intel-ucode.img /initramfs-linux.img".

dmp1ce · 2015-04-29 17:53:00

I've learned, from reading the wiki, that the correct thing for me to do was to run "grub-mkconfig -o /boot/grub/grub.cfg" after installing the intel-ucode package.

thedeli · 2015-04-30 13:20:03

After installing intel-ucode gnome has started. But I have problem with icons. Some are old ones (topright gnome panel icons) and some are not even present (window control buttons) is there any solution for this?
http://imgur.com/MNXCTrJ

nullie · 2015-05-10 08:31:23

I had "oh no" message when starting from xinitrc and gdm didn't work at all. I found following error in log:

May 10 13:10:19 nullie-vbox gnome-session[1451]: (gnome-shell:1509): Gjs-WARNING **: JS ERROR: Error: Requiring NMGtk, version none: Typelib file for namespace 'NMGtk' (any version) not found
May 10 13:10:19 nullie-vbox gnome-session[1451]: @resource:///org/gnome/shell/ui/status/network.js:10
May 10 13:10:19 nullie-vbox gnome-session[1451]: AggregateMenu<._init@resource:///org/gnome/shell/ui/panel.js:657
May 10 13:10:19 nullie-vbox gnome-session[1451]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
May 10 13:10:19 nullie-vbox gnome-session[1451]: _Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110
May 10 13:10:19 nullie-vbox gnome-session[1451]: Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:204
May 10 13:10:19 nullie-vbox gnome-session[1451]: Panel<._ensureIndicator@resource:///org/gnome/shell/ui/panel.js:971
May 10 13:10:19 nullie-vbox gnome-session[1451]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
May 10 13:10:19 nullie-vbox gnome-session[1451]: Panel<._updateBox@resource:///org/gnome/shell/ui/panel.js:982
May 10 13:10:19 nullie-vbox gnome-session[1451]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
May 10 13:10:19 nullie-vbox gnome-session[1451]: Panel<._updatePanel@resource:///org/gnome/shell/ui/panel.js:934
May 10 13:10:19 nullie-vbox gnome-session[1451]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
May 10 13:10:19 nullie-vbox gnome-session[1451]: Panel<._init@resource:///org/gnome/shell/ui/panel.js:759
May 10 13:10:19 nullie-vbox gnome-session[1451]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
May 10 13:10:19 nullie-vbox gnome-session[1451]: _Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110
May 10 13:10:19 nullie-vbox gnome-session[1451]: Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:204
May 10 13:10:19 nullie-vbox gnome-session[1451]: _initializeUI@resource:///org/gnome/shell/ui/main.js:166
May 10 13:10:19 nullie-vbox gnome-session[1451]: start@resource:///org/gnome/shell/ui/main.js:120
May 10 13:10:19 nullie-vbox gnome-session[1451]: @<main>:1
May 10 13:10:19 nullie-vbox gnome-session[1451]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed

I figured out it needs NMGtk lib. Search with

pacman -Ss nm-gtk

returned

extra/nm-connection-editor

.

After installing it both gdm and gnome-shell started working.

pokulo · 2015-05-11 12:36:12

I ignored the following pacman warnings after upgrading NetworkManager. overwriting old NetworkManager.conf with the pacnew version let me start my gnome-session again:
[2015-05-07 13:43] [ALPM] upgraded nm-connection-editor (1.0.0-2 -> 1.0.2-1)
[2015-05-07 13:43] [ALPM] upgraded network-manager-applet (1.0.0-2 -> 1.0.2-1)
[2015-05-07 13:43] [ALPM] warning: /etc/NetworkManager/NetworkManager.conf installed as /etc/NetworkManager/NetworkManager.conf.pacnew

Arch Linux

#26 2015-04-13 19:05:35

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#27 2015-04-13 21:58:37

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#28 2015-04-14 15:23:13

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#29 2015-04-14 15:42:16

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#30 2015-04-14 16:55:16

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#31 2015-04-16 08:00:51

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#32 2015-04-16 21:54:38

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#33 2015-04-26 03:30:45

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#34 2015-04-26 03:40:42

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#35 2015-04-26 04:07:22

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#36 2015-04-26 17:52:30

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#37 2015-04-27 21:53:11

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#38 2015-04-27 22:44:02

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#39 2015-04-29 03:29:02

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#40 2015-04-29 17:53:00

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#41 2015-04-30 13:20:03

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#42 2015-05-10 08:31:23

Re: Gnome 3.16 "Oh no! Something has gone wrong."

#43 2015-05-11 12:36:12

Re: Gnome 3.16 "Oh no! Something has gone wrong."

Board footer