The Computer Oracle

How can I disable the "Chromium didn’t shut down correctly" message when my browser opens?

--------------------------------------------------
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------

Music by Eric Matyas
https://www.soundimage.org
Track title: Melt

--

Chapters
00:00 How Can I Disable The &Quot;Chromium Didn’T Shut Down Correctly&Quot; Message When My Browser Opens?
00:46 Accepted Answer Score 24
01:09 Answer 2 Score 3
01:30 Answer 3 Score 16
01:52 Answer 4 Score 5
02:19 Thank you

--

Full question
https://superuser.com/questions/873381/h...

--

Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...

--

Tags
#linux #browser #shutdown #chromium

#avk47



ACCEPTED ANSWER

Score 24


Much easier solution, start Chromium with the --disable-infobars flag. I tried all of the above before finding it, and it does exactly what I wanted. You can leave all of the other stuff alone.

My specific command line is:

/usr/bin/chromium-browser --start-fullscreen --disable-session-crashed-bubble --disable-infobars http://www.example.com



ANSWER 2

Score 16


Also, apparently running in incognito mode by default will also prevent the error because nothing is saved from the session against which to check for a crash.

example: chromium-browser --kiosk --start-maximized --incognito kiosk.html




ANSWER 3

Score 5


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




ANSWER 4

Score 3


Solution/Hack in 5 seconds (https://askubuntu.com/a/720855) Settings->Advanced Settings->System-> uncheck Continue running background apps when Chrome is closed

(read the whole thread for hints on why the issue happens. Makes a lot of sense)