GNOME Bugzilla – Bug 87063
gnome-terminal --command no longer works
Last modified: 2003-02-09 02:51:15 UTC
Package: gnome-core Severity: critical Version: 1.4.1-1.ximian.4 Synopsis: gnome-terminal --command no longer works Bugzilla-Product: gnome-core Bugzilla-Component: gnome-terminal Description: Neither --command nor --execute seem to work. I just noticed, but the last time I remember it working was maybe 2 months ago. (I upgrade pretty regularly with red-carpet.) Example: gnome-terminal --command '/bin/sleep 1000' gnome-terminal --command 'ssh wherever' With both such commands, most of the time, gnome-terminal just exits immediately without any visible window being mapped (or maybe it's just mapping and vanishing faster than I can see.) Sometimes, but not always, it prints "Error: unable to fork: Success" to stderr. About 1 time in 5, I get a non-functional terminal window, and a dialog that says There has been an error while trying to log in. If you are using Linux 2.2.x with glibc 2.1.x, this is probably due to incorrectly setup [sic] Unix98 ptys. Please read linux/Documentation/Changes for how to set them up correctly. That error message is, of course, moronic: before presenting this obscure suggestion that just about nobody is going to actually understand, gnome-terminal should check to see whether I am, in fact, running Linux 2.2.x (I am not) or whether I am using glibc 2.1.x (I am running 2.2.4-24.) gnome-core-1.4.1-1.ximian.4 glibc-2.2.4-24 Linux 2.4.9-13smp #1 SMP Tue Oct 30 19:06:50 EST 2001 i686 unknown ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-07-01 20:57 ------- Reassigning to the default owner of the component, gnome-core-maint@bugzilla.gnome.org.
Does it work if you remove the '' around the command?
Yes, this works: gnome-terminal --command ssh foo but that didn't use to be necessary (and I have shell scripts that used to work to prove it...) But there's no way to do stuff like this without an intermediate shell script: gnome-terminal --command echo foo \; /bin/sleep 1000 Specifically commands like 'ssh -n host command; echo done; read x' to make sure you need to hit return to dismiss the window, so that you have a chance to read the output of the command. And, let's not forget, the dumb "error trying to log in" message needs to be fixed regardless.
Maybe this is a regression from trying to stop gnome-terminal from crashing with a NULL command. I'll attach the diff that was done with the last release.
Created attachment 10250 [details] [review] Patch from last release that was meant to fix a crash with null commands
Does this look like it would cause the error?
Could you take a look at the patch and comment?
*** Bug 86309 has been marked as a duplicate of this bug. ***
*** Bug 84272 has been marked as a duplicate of this bug. ***
> Could you take a look at the patch and comment? Did you mean me? I have no idea, I'm completely unfamiliar with the gnome-terminal code...
Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gnome-core product is being closed. If y0u feel your bug is still of relevance to GNOME 2, please reopen it and refile it against a more appropriate component. Thanks...
Argh. Apologies for the double spam. Actually closing this time.