How to get rid of errors while launching browser from terminal?
up vote
1
down vote
favorite
I have been facing problems to run the browser from the terminal. If I launch Firefox it shows below:
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:34:
Expected ')' in color definition
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:77:
Expected
')' in color definition
Then I tried to launch chromium -browser the errors are more:
[1:1:1015/225808.162350:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.257010:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.289346:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.312381:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
Is there any way to resolve these issue? Please help me out. Because of my software I have to launch the browser from the terminal.
16.04 bash firefox chromium
asked Oct 15 at 21:00
zesan
91
add a comment |
up vote
1
down vote
favorite
I have been facing problems to run the browser from the terminal. If I launch Firefox it shows below:
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:34:
Expected ')' in color definition
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:77:
Expected
')' in color definition
Then I tried to launch chromium -browser the errors are more:
[1:1:1015/225808.162350:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.257010:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.289346:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.312381:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
Is there any way to resolve these issue? Please help me out. Because of my software I have to launch the browser from the terminal.
16.04 bash firefox chromium
asked Oct 15 at 21:00
zesan
91
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have been facing problems to run the browser from the terminal. If I launch Firefox it shows below:
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:34:
Expected ')' in color definition
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:77:
Expected
')' in color definition
Then I tried to launch chromium -browser the errors are more:
[1:1:1015/225808.162350:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.257010:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.289346:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.312381:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
Is there any way to resolve these issue? Please help me out. Because of my software I have to launch the browser from the terminal.
16.04 bash firefox chromium
asked Oct 15 at 21:00
zesan
91
I have been facing problems to run the browser from the terminal. If I launch Firefox it shows below:
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:34:
Expected ')' in color definition
(firefox:12544): Gtk-WARNING **: Theme parsing error: :1:77:
Expected
')' in color definition
Then I tried to launch chromium -browser the errors are more:
[1:1:1015/225808.162350:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.257010:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.289346:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[1:1:1015/225809.312381:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
Is there any way to resolve these issue? Please help me out. Because of my software I have to launch the browser from the terminal.
16.04 bash firefox chromium
16.04 bash firefox chromium
asked Oct 15 at 21:00
zesan
91
asked Oct 15 at 21:00
zesan
91
asked Oct 15 at 21:00
zesan
91
asked Oct 15 at 21:00
zesan
91
asked Oct 15 at 21:00
zesan
91
91
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
If it’s just the output that’s bothering you, you can send it into a dark oblivion by adding
&>/dev/null
to the command line. Note that this will swallow all output, use 2>/dev/null instead to redirect error messages only.
answered Oct 15 at 21:07
dessert
21.3k55896
add a comment |
up vote
0
down vote
Basically there is no need to do that. All that errors you see is merely diagnostic messages sent by browser to stderr output. Obviously seeing whose messages is intended more for developers, since its not "common" way to launch browser nowadays and those messages barely useful at all.
You can redirect output to /dev/null by launching browser this way
firefox > /dev/null
but i dont bother to do that, since sometimes those output can help especially in case of shutdown-hangs or crashes. Interestingly enough those output once helped me to understand why watching long Youtube videos often failed me - its turned out my /tmp was too small and it was clearly stated in console output.
answered Nov 25 at 18:02
Kuribo Kutsu
1819
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
If it’s just the output that’s bothering you, you can send it into a dark oblivion by adding
&>/dev/null
to the command line. Note that this will swallow all output, use 2>/dev/null instead to redirect error messages only.
answered Oct 15 at 21:07
dessert
21.3k55896
add a comment |
up vote
2
down vote
If it’s just the output that’s bothering you, you can send it into a dark oblivion by adding
&>/dev/null
to the command line. Note that this will swallow all output, use 2>/dev/null instead to redirect error messages only.
answered Oct 15 at 21:07
dessert
21.3k55896
add a comment |
up vote
2
down vote
up vote
2
down vote
If it’s just the output that’s bothering you, you can send it into a dark oblivion by adding
&>/dev/null
to the command line. Note that this will swallow all output, use 2>/dev/null instead to redirect error messages only.
answered Oct 15 at 21:07
dessert
21.3k55896
If it’s just the output that’s bothering you, you can send it into a dark oblivion by adding
&>/dev/null
to the command line. Note that this will swallow all output, use 2>/dev/null instead to redirect error messages only.
answered Oct 15 at 21:07
dessert
21.3k55896
answered Oct 15 at 21:07
dessert
21.3k55896
answered Oct 15 at 21:07
dessert
21.3k55896
answered Oct 15 at 21:07
dessert
21.3k55896
21.3k55896
add a comment |
add a comment |
up vote
0
down vote
Basically there is no need to do that. All that errors you see is merely diagnostic messages sent by browser to stderr output. Obviously seeing whose messages is intended more for developers, since its not "common" way to launch browser nowadays and those messages barely useful at all.
You can redirect output to /dev/null by launching browser this way
firefox > /dev/null
but i dont bother to do that, since sometimes those output can help especially in case of shutdown-hangs or crashes. Interestingly enough those output once helped me to understand why watching long Youtube videos often failed me - its turned out my /tmp was too small and it was clearly stated in console output.
answered Nov 25 at 18:02
Kuribo Kutsu
1819
add a comment |
up vote
0
down vote
Basically there is no need to do that. All that errors you see is merely diagnostic messages sent by browser to stderr output. Obviously seeing whose messages is intended more for developers, since its not "common" way to launch browser nowadays and those messages barely useful at all.
You can redirect output to /dev/null by launching browser this way
firefox > /dev/null
but i dont bother to do that, since sometimes those output can help especially in case of shutdown-hangs or crashes. Interestingly enough those output once helped me to understand why watching long Youtube videos often failed me - its turned out my /tmp was too small and it was clearly stated in console output.
answered Nov 25 at 18:02
Kuribo Kutsu
1819
add a comment |
up vote
0
down vote
up vote
0
down vote
Basically there is no need to do that. All that errors you see is merely diagnostic messages sent by browser to stderr output. Obviously seeing whose messages is intended more for developers, since its not "common" way to launch browser nowadays and those messages barely useful at all.
You can redirect output to /dev/null by launching browser this way
firefox > /dev/null
but i dont bother to do that, since sometimes those output can help especially in case of shutdown-hangs or crashes. Interestingly enough those output once helped me to understand why watching long Youtube videos often failed me - its turned out my /tmp was too small and it was clearly stated in console output.
answered Nov 25 at 18:02
Kuribo Kutsu
1819
Basically there is no need to do that. All that errors you see is merely diagnostic messages sent by browser to stderr output. Obviously seeing whose messages is intended more for developers, since its not "common" way to launch browser nowadays and those messages barely useful at all.
You can redirect output to /dev/null by launching browser this way
firefox > /dev/null
but i dont bother to do that, since sometimes those output can help especially in case of shutdown-hangs or crashes. Interestingly enough those output once helped me to understand why watching long Youtube videos often failed me - its turned out my /tmp was too small and it was clearly stated in console output.
answered Nov 25 at 18:02
Kuribo Kutsu
1819
answered Nov 25 at 18:02
Kuribo Kutsu
1819
answered Nov 25 at 18:02
Kuribo Kutsu
1819
answered Nov 25 at 18:02
Kuribo Kutsu
1819
1819
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%2f1084052%2fhow-to-get-rid-of-errors-while-launching-browser-from-terminal%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
