Chrome fails to detect XFCE desktop environment, therefore not using correct password store
Reported by
mich...@fds-team.de,
Jul 14
|
|||
Issue descriptionChrome Version (from the about:version page): 67.0.3396.99 Is this the most recent version: yes (stable) OS + version: Debian buster CPU architecture (32-bit / 64-bit): 64-bit Window manager: XFCE URLs (if relevant): Behavior in Linux Firefox: Behavior in Windows Chrome (if you have access to it): What steps will reproduce the problem? (1) Start chromium with --v=1 What is the expected result? Chromium should print the following log lines: [5867:5867:0714/211544.354457:VERBOSE1:key_storage_util_linux.cc(53)] Password storage detected desktop environment: XFCE [5867:5867:0714/211544.354490:VERBOSE1:password_store_factory.cc(226)] Trying libsecret for password storage. [5867:5867:0714/211544.362965:VERBOSE1:password_store_factory.cc(229)] Using libsecret keyring for password storage. What happens instead? Chromium does not detect XFCE and prints instead: [8849:8849:0714/213137.931289:VERBOSE1:key_storage_util_linux.cc(53)] Password storage detected desktop environment: (unknown) [8849:8849:0714/213137.931333:WARNING:password_store_factory.cc(253)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options. Please provide any additional information below. Attach a screenshot and backtrace if possible. I have created a fix for the problem and will upload it for code review.
,
Jul 16
We were unable to reproduce the issue on Ubuntu 14.04 and currently we do not have Debian to test and confirm the fix ... hence cc'ing thomasanderson@ for further action on this. Changing the status of the bug to Untriaged as the fix has landed. Thanks!
,
Jul 16
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Jul 15