On Fri, Sep 08, 2023 at 06:23:22AM -0000, Nathan Teodosio wrote:
> In bug description:
> 1> when I went to use my saved passwords in chromium today, I found that
> they were absent.
> In your last comment:
> 2> chromium continues to be able to *use* my saved passwords. But I
> don't know where they're actually saved
> Which one is correct/up to date?
The second. Somehow the initial problem corrected itself along the way. So
Chromium can *use* passwords and *save* passwords but it will not *display*
passwords.
> Likewise for
> 3> I found that there was a
> ~/snap/chromium/common/chromium/Default/Login Data.old containing all of
> my passwords, and a ~/snap/chromium/common/chromium/Default/Login Data
> containing a single password entry
> and
> 4> But I don't know where they're actually saved
> It looks impossible that Chromium is accessing passwords from 'Login
> Data.old'; there is no longer any reference to that, anywhere, so I
> think quote 3 might not be up to date.
It contained all passwords that had been saved in my browser prior to this
issue.
Currently, I have a ~/snap/chromium/common/chromium/Default/Login Data which
was last modified September 5. So perhaps passwords are still being written
here.
> Depending on the situation you could try --password-store=basic, but
> given the already buggy circumstances, better have those configuration
> files backed up.
> Without a reproducible case and access to those data files, which of
> course you must not share as it contains passwords, this is hard to debug.
So for you, chrome://settings/passwords shows your passwords under 'Saved
Passwords' without having to specify --password-store=basic?
On Fri, Sep 08, 2023 at 06:23:22AM -0000, Nathan Teodosio wrote:
> In bug description:
> 1> when I went to use my saved passwords in chromium today, I found that
> they were absent.
> In your last comment:
> 2> chromium continues to be able to *use* my saved passwords. But I
> don't know where they're actually saved
> Which one is correct/up to date?
The second. Somehow the initial problem corrected itself along the way. So
Chromium can *use* passwords and *save* passwords but it will not *display*
passwords.
> Likewise for
> 3> I found that there was a chromium/ common/ chromium/ Default/ Login Data.old containing all of chromium/ common/ chromium/ Default/ Login Data
> ~/snap/
> my passwords, and a ~/snap/
> containing a single password entry
> and
> 4> But I don't know where they're actually saved
> It looks impossible that Chromium is accessing passwords from 'Login
> Data.old'; there is no longer any reference to that, anywhere, so I
> think quote 3 might not be up to date.
It contained all passwords that had been saved in my browser prior to this
issue.
Currently, I have a ~/snap/ chromium/ common/ chromium/ Default/ Login Data which
was last modified September 5. So perhaps passwords are still being written
here.
> Depending on the situation you could try --password- store=basic, but
> given the already buggy circumstances, better have those configuration
> files backed up.
> Without a reproducible case and access to those data files, which of
> course you must not share as it contains passwords, this is hard to debug.
So for you, chrome: //settings/ passwords shows your passwords under 'Saved store=basic?
Passwords' without having to specify --password-