gnome-terminal --disable-factory support problem
$ gnome-terminal --tab --title="700" --disable-factory -e
Failed to parse arguments: Option "--disable-factory" is no longer supported in this version of gnome-terminal.
I am using GNOME 3.
14.04 command-line gnome gnome-terminal
add a comment |
$ gnome-terminal --tab --title="700" --disable-factory -e
Failed to parse arguments: Option "--disable-factory" is no longer supported in this version of gnome-terminal.
I am using GNOME 3.
14.04 command-line gnome gnome-terminal
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52
add a comment |
$ gnome-terminal --tab --title="700" --disable-factory -e
Failed to parse arguments: Option "--disable-factory" is no longer supported in this version of gnome-terminal.
I am using GNOME 3.
14.04 command-line gnome gnome-terminal
$ gnome-terminal --tab --title="700" --disable-factory -e
Failed to parse arguments: Option "--disable-factory" is no longer supported in this version of gnome-terminal.
I am using GNOME 3.
14.04 command-line gnome gnome-terminal
14.04 command-line gnome gnome-terminal
edited 1 hour ago
ubashu
2,37821837
2,37821837
asked Feb 3 '16 at 3:51
Ahmed Zain El DeinAhmed Zain El Dein
3211918
3211918
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52
add a comment |
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52
add a comment |
2 Answers
2
active
oldest
votes
If you really need multiple instances of gnome-terminal process running (but why should you?), follow the steps at https://wiki.gnome.org/Apps/Terminal/Debugging except for the gdb part.
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
add a comment |
For the benefit of the reader.
The problem
Option --disable-factory
got removed in V3.8 of gnome-terminal
and there is no way to archive this behavior the easy way. At least not a way, which can be explained to people, who are not fluent in shell syntax.
Hence the command line
gnome-terminal --tab --title="700" --disable-factory -e ...
fails with the error presented in the question.
Please excuse this very personal side note: I really do not understand, why this crucial option got removed. Even Microsoft introduced an option to run
cmd
,explorer
orpowershell
the blocking way. Microsoft listens to their users. But Gnome does not. Instead of officially documenting the hidden option--disable-factory
, Gnome suddenly removed it. If they continue this course, they will make Microsoft win on the long term. That is very very sad and extraordinary stupid. (Sorry for this rant, but it has to be be said.)
BTW: Ubuntu 16.04 restored --disable-factory
using a wrapper which emulates this feature. (If you look at the complexity of this wrapper, my rant still applies even more than before.)
Variant 0
I call this 0
, because both are not really proper solutions. A proper solution is shown in Variant 1.
Varriant 0a
A first thing, you can try, is to remove option --disable-server
:
gnome-terminal --tab --title="700" -e ...
However this has following drawback:
This does no more wait until gnome-terminal
finishes. If there is another gnome-terminal
running, the command immediately comes back. Usually this is not what you want, because this is, why option --disable-factory
was present in the first place.
Variant 0b
So removing this option is only feasible in the case, where you can make sure, that in all and every case, no other gnome-terminal
is running, ever.
If this is not the case, but you are in a case, where another running gnome-terminal
must not be supported, you can try following desparate fallback variant:
killall -9 gnome-terminal
gnome-terminal --tab --title="700" -e ...
But beware! This unconditionally kills all gnome-terminal
s which are still open. In a production environment this usually will cause greater harm then it helps. You have been warned!
Variant 1
If you do not need to run it in gnome-terminal
and can run it in some other terminal emulator. @muru commented a good replacement.
xfce4-terminal
understands nearly the same set of options as gnome-terminal
(and adds some very handy other options which are missing in gnome-terminal
for years). It also has a documented option, which does, what --disable-factory
did for gnome-terminal
. The option --tab
works differently to gnome-terminal
and thus must be removed, too, to get something working. The replacement is:
xfce4-terminal --title="700" --disable-server -e ...
Also you can add a --hold
option, if you want to be able to see the full output of the command before the window is closed:
xfce4-terminal --hold --title="700" --disable-server -e ...
Please note that xfce4-terminal
has a little race-condition, which unfortunately truncates the output, so --hold
is not fully effective. Fixing this properly (such that you can use it copy'n'paste) is beyond the scope of the answer, however usually adding a little echo $? && read -t.1
to the script which is executed with (behind) -e
can solve it 99% of the time.
In case you get the message, that xfce4-terminal
is missing, then you have to install it first. It can be installed in parallel to gnome
, even that it belongs to another desktop variant (Xfce):
sudo apt-get install xfce4-terminal
The only drawback is, that xfce4-terminal
has another look than gnome-terminal
, and follows some other
Variant 2..∞
There are endless other possible variants to fix that issue. Most of them are really complicated. Too complicated for normal people, those, who are not really into shells.
So I leave them away. My recommendation is:
As noted by @muru, try to use xfce4-terminal
instead of gnome-terminal
.
Note to those, who grok shells
All simple solutions are not really perfect, as they do not return the command's return value (gnome-terminal
does not, too). Sadly. To fix that this is a completely different story.
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%2f729034%2fgnome-terminal-disable-factory-support-problem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you really need multiple instances of gnome-terminal process running (but why should you?), follow the steps at https://wiki.gnome.org/Apps/Terminal/Debugging except for the gdb part.
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
add a comment |
If you really need multiple instances of gnome-terminal process running (but why should you?), follow the steps at https://wiki.gnome.org/Apps/Terminal/Debugging except for the gdb part.
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
add a comment |
If you really need multiple instances of gnome-terminal process running (but why should you?), follow the steps at https://wiki.gnome.org/Apps/Terminal/Debugging except for the gdb part.
If you really need multiple instances of gnome-terminal process running (but why should you?), follow the steps at https://wiki.gnome.org/Apps/Terminal/Debugging except for the gdb part.
answered Feb 3 '16 at 7:58
egmontegmont
3,86611024
3,86611024
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
add a comment |
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
i can't understand what will i replace the sentence gnome-terminal --tab --title="700" --disable-factory with , will i write instead of it gnome-terminal-server --app-id my.foo.Terminal?
– Ahmed Zain El Dein
Feb 3 '16 at 15:07
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
Here's my reason for running separate gnome-terminal processes - I don't limit myself to a single X screen in my X desktop. I have multiple independent X screens. gnome-terminal, apart from the helpful gdb hack you link, is no longer able to have a terminal on more than one screen at a time.
– Troy Folger
Jun 25 '18 at 22:43
add a comment |
For the benefit of the reader.
The problem
Option --disable-factory
got removed in V3.8 of gnome-terminal
and there is no way to archive this behavior the easy way. At least not a way, which can be explained to people, who are not fluent in shell syntax.
Hence the command line
gnome-terminal --tab --title="700" --disable-factory -e ...
fails with the error presented in the question.
Please excuse this very personal side note: I really do not understand, why this crucial option got removed. Even Microsoft introduced an option to run
cmd
,explorer
orpowershell
the blocking way. Microsoft listens to their users. But Gnome does not. Instead of officially documenting the hidden option--disable-factory
, Gnome suddenly removed it. If they continue this course, they will make Microsoft win on the long term. That is very very sad and extraordinary stupid. (Sorry for this rant, but it has to be be said.)
BTW: Ubuntu 16.04 restored --disable-factory
using a wrapper which emulates this feature. (If you look at the complexity of this wrapper, my rant still applies even more than before.)
Variant 0
I call this 0
, because both are not really proper solutions. A proper solution is shown in Variant 1.
Varriant 0a
A first thing, you can try, is to remove option --disable-server
:
gnome-terminal --tab --title="700" -e ...
However this has following drawback:
This does no more wait until gnome-terminal
finishes. If there is another gnome-terminal
running, the command immediately comes back. Usually this is not what you want, because this is, why option --disable-factory
was present in the first place.
Variant 0b
So removing this option is only feasible in the case, where you can make sure, that in all and every case, no other gnome-terminal
is running, ever.
If this is not the case, but you are in a case, where another running gnome-terminal
must not be supported, you can try following desparate fallback variant:
killall -9 gnome-terminal
gnome-terminal --tab --title="700" -e ...
But beware! This unconditionally kills all gnome-terminal
s which are still open. In a production environment this usually will cause greater harm then it helps. You have been warned!
Variant 1
If you do not need to run it in gnome-terminal
and can run it in some other terminal emulator. @muru commented a good replacement.
xfce4-terminal
understands nearly the same set of options as gnome-terminal
(and adds some very handy other options which are missing in gnome-terminal
for years). It also has a documented option, which does, what --disable-factory
did for gnome-terminal
. The option --tab
works differently to gnome-terminal
and thus must be removed, too, to get something working. The replacement is:
xfce4-terminal --title="700" --disable-server -e ...
Also you can add a --hold
option, if you want to be able to see the full output of the command before the window is closed:
xfce4-terminal --hold --title="700" --disable-server -e ...
Please note that xfce4-terminal
has a little race-condition, which unfortunately truncates the output, so --hold
is not fully effective. Fixing this properly (such that you can use it copy'n'paste) is beyond the scope of the answer, however usually adding a little echo $? && read -t.1
to the script which is executed with (behind) -e
can solve it 99% of the time.
In case you get the message, that xfce4-terminal
is missing, then you have to install it first. It can be installed in parallel to gnome
, even that it belongs to another desktop variant (Xfce):
sudo apt-get install xfce4-terminal
The only drawback is, that xfce4-terminal
has another look than gnome-terminal
, and follows some other
Variant 2..∞
There are endless other possible variants to fix that issue. Most of them are really complicated. Too complicated for normal people, those, who are not really into shells.
So I leave them away. My recommendation is:
As noted by @muru, try to use xfce4-terminal
instead of gnome-terminal
.
Note to those, who grok shells
All simple solutions are not really perfect, as they do not return the command's return value (gnome-terminal
does not, too). Sadly. To fix that this is a completely different story.
add a comment |
For the benefit of the reader.
The problem
Option --disable-factory
got removed in V3.8 of gnome-terminal
and there is no way to archive this behavior the easy way. At least not a way, which can be explained to people, who are not fluent in shell syntax.
Hence the command line
gnome-terminal --tab --title="700" --disable-factory -e ...
fails with the error presented in the question.
Please excuse this very personal side note: I really do not understand, why this crucial option got removed. Even Microsoft introduced an option to run
cmd
,explorer
orpowershell
the blocking way. Microsoft listens to their users. But Gnome does not. Instead of officially documenting the hidden option--disable-factory
, Gnome suddenly removed it. If they continue this course, they will make Microsoft win on the long term. That is very very sad and extraordinary stupid. (Sorry for this rant, but it has to be be said.)
BTW: Ubuntu 16.04 restored --disable-factory
using a wrapper which emulates this feature. (If you look at the complexity of this wrapper, my rant still applies even more than before.)
Variant 0
I call this 0
, because both are not really proper solutions. A proper solution is shown in Variant 1.
Varriant 0a
A first thing, you can try, is to remove option --disable-server
:
gnome-terminal --tab --title="700" -e ...
However this has following drawback:
This does no more wait until gnome-terminal
finishes. If there is another gnome-terminal
running, the command immediately comes back. Usually this is not what you want, because this is, why option --disable-factory
was present in the first place.
Variant 0b
So removing this option is only feasible in the case, where you can make sure, that in all and every case, no other gnome-terminal
is running, ever.
If this is not the case, but you are in a case, where another running gnome-terminal
must not be supported, you can try following desparate fallback variant:
killall -9 gnome-terminal
gnome-terminal --tab --title="700" -e ...
But beware! This unconditionally kills all gnome-terminal
s which are still open. In a production environment this usually will cause greater harm then it helps. You have been warned!
Variant 1
If you do not need to run it in gnome-terminal
and can run it in some other terminal emulator. @muru commented a good replacement.
xfce4-terminal
understands nearly the same set of options as gnome-terminal
(and adds some very handy other options which are missing in gnome-terminal
for years). It also has a documented option, which does, what --disable-factory
did for gnome-terminal
. The option --tab
works differently to gnome-terminal
and thus must be removed, too, to get something working. The replacement is:
xfce4-terminal --title="700" --disable-server -e ...
Also you can add a --hold
option, if you want to be able to see the full output of the command before the window is closed:
xfce4-terminal --hold --title="700" --disable-server -e ...
Please note that xfce4-terminal
has a little race-condition, which unfortunately truncates the output, so --hold
is not fully effective. Fixing this properly (such that you can use it copy'n'paste) is beyond the scope of the answer, however usually adding a little echo $? && read -t.1
to the script which is executed with (behind) -e
can solve it 99% of the time.
In case you get the message, that xfce4-terminal
is missing, then you have to install it first. It can be installed in parallel to gnome
, even that it belongs to another desktop variant (Xfce):
sudo apt-get install xfce4-terminal
The only drawback is, that xfce4-terminal
has another look than gnome-terminal
, and follows some other
Variant 2..∞
There are endless other possible variants to fix that issue. Most of them are really complicated. Too complicated for normal people, those, who are not really into shells.
So I leave them away. My recommendation is:
As noted by @muru, try to use xfce4-terminal
instead of gnome-terminal
.
Note to those, who grok shells
All simple solutions are not really perfect, as they do not return the command's return value (gnome-terminal
does not, too). Sadly. To fix that this is a completely different story.
add a comment |
For the benefit of the reader.
The problem
Option --disable-factory
got removed in V3.8 of gnome-terminal
and there is no way to archive this behavior the easy way. At least not a way, which can be explained to people, who are not fluent in shell syntax.
Hence the command line
gnome-terminal --tab --title="700" --disable-factory -e ...
fails with the error presented in the question.
Please excuse this very personal side note: I really do not understand, why this crucial option got removed. Even Microsoft introduced an option to run
cmd
,explorer
orpowershell
the blocking way. Microsoft listens to their users. But Gnome does not. Instead of officially documenting the hidden option--disable-factory
, Gnome suddenly removed it. If they continue this course, they will make Microsoft win on the long term. That is very very sad and extraordinary stupid. (Sorry for this rant, but it has to be be said.)
BTW: Ubuntu 16.04 restored --disable-factory
using a wrapper which emulates this feature. (If you look at the complexity of this wrapper, my rant still applies even more than before.)
Variant 0
I call this 0
, because both are not really proper solutions. A proper solution is shown in Variant 1.
Varriant 0a
A first thing, you can try, is to remove option --disable-server
:
gnome-terminal --tab --title="700" -e ...
However this has following drawback:
This does no more wait until gnome-terminal
finishes. If there is another gnome-terminal
running, the command immediately comes back. Usually this is not what you want, because this is, why option --disable-factory
was present in the first place.
Variant 0b
So removing this option is only feasible in the case, where you can make sure, that in all and every case, no other gnome-terminal
is running, ever.
If this is not the case, but you are in a case, where another running gnome-terminal
must not be supported, you can try following desparate fallback variant:
killall -9 gnome-terminal
gnome-terminal --tab --title="700" -e ...
But beware! This unconditionally kills all gnome-terminal
s which are still open. In a production environment this usually will cause greater harm then it helps. You have been warned!
Variant 1
If you do not need to run it in gnome-terminal
and can run it in some other terminal emulator. @muru commented a good replacement.
xfce4-terminal
understands nearly the same set of options as gnome-terminal
(and adds some very handy other options which are missing in gnome-terminal
for years). It also has a documented option, which does, what --disable-factory
did for gnome-terminal
. The option --tab
works differently to gnome-terminal
and thus must be removed, too, to get something working. The replacement is:
xfce4-terminal --title="700" --disable-server -e ...
Also you can add a --hold
option, if you want to be able to see the full output of the command before the window is closed:
xfce4-terminal --hold --title="700" --disable-server -e ...
Please note that xfce4-terminal
has a little race-condition, which unfortunately truncates the output, so --hold
is not fully effective. Fixing this properly (such that you can use it copy'n'paste) is beyond the scope of the answer, however usually adding a little echo $? && read -t.1
to the script which is executed with (behind) -e
can solve it 99% of the time.
In case you get the message, that xfce4-terminal
is missing, then you have to install it first. It can be installed in parallel to gnome
, even that it belongs to another desktop variant (Xfce):
sudo apt-get install xfce4-terminal
The only drawback is, that xfce4-terminal
has another look than gnome-terminal
, and follows some other
Variant 2..∞
There are endless other possible variants to fix that issue. Most of them are really complicated. Too complicated for normal people, those, who are not really into shells.
So I leave them away. My recommendation is:
As noted by @muru, try to use xfce4-terminal
instead of gnome-terminal
.
Note to those, who grok shells
All simple solutions are not really perfect, as they do not return the command's return value (gnome-terminal
does not, too). Sadly. To fix that this is a completely different story.
For the benefit of the reader.
The problem
Option --disable-factory
got removed in V3.8 of gnome-terminal
and there is no way to archive this behavior the easy way. At least not a way, which can be explained to people, who are not fluent in shell syntax.
Hence the command line
gnome-terminal --tab --title="700" --disable-factory -e ...
fails with the error presented in the question.
Please excuse this very personal side note: I really do not understand, why this crucial option got removed. Even Microsoft introduced an option to run
cmd
,explorer
orpowershell
the blocking way. Microsoft listens to their users. But Gnome does not. Instead of officially documenting the hidden option--disable-factory
, Gnome suddenly removed it. If they continue this course, they will make Microsoft win on the long term. That is very very sad and extraordinary stupid. (Sorry for this rant, but it has to be be said.)
BTW: Ubuntu 16.04 restored --disable-factory
using a wrapper which emulates this feature. (If you look at the complexity of this wrapper, my rant still applies even more than before.)
Variant 0
I call this 0
, because both are not really proper solutions. A proper solution is shown in Variant 1.
Varriant 0a
A first thing, you can try, is to remove option --disable-server
:
gnome-terminal --tab --title="700" -e ...
However this has following drawback:
This does no more wait until gnome-terminal
finishes. If there is another gnome-terminal
running, the command immediately comes back. Usually this is not what you want, because this is, why option --disable-factory
was present in the first place.
Variant 0b
So removing this option is only feasible in the case, where you can make sure, that in all and every case, no other gnome-terminal
is running, ever.
If this is not the case, but you are in a case, where another running gnome-terminal
must not be supported, you can try following desparate fallback variant:
killall -9 gnome-terminal
gnome-terminal --tab --title="700" -e ...
But beware! This unconditionally kills all gnome-terminal
s which are still open. In a production environment this usually will cause greater harm then it helps. You have been warned!
Variant 1
If you do not need to run it in gnome-terminal
and can run it in some other terminal emulator. @muru commented a good replacement.
xfce4-terminal
understands nearly the same set of options as gnome-terminal
(and adds some very handy other options which are missing in gnome-terminal
for years). It also has a documented option, which does, what --disable-factory
did for gnome-terminal
. The option --tab
works differently to gnome-terminal
and thus must be removed, too, to get something working. The replacement is:
xfce4-terminal --title="700" --disable-server -e ...
Also you can add a --hold
option, if you want to be able to see the full output of the command before the window is closed:
xfce4-terminal --hold --title="700" --disable-server -e ...
Please note that xfce4-terminal
has a little race-condition, which unfortunately truncates the output, so --hold
is not fully effective. Fixing this properly (such that you can use it copy'n'paste) is beyond the scope of the answer, however usually adding a little echo $? && read -t.1
to the script which is executed with (behind) -e
can solve it 99% of the time.
In case you get the message, that xfce4-terminal
is missing, then you have to install it first. It can be installed in parallel to gnome
, even that it belongs to another desktop variant (Xfce):
sudo apt-get install xfce4-terminal
The only drawback is, that xfce4-terminal
has another look than gnome-terminal
, and follows some other
Variant 2..∞
There are endless other possible variants to fix that issue. Most of them are really complicated. Too complicated for normal people, those, who are not really into shells.
So I leave them away. My recommendation is:
As noted by @muru, try to use xfce4-terminal
instead of gnome-terminal
.
Note to those, who grok shells
All simple solutions are not really perfect, as they do not return the command's return value (gnome-terminal
does not, too). Sadly. To fix that this is a completely different story.
answered Jun 17 '17 at 10:26
TinoTino
44147
44147
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.
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%2f729034%2fgnome-terminal-disable-factory-support-problem%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
What version of gnome-terminal do you have? Considered using another terminal emulator? Maybe xfce4-terminal?
– muru
Feb 3 '16 at 5:42
I do not understand why this was downvoted. This is a legitimate question. Ubuntu is for all, not only for Linux-Pros! Please do not discriminate people because they are not fluent in English or do not grok shell syntax. We are here to help them!
– Tino
Jun 17 '17 at 8:52