Arch Linux

Johnburrell

Member

Registered: 2014-07-16

Posts: 21

Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

I get these messages from journalctl:

Oct 17 20:37:20 gt70-dom gnome-keyring-daemon[584]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-keyring-daemon[588]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-keyring-daemon[582]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-keyring-daemon[586]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-session[532]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-session[532]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-session[532]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-session[532]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Oct 17 20:37:20 gt70-dom gnome-session[532]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 17 20:37:20 gt70-dom gnome-session[532]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 17 20:37:20 gt70-dom gnome-session[532]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 17 20:37:20 gt70-dom gnome-session[532]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 17 20:37:20 gt70-dom gnome-session[532]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 17 20:37:20 gt70-dom gnome-session[532]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 17 20:37:20 gt70-dom gnome-session[532]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Oct 17 20:37:25 gt70-dom gnome-session[532]: X Error of failed request:  BadMatch (invalid parameter attributes)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Major opcode of failed request:  140 (RANDR)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Minor opcode of failed request:  30 (RRSetOutputPrimary)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Serial number of failed request:  178
Oct 17 20:37:25 gt70-dom gnome-session[532]: Current serial number in output stream:  181
Oct 17 20:37:25 gt70-dom gnome-session[532]: gnome-session[532]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 17 20:37:25 gt70-dom gnome-session[532]: WARNING: App 'gnome-shell.desktop' exited with code 1
Oct 17 20:37:25 gt70-dom gnome-session[532]: X Error of failed request:  BadMatch (invalid parameter attributes)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Major opcode of failed request:  140 (RANDR)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Minor opcode of failed request:  30 (RRSetOutputPrimary)
Oct 17 20:37:25 gt70-dom gnome-session[532]: Serial number of failed request:  178
Oct 17 20:37:25 gt70-dom gnome-session[532]: Current serial number in output stream:  181
Oct 17 20:38:53 gt70-dom gnome-session[532]: WARNING: Application 'gnome-shell.desktop' failed to register before timeout
Oct 17 20:38:53 gt70-dom gnome-session[532]: gnome-session[532]: WARNING: Application 'gnome-shell.desktop' failed to register before timeout
Oct 17 20:38:54 gt70-dom gnome-session[532]: Unrecoverable failure in required component gnome-shell.desktop
Oct 17 20:38:54 gt70-dom gnome-session[532]: Failed to play sound: File or data not found
Oct 17 20:38:54 gt70-dom gnome-session[532]: Entering running state
Oct 17 20:38:54 gt70-dom gnome-session[532]: (nm-applet:693): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future
 version.
Oct 17 20:38:54 gt70-dom gnome-session[532]: (nm-applet:693): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed i
n a future version.
Oct 17 20:38:54 gt70-dom gnome-session[532]: (nm-applet:693): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future vers
ion.
Oct 17 20:38:55 gt70-dom gnome-session[532]: (nm-applet:693): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in 
a future version.
Oct 17 20:38:55 gt70-dom org.gnome.zeitgeist.Engine[545]: ** (zeitgeist-datahub:718): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Oct 17 20:38:55 gt70-dom gnome-session[532]: (zeitgeist-datahub:695): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Oct 17 20:38:55 gt70-dom gnome-session[532]: (zeitgeist-datahub:695): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Oct 17 20:38:56 gt70-dom gnome-session[532]: (uint32 1,)
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:1->'Hangup'
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:1->'Hangup'
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:1->'Hangup'
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:1->'Hangup'
Oct 17 20:39:04 gt70-dom gnome-session[532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Oct 17 20:39:04 gt70-dom gnome-session[532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:15->'Terminated'
Oct 17 20:39:04 gt70-dom gnome-session[532]: OK
Oct 17 20:39:04 gt70-dom org.gnome.zeitgeist.Engine[545]: g_dbus_connection_real_closed: Remote peer vanished with error: Error sending message: Broken pipe (g-io-error-quark, 44). Exiting.
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:15->'Terminated'
Oct 17 20:39:04 gt70-dom gnome-session[532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:15->'Terminated'
Oct 17 20:39:04 gt70-dom gnome-session[532]: (tracker-miner-fs:684): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Oct 17 20:39:04 gt70-dom gnome-session[532]: (tracker-miner-fs:684): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Oct 17 20:39:04 gt70-dom gnome-session[532]: (tracker-miner-fs:684): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
Oct 17 20:39:04 gt70-dom gnome-session[532]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Oct 17 20:39:04 gt70-dom gnome-session[532]: Received signal:15->'Terminated'
Oct 17 20:39:04 gt70-dom gnome-session[532]: OK
Oct 17 20:39:04 gt70-dom gnome-session[532]: OK
Oct 17 20:39:04 gt70-dom org.gnome.zeitgeist.Engine[545]: [01:39:04.210298 WARNING] zeitgeist-daemon.vala:449: The connection is closed

It was all working fine in 3.12

Not only does /run/user/1000/keyring/control not exist

but the directory

/run/user/1000/keyring doesn't exist either. Is gnome-keyring supposed to create this?

TIA

jb.

Spider.007

Member

Registered: 2004-06-20

Posts: 1,175

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

Does /run/user/1000/ exist? What does ls -l /etc/xdg/autostart/gnome-keyring-* output?

Last edited by Spider.007 (2014-10-18 08:54:48)

Johnburrell

Member

Registered: 2014-07-16

Posts: 21

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

yes  /run/user/1000/ exists.

ls -l /etc/xdg/autostart/gnome-keyring-* gives:

-rw-r--r-- 1 root root 6351 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-gpg.desktop
-rw-r--r-- 1 root root 7777 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root 7339 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root 5996 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-ssh.desktop

jb.

billy123

Member

Registered: 2009-09-22

Posts: 11

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

I can't login either after the gnome update. Same error as johnburrell. I tried a fix suggested here http://ubuntuforums.org/showthread.php?t=1749189 but didn't work.

billy123

Member

Registered: 2009-09-22

Posts: 11

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

Not a Gnome issue but an nvidia issue after nvidia dropped support for older GPUS.  Switching to nvidia-340xx solved the issue. More info here https://www.archlinux.org/news/nvidia-340xx-and-nvidia/

Spider.007

Member

Registered: 2004-06-20

Posts: 1,175

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

yes  /run/user/1000/ exists.

ls -l /etc/xdg/autostart/gnome-keyring-* gives:

-rw-r--r-- 1 root root 6351 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-gpg.desktop
-rw-r--r-- 1 root root 7777 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root 7339 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root 5996 Sep 23 03:52 /etc/xdg/autostart/gnome-keyring-ssh.desktop

jb.

Hmm, that looks fine; so the daemon should really autostart and create those directories...  I think the issue isn't caused by those errors although they are on top; I think it's caused by the RRSetOutputPrimary failure. Do you have multiple displays?

Johnburrell

Member

Registered: 2014-07-16

Posts: 21

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

No it's a laptop. But it does have a hybrid graphics card, so to get it working with gnome-3.12 I had to install nvidia (current version is 343.22) then create the following xorg.conf file:

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0:2:0
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

and then put this at the top of my .xinitrc file:

xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto

so may be it's this xrandr request that is failing?

jb.

Johnburrell

Member

Registered: 2014-07-16

Posts: 21

Re: Gnome 3.14 upgrade gives "Oh no something has gone wrong" message

Well I wasn't able to solve this so I reverted to Gnome-3.12 and everything is fine again - wierd.

No more upgrades for me!

jb.