xdg-open still prints noise from programs
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
After using xdg-open
to open, for example, a .odp file, I will still get background noise printed to the console from the program like the following:
** (soffice:20731): WARNING **: Unknown event notification 38
** (soffice:20731): WARNING **: Invalidate all children called
I know that this is all background noise stuff that can be ignored, but it's really annoying when it prints in the middle of me typing commands half an hour later. Is there anything I can do so that this doesn't get printed?
xdg-open
New contributor
add a comment |
up vote
0
down vote
favorite
After using xdg-open
to open, for example, a .odp file, I will still get background noise printed to the console from the program like the following:
** (soffice:20731): WARNING **: Unknown event notification 38
** (soffice:20731): WARNING **: Invalidate all children called
I know that this is all background noise stuff that can be ignored, but it's really annoying when it prints in the middle of me typing commands half an hour later. Is there anything I can do so that this doesn't get printed?
xdg-open
New contributor
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After using xdg-open
to open, for example, a .odp file, I will still get background noise printed to the console from the program like the following:
** (soffice:20731): WARNING **: Unknown event notification 38
** (soffice:20731): WARNING **: Invalidate all children called
I know that this is all background noise stuff that can be ignored, but it's really annoying when it prints in the middle of me typing commands half an hour later. Is there anything I can do so that this doesn't get printed?
xdg-open
New contributor
After using xdg-open
to open, for example, a .odp file, I will still get background noise printed to the console from the program like the following:
** (soffice:20731): WARNING **: Unknown event notification 38
** (soffice:20731): WARNING **: Invalidate all children called
I know that this is all background noise stuff that can be ignored, but it's really annoying when it prints in the middle of me typing commands half an hour later. Is there anything I can do so that this doesn't get printed?
xdg-open
xdg-open
New contributor
New contributor
New contributor
asked yesterday
rtpax
1011
1011
New contributor
New contributor
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday
add a comment |
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
rtpax is a new contributor. Be nice, and check out our Code of Conduct.
rtpax is a new contributor. Be nice, and check out our Code of Conduct.
rtpax is a new contributor. Be nice, and check out our Code of Conduct.
rtpax is a new contributor. Be nice, and check out our Code of Conduct.
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481545%2fxdg-open-still-prints-noise-from-programs%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Those lines were printed by soffice, not xdg-open.
– Ipor Sircer
yesterday
@IporSircer I'm aware, but xdg-open is relevant because after calling with xdg-open I can resume work as normally and soffice is not running in the foreground or background after
– rtpax
yesterday