Why won't Google Chrome remember my Google logins?

[Clark Venable]

I've managed to install Google Chrome in my 'personal' domain (not the template). I can log into my google account(s), but once I stop and restart the Chrome app in the personal domain I am asked to log into Google again. I was under the impression that only disposable VM's would discard all session data. How can I get Chrome to remember my login so I can access Gmail with Chrome without logging in each time?

Clark

[Chris Laprise]

On 09/24/2016 04:02 PM, Clark Venable wrote:
> I've managed to install Google Chrome in my 'personal' domain (not the template). I can log into my google account(s), but once I stop and restart the Chrome app in the personal domain I am asked to log into Google again. I was under the impression that only disposable VM's would discard all session data. How can I get Chrome to remember my login so I can access Gmail with Chrome without logging in each time?
>
> Clark
>

Are you also stopping then starting the vm that's running Chrome? If
Chrome is forgetting without stopping/starting the vm, that sounds like
a Chrome bug.

If the problem hinges on stopping/starting, then Chrome may be storing
session data in a nonstandard location (instead of /home/user) such as
/var. When you are running Chrome, look in /var/lib to see if Chrome is
writing files there.

Chris

[Clark Venable]

It looks like Chrome is saving to:

/home/user/.config/google-chrome/Default

Could it be that each new VM instance appears to be a different computer, therefore prompting confirmation of credentials?

[Chris Laprise]

That looks normal. So there must be another reason.

Chris

[Franck Ridel]

Can you check content settings ? I guess Cookies is set on "Keep local data only until you quit your browser" 

--

Franck Ridel

http://franck-ridel.fr/

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/92cf88cc-227d-125c-96eb-c6eed93fb31f%40openmailbox.org.

For more options, visit https://groups.google.com/d/optout.

[Clark Venable]

Nope. Allow local data to be set is enabled.

[Clark Venable]

On Sunday, September 25, 2016 at 8:42:08 AM UTC-4, Clark Venable wrote:
> Nope. Allow local data to be set is enabled.

It all works as I expect in Firefox, So I'm happy to leave this alone and just use Firefox rather than Chrome (which is probably what the devlopers intended by including Firefox in the distro. :-)

[Mathew Evans]

I can confirm i had the same issue with Chrome. There is somthing funky going on between seahorse and chrome and how in the AppVMs details are stored. As long as you do not restart the AppVM you can close and reopen chrome as many times as you want and it will work fine, even with disable background processes. when you restart the AppVM the info in seahorse seams to expire instantly.

[Clark Venable]

Thanks for the confirmation, Mat. I was just chalking it up to not having done something right. As I indicated, Firefox works as I expect, so I've just switched to that as my main browser.

Clark

[chk...@gmail.com]

https://bugs.chromium.org/p/chromium/issues/detail?id=631171

[raah...@gmail.com]

Just use keepassx in the vault vm.