How to hide chrome warning after crash?












26















When Chrome has crashed, it displays a warning (under the address bar) upon restart, offering to restore tabs. I'm launching chrome in kiosk mode and I don't want theses warnings to be displayed.



Is there a way to do this ?










share|improve this question

























  • This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

    – nc4pk
    Jul 23 '15 at 0:31
















26















When Chrome has crashed, it displays a warning (under the address bar) upon restart, offering to restore tabs. I'm launching chrome in kiosk mode and I don't want theses warnings to be displayed.



Is there a way to do this ?










share|improve this question

























  • This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

    – nc4pk
    Jul 23 '15 at 0:31














26












26








26


11






When Chrome has crashed, it displays a warning (under the address bar) upon restart, offering to restore tabs. I'm launching chrome in kiosk mode and I don't want theses warnings to be displayed.



Is there a way to do this ?










share|improve this question
















When Chrome has crashed, it displays a warning (under the address bar) upon restart, offering to restore tabs. I'm launching chrome in kiosk mode and I don't want theses warnings to be displayed.



Is there a way to do this ?







google-chrome crash session-restore






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 4 '17 at 21:17









InterLinked

1,1211131




1,1211131










asked Jan 25 '11 at 13:44









OlivierOlivier

65931020




65931020













  • This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

    – nc4pk
    Jul 23 '15 at 0:31



















  • This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

    – nc4pk
    Jul 23 '15 at 0:31

















This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

– nc4pk
Jul 23 '15 at 0:31





This is a probable duplicate of superuser.com/questions/461035/…. Even though this question is older, it has 10x fewer views and 3x fewer votes.

– nc4pk
Jul 23 '15 at 0:31










7 Answers
7






active

oldest

votes


















16














You should run Chrome in Incognito Mode with this command:



chrome --incognito --kiosk http://127.0.0.1


Here they talk about running this command before starting Chrome to stop the Restore Bar from appearing:



sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' 
~/.config/google-chrome/Default/Preferences





share|improve this answer
























  • incognito does the trick for me.

    – Olivier
    Jan 27 '11 at 15:40






  • 7





    Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

    – Davide Andrea
    Oct 1 '17 at 23:44













  • I added the sed line in my cron file after @reboot

    – Aryeh Beitz
    Jan 8 '18 at 16:07



















18














Based on @MiQUEL's answer to this duplicate question:



There are a few approaches.



Incognito mode (--incognito) helps, but it has several disadvantages, such as disabling the cache.



Passing --disable-infobars --disable-session-crashed-bubble works in some versions of Chrome, but, as of Chrome 58, it no longer works. (Removing the --disable-session-crashed-bubble was done as part of this issue; comments there suggest that the flag was intended to test the bubble feature and was not intended as an end-user feature to hide the Chrome warning).



The most reliable approach I've found is to manually edit Chrome's on-disk preferences. Here's how you do this on Linux. (Note that these instructions are for chromium-browser; Google Chrome itself uses ~/.config/google-chrome instead of ~/.config/chromium.)



sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences


Putting it all together with a couple of additional flags that have been helpful for kiosk mode in one Chrome version or another:



#!/bin/sh
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble "http://some_url/"





share|improve this answer
























  • For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

    – mark.sagikazar
    Nov 13 '17 at 14:05



















11














--disable-infobars --disable-session-crashed-bubble



while true; do
chromium-browser --kiosk http://fotolia.com/ --no-first-run --touch-events=enabled --fast --fast-start --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --disable-tab-switcher --disable-translate --enable-low-res-tiling
sleep 10s;
done





share|improve this answer



















  • 1





    Confirmed, this works for me on Chromium 47 on Linux.

    – Sundae
    Dec 9 '15 at 15:42






  • 1





    Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

    – cljk
    Feb 19 '16 at 6:59











  • doesn't work anymore (Chromium 65 on RaspberryPi)

    – david114
    Dec 13 '18 at 9:54



















4














I believe --restore-last-session will also do the job.



Source: http://peter.sh/experiments/chromium-command-line-switches/






share|improve this answer































    4














    This finally worked for me, and it's pretty simple:




    1. Shut down Chromium gracefully

    2. Change the "Change content" permissions of ~/.config/chromium/Default/Preferences to "Nobody"


    That will lock the state of two variables, regardless of how Chromium
    was shut down:




    • "exit_type": "Normal"

    • "exited_cleanly": true


    Of course, only do that after you're done setting preferences






    share|improve this answer





















    • 1





      Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

      – DavidPostill
      Oct 2 '17 at 5:01






    • 1





      Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

      – Justin Force
      Dec 5 '17 at 20:55






    • 2





      This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

      – Scott Dudley
      Jul 11 '18 at 20:23



















    3














    I have been trying to solve this problem for days. Incognito mode comes without cache, and changing Preferences file did not work for me.



    Finally I have been able to solve by following steps below:




    1. Go to chrome://flags url. Search for “Enable session restore bubble UI” and set it to Disabled.

    2. open chrome with --kiosk --disable-infobars options.






    share|improve this answer


























    • Looks like that flag no longer exists

      – AJ Richardson
      Feb 23 '18 at 18:12



















    0














    --restore-last-session argument when launching Chrome.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      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
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f237608%2fhow-to-hide-chrome-warning-after-crash%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









      16














      You should run Chrome in Incognito Mode with this command:



      chrome --incognito --kiosk http://127.0.0.1


      Here they talk about running this command before starting Chrome to stop the Restore Bar from appearing:



      sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' 
      ~/.config/google-chrome/Default/Preferences





      share|improve this answer
























      • incognito does the trick for me.

        – Olivier
        Jan 27 '11 at 15:40






      • 7





        Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

        – Davide Andrea
        Oct 1 '17 at 23:44













      • I added the sed line in my cron file after @reboot

        – Aryeh Beitz
        Jan 8 '18 at 16:07
















      16














      You should run Chrome in Incognito Mode with this command:



      chrome --incognito --kiosk http://127.0.0.1


      Here they talk about running this command before starting Chrome to stop the Restore Bar from appearing:



      sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' 
      ~/.config/google-chrome/Default/Preferences





      share|improve this answer
























      • incognito does the trick for me.

        – Olivier
        Jan 27 '11 at 15:40






      • 7





        Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

        – Davide Andrea
        Oct 1 '17 at 23:44













      • I added the sed line in my cron file after @reboot

        – Aryeh Beitz
        Jan 8 '18 at 16:07














      16












      16








      16







      You should run Chrome in Incognito Mode with this command:



      chrome --incognito --kiosk http://127.0.0.1


      Here they talk about running this command before starting Chrome to stop the Restore Bar from appearing:



      sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' 
      ~/.config/google-chrome/Default/Preferences





      share|improve this answer













      You should run Chrome in Incognito Mode with this command:



      chrome --incognito --kiosk http://127.0.0.1


      Here they talk about running this command before starting Chrome to stop the Restore Bar from appearing:



      sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' 
      ~/.config/google-chrome/Default/Preferences






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jan 26 '11 at 18:41









      jowidojowido

      56634




      56634













      • incognito does the trick for me.

        – Olivier
        Jan 27 '11 at 15:40






      • 7





        Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

        – Davide Andrea
        Oct 1 '17 at 23:44













      • I added the sed line in my cron file after @reboot

        – Aryeh Beitz
        Jan 8 '18 at 16:07



















      • incognito does the trick for me.

        – Olivier
        Jan 27 '11 at 15:40






      • 7





        Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

        – Davide Andrea
        Oct 1 '17 at 23:44













      • I added the sed line in my cron file after @reboot

        – Aryeh Beitz
        Jan 8 '18 at 16:07

















      incognito does the trick for me.

      – Olivier
      Jan 27 '11 at 15:40





      incognito does the trick for me.

      – Olivier
      Jan 27 '11 at 15:40




      7




      7





      Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

      – Davide Andrea
      Oct 1 '17 at 23:44







      Yes, incognito works, but it disables cookies and cache, and (in my case) they are required.

      – Davide Andrea
      Oct 1 '17 at 23:44















      I added the sed line in my cron file after @reboot

      – Aryeh Beitz
      Jan 8 '18 at 16:07





      I added the sed line in my cron file after @reboot

      – Aryeh Beitz
      Jan 8 '18 at 16:07













      18














      Based on @MiQUEL's answer to this duplicate question:



      There are a few approaches.



      Incognito mode (--incognito) helps, but it has several disadvantages, such as disabling the cache.



      Passing --disable-infobars --disable-session-crashed-bubble works in some versions of Chrome, but, as of Chrome 58, it no longer works. (Removing the --disable-session-crashed-bubble was done as part of this issue; comments there suggest that the flag was intended to test the bubble feature and was not intended as an end-user feature to hide the Chrome warning).



      The most reliable approach I've found is to manually edit Chrome's on-disk preferences. Here's how you do this on Linux. (Note that these instructions are for chromium-browser; Google Chrome itself uses ~/.config/google-chrome instead of ~/.config/chromium.)



      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences


      Putting it all together with a couple of additional flags that have been helpful for kiosk mode in one Chrome version or another:



      #!/bin/sh
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
      chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble "http://some_url/"





      share|improve this answer
























      • For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

        – mark.sagikazar
        Nov 13 '17 at 14:05
















      18














      Based on @MiQUEL's answer to this duplicate question:



      There are a few approaches.



      Incognito mode (--incognito) helps, but it has several disadvantages, such as disabling the cache.



      Passing --disable-infobars --disable-session-crashed-bubble works in some versions of Chrome, but, as of Chrome 58, it no longer works. (Removing the --disable-session-crashed-bubble was done as part of this issue; comments there suggest that the flag was intended to test the bubble feature and was not intended as an end-user feature to hide the Chrome warning).



      The most reliable approach I've found is to manually edit Chrome's on-disk preferences. Here's how you do this on Linux. (Note that these instructions are for chromium-browser; Google Chrome itself uses ~/.config/google-chrome instead of ~/.config/chromium.)



      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences


      Putting it all together with a couple of additional flags that have been helpful for kiosk mode in one Chrome version or another:



      #!/bin/sh
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
      chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble "http://some_url/"





      share|improve this answer
























      • For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

        – mark.sagikazar
        Nov 13 '17 at 14:05














      18












      18








      18







      Based on @MiQUEL's answer to this duplicate question:



      There are a few approaches.



      Incognito mode (--incognito) helps, but it has several disadvantages, such as disabling the cache.



      Passing --disable-infobars --disable-session-crashed-bubble works in some versions of Chrome, but, as of Chrome 58, it no longer works. (Removing the --disable-session-crashed-bubble was done as part of this issue; comments there suggest that the flag was intended to test the bubble feature and was not intended as an end-user feature to hide the Chrome warning).



      The most reliable approach I've found is to manually edit Chrome's on-disk preferences. Here's how you do this on Linux. (Note that these instructions are for chromium-browser; Google Chrome itself uses ~/.config/google-chrome instead of ~/.config/chromium.)



      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences


      Putting it all together with a couple of additional flags that have been helpful for kiosk mode in one Chrome version or another:



      #!/bin/sh
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
      chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble "http://some_url/"





      share|improve this answer













      Based on @MiQUEL's answer to this duplicate question:



      There are a few approaches.



      Incognito mode (--incognito) helps, but it has several disadvantages, such as disabling the cache.



      Passing --disable-infobars --disable-session-crashed-bubble works in some versions of Chrome, but, as of Chrome 58, it no longer works. (Removing the --disable-session-crashed-bubble was done as part of this issue; comments there suggest that the flag was intended to test the bubble feature and was not intended as an end-user feature to hide the Chrome warning).



      The most reliable approach I've found is to manually edit Chrome's on-disk preferences. Here's how you do this on Linux. (Note that these instructions are for chromium-browser; Google Chrome itself uses ~/.config/google-chrome instead of ~/.config/chromium.)



      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences


      Putting it all together with a couple of additional flags that have been helpful for kiosk mode in one Chrome version or another:



      #!/bin/sh
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
      sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
      chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble "http://some_url/"






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered May 4 '17 at 20:27









      Josh KelleyJosh Kelley

      1,04711122




      1,04711122













      • For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

        – mark.sagikazar
        Nov 13 '17 at 14:05



















      • For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

        – mark.sagikazar
        Nov 13 '17 at 14:05

















      For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

      – mark.sagikazar
      Nov 13 '17 at 14:05





      For some reasons tilde wasn't resolved for me, I had to use $HOME in I use lxsession autostart.

      – mark.sagikazar
      Nov 13 '17 at 14:05











      11














      --disable-infobars --disable-session-crashed-bubble



      while true; do
      chromium-browser --kiosk http://fotolia.com/ --no-first-run --touch-events=enabled --fast --fast-start --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --disable-tab-switcher --disable-translate --enable-low-res-tiling
      sleep 10s;
      done





      share|improve this answer



















      • 1





        Confirmed, this works for me on Chromium 47 on Linux.

        – Sundae
        Dec 9 '15 at 15:42






      • 1





        Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

        – cljk
        Feb 19 '16 at 6:59











      • doesn't work anymore (Chromium 65 on RaspberryPi)

        – david114
        Dec 13 '18 at 9:54
















      11














      --disable-infobars --disable-session-crashed-bubble



      while true; do
      chromium-browser --kiosk http://fotolia.com/ --no-first-run --touch-events=enabled --fast --fast-start --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --disable-tab-switcher --disable-translate --enable-low-res-tiling
      sleep 10s;
      done





      share|improve this answer



















      • 1





        Confirmed, this works for me on Chromium 47 on Linux.

        – Sundae
        Dec 9 '15 at 15:42






      • 1





        Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

        – cljk
        Feb 19 '16 at 6:59











      • doesn't work anymore (Chromium 65 on RaspberryPi)

        – david114
        Dec 13 '18 at 9:54














      11












      11








      11







      --disable-infobars --disable-session-crashed-bubble



      while true; do
      chromium-browser --kiosk http://fotolia.com/ --no-first-run --touch-events=enabled --fast --fast-start --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --disable-tab-switcher --disable-translate --enable-low-res-tiling
      sleep 10s;
      done





      share|improve this answer













      --disable-infobars --disable-session-crashed-bubble



      while true; do
      chromium-browser --kiosk http://fotolia.com/ --no-first-run --touch-events=enabled --fast --fast-start --disable-popup-blocking --disable-infobars --disable-session-crashed-bubble --disable-tab-switcher --disable-translate --enable-low-res-tiling
      sleep 10s;
      done






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Dec 6 '15 at 2:12









      frekelefrekele

      21124




      21124








      • 1





        Confirmed, this works for me on Chromium 47 on Linux.

        – Sundae
        Dec 9 '15 at 15:42






      • 1





        Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

        – cljk
        Feb 19 '16 at 6:59











      • doesn't work anymore (Chromium 65 on RaspberryPi)

        – david114
        Dec 13 '18 at 9:54














      • 1





        Confirmed, this works for me on Chromium 47 on Linux.

        – Sundae
        Dec 9 '15 at 15:42






      • 1





        Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

        – cljk
        Feb 19 '16 at 6:59











      • doesn't work anymore (Chromium 65 on RaspberryPi)

        – david114
        Dec 13 '18 at 9:54








      1




      1





      Confirmed, this works for me on Chromium 47 on Linux.

      – Sundae
      Dec 9 '15 at 15:42





      Confirmed, this works for me on Chromium 47 on Linux.

      – Sundae
      Dec 9 '15 at 15:42




      1




      1





      Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

      – cljk
      Feb 19 '16 at 6:59





      Did the trick for me. My Chromium ignored the "exited_cleanly" Preferences.

      – cljk
      Feb 19 '16 at 6:59













      doesn't work anymore (Chromium 65 on RaspberryPi)

      – david114
      Dec 13 '18 at 9:54





      doesn't work anymore (Chromium 65 on RaspberryPi)

      – david114
      Dec 13 '18 at 9:54











      4














      I believe --restore-last-session will also do the job.



      Source: http://peter.sh/experiments/chromium-command-line-switches/






      share|improve this answer




























        4














        I believe --restore-last-session will also do the job.



        Source: http://peter.sh/experiments/chromium-command-line-switches/






        share|improve this answer


























          4












          4








          4







          I believe --restore-last-session will also do the job.



          Source: http://peter.sh/experiments/chromium-command-line-switches/






          share|improve this answer













          I believe --restore-last-session will also do the job.



          Source: http://peter.sh/experiments/chromium-command-line-switches/







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 26 '14 at 3:40









          GiliGili

          1,05731326




          1,05731326























              4














              This finally worked for me, and it's pretty simple:




              1. Shut down Chromium gracefully

              2. Change the "Change content" permissions of ~/.config/chromium/Default/Preferences to "Nobody"


              That will lock the state of two variables, regardless of how Chromium
              was shut down:




              • "exit_type": "Normal"

              • "exited_cleanly": true


              Of course, only do that after you're done setting preferences






              share|improve this answer





















              • 1





                Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

                – DavidPostill
                Oct 2 '17 at 5:01






              • 1





                Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

                – Justin Force
                Dec 5 '17 at 20:55






              • 2





                This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

                – Scott Dudley
                Jul 11 '18 at 20:23
















              4














              This finally worked for me, and it's pretty simple:




              1. Shut down Chromium gracefully

              2. Change the "Change content" permissions of ~/.config/chromium/Default/Preferences to "Nobody"


              That will lock the state of two variables, regardless of how Chromium
              was shut down:




              • "exit_type": "Normal"

              • "exited_cleanly": true


              Of course, only do that after you're done setting preferences






              share|improve this answer





















              • 1





                Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

                – DavidPostill
                Oct 2 '17 at 5:01






              • 1





                Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

                – Justin Force
                Dec 5 '17 at 20:55






              • 2





                This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

                – Scott Dudley
                Jul 11 '18 at 20:23














              4












              4








              4







              This finally worked for me, and it's pretty simple:




              1. Shut down Chromium gracefully

              2. Change the "Change content" permissions of ~/.config/chromium/Default/Preferences to "Nobody"


              That will lock the state of two variables, regardless of how Chromium
              was shut down:




              • "exit_type": "Normal"

              • "exited_cleanly": true


              Of course, only do that after you're done setting preferences






              share|improve this answer















              This finally worked for me, and it's pretty simple:




              1. Shut down Chromium gracefully

              2. Change the "Change content" permissions of ~/.config/chromium/Default/Preferences to "Nobody"


              That will lock the state of two variables, regardless of how Chromium
              was shut down:




              • "exit_type": "Normal"

              • "exited_cleanly": true


              Of course, only do that after you're done setting preferences







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Oct 2 '17 at 14:51

























              answered Oct 2 '17 at 0:20









              Davide AndreaDavide Andrea

              1814




              1814








              • 1





                Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

                – DavidPostill
                Oct 2 '17 at 5:01






              • 1





                Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

                – Justin Force
                Dec 5 '17 at 20:55






              • 2





                This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

                – Scott Dudley
                Jul 11 '18 at 20:23














              • 1





                Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

                – DavidPostill
                Oct 2 '17 at 5:01






              • 1





                Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

                – Justin Force
                Dec 5 '17 at 20:55






              • 2





                This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

                – Scott Dudley
                Jul 11 '18 at 20:23








              1




              1





              Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

              – DavidPostill
              Oct 2 '17 at 5:01





              Please do not post the same answer to multiple questions. If the same information really answers both questions, then one question (usually the newer one) should be closed as a duplicate of the other. You can indicate this by voting to close it as a duplicate or, if you don't have enough reputation for that, raise a flag to indicate that it's a duplicate. Otherwise tailor your answer to this question and don't just paste the same answer in multiple places.

              – DavidPostill
              Oct 2 '17 at 5:01




              1




              1





              Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

              – Justin Force
              Dec 5 '17 at 20:55





              Repeated admonishments from moderator aside, unlike every other suggested solution for this problem, this one actually worked for me. So thank you for sharing it.

              – Justin Force
              Dec 5 '17 at 20:55




              2




              2





              This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

              – Scott Dudley
              Jul 11 '18 at 20:23





              This seemed like a great solution at first glance. The main problem is that when using this with WebDriver under Selenium, chromedriver complains (at least on a Windows node) that it can't write to the prefs file at startup, so it won't let you launch a session when the prefs file is read-only.

              – Scott Dudley
              Jul 11 '18 at 20:23











              3














              I have been trying to solve this problem for days. Incognito mode comes without cache, and changing Preferences file did not work for me.



              Finally I have been able to solve by following steps below:




              1. Go to chrome://flags url. Search for “Enable session restore bubble UI” and set it to Disabled.

              2. open chrome with --kiosk --disable-infobars options.






              share|improve this answer


























              • Looks like that flag no longer exists

                – AJ Richardson
                Feb 23 '18 at 18:12
















              3














              I have been trying to solve this problem for days. Incognito mode comes without cache, and changing Preferences file did not work for me.



              Finally I have been able to solve by following steps below:




              1. Go to chrome://flags url. Search for “Enable session restore bubble UI” and set it to Disabled.

              2. open chrome with --kiosk --disable-infobars options.






              share|improve this answer


























              • Looks like that flag no longer exists

                – AJ Richardson
                Feb 23 '18 at 18:12














              3












              3








              3







              I have been trying to solve this problem for days. Incognito mode comes without cache, and changing Preferences file did not work for me.



              Finally I have been able to solve by following steps below:




              1. Go to chrome://flags url. Search for “Enable session restore bubble UI” and set it to Disabled.

              2. open chrome with --kiosk --disable-infobars options.






              share|improve this answer















              I have been trying to solve this problem for days. Incognito mode comes without cache, and changing Preferences file did not work for me.



              Finally I have been able to solve by following steps below:




              1. Go to chrome://flags url. Search for “Enable session restore bubble UI” and set it to Disabled.

              2. open chrome with --kiosk --disable-infobars options.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Aug 4 '16 at 10:40









              Community

              1




              1










              answered Dec 15 '15 at 11:24









              yjcxy12yjcxy12

              1311




              1311













              • Looks like that flag no longer exists

                – AJ Richardson
                Feb 23 '18 at 18:12



















              • Looks like that flag no longer exists

                – AJ Richardson
                Feb 23 '18 at 18:12

















              Looks like that flag no longer exists

              – AJ Richardson
              Feb 23 '18 at 18:12





              Looks like that flag no longer exists

              – AJ Richardson
              Feb 23 '18 at 18:12











              0














              --restore-last-session argument when launching Chrome.






              share|improve this answer




























                0














                --restore-last-session argument when launching Chrome.






                share|improve this answer


























                  0












                  0








                  0







                  --restore-last-session argument when launching Chrome.






                  share|improve this answer













                  --restore-last-session argument when launching Chrome.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 7 at 18:39









                  MattMatt

                  13319




                  13319






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • 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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f237608%2fhow-to-hide-chrome-warning-after-crash%23new-answer', 'question_page');
                      }
                      );

                      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







                      Popular posts from this blog

                      How to make a Squid Proxy server?

                      Is this a new Fibonacci Identity?

                      Touch on Surface Book