-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay, some further information.  After I start gnome-terminal from a
command line with 'gnome-terminal -x /bin/sh' I can issue a 'w' command
(in another terminal) and see that an instance of 'sh' for my account
has been started.  This has to be the sh in the gnome-terminal,
because my default shell is 'bash'.  So I was apparently wrong
initially when I said no shell instance is being started.  The issue,
more accurately,
is that no output appears in the gnome-terminal window.

When I then focus the konsole where I issued the command to start
gnome-terminal and hit control-z to suspend the running job,
gnome-terminal freezes (will not repaint its window, etc).  When I type
'fg' to resume the suspended job, gnome-terminal resumes (will
repaint its window, etc).

As a test, I did the following:

echo "cat /home/bear/quotations.txt" > sayquotes
chmod +x sayquotes
gnome-terminal -x sayquotes

gnome-terminal came up, very briefly, and then exited.  The
'quotations.txt' file is fairly long, but I did not see any
output on the gnome-terminal screen.  The length of time the
window was up however, was about the same as the length of time
that a shell running in konsole takes to cat that same file.

All this is consistent with gnome-terminal starting the shell (or
command) process and running it normally, but failing to display
any output.

So I did another test, of using gnome-terminal 'blindly' assuming
that a command shell is running.

After starting gnome-terminal from konsole using 'gnome-terminal'
I focused the gnome-terminal window and typed 'iceweasel'  - and
the browser came up.  I quit out of iceweasel and typed 'exit' -
and gnome-terminal quit, refocusing konsole.

So.  Evidently there is a shell process getting started, and it
is reading and executing commands.  But gnome-terminal is not
displaying any output.

So now it seems more like some kind of font problem that gnome-
terminal is not detecting or reporting.  Or, perhaps, if irony
is particularly lovely today, it may be reporting the problem
on the screen in the very same font that won't display due to
the problem it's trying to report.

Please downgrade this bug from 'grave' (which it would be if no
shell were running, as I initially thought) to 'normal.'

                                        Bear
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP2p1YAAoJEAOzWkqOibfN3XwH/itdaXzCvy1CF9cyx/WGg2fx
9VGQG2ZqFvkUHYIhO8RbjxU2Dtz/i20/MFCf//HcLkLyBjGx6zKU2QSkea30UQMg
LIWMVfUucN/xSac9Do8ouFBJcEH6FjTCghKeq+mV7zTslpQrBKfO2gQR5Xcv3WSt
7wNnbIU/ByjIYzDpkAOGQyW0c4eSJOW+SH+vvkuGyQG84AGLJCiPbQ8Yj5RFHJFL
7ZcrgnVCYe53BsHmPubN+eozxlXCXeILjtH+Ckd02ftliD+JCZgxJ7PtYzsOyK6N
ZatDHy7sGVIIoeFNP0gjIkwiJufXPVJiS3Ik+cgMKga0n6jDAeRZzbnsndaUSVI=
=Bsgj
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to