Bug#216248: /usr/bin/gnome-remote-shell: The problem seems to be
still there
Quim Gil
Quim Gil <qgil@lawebespiral.org>, 216248@bugs.debian.org
Mon, 03 Nov 2003 20:02:46 +0100
> What are you using as your clients for SSH and terminal?
I use the SSH commandline and it works. I also use gFTP, also works. And
Gnome Terminal.
> Is your
> password being stored by ssh-agent?
Mmm I don't understand the question. :) I see I've ssh-agent
installed. Under /home/qgil/.ssh there is only one file: known_hosts. I
type the password anytime I connect via ssh.
> Are both your ssh usernames and
> pasword entirely in ASCII?
Yes of course.
> Does your bug disappear if you start
> gnome-network under LANG=C LC_CTYPE=C?
Same story:
qgil@tort:~$ gnome-remote-shell
qgil@tort:~$ Invalid argument: "ssh"
> I really don't know what's going on unless you can provide us with a
> strace (make sure any passwords are obscured).
Sure:
qgil@tort:~$ strace -c gnome-remote-shell
execve("/usr/bin/gnome-remote-shell", ["gnome-remote-shell"], [/* 26
vars */]) = 0
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
80.31 0.658451 2097 314 poll
12.64 0.103649 652 159 write
2.21 0.018128 412 44 writev
1.73 0.014173 15 929 read
1.03 0.008460 8460 1 chmod
0.49 0.004012 16 249 12 open
0.27 0.002179 10 225 old_mmap
0.18 0.001476 5 319 1 ioctl
0.17 0.001395 279 5 1 connect
0.17 0.001373 6 247 close
0.13 0.001096 1096 1 fork
0.11 0.000897 9 95 72 access
0.09 0.000725 10 74 munmap
0.08 0.000634 634 1 unlink
0.07 0.000569 2 308 gettimeofday
0.06 0.000488 7 75 2 stat64
0.05 0.000382 3 146 fstat64
0.03 0.000272 45 6 socket
0.03 0.000250 5 51 brk
0.02 0.000196 33 6 pipe
0.02 0.000125 31 4 getdents64
0.01 0.000103 21 5 5 mkdir
0.01 0.000101 14 7 4 lstat64
0.01 0.000085 7 13 uname
0.01 0.000062 3 20 fcntl64
0.01 0.000055 55 1 shmat
0.01 0.000053 3 16 rt_sigaction
0.01 0.000051 17 3 readv
0.01 0.000044 44 1 mmap2
0.01 0.000044 44 1 shmget
0.01 0.000043 43 1 accept
0.00 0.000035 5 7 _llseek
0.00 0.000033 33 1 getpriority
0.00 0.000032 32 1 utime
0.00 0.000030 2 13 getpid
0.00 0.000024 24 1 shutdown
0.00 0.000019 19 1 listen
0.00 0.000014 14 1 getcwd
0.00 0.000010 2 6 getuid32
0.00 0.000010 10 1 geteuid32
0.00 0.000009 5 2 time
0.00 0.000009 9 1 _sysctl
0.00 0.000009 9 1 sched_getscheduler
0.00 0.000009 9 1 setsockopt
0.00 0.000008 3 3 rt_sigprocmask
0.00 0.000008 8 1 getsockname
0.00 0.000006 6 1 sigreturn
0.00 0.000006 6 1 getresuid32
0.00 0.000003 3 1 setrlimit
0.00 0.000003 3 1 sched_getparam
0.00 0.000003 3 1 getrlimit
0.00 0.000003 3 1 getresgid32
0.00 0.000003 3 1 shmctl
0.00 0.000002 1 2
sched_get_priority_max
0.00 0.000002 2 1
sched_get_priority_min
0.00 0.000002 2 1 getgid32
0.00 0.000002 2 1 getegid32
0.00 0.000001 1 1 waitpid
0.00 0.000001 1 1 bind
------ ----------- ----------- --------- --------- ----------------
100.00 0.819867 3382 97 total
qgil@tort:~$ Invalid argument: "ssh"
((((Ctrl-C))))
> I haven't been able to
> reproduce your bug in gnome-network 1.99.2-2 at all. It's been working
> fine for me ever since 1.99.2-1.
That's not a long time. ;)
Thanks for your patience.
Quim