I found a temporary workaround by switching to a Window/Desktop Manager working without DBUS: i3, twm, or other lightweight Window Managers. The problem comes back when using XFCE or GNOME.

Try running Chrome from the command-line and see if anything will be reported in the console.

Unable to reproduce the issue on Ubuntu 14.04 using chrome stable #61.0.3163.100

Following are the steps followed to reproduce the issue.
------------
1. Installed google chrome 61 on Ubuntu 14.04
2. Launched the browser and signed in to google account.
3. Restarted chrome and observed that chrome relaunched without any issues.

Note: This issue may reproduce on Linux Mint 18.2 Sonya. Hence, adding TE-Hardware-Dependency as TE-India doesn't seem to have that particular linux flavour and requesting MTV team to please have a look into the issue.

Thanks...!!

Happens to me too. 

I am using Xubuntu 16.04. Its Chrome 61 (I can't currently open 
chrome to find out the exact build number)

Starting from the command line I get this:

"Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files"

and it sits there "forever". 

If I reinstall chrome or update chrome via apt it will work again - once. If I reboot then go to run chrome again, it gets hung as mentioned above. 

Same thing for chromium. 

Hi, 

This issue seems to be fixed in Google chrome version 62.0.3202.62. After updating to this version, I do NOT see the issue.

Thanks for the update, closing this as per C#5.

This is *not* fixed. I'm still seeing it with chrome build 62.0.3202.94 on current Arch Linux x86_64 with the xfce desktop.

This very version worked fine until I changed my google password. I can't remember the exact timeline what happened then, but I *think* as I've changed the PW from running chrome I was signed out of chrome (as expected) and was able to sign in and set up syncing again. But on the next fresh start chrome refused to start with the symptoms described by the OP and #4:

If I delete ~/.config/google-chrome/Default chrome starts, I can set it up and it works, but on the next restart it just hangs "forever" and the last message when starting from the shell is the "Gkr-Message ..." cited in #4. If I start with strace, these are the last lines of output:

sendmsg(114, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\1\0\1\0\0\0\0\4\0\0\0}\0\0\0\1\1o\0\30\0\0\0/org/fre"..., iov_len=144}, {iov_base="", iov_len=0}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 144
poll([{fd=114, events=POLLIN}], 1, 25000) = 1 ([{fd=114, revents=POLLIN}])
recvmsg(114, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="l\3\1\1L\0\0\0\3\0\0\0u\0\0\0\6\1s\0\5\0\0\0:1.60\0\0\0"..., iov_len=2048}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 212
write(12, "\1\0\0\0\0\0\0\0", 8)        = 8
recvmsg(114, {msg_namelen=0}, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
getpeername(2, 0x7fff7a7397d0, [128])   = -1 ENOTSOCK (Socket operation on non-socket)
futex(0x7f8bcdb6db08, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, 0x7fff7a7397b0)        = -1 ENOTTY (Inappropriate ioctl for device)
write(2, "Gkr-Message: secret service oper"..., 118) = 118
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
futex(0x7f8bb528dba0, FUTEX_WAKE_PRIVATE, 2147483647) = 1
futex(0x7f8bb528db50, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xd75f05365f8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xd75f00878d0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f84ccf5158, FUTEX_WAIT_PRIVATE, 2, NULL

A few random remarks:

1. I've installed chrome from this AUR package which I think just installs the official binary packages: https://aur.archlinux.org/packages/google-chrome/
2. In contrast to what #4 wrote, a parallel chromium install works just fine on the very same machine.
3. I have a second machine with basically the same environment (Arch, XFCE, x64_64) where chrome installed from the same AUR package also works just fine, so it seems to be something specific to my install.

Let me know if I can do anything else to help you debug this.

Literally just seconds after I posted my comment I found this thread which provided the solution: 

https://forum.manjaro.org/t/google-chrome-dont-start-after-update/31555

After running "google-chrome-stable %U --password-store=basic" chrome starts again.

I still think this is a bug. Whatever goes wrong, it shouldn't just hang.

Happened to me on Version 65.0.3325.181 (Official Build) (64-bit).

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

Running Cinnamon desktop environment. I was minding my own business and all of a sudden Chrome wouldn't launch anymore. Saw all the processes active in ps, launching from command line didn't give me any clues:

$ google-chrome --enable-logging
[2476:2476:0330/095948.717546:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: NTPContentSuggestionsEnabled
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
ATTENTION: default value of option force_s3tc_enable overridden by environment.

I ended up using the --password-store=basic line mentioned in #9, and sure enough, it launched once again, and yes my Google account was signed out. I signed back in and everything was fine.

This bug is disturbing, though, because Chrome just plain dies for no apparent reason. I doubt a regular user would be able to figure out how to recover.

I have the same  issue 7  months after this issue was posted
My linux is Linux Mint 14.04.5 LTS, Trusty Tahr and google chrome version is 66.0.3359.139-1.
Is this issue closed? Seriously? What is going to happen? Are we stuck with using that command and needing to login every time?

Did anyone else find another solution? Could we possibly escalate this to google developers?

I tried installing gnome-keyring, and it fixes the startup problem. Seems like it relies on that to store the login information? However, I still have to login after every restart, so it really doesn't solve the problem.

I am running Ubuntu Server 18.04 with XFCE desktop.