After rebooting I need to log in each time in Chrome Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Undo automatic apt-get cleanEver since I upgraded to 16.04, Chrome logs me out of sites with every reboot. What gives?Ubuntu 18 Disable Auto LoginCan't stay logged in on Google ChromeAlways logged out from ChromeGoogle Chrome for Linux keeps requesting me to loginWhy do I get Ubuntu Classic instead of Unity the first time I log in after rebooting?Web sites do not work when I am logged into Google Chrome or need to log in to GoogleGoogle Chrome slowdown after some timeGoogle Chrome cursor and text selection issues after upgrading to google-chrome-stable_41.0.2272.76-1_amd64Google chrome removal after deleting /opt/googleMy PC logs out accidently when hit enter from Chrome addressbar after some time periodAlways logged out from ChromeChrome (not Chromium) Application name changed after disconnecting it from Google AccountNeed to see my passwords in ChromeChrome logs out every time I reboot
Where did Ptolemy compare the Earth to the distance of fixed stars?
How to make triangles with rounded sides and corners? (squircle with 3 sides)
Twin's vs. Twins'
By what mechanism was the 2017 UK General Election called?
How do Java 8 default methods hеlp with lambdas?
Is it OK to use the testing sample to compare algorithms?
Is the time—manner—place ordering of adverbials an oversimplification?
Understanding piped commands in GNU/Linux
The test team as an enemy of development? And how can this be avoided?
Why can't fire hurt Daenerys but it did to Jon Snow in season 1?
Is there a spell that can create a permanent fire?
Found this skink in my tomato plant bucket. Is he trapped? Or could he leave if he wanted?
Calculation of line of sight system gain
Is the Mordenkainen's Sword spell underpowered?
What does 丫 mean? 丫是什么意思?
First paper to introduce the "principal-agent problem"
Why not use the yoke to control yaw, as well as pitch and roll?
How can I prevent/balance waiting and turtling as a response to cooldown mechanics
How do I say "this must not happen"?
How could a hydrazine and N2O4 cloud (or it's reactants) show up in weather radar?
How to resize main filesystem
Was the pager message from Nick Fury to Captain Marvel unnecessary?
What is "Lambda" in Heston's original paper on stochastic volatility models?
Is there a verb for listening stealthily?
After rebooting I need to log in each time in Chrome
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Undo automatic apt-get cleanEver since I upgraded to 16.04, Chrome logs me out of sites with every reboot. What gives?Ubuntu 18 Disable Auto LoginCan't stay logged in on Google ChromeAlways logged out from ChromeGoogle Chrome for Linux keeps requesting me to loginWhy do I get Ubuntu Classic instead of Unity the first time I log in after rebooting?Web sites do not work when I am logged into Google Chrome or need to log in to GoogleGoogle Chrome slowdown after some timeGoogle Chrome cursor and text selection issues after upgrading to google-chrome-stable_41.0.2272.76-1_amd64Google chrome removal after deleting /opt/googleMy PC logs out accidently when hit enter from Chrome addressbar after some time periodAlways logged out from ChromeChrome (not Chromium) Application name changed after disconnecting it from Google AccountNeed to see my passwords in ChromeChrome logs out every time I reboot
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
If I reboot Ubuntu, then I need to log on each site and into Google Chrome account. What is the reason?
My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
google-chrome reboot
|
show 6 more comments
If I reboot Ubuntu, then I need to log on each site and into Google Chrome account. What is the reason?
My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
google-chrome reboot
1
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
How I can fix this?
– Novah
Sep 9 '16 at 5:44
2
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14
|
show 6 more comments
If I reboot Ubuntu, then I need to log on each site and into Google Chrome account. What is the reason?
My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
google-chrome reboot
If I reboot Ubuntu, then I need to log on each site and into Google Chrome account. What is the reason?
My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
google-chrome reboot
google-chrome reboot
edited Nov 20 '16 at 12:10
David Foerster
28.7k1367113
28.7k1367113
asked Sep 9 '16 at 5:28
NovahNovah
123117
123117
1
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
How I can fix this?
– Novah
Sep 9 '16 at 5:44
2
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14
|
show 6 more comments
1
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
How I can fix this?
– Novah
Sep 9 '16 at 5:44
2
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14
1
1
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
How I can fix this?
– Novah
Sep 9 '16 at 5:44
How I can fix this?
– Novah
Sep 9 '16 at 5:44
2
2
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14
|
show 6 more comments
7 Answers
7
active
oldest
votes
Had the same issue. My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
Here is my workaround:
- Go to Ubuntu System Settings -> Online Accounts
- add your Google account there
- turned on the switcher (not sure if it is necessary though)
- go to Chrome browser and login there again
- close the browser window
Note: you must prevent chrome processes from running after closing the window. To do this go to Chrome settings > Advanced settings (at the bottom) > Uncheck 'Continue running background apps when Google Chrome is closed'
Once I did it Chrome stopped dropping authentication after logging out in Ubuntu and also after rebooting
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
|
show 1 more comment
You have to enable this feature in Privacy
settings. You can get there by going into Chrome settings:
Enable saving passwords
- Click the Chrome menu icon (the three dots on the top right).
- Click Settings
- Click Show advance settings (new the bottom of the page)
- (Under Privacy - Passwords and forms)Place check marks under the following:
- Enable Autofill to fill out web forms
- Offer Save your web passwords
- Enable Autofill to fill out web forms
Passwords can be saved even with cookies disabled. You can still check your cookie settings with the steps below.
Enable or disable cookies
- Click the Chrome menu icon
- Click Settings
- Click Show advance settings
- In the Privacy section, select Content settings
- Select Allow local data to be set
If all settings are set for saving passwords and it still fails check the integrity of Chrome's setting by bring it to the defaults with the following steps.
First exit out of Chrome. Then run these commands to temporarily remove the current settings.
$ cd ~/.config
$ mv google-chrome google-chrome.bak
You can get the previous settings back by renaming google-chrome.bak to the it's original.
The issue was resolved as detailed in the chat comment section by renaming the home directory to a backup name, then creating a new home directory where Google Chrome worked. Then the backup directory was migrated to the new space.
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, clickManage Passwords
then checkmarkAuto Sign-in
. Also in the manage password section, scroll to the bottom and make sureNever Saved
isn't set for the site you're having problems with.
– L. D. James
Sep 9 '16 at 13:19
CheckboxAuto Sign-in
, and so checked
– Novah
Sep 9 '16 at 13:25
|
show 6 more comments
Workaround
If above answer does not solve the issue, installing the beta version of Google Chrome can workaround the problem.
apt install google-chrome-beta
This seems not to solve it (entry preserved for historical reasons):
I have the very same problem and did a few hours of debugging.
My problem is only related to google-chrome-stable Version 53.0.2785.101 (64-bit) on ubuntu 16.04.
When I login at a website, cookies are set correctly. When I close chrome, log out, log back in again, the cookies are still there and everything is fine. However, if I reboot, the cookies are gone and I need to login again.
I did some debugging (reinstalling chrome, reverting to default config, starting from a clean config, everything as suggested above, ...) and the bug persits.
I installed google-chrome-unstable Version 55.0.2853.0 dev (64-bit) and everything works fine (while stable still has the issue). So this is probably a chrome software bug.
My "solution": Use firefox/chrome-unstable for a few days/weeks, just wait for the update which fixes the issue to propagate to google-chrome-stable.
By the way, I'm using ubuntu 16.04 (systemd) with dm mapper/cryptsetup which was upgraded from 14.04 and I'm still not 100% sure that my crypt partition is unmounted every time 100% correctly (though the fs is always clean). @Novah, do you have a similar setup?
It is September 2016 when I write this advice. If it hasn't resolved within a month automatically, my answer is wrong ;-)
I hope to spare you a lot of debugging and frustration.
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
add a comment |
Please note this is already reported to the Chromium Bug Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=631171
add a comment |
I had the same problem, but my system is ubuntu 14.04.
If your system also asked for keyring password every start google chrome (also restart system), i think that because Google chrome cannot get your saved google-password because your saved google-password locked by the keyring. You have to make sure that keyring is unlocked before you start Google chrome, not after. Here is my solution:
- Open google chrome.
- Login back to google account as usual and make sure there is no yellow warning icon before your username at top right corner. (just do it)
- Close google chrome.
- Open up Dash and open User Account, then turn "off" automatic login.
- Restart system.
By turning automatic login to "off", I thought this automatically will unlock keyring every login system, so Google chrome can get your google account password from keyring.
I know there are also another solution about disable keyring (by set keyring password to blank), but i think that is not secure.
add a comment |
I was facing same issues. In new install, I installed chrome as root ( not sudo). After restarting the program worked well.
Learning this, I uninstalled chrome from the previous PC and installed it again as root user.
Now everything is fine and the annoying login prompt is gone.
sudo -i
apt-get remove google-chrome*
apt-get autoremove
apt-get clean
apt-get install google-chrome-stable
Doingsudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.
– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
add a comment |
I have encountered the same problem. For the issue, it is because of the automatic ubuntu login.
So, for the easiest fix, just disable the automatic login.
Disable the automatic login for Ubuntu:
Ubuntu disable automatic login
Disable the automatic login for Ubuntu:
Open terminal
Enter,
sudo nano /etc/lightdm/lightdm.conf
Comment your username,
#autologin-user=MyNameIsSyirasky
- Save and exit, reboot.
New contributor
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f822804%2fafter-rebooting-i-need-to-log-in-each-time-in-chrome%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
Had the same issue. My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
Here is my workaround:
- Go to Ubuntu System Settings -> Online Accounts
- add your Google account there
- turned on the switcher (not sure if it is necessary though)
- go to Chrome browser and login there again
- close the browser window
Note: you must prevent chrome processes from running after closing the window. To do this go to Chrome settings > Advanced settings (at the bottom) > Uncheck 'Continue running background apps when Google Chrome is closed'
Once I did it Chrome stopped dropping authentication after logging out in Ubuntu and also after rebooting
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
|
show 1 more comment
Had the same issue. My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
Here is my workaround:
- Go to Ubuntu System Settings -> Online Accounts
- add your Google account there
- turned on the switcher (not sure if it is necessary though)
- go to Chrome browser and login there again
- close the browser window
Note: you must prevent chrome processes from running after closing the window. To do this go to Chrome settings > Advanced settings (at the bottom) > Uncheck 'Continue running background apps when Google Chrome is closed'
Once I did it Chrome stopped dropping authentication after logging out in Ubuntu and also after rebooting
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
|
show 1 more comment
Had the same issue. My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
Here is my workaround:
- Go to Ubuntu System Settings -> Online Accounts
- add your Google account there
- turned on the switcher (not sure if it is necessary though)
- go to Chrome browser and login there again
- close the browser window
Note: you must prevent chrome processes from running after closing the window. To do this go to Chrome settings > Advanced settings (at the bottom) > Uncheck 'Continue running background apps when Google Chrome is closed'
Once I did it Chrome stopped dropping authentication after logging out in Ubuntu and also after rebooting
Had the same issue. My system is Ubuntu 16.04 and Google Chrome 53.0.2785.101 (64-bit).
Here is my workaround:
- Go to Ubuntu System Settings -> Online Accounts
- add your Google account there
- turned on the switcher (not sure if it is necessary though)
- go to Chrome browser and login there again
- close the browser window
Note: you must prevent chrome processes from running after closing the window. To do this go to Chrome settings > Advanced settings (at the bottom) > Uncheck 'Continue running background apps when Google Chrome is closed'
Once I did it Chrome stopped dropping authentication after logging out in Ubuntu and also after rebooting
answered Sep 11 '16 at 21:34
Igor BukinIgor Bukin
27614
27614
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
|
show 1 more comment
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@IgorBukin It helped me.
– Novah
Sep 12 '16 at 13:01
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
@Novah That was one of the suggestions in chat. I suggested it as a resolution. You said you didn't want it to be associated with your Google account (chat.stackexchange.com/transcript/message/32209536#32209536).
– L. D. James
Sep 13 '16 at 1:59
1
1
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Do you have any idea why this might work?
– corny
Sep 13 '16 at 13:44
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Thanks, I only cleared the password of my gnome keyring (not giving ubuntu my google password) and now it also works.
– corny
Sep 14 '16 at 8:15
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
Per some comments on the bug report (bugs.chromium.org/p/chromium/issues/detail?id=631171), this probably works because it forces opening of the keyring before Chromium is started. It appears this has a shot of being fixed with Chromium 55. Now the real question is whether we can get Ubuntu to push out Chromium 55 on a more timely basis than its typical Chromium builds.
– Aren Cambre
Nov 8 '16 at 14:29
|
show 1 more comment
You have to enable this feature in Privacy
settings. You can get there by going into Chrome settings:
Enable saving passwords
- Click the Chrome menu icon (the three dots on the top right).
- Click Settings
- Click Show advance settings (new the bottom of the page)
- (Under Privacy - Passwords and forms)Place check marks under the following:
- Enable Autofill to fill out web forms
- Offer Save your web passwords
- Enable Autofill to fill out web forms
Passwords can be saved even with cookies disabled. You can still check your cookie settings with the steps below.
Enable or disable cookies
- Click the Chrome menu icon
- Click Settings
- Click Show advance settings
- In the Privacy section, select Content settings
- Select Allow local data to be set
If all settings are set for saving passwords and it still fails check the integrity of Chrome's setting by bring it to the defaults with the following steps.
First exit out of Chrome. Then run these commands to temporarily remove the current settings.
$ cd ~/.config
$ mv google-chrome google-chrome.bak
You can get the previous settings back by renaming google-chrome.bak to the it's original.
The issue was resolved as detailed in the chat comment section by renaming the home directory to a backup name, then creating a new home directory where Google Chrome worked. Then the backup directory was migrated to the new space.
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, clickManage Passwords
then checkmarkAuto Sign-in
. Also in the manage password section, scroll to the bottom and make sureNever Saved
isn't set for the site you're having problems with.
– L. D. James
Sep 9 '16 at 13:19
CheckboxAuto Sign-in
, and so checked
– Novah
Sep 9 '16 at 13:25
|
show 6 more comments
You have to enable this feature in Privacy
settings. You can get there by going into Chrome settings:
Enable saving passwords
- Click the Chrome menu icon (the three dots on the top right).
- Click Settings
- Click Show advance settings (new the bottom of the page)
- (Under Privacy - Passwords and forms)Place check marks under the following:
- Enable Autofill to fill out web forms
- Offer Save your web passwords
- Enable Autofill to fill out web forms
Passwords can be saved even with cookies disabled. You can still check your cookie settings with the steps below.
Enable or disable cookies
- Click the Chrome menu icon
- Click Settings
- Click Show advance settings
- In the Privacy section, select Content settings
- Select Allow local data to be set
If all settings are set for saving passwords and it still fails check the integrity of Chrome's setting by bring it to the defaults with the following steps.
First exit out of Chrome. Then run these commands to temporarily remove the current settings.
$ cd ~/.config
$ mv google-chrome google-chrome.bak
You can get the previous settings back by renaming google-chrome.bak to the it's original.
The issue was resolved as detailed in the chat comment section by renaming the home directory to a backup name, then creating a new home directory where Google Chrome worked. Then the backup directory was migrated to the new space.
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, clickManage Passwords
then checkmarkAuto Sign-in
. Also in the manage password section, scroll to the bottom and make sureNever Saved
isn't set for the site you're having problems with.
– L. D. James
Sep 9 '16 at 13:19
CheckboxAuto Sign-in
, and so checked
– Novah
Sep 9 '16 at 13:25
|
show 6 more comments
You have to enable this feature in Privacy
settings. You can get there by going into Chrome settings:
Enable saving passwords
- Click the Chrome menu icon (the three dots on the top right).
- Click Settings
- Click Show advance settings (new the bottom of the page)
- (Under Privacy - Passwords and forms)Place check marks under the following:
- Enable Autofill to fill out web forms
- Offer Save your web passwords
- Enable Autofill to fill out web forms
Passwords can be saved even with cookies disabled. You can still check your cookie settings with the steps below.
Enable or disable cookies
- Click the Chrome menu icon
- Click Settings
- Click Show advance settings
- In the Privacy section, select Content settings
- Select Allow local data to be set
If all settings are set for saving passwords and it still fails check the integrity of Chrome's setting by bring it to the defaults with the following steps.
First exit out of Chrome. Then run these commands to temporarily remove the current settings.
$ cd ~/.config
$ mv google-chrome google-chrome.bak
You can get the previous settings back by renaming google-chrome.bak to the it's original.
The issue was resolved as detailed in the chat comment section by renaming the home directory to a backup name, then creating a new home directory where Google Chrome worked. Then the backup directory was migrated to the new space.
You have to enable this feature in Privacy
settings. You can get there by going into Chrome settings:
Enable saving passwords
- Click the Chrome menu icon (the three dots on the top right).
- Click Settings
- Click Show advance settings (new the bottom of the page)
- (Under Privacy - Passwords and forms)Place check marks under the following:
- Enable Autofill to fill out web forms
- Offer Save your web passwords
- Enable Autofill to fill out web forms
Passwords can be saved even with cookies disabled. You can still check your cookie settings with the steps below.
Enable or disable cookies
- Click the Chrome menu icon
- Click Settings
- Click Show advance settings
- In the Privacy section, select Content settings
- Select Allow local data to be set
If all settings are set for saving passwords and it still fails check the integrity of Chrome's setting by bring it to the defaults with the following steps.
First exit out of Chrome. Then run these commands to temporarily remove the current settings.
$ cd ~/.config
$ mv google-chrome google-chrome.bak
You can get the previous settings back by renaming google-chrome.bak to the it's original.
The issue was resolved as detailed in the chat comment section by renaming the home directory to a backup name, then creating a new home directory where Google Chrome worked. Then the backup directory was migrated to the new space.
edited Sep 10 '16 at 4:41
answered Sep 9 '16 at 6:47
L. D. JamesL. D. James
19k43990
19k43990
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, clickManage Passwords
then checkmarkAuto Sign-in
. Also in the manage password section, scroll to the bottom and make sureNever Saved
isn't set for the site you're having problems with.
– L. D. James
Sep 9 '16 at 13:19
CheckboxAuto Sign-in
, and so checked
– Novah
Sep 9 '16 at 13:25
|
show 6 more comments
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, clickManage Passwords
then checkmarkAuto Sign-in
. Also in the manage password section, scroll to the bottom and make sureNever Saved
isn't set for the site you're having problems with.
– L. D. James
Sep 9 '16 at 13:19
CheckboxAuto Sign-in
, and so checked
– Novah
Sep 9 '16 at 13:25
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
At me it is all configured had already been. If click All cockies and site data cookies there, so it does not delete cookies when closing Google Chrome
– Novah
Sep 9 '16 at 13:05
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
@Novah The cookies isn't your issue. I put the steps referring to cookies because of your reference to it in the comments. You issue should be resolved by following the steps for passwords in the answer. Did those steps work?
– L. D. James
Sep 9 '16 at 13:10
no, it does not work.
– Novah
Sep 9 '16 at 13:13
no, it does not work.
– Novah
Sep 9 '16 at 13:13
@Novah In the password section, click
Manage Passwords
then checkmark Auto Sign-in
. Also in the manage password section, scroll to the bottom and make sure Never Saved
isn't set for the site you're having problems with.– L. D. James
Sep 9 '16 at 13:19
@Novah In the password section, click
Manage Passwords
then checkmark Auto Sign-in
. Also in the manage password section, scroll to the bottom and make sure Never Saved
isn't set for the site you're having problems with.– L. D. James
Sep 9 '16 at 13:19
Checkbox
Auto Sign-in
, and so checked– Novah
Sep 9 '16 at 13:25
Checkbox
Auto Sign-in
, and so checked– Novah
Sep 9 '16 at 13:25
|
show 6 more comments
Workaround
If above answer does not solve the issue, installing the beta version of Google Chrome can workaround the problem.
apt install google-chrome-beta
This seems not to solve it (entry preserved for historical reasons):
I have the very same problem and did a few hours of debugging.
My problem is only related to google-chrome-stable Version 53.0.2785.101 (64-bit) on ubuntu 16.04.
When I login at a website, cookies are set correctly. When I close chrome, log out, log back in again, the cookies are still there and everything is fine. However, if I reboot, the cookies are gone and I need to login again.
I did some debugging (reinstalling chrome, reverting to default config, starting from a clean config, everything as suggested above, ...) and the bug persits.
I installed google-chrome-unstable Version 55.0.2853.0 dev (64-bit) and everything works fine (while stable still has the issue). So this is probably a chrome software bug.
My "solution": Use firefox/chrome-unstable for a few days/weeks, just wait for the update which fixes the issue to propagate to google-chrome-stable.
By the way, I'm using ubuntu 16.04 (systemd) with dm mapper/cryptsetup which was upgraded from 14.04 and I'm still not 100% sure that my crypt partition is unmounted every time 100% correctly (though the fs is always clean). @Novah, do you have a similar setup?
It is September 2016 when I write this advice. If it hasn't resolved within a month automatically, my answer is wrong ;-)
I hope to spare you a lot of debugging and frustration.
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
add a comment |
Workaround
If above answer does not solve the issue, installing the beta version of Google Chrome can workaround the problem.
apt install google-chrome-beta
This seems not to solve it (entry preserved for historical reasons):
I have the very same problem and did a few hours of debugging.
My problem is only related to google-chrome-stable Version 53.0.2785.101 (64-bit) on ubuntu 16.04.
When I login at a website, cookies are set correctly. When I close chrome, log out, log back in again, the cookies are still there and everything is fine. However, if I reboot, the cookies are gone and I need to login again.
I did some debugging (reinstalling chrome, reverting to default config, starting from a clean config, everything as suggested above, ...) and the bug persits.
I installed google-chrome-unstable Version 55.0.2853.0 dev (64-bit) and everything works fine (while stable still has the issue). So this is probably a chrome software bug.
My "solution": Use firefox/chrome-unstable for a few days/weeks, just wait for the update which fixes the issue to propagate to google-chrome-stable.
By the way, I'm using ubuntu 16.04 (systemd) with dm mapper/cryptsetup which was upgraded from 14.04 and I'm still not 100% sure that my crypt partition is unmounted every time 100% correctly (though the fs is always clean). @Novah, do you have a similar setup?
It is September 2016 when I write this advice. If it hasn't resolved within a month automatically, my answer is wrong ;-)
I hope to spare you a lot of debugging and frustration.
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
add a comment |
Workaround
If above answer does not solve the issue, installing the beta version of Google Chrome can workaround the problem.
apt install google-chrome-beta
This seems not to solve it (entry preserved for historical reasons):
I have the very same problem and did a few hours of debugging.
My problem is only related to google-chrome-stable Version 53.0.2785.101 (64-bit) on ubuntu 16.04.
When I login at a website, cookies are set correctly. When I close chrome, log out, log back in again, the cookies are still there and everything is fine. However, if I reboot, the cookies are gone and I need to login again.
I did some debugging (reinstalling chrome, reverting to default config, starting from a clean config, everything as suggested above, ...) and the bug persits.
I installed google-chrome-unstable Version 55.0.2853.0 dev (64-bit) and everything works fine (while stable still has the issue). So this is probably a chrome software bug.
My "solution": Use firefox/chrome-unstable for a few days/weeks, just wait for the update which fixes the issue to propagate to google-chrome-stable.
By the way, I'm using ubuntu 16.04 (systemd) with dm mapper/cryptsetup which was upgraded from 14.04 and I'm still not 100% sure that my crypt partition is unmounted every time 100% correctly (though the fs is always clean). @Novah, do you have a similar setup?
It is September 2016 when I write this advice. If it hasn't resolved within a month automatically, my answer is wrong ;-)
I hope to spare you a lot of debugging and frustration.
Workaround
If above answer does not solve the issue, installing the beta version of Google Chrome can workaround the problem.
apt install google-chrome-beta
This seems not to solve it (entry preserved for historical reasons):
I have the very same problem and did a few hours of debugging.
My problem is only related to google-chrome-stable Version 53.0.2785.101 (64-bit) on ubuntu 16.04.
When I login at a website, cookies are set correctly. When I close chrome, log out, log back in again, the cookies are still there and everything is fine. However, if I reboot, the cookies are gone and I need to login again.
I did some debugging (reinstalling chrome, reverting to default config, starting from a clean config, everything as suggested above, ...) and the bug persits.
I installed google-chrome-unstable Version 55.0.2853.0 dev (64-bit) and everything works fine (while stable still has the issue). So this is probably a chrome software bug.
My "solution": Use firefox/chrome-unstable for a few days/weeks, just wait for the update which fixes the issue to propagate to google-chrome-stable.
By the way, I'm using ubuntu 16.04 (systemd) with dm mapper/cryptsetup which was upgraded from 14.04 and I'm still not 100% sure that my crypt partition is unmounted every time 100% correctly (though the fs is always clean). @Novah, do you have a similar setup?
It is September 2016 when I write this advice. If it hasn't resolved within a month automatically, my answer is wrong ;-)
I hope to spare you a lot of debugging and frustration.
edited Oct 24 '16 at 15:02
desgua
28k883112
28k883112
answered Sep 9 '16 at 21:39
cornycorny
1234
1234
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
add a comment |
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
Hey! Unfortunately didn't work for me :( . Still struggling with this issue. My steps were the following: removed the stable version, removed google-chrome from ~/.config, installed latest dev version which is 55.0.2853.0 dev (64-bit). Authentication is dropped even when I just close the browser window. And every time I open it back I get a message "your profile could not be opened correctly...". (Ubuntu 16.04)
– Igor Bukin
Sep 11 '16 at 19:10
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
@corny I have installed google-chrome-beta and the problem persists
– Novah
Sep 12 '16 at 12:49
add a comment |
Please note this is already reported to the Chromium Bug Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=631171
add a comment |
Please note this is already reported to the Chromium Bug Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=631171
add a comment |
Please note this is already reported to the Chromium Bug Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=631171
Please note this is already reported to the Chromium Bug Tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=631171
answered Sep 21 '16 at 19:50
user597677user597677
111
111
add a comment |
add a comment |
I had the same problem, but my system is ubuntu 14.04.
If your system also asked for keyring password every start google chrome (also restart system), i think that because Google chrome cannot get your saved google-password because your saved google-password locked by the keyring. You have to make sure that keyring is unlocked before you start Google chrome, not after. Here is my solution:
- Open google chrome.
- Login back to google account as usual and make sure there is no yellow warning icon before your username at top right corner. (just do it)
- Close google chrome.
- Open up Dash and open User Account, then turn "off" automatic login.
- Restart system.
By turning automatic login to "off", I thought this automatically will unlock keyring every login system, so Google chrome can get your google account password from keyring.
I know there are also another solution about disable keyring (by set keyring password to blank), but i think that is not secure.
add a comment |
I had the same problem, but my system is ubuntu 14.04.
If your system also asked for keyring password every start google chrome (also restart system), i think that because Google chrome cannot get your saved google-password because your saved google-password locked by the keyring. You have to make sure that keyring is unlocked before you start Google chrome, not after. Here is my solution:
- Open google chrome.
- Login back to google account as usual and make sure there is no yellow warning icon before your username at top right corner. (just do it)
- Close google chrome.
- Open up Dash and open User Account, then turn "off" automatic login.
- Restart system.
By turning automatic login to "off", I thought this automatically will unlock keyring every login system, so Google chrome can get your google account password from keyring.
I know there are also another solution about disable keyring (by set keyring password to blank), but i think that is not secure.
add a comment |
I had the same problem, but my system is ubuntu 14.04.
If your system also asked for keyring password every start google chrome (also restart system), i think that because Google chrome cannot get your saved google-password because your saved google-password locked by the keyring. You have to make sure that keyring is unlocked before you start Google chrome, not after. Here is my solution:
- Open google chrome.
- Login back to google account as usual and make sure there is no yellow warning icon before your username at top right corner. (just do it)
- Close google chrome.
- Open up Dash and open User Account, then turn "off" automatic login.
- Restart system.
By turning automatic login to "off", I thought this automatically will unlock keyring every login system, so Google chrome can get your google account password from keyring.
I know there are also another solution about disable keyring (by set keyring password to blank), but i think that is not secure.
I had the same problem, but my system is ubuntu 14.04.
If your system also asked for keyring password every start google chrome (also restart system), i think that because Google chrome cannot get your saved google-password because your saved google-password locked by the keyring. You have to make sure that keyring is unlocked before you start Google chrome, not after. Here is my solution:
- Open google chrome.
- Login back to google account as usual and make sure there is no yellow warning icon before your username at top right corner. (just do it)
- Close google chrome.
- Open up Dash and open User Account, then turn "off" automatic login.
- Restart system.
By turning automatic login to "off", I thought this automatically will unlock keyring every login system, so Google chrome can get your google account password from keyring.
I know there are also another solution about disable keyring (by set keyring password to blank), but i think that is not secure.
answered Oct 18 '16 at 6:53
mnemonic brianmnemonic brian
101
101
add a comment |
add a comment |
I was facing same issues. In new install, I installed chrome as root ( not sudo). After restarting the program worked well.
Learning this, I uninstalled chrome from the previous PC and installed it again as root user.
Now everything is fine and the annoying login prompt is gone.
sudo -i
apt-get remove google-chrome*
apt-get autoremove
apt-get clean
apt-get install google-chrome-stable
Doingsudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.
– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
add a comment |
I was facing same issues. In new install, I installed chrome as root ( not sudo). After restarting the program worked well.
Learning this, I uninstalled chrome from the previous PC and installed it again as root user.
Now everything is fine and the annoying login prompt is gone.
sudo -i
apt-get remove google-chrome*
apt-get autoremove
apt-get clean
apt-get install google-chrome-stable
Doingsudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.
– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
add a comment |
I was facing same issues. In new install, I installed chrome as root ( not sudo). After restarting the program worked well.
Learning this, I uninstalled chrome from the previous PC and installed it again as root user.
Now everything is fine and the annoying login prompt is gone.
sudo -i
apt-get remove google-chrome*
apt-get autoremove
apt-get clean
apt-get install google-chrome-stable
I was facing same issues. In new install, I installed chrome as root ( not sudo). After restarting the program worked well.
Learning this, I uninstalled chrome from the previous PC and installed it again as root user.
Now everything is fine and the annoying login prompt is gone.
sudo -i
apt-get remove google-chrome*
apt-get autoremove
apt-get clean
apt-get install google-chrome-stable
edited Dec 30 '16 at 4:51
karel
61.3k13133155
61.3k13133155
answered Dec 30 '16 at 4:47
Vikas AvnishVikas Avnish
1211
1211
Doingsudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.
– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
add a comment |
Doingsudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.
– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
Doing
sudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.– George Udosen
Dec 30 '16 at 5:10
Doing
sudo apt-get package_name
should also work. One should stay away from running commands from the root account directly as a miss-typed command can lead to very unpleasant results.– George Udosen
Dec 30 '16 at 5:10
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
thanks karel. Running any program as root require special attention otherwise system could be broken
– Vikas Avnish
Dec 30 '16 at 6:02
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
Its george not karel look at the end of the comment to see who made it ;).
– George Udosen
Dec 30 '16 at 6:08
1
1
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
I want to thank both of You . George and Karel
– Vikas Avnish
Dec 30 '16 at 12:27
add a comment |
I have encountered the same problem. For the issue, it is because of the automatic ubuntu login.
So, for the easiest fix, just disable the automatic login.
Disable the automatic login for Ubuntu:
Ubuntu disable automatic login
Disable the automatic login for Ubuntu:
Open terminal
Enter,
sudo nano /etc/lightdm/lightdm.conf
Comment your username,
#autologin-user=MyNameIsSyirasky
- Save and exit, reboot.
New contributor
add a comment |
I have encountered the same problem. For the issue, it is because of the automatic ubuntu login.
So, for the easiest fix, just disable the automatic login.
Disable the automatic login for Ubuntu:
Ubuntu disable automatic login
Disable the automatic login for Ubuntu:
Open terminal
Enter,
sudo nano /etc/lightdm/lightdm.conf
Comment your username,
#autologin-user=MyNameIsSyirasky
- Save and exit, reboot.
New contributor
add a comment |
I have encountered the same problem. For the issue, it is because of the automatic ubuntu login.
So, for the easiest fix, just disable the automatic login.
Disable the automatic login for Ubuntu:
Ubuntu disable automatic login
Disable the automatic login for Ubuntu:
Open terminal
Enter,
sudo nano /etc/lightdm/lightdm.conf
Comment your username,
#autologin-user=MyNameIsSyirasky
- Save and exit, reboot.
New contributor
I have encountered the same problem. For the issue, it is because of the automatic ubuntu login.
So, for the easiest fix, just disable the automatic login.
Disable the automatic login for Ubuntu:
Ubuntu disable automatic login
Disable the automatic login for Ubuntu:
Open terminal
Enter,
sudo nano /etc/lightdm/lightdm.conf
Comment your username,
#autologin-user=MyNameIsSyirasky
- Save and exit, reboot.
New contributor
New contributor
answered 24 mins ago
RasRas
11
11
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f822804%2fafter-rebooting-i-need-to-log-in-each-time-in-chrome%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
That means your cookies are getting deleted every time you close Chrome.
– edwinksl
Sep 9 '16 at 5:41
How I can fix this?
– Novah
Sep 9 '16 at 5:44
2
Did you install Ubuntu on your computer or are you on a live system without persistence? Except for the latter case this is a Chrome issue that has nothing to do with Ubuntu.
– David Foerster
Sep 9 '16 at 7:40
@DavidFoerster I installed Ubuntu on my computer
– Novah
Sep 9 '16 at 12:53
Asked yesterday! I am having same issue. :-)
– Paritosh
Sep 11 '16 at 3:14