Issue metadata
Sign in to add a comment
|
Browser fails to start again after signing into an account, hangs on '...org.freedesktop.secrets not provided...'
Reported by
bernard....@gmail.com,
Feb 1 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 Steps to reproduce the problem: 1. Open browser with a blank/default profile 2. Sign into Chrome/Chromium (to sync bookmarks etc) 3. Wait for sync to complete, then close the browser 4. Open the browser again What is the expected behavior? The browser opens What went wrong? The browser doesn't open. Running the program from the commandline yields the following error: - Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files No browser window appears Did this work before? Yes 61.0.3163.100-1 (as far as I can confirm) Chrome version: 63.0.3239.132 Channel: stable OS Version: Ubuntu 17.10 Flash Version: The workaround: Install a package that provides this dbus service (eg gnome-keyring) There are two bugs that I can see here: 1. It should handle the missing service more gracefully than permanent hanging. Either fail, or ignore and continue 2. If it does need to fail, then there should be an update in the source package to add a list of dependencies providing the required dbus service Some discussion here: https://productforums.google.com/forum/#!topic/chrome/TP5RDsoaoeg
,
Feb 1 2018
,
Feb 2 2018
bernard.gray@ Thanks for the issue. Tested this issue on Ubuntu 17.10 on the reported version 61.0.3163.100 and latest Stable 64.0.3282.140 and unable to reproduce the issue by following the below steps. 1. Launched Chrome and signed into Chrome to sync all the bookmarks, history, passwords. 2. Closed the browser and relaunched it again. 3. Can see the the browser is getting launched without any issues. 4. launched chrome through Command line and can observe no issues there as well. Request you to please update chrome to the latest Stable and retry the issue and update the thread with the observations. Thanks..
,
Feb 6 2018
Hi, thanks for the reply.
I just tested with chromium-browser=64.0.3282.119 on ubuntu 17.10, the issue is still there.
Critical point to note, you probably have a package installed on your test machine that provides the org.freedesktop.secrets dbus service. You can check with the following:
dbus-send --dest=org.freedesktop.DBus --type=method_call --print-reply \
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep secret
If this returns:
string "org.freedesktop.secrets"
Then you already have some package providing that dependency incidentally, and your test only worked through sheer luck.
On my system, the above command does not return anything - this is the critical part of the bug report:
If Chrome *needs* it, it must add a dependency
Else If Chrome *does not* need it, it must not hang looking for it
,
Feb 6 2018
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 7 2018
bernard.gray@ Thanks for the feedback. As per comment #4, executed the command in the terminal and can see the output "string "org.freedesktop.secrets" is returned. Attached is the screen shot for reference. Request you please check and update further on triaging this issue. Thanks..
,
Feb 7 2018
Hi, As expected, your system has a package providing the "org.freedesktop.secrets" package. If it is standard ubuntu, then the package is gnome-keyring. To highlight the problem, remove this package: $ sudo apt-get remove gnome-keyring Restart your computer to force the Dbus services to refresh, then start your chrome/ium that you have previously signed in on. You should be able to replicate the problem now -
,
Feb 7 2018
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 8 2018
As per comment #7, removed the package using the command $ sudo apt-get remove gnome-keyring, after restarting the system the system did not render anything and it showed a black screen. Forwarding it to inhouse team for further triaging of the issue. Thanks...!!
,
Feb 15 2018
Tested this issue on Debian Rodete with chrome #64.0.3282.167 Observed that on uninstalling the gnome-keyring, i was unable to launch chrome Adding appropriate label and cc'ing prudvi@ for further triage |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Feb 1 2018