Issue metadata
Sign in to add a comment
|
Need to re-sign-in after each reboot
Reported by
blkcho...@gmail.com,
Sep 8 2016
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36
Steps to reproduce the problem:
1. Sign in to Chromium
2. Reboot
3. Open Chromium again
What is the expected behavior?
Chromium should work normally without me having to sign in again.
What went wrong?
It asks me for my credentials again. ("Account sign-in details are out of date. Sign in again")
Did this work before? N/A
Chrome version: 53.0.2785.101 Channel: stable
OS Version: Antergos/Arch
Flash Version:
It looked through many different bugs for the last hours with the same problem, but they seem to be fixed or being worked around each time.
I tried:
- Deleting my profile
- Resetting sync data
- Copying the profile from my Laptop (it works over there, on the same distro (Antergos) with the same settings in the same environment (lightdm+xfce4))
- Re-configuring my keyring or not using it at all (with --password-store=base)
- Disconnect account, add Person, etc.
No, my email does not contain a dot.
When I run chromium in the Terminal, it outputs: OnGetTokenFailure: Not authorized.
Will add pictures from chrome://signin-internals after I rebooted.
If this might be of interest: The only difference to my laptop is that I'm dual-booting Antergos and Windows.
Greetings, BlkChockr
,
Sep 14 2016
i confirm this! i have the exact same problem with stable chrome on ubuntu 16.04 LTS. Version 53.0.2785.113 (64-bit) previous version had the same problem!
,
Sep 14 2016
Assigning to the signin TL anthonyvd@ to triage.
,
Sep 14 2016
Where is your Chrome build coming from? I'm not familiar with this "Entickler-Build" part in your version string.
,
Sep 14 2016
"Entwickler" means "Developer" in German :) I didn't choose that one in specific, though. I just did a "sudo pacman -S chromium" on Antergos/Arch Linux to get it... As I am on x64, it should be this one: https://www.archlinux.org/packages/extra/x86_64/chromium/
,
Sep 14 2016
Ahh thanks! chrome://signin-internals seems to think your credentials are invalid. I imagine you're not changing your Google password between each reboot? Does the same thing happen if you sign in to a fresh profile/with a different Google account?
,
Sep 15 2016
for me it is still happening even after a complete erase of my profile and the synced data.
,
Sep 15 2016
Yes, I tested deleting my whole profile/config before. Same result. Just to be sure, I just created another Google account and tried with it. The result was even worse: Instead of having to sign in after each reboot, I had to re-sign-in each time I closed chromium. :( Switching back to my own account (and deleting the configs/profiles again), it went back to after each reboot. Strange. PS: Just updated to 53.0.2785.116 and the bug still exists.
,
Sep 15 2016
yeah Version 53.0.2785.116 (64-bit) linux and still the same problem. they must know they screwd the putch because 3 version of chrome STABLE in like 5 days....
,
Sep 19 2016
This looks like a dupe of 621378. I'll try to see if something changed in the code that interacts with gnome-keyring-daemon since that seems to be the root cause. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by blkcho...@gmail.com
, Sep 8 2016160 KB
160 KB View Download
112 KB
112 KB View Download