Chromium starts slowly after gnome 3.12 update

oconnor663 · 2014-04-15 04:26:48

Previously chromium started on my machine in under a second. After the latest gnome update, it takes 5-10 seconds. Is anyone else seeing the same issue?

bulletmark · 2014-04-15 06:01:18

Yes, GNOME updated to 3.12 today on my x64 box and now google chrome beta version 35.0.1916.27 beta aura (from the AUR - it updated last week) comes up normally but then completely freezes for about 30 secs. Can't select anything, close/open a tab/window etc. After that 30 secs it behaves normally, as far as I can tell.

Other than this issue, everything else on GNOME 3.12 looks good. I've not seen any other bugs.

PS edit 1: I just noticed that when I start a terminal using my custom keyboard shortcut then it takes about 30 secs to appear. Behaviour is very different but that common 30 sec delay seems to point to to a GNOME bug.

PS edit 2: Have the same 2 problems in an updated Arch x64 guest system running in current version Virtualbox on my Arch host. And also in an Arch x64 guest running in current version Virtualbox on a Mac OSX 10.9.3 host. So seems like a universal bug.

Last edited by bulletmark (2014-04-15 06:55:28)

Jojonintendo · 2014-04-15 09:55:17

I have the same issues pointed above. I just subscribed to this thread

gvenkat1994 · 2014-04-15 12:27:17

Terminal starts slowly for me too, but only if I use the keyboard shortcut! If I access it from the applications menu it loads smoothly. I am having problems with chromium too. It crashes when I open for the first time(as soon as I login), after that it takes 30 seconds to load.
Rhythmbox also seems to be having problems. I'm gonna try and reinstall these applications.

Last edited by gvenkat1994 (2014-04-15 12:44:54)

themax · 2014-04-15 12:30:34

Chromium stores its passwords in the gnome-keyring. If I login without entering my password (by fingerprint), then Chromium takes very long to start up.

I'm not sure if your issue is because of this. Prior to 3.12 I used to get a prompt "gnome keyring could not be unlocked, please enter password", but now it acts as if the login keyring doesn't exist.

oconnor663 · 2014-04-15 15:36:23

It's definitely a keyring issue. When I start chromium in the terminal, I see these errors:

[4167:4167:0415/083041:ERROR:content_settings_pref_provider.cc(520)] Invalid pattern strings: http://maps.google.com:80,
[4167:4167:0415/083041:ERROR:content_settings_pref_provider.cc(402)] Invalid pattern strings: http://maps.google.com:80,

(chromium hangs at this point for 10 seconds, then...)

Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4167:4206:0415/083107:ERROR:download.cc(109)] PostClientToServerMessage() failed during GetUpdates

Note that "Gkr" is the gnome keyring. If I launch chromium with

chromium --password-store=basic

then all these problems seem to go away, and startup is fast again.

Does anyone know enough about the gnome keyring to suggest a better fix?

Last edited by oconnor663 (2014-04-15 15:38:45)

marcosonoio · 2014-04-15 21:10:29

here a similar problem https://bbs.archlinux.org/viewtopic.php?pid=1404490
and the workaround:

Matt3o wrote:

create the ~/.config/autostart/gnome-keyring-daemon.desktop file and paste the following:

[Desktop Entry]
Type=Application
Exec=/usr/bin/gnome-keyring-daemon
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=Gnome Keyring Daemon
Name=Gnome Keyring Daemon
Comment[en_US]=Load gnome keyring daemon
Comment=Load gnome keyring daemon

gvenkat1994 · 2014-04-16 00:56:17

Thanks marcosonoio, that solved both the chromium problem and the terminal keyboard shortcut problem(I don't get what the keyring daemon has to do with launching terminal via a custom shortcut?)
I don't know if this is in anyway related, but rhythmbox is still functioning slowly and hangs every now and then. Banshee and other music players seem cool though.

bulletmark · 2014-04-16 01:54:10

Adding that gnome-keyring-daemon to autostart as marcosonoio says does fix both the chrome and terminal (from shortcut) startup delay. However, I find that daemon was already running at session startup so now we get two instances.

Doesn't seem to matter and it does fix the problem but the a-retentive side of me says there is still a bug there.

Last edited by bulletmark (2014-04-16 01:54:55)

sedot · 2014-04-17 23:04:39

bulletmark wrote:

Doesn't seem to matter and it does fix the problem but the a-retentive side of me says there is still a bug there.

I feel the same way.

$ ls /etc/xdg/autostart | grep keyring
gnome-keyring-gpg.desktop
gnome-keyring-pkcs11.desktop
gnome-keyring-secrets.desktop
gnome-keyring-ssh.desktop

$ ps -e | grep keyring
985 ?        00:00:00 gnome-keyring-d

So apparently the keyring daemon is autostarting. What is more? I got this on startup:

$ journalctl -b | grep keyring
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The GPG agent was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The PKCS#11 component was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The Secret Service was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The SSH agent was already initialized

When I press a custom shortcut, this happens:

Apr 18 00:59:00 atlas gnome-session[987]: (gnome-settings-daemon:1058): media-keys-plugin-WARNING **: Failed to call GetEnvironment on keyring daemon: Timeout was reached

And this keeps popping up in the log for about five times until the application mapped on the short cut starts:

Apr 18 00:58:35 atlas gnome-keyring-daemon[985]: The Secret Service was already initialized
Apr 18 00:44:11 atlas org.freedesktop.secrets[1007]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Apr 18 00:44:11 atlas org.freedesktop.secrets[1007]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1

Any ideas on why this happens?

bulletmark · 2014-04-19 04:04:57

With today's update of gdm from 3.12.1-1 to 3.12.1-2 this problem seems fixed. Both chrome/chromium start and the terminal keyboard shortcut have no delay. So you can remove that temp gnome.keyring.desktop.

gvenkat1994 · 2014-04-19 08:57:10

No, It still isn't fixed. I'm getting same problem after upgrading.

bulletmark · 2014-04-19 09:46:53

gvenkat1994 wrote:

No, It still isn't fixed. I'm getting same problem after upgrading.

Did gdm update for you? Did you reboot? I don't understand why the gdm update would fix those 2 problems for me but not for you?

sedot · 2014-04-19 15:39:47

It's not fixed for me. I did the update and a reboot.
Starting gnome-keyring-daemon manually with gnome-keyring-daemon -s -f does not fix the problem but replacing the current daemon with gnome-keyring-daemon -f -r does. Why does it work now and not while booting? Could it be that it is started to early?

wilberfan · 2014-04-20 01:43:05

Did an update and reboot here, too.... Still a full 30 seconds to start Chrome just now.

I'm under XFCE (although I have gnome-keyring installed).

Last edited by wilberfan (2014-04-20 01:44:04)

time132 · 2014-04-20 08:20:09

Yesterday, I did an update and it's fixed for me (Chromium and terminal shortcut).

gvenkat1994 · 2014-04-20 13:11:41

It is fixed for me now. Just upgrade and ensure that gdm 3.12.1.2 is being upgraded. That upgrade did not happen yesterday for me. I guess we can mark this solved.

wilberfan · 2014-04-21 03:23:33

gvenkat1994 wrote:

It is fixed for me now. Just upgrade and ensure that gdm 3.12.1.2 is being upgraded. That upgrade did not happen yesterday for me. I guess we can mark this solved.

I don't even have gdm installed!

# pacman -Qi gdm
error: package 'gdm' was not found

gvenkat1994 · 2014-04-21 17:14:18

@wilberfan : What login manager are you using if not gdm? I thought this bug affected only gnome.

wilberfan · 2014-04-21 22:51:22

gvenkat1994 wrote:

@wilberfan : What login manager are you using if not gdm? I thought this bug affected only gnome.

LXDM, apparently... (I have no memory of installing that one--nor why...)

$ sudo pacman -Qi lxdm
Name           : lxdm
Version        : 0.4.1-29
Description    : Lightweight X11 Display Manager
Architecture   : i686
URL            : http://sourceforge.net/projects/lxdm/
Licenses       : GPL
Groups         : lxde
Provides       : None
Depends On     : gtk2  xorg-server
Optional Deps  : gtk-engines: default GTK+ theme [installed]
                 librsvg: display the default background [installed]
Required By    : None
Optional For   : None
Conflicts With : None
Replaces       : None
Installed Size : 286.00 KiB
Packager       : Balló György <ballogyor+arch@gmail.com>
Build Date     : Tue 26 Nov 2013 11:01:45 AM PST
Install Date   : Thu 05 Dec 2013 04:46:56 PM PST
Install Reason : Explicitly installed
Install Script : Yes
Validated By   : Signature

spikeh · 2014-04-23 11:17:55

sedot wrote:

bulletmark wrote:

Doesn't seem to matter and it does fix the problem but the a-retentive side of me says there is still a bug there.

I feel the same way.

$ ls /etc/xdg/autostart | grep keyring
gnome-keyring-gpg.desktop
gnome-keyring-pkcs11.desktop
gnome-keyring-secrets.desktop
gnome-keyring-ssh.desktop

$ ps -e | grep keyring
985 ?        00:00:00 gnome-keyring-d

So apparently the keyring daemon is autostarting. What is more? I got this on startup:

$ journalctl -b | grep keyring
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The GPG agent was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The PKCS#11 component was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The Secret Service was already initialized
Apr 18 00:28:55 atlas gnome-keyring-daemon[985]: The SSH agent was already initialized

When I press a custom shortcut, this happens:

Apr 18 00:59:00 atlas gnome-session[987]: (gnome-settings-daemon:1058): media-keys-plugin-WARNING **: Failed to call GetEnvironment on keyring daemon: Timeout was reached

And this keeps popping up in the log for about five times until the application mapped on the short cut starts:

Apr 18 00:58:35 atlas gnome-keyring-daemon[985]: The Secret Service was already initialized
Apr 18 00:44:11 atlas org.freedesktop.secrets[1007]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Apr 18 00:44:11 atlas org.freedesktop.secrets[1007]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1

Any ideas on why this happens?

Hello! Thank you for your informative post. I've noticed that since upgrading Cinnamon/GNOME I have been unable to use Ctrl+Alt+T to open terminals and Chromium has been freezing on startup. I can confirm I have the same symptoms, with the "Timeout was reached" messages in journalctl.

I am using SLiM as my login manager. Since I use dm-crypt, I had SLiM set up to auto log in. This does not unlock my GNOME keyring however, so when I use the keyring e.g. SSH using private keys, I have to enter my password.

After reading this thread and reports that updating GDM have resolved the issue for some, I've turned off auto log in and now everything's working as intended again. For those using alternative login managers, I hope this helps.

sedot · 2014-04-23 18:47:07

I am also using SLiM by the way. This post might explain why it does not work with SLiM's autologin enabled but now I am super confused that it has actually worked in the past for me. For now I am switching to gdm and wait for a SLiM update if this is a SLiM bug.

chadversary · 2014-05-07 22:42:39

I fixed my issue without touching gnome-keyring. My problem was in systemd.

I believe I was hitting the same issue as everyone else. After logging into gnome-shell through gdm, Chromium and gnome-terminal had difficulty starting. Chromium would hang unresponsively for over a minute (I impatiently xkilled it). gnome-terminal had long, over a minute delay when spawning new terminals though the Gnome Shell launcher or though my keyboard hotkey.

My problem was that my home directory contained forgotten systemd units. Pre-upgrade, the units were not used. Post-upgrade, systemd tried starting the bogus long-forgotten units.

Solution: rm -r ~/.config/system/user/* . This solution was safe for me because I no longer wanted the units.

wilberfan · 2014-05-08 18:33:11

I'm experiencing a variation where the browser window opens relatively quickly, but then the page contents takes 30 seconds to render...

jichuan89 · 2014-08-21 07:34:41

sedot wrote:

I am also using SLiM by the way. This post might explain why it does not work with SLiM's autologin enabled but now I am super confused that it has actually worked in the past for me. For now I am switching to gdm and wait for a SLiM update if this is a SLiM bug.

Thanks for the pointer to the SLiM thread! Disabling auto_login in /etc/slim.conf fixed it for me.

Arch Linux

#1 2014-04-15 04:26:48

Chromium starts slowly after gnome 3.12 update

#2 2014-04-15 06:01:18

Re: Chromium starts slowly after gnome 3.12 update

#3 2014-04-15 09:55:17

Re: Chromium starts slowly after gnome 3.12 update

#4 2014-04-15 12:27:17

Re: Chromium starts slowly after gnome 3.12 update

#5 2014-04-15 12:30:34

Re: Chromium starts slowly after gnome 3.12 update

#6 2014-04-15 15:36:23

Re: Chromium starts slowly after gnome 3.12 update

#7 2014-04-15 21:10:29

Re: Chromium starts slowly after gnome 3.12 update

#8 2014-04-16 00:56:17

Re: Chromium starts slowly after gnome 3.12 update

#9 2014-04-16 01:54:10

Re: Chromium starts slowly after gnome 3.12 update

#10 2014-04-17 23:04:39

Re: Chromium starts slowly after gnome 3.12 update

#11 2014-04-19 04:04:57

Re: Chromium starts slowly after gnome 3.12 update

#12 2014-04-19 08:57:10

Re: Chromium starts slowly after gnome 3.12 update

#13 2014-04-19 09:46:53

Re: Chromium starts slowly after gnome 3.12 update

#14 2014-04-19 15:39:47

Re: Chromium starts slowly after gnome 3.12 update

#15 2014-04-20 01:43:05

Re: Chromium starts slowly after gnome 3.12 update

#16 2014-04-20 08:20:09

Re: Chromium starts slowly after gnome 3.12 update

#17 2014-04-20 13:11:41

Re: Chromium starts slowly after gnome 3.12 update

#18 2014-04-21 03:23:33

Re: Chromium starts slowly after gnome 3.12 update

#19 2014-04-21 17:14:18

Re: Chromium starts slowly after gnome 3.12 update

#20 2014-04-21 22:51:22

Re: Chromium starts slowly after gnome 3.12 update

#21 2014-04-23 11:17:55

Re: Chromium starts slowly after gnome 3.12 update

#22 2014-04-23 18:47:07

Re: Chromium starts slowly after gnome 3.12 update

#23 2014-05-07 22:42:39

Re: Chromium starts slowly after gnome 3.12 update

#24 2014-05-08 18:33:11

Re: Chromium starts slowly after gnome 3.12 update

#25 2014-08-21 07:34:41

Re: Chromium starts slowly after gnome 3.12 update

Board footer