You are not logged in.
Hello there, I just received the gnome update and everything works fine but a big message from gnome: "oh no, something has gone wrong".
I can still use gnome by pressing the "super" key and accessing my programs but this message overlays most of my double screen setup. Also I can't see the top menu normally, but it works fine when I hit the "super" key.
Here is a photo of my screen (printscreen does not work also..)
http://imgur.com/gtOCBdz
Does anyone got this error? Can I solve it? I think some library is missing or something.
Edit: I forgot to put gnome-shell starting log.
Last edited by Gatto (2015-04-10 10:08:51)
Offline
Googling the errors in the log you posted would be a good place to start ... please make at least a little effort to help yourself.
Offline
I would not have written a post if I had not already searched carefully on google.
Offline
I'm also getting the "Oh no!" screen after updating. This is (I think) all the relevant info from journalctl:
apr 10 13:56:58 arch gnome-session[26450]: start@resource:///org/gnome/shell/ui/main.js:120
apr 10 13:56:58 arch gnome-session[26450]: @<main>:1
apr 10 13:56:58 arch gnome-session[26450]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed
apr 10 13:56:58 arch gnome-session[26450]: WARNING: App 'gnome-shell.desktop' exited with code 1
apr 10 13:56:58 arch gnome-session[26450]: WARNING: App 'gnome-shell.desktop' respawning too quickly
apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: App 'gnome-shell.desktop' exited with code 1
apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: App 'gnome-shell.desktop' respawning too quickly
apr 10 13:56:58 arch gnome-session[26450]: WARNING: Extension with dirname 'atom-dash@ozonos.org' does not match metadata's UUID of 'atom-launcher@ozonos.org'. Skipping.
apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: Extension with dirname 'atom-dash@ozonos.org' does not match metadata's UUID of 'atom-launcher@ozonos.org'. Skipping.
apr 10 13:56:58 arch gnome-session[26450]: WARNING: Extension with dirname 'atom-panel@numixproject.org' does not match metadata's UUID of 'atom-panel@ozonos.org'. Skipping.
apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: Extension with dirname 'atom-panel@numixproject.org' does not match metadata's UUID of 'atom-panel@ozonos.org'. Skipping.
apr 10 13:56:58 arch gnome-session[26450]: Unrecoverable failure in required component gnome-shell.desktop
Offline
I'm also getting the "Oh no!" screen after updating. This is (I think) all the relevant info from journalctl:
apr 10 13:56:58 arch gnome-session[26450]: start@resource:///org/gnome/shell/ui/main.js:120 apr 10 13:56:58 arch gnome-session[26450]: @<main>:1 apr 10 13:56:58 arch gnome-session[26450]: ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed apr 10 13:56:58 arch gnome-session[26450]: WARNING: App 'gnome-shell.desktop' exited with code 1 apr 10 13:56:58 arch gnome-session[26450]: WARNING: App 'gnome-shell.desktop' respawning too quickly apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: App 'gnome-shell.desktop' exited with code 1 apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: App 'gnome-shell.desktop' respawning too quickly apr 10 13:56:58 arch gnome-session[26450]: WARNING: Extension with dirname 'atom-dash@ozonos.org' does not match metadata's UUID of 'atom-launcher@ozonos.org'. Skipping. apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: Extension with dirname 'atom-dash@ozonos.org' does not match metadata's UUID of 'atom-launcher@ozonos.org'. Skipping. apr 10 13:56:58 arch gnome-session[26450]: WARNING: Extension with dirname 'atom-panel@numixproject.org' does not match metadata's UUID of 'atom-panel@ozonos.org'. Skipping. apr 10 13:56:58 arch gnome-session[26450]: gnome-session[26450]: WARNING: Extension with dirname 'atom-panel@numixproject.org' does not match metadata's UUID of 'atom-panel@ozonos.org'. Skipping. apr 10 13:56:58 arch gnome-session[26450]: Unrecoverable failure in required component gnome-shell.desktop
I think your problem is different from mine..
Offline
@Gatto & @ixi -- try disabling all your shell extensions.
Para todos todo, para nosotros nada
Online
@Gatto & @ixi -- try disabling all your shell extensions.
Already disabled
Offline
I user a fresh /home to troubleshoot so default gnome settings and no extensions enabled. I uninstalled the extensions giving errors in my log to make sure but that did not fix it.
Offline
Same issue with GNOME, GNOME Classic, Cinnamon and Cinnamon (Software mode).
Offline
I had that error when 3.16 hit testing. Do you guys have some patched version of GTK3 running, like gtk3-ubuntu?
Inspiron 3520, i5-3210M, 6GB
ThinkPad X201, i5-540M, 2GB (needs fan)
linux user 520773
Offline
I have the same issue, i have reported it here https://bbs.archlinux.org/viewtopic.php?id=195866 , also i made a fresh install just for testing, fresh arch install + gnome + nvidia blob (gtx 760) and to my surprise the issue remained, fortunately i had a rsync backup of my stuff, so i rolled back to before the upgrade, and configured pacman to ignore the gnome upgrades until someone that understands the problem (that could be on gnome itself or on the arch packaging of it) take a closer look (if you still want gnome 3.16 you can stop gdm and use LightDM on its place), i lost all my day trying to figure this one out, hope someone more knowledgeable can have better luck
Offline
I had similar problems, going through many attempts to fix it, yet i assume the last one was the cause: i have both mesa and nvidia-libgl installed and so i assume my libgl setup might have been overwritten by mesa during the update so the fix was to reinstall the nvidia-libgl package. Hope it helps at least find a direction! Gnome 3.16 works perfectly on my machine now.
edit: in my attempts to fix the problem, using startx without an .xinitrc to see if i could get a default xserver running, then trying to launch graphical apps (like chromium), gave me the most information on the problem as thats where i found what libraries were missing/not found.
Last edited by nOvoid (2015-04-11 08:56:35)
Offline
I had similar problems, going through many attempts to fix it, yet i assume the last one was the cause: i have both mesa and nvidia-libgl installed and so i assume my libgl setup might have been overwritten by mesa during the update so the fix was to reinstall the nvidia-libgl package. Hope it helps at least find a direction! Gnome 3.16 works perfectly on my machine now.
edit: in my attempts to fix the problem, using startx without an .xinitrc to see if i could get a default xserver running, then trying to launch graphical apps (like chromium), gave me the most information on the problem as thats where i found what libraries were missing/not found.
Unfortunately, this does not fix it for me.
Offline
nOvoid are you using GDM ? or you decided to bypass it?
Offline
by the way i opened a bug report https://bugs.archlinux.org/task/44548
Offline
by the way i opened a bug report https://bugs.archlinux.org/task/44548
As you said before, I think this might be a different problem than mine. The super key does not work and switching from gdm didn't solve anything either.
Offline
edit: Later on i found through gnome-session logs that gnome-settings-daemon kept failing with a segfault, probably causing the "oh no!" in my case and by running it with --debug i noticed that a wacom tablet i had connected wasn't getting recognized and disconnecting it during session start seems to have fixed it for me! Although it looks like ixi's problem is a different one, it's kinda weird how so many different things are failing during this gnome 3.16 update.
Last edited by nOvoid (2015-04-11 17:04:03)
Offline
edit: Later on i found through gnome-session logs that gnome-settings-daemon kept failing with a segfault, probably causing the "oh no!" in my case and by running it with --debug i noticed that a wacom tablet i had connected wasn't getting recognized and disconnecting it during session start seems to have fixed it for me! Although it looks like ixi's problem is a different one, it's kinda weird how so many different things are failing during this gnome 3.16 update.
I'm not sure what exactly triggers the error, but it's definitely wacom tablet related. I'm using a laptop with a wacom touchscreen/tablet(thinkpad x220 tablet) so I can't really disconnect the tablet during session start. Out-of-the box, gnome control center does not recognize a wacom tablet, although it still works and shows up in xinput fine except for the eraser on the stylus. Installing the xf86-input-wacom driver makes the tablet settings in gcc show up. On every session start it says that the tablet needs calibration and the calibration tool does not register stylus clicks(it did in 3.14) and eventually hangs and I have to killall gnome-control-center in order for it to go away.
edit: So I found out one thing that triggers the error every time. Rotating the screen. In order to use my laptop properly in tablet mode, I have to flip the screen 180 degrees. I have a button that does this and there is one in display settings in gcc. Either of those brings up the 'Oh no' thing evety time. Weirdly enough, rotating 90 degrees only(portrait mode) does not trigger the error.
Last edited by svinqvmraka (2015-04-11 18:58:43)
Offline
I have this issue on a desktop, no wacom no nothing.
Offline
Toggling the touchpad also crashes the shell with the "Oh, no" error.
Offline
has anybody already tried to run
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug
while the daemon isn't running and what was the output?
Offline
nOvoid wrote:edit: Later on i found through gnome-session logs that gnome-settings-daemon kept failing with a segfault, probably causing the "oh no!" in my case and by running it with --debug i noticed that a wacom tablet i had connected wasn't getting recognized and disconnecting it during session start seems to have fixed it for me! Although it looks like ixi's problem is a different one, it's kinda weird how so many different things are failing during this gnome 3.16 update.
I'm not sure what exactly triggers the error, but it's definitely wacom tablet related. I'm using a laptop with a wacom touchscreen/tablet(thinkpad x220 tablet) so I can't really disconnect the tablet during session start. Out-of-the box, gnome control center does not recognize a wacom tablet, although it still works and shows up in xinput fine except for the eraser on the stylus. Installing the xf86-input-wacom driver makes the tablet settings in gcc show up. On every session start it says that the tablet needs calibration and the calibration tool does not register stylus clicks(it did in 3.14) and eventually hangs and I have to killall gnome-control-center in order for it to go away.
edit: So I found out one thing that triggers the error every time. Rotating the screen. In order to use my laptop properly in tablet mode, I have to flip the screen 180 degrees. I have a button that does this and there is one in display settings in gcc. Either of those brings up the 'Oh no' thing evety time. Weirdly enough, rotating 90 degrees only(portrait mode) does not trigger the error.
Disconnecting my wacom "solved" the problem. Also i noticed that some basic interactions (such as copy-paste and double click on nautilus folders) does not work properly.
Offline
Yep, a wacom is the issue. I had no problems with copy/paste, but double click indeed doesn't work, and GNOME apps with the new style scrollbars don't show their scrollbars when moving the mouse towards the side of the window.
Offline
has anybody already tried to run
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug
while the daemon isn't running and what was the output?
Mine ends in a Seg Fault, I can attach an strace but it doesn't show anything immediately obvious.
Offline
nOvoid wrote:has anybody already tried to run
/usr/lib/gnome-settings-daemon/gnome-settings-daemon --debug
while the daemon isn't running and what was the output?
Mine ends in a Seg Fault, I can attach an strace but it doesn't show anything immediately obvious.
Well that very segfault is probably what's causing the gnome crash. Doesn't it give any hints to what the cause might be?
Offline