Chromium will not start,
I did an ubuntu upgrade this morning and when I reboot the machine, chromium-browser will not run. I purged it with sudo apt-get purge chromium-browser and reinstalled it with sudo apt-get install chromium-browser.
When I try to run it from a terminal I get a message like:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[22032:22032:1214/132224.411454:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
The command hangs and I have to ctrl-c to get the shell back.
No chromium processes are running when it is done.
If while the command is hung I get and I check for processes I see 5
1) --enable-pinc
2) --type=zygote
1) --type=gpu-process -- field-trial-handle=somelongnumber --gpu-preference=KAA...
1) --type=-broker
Does anyone have any suggestions?
Edit:
I decided on a whim to run sudo chromium-browser, got an error message about not using the option --no-sandbox. I ran with sudo chromium-browser --no-sandbox and it seemed to work, I got a dialog that said "Profile error occured" Your preferences could not be read?
I then pinned the browser to the Launcher and it runs without sudo but I always get the "Profile error occured " dialog. It won't save preferences, and some features are unavailable.
chromium
asked Dec 14 at 21:33
Nefarious
33
add a comment |
I did an ubuntu upgrade this morning and when I reboot the machine, chromium-browser will not run. I purged it with sudo apt-get purge chromium-browser and reinstalled it with sudo apt-get install chromium-browser.
When I try to run it from a terminal I get a message like:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[22032:22032:1214/132224.411454:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
The command hangs and I have to ctrl-c to get the shell back.
No chromium processes are running when it is done.
If while the command is hung I get and I check for processes I see 5
1) --enable-pinc
2) --type=zygote
1) --type=gpu-process -- field-trial-handle=somelongnumber --gpu-preference=KAA...
1) --type=-broker
Does anyone have any suggestions?
Edit:
I decided on a whim to run sudo chromium-browser, got an error message about not using the option --no-sandbox. I ran with sudo chromium-browser --no-sandbox and it seemed to work, I got a dialog that said "Profile error occured" Your preferences could not be read?
I then pinned the browser to the Launcher and it runs without sudo but I always get the "Profile error occured " dialog. It won't save preferences, and some features are unavailable.
chromium
asked Dec 14 at 21:33
Nefarious
33
add a comment |
I did an ubuntu upgrade this morning and when I reboot the machine, chromium-browser will not run. I purged it with sudo apt-get purge chromium-browser and reinstalled it with sudo apt-get install chromium-browser.
When I try to run it from a terminal I get a message like:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[22032:22032:1214/132224.411454:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
The command hangs and I have to ctrl-c to get the shell back.
No chromium processes are running when it is done.
If while the command is hung I get and I check for processes I see 5
1) --enable-pinc
2) --type=zygote
1) --type=gpu-process -- field-trial-handle=somelongnumber --gpu-preference=KAA...
1) --type=-broker
Does anyone have any suggestions?
Edit:
I decided on a whim to run sudo chromium-browser, got an error message about not using the option --no-sandbox. I ran with sudo chromium-browser --no-sandbox and it seemed to work, I got a dialog that said "Profile error occured" Your preferences could not be read?
I then pinned the browser to the Launcher and it runs without sudo but I always get the "Profile error occured " dialog. It won't save preferences, and some features are unavailable.
chromium
asked Dec 14 at 21:33
Nefarious
33
I did an ubuntu upgrade this morning and when I reboot the machine, chromium-browser will not run. I purged it with sudo apt-get purge chromium-browser and reinstalled it with sudo apt-get install chromium-browser.
When I try to run it from a terminal I get a message like:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[22032:22032:1214/132224.411454:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
The command hangs and I have to ctrl-c to get the shell back.
No chromium processes are running when it is done.
If while the command is hung I get and I check for processes I see 5
1) --enable-pinc
2) --type=zygote
1) --type=gpu-process -- field-trial-handle=somelongnumber --gpu-preference=KAA...
1) --type=-broker
Does anyone have any suggestions?
Edit:
I decided on a whim to run sudo chromium-browser, got an error message about not using the option --no-sandbox. I ran with sudo chromium-browser --no-sandbox and it seemed to work, I got a dialog that said "Profile error occured" Your preferences could not be read?
I then pinned the browser to the Launcher and it runs without sudo but I always get the "Profile error occured " dialog. It won't save preferences, and some features are unavailable.
chromium
chromium
asked Dec 14 at 21:33
Nefarious
33
asked Dec 14 at 21:33
Nefarious
33
edited Dec 14 at 21:59
asked Dec 14 at 21:33
Nefarious
33
asked Dec 14 at 21:33
Nefarious
33
asked Dec 14 at 21:33
Nefarious
33
33
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Try this
I also found the 14.04 build of (at this point, chromium 53) worked
fine after I set "--disable-namespace-sandbox"... I had the "Aw,
snap!" but found (per google) that "--disable-namespace-sandbox" fixed
it without the ill effects of "--no-sandbox".
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f1100968%2fchromium-will-not-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try this
I also found the 14.04 build of (at this point, chromium 53) worked
fine after I set "--disable-namespace-sandbox"... I had the "Aw,
snap!" but found (per google) that "--disable-namespace-sandbox" fixed
it without the ill effects of "--no-sandbox".
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Try this
I also found the 14.04 build of (at this point, chromium 53) worked
fine after I set "--disable-namespace-sandbox"... I had the "Aw,
snap!" but found (per google) that "--disable-namespace-sandbox" fixed
it without the ill effects of "--no-sandbox".
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Try this
I also found the 14.04 build of (at this point, chromium 53) worked
fine after I set "--disable-namespace-sandbox"... I had the "Aw,
snap!" but found (per google) that "--disable-namespace-sandbox" fixed
it without the ill effects of "--no-sandbox".
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Try this
I also found the 14.04 build of (at this point, chromium 53) worked
fine after I set "--disable-namespace-sandbox"... I had the "Aw,
snap!" but found (per google) that "--disable-namespace-sandbox" fixed
it without the ill effects of "--no-sandbox".
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 19 hours ago
Olegus Testerovichus
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 19 hours ago
Olegus Testerovichus
11
answered 19 hours ago
Olegus Testerovichus
11
11
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Olegus Testerovichus is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1100968%2fchromium-will-not-start%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
