Ubuntu's 0.8 packages already include changes from SVN, that were
officially released in the 0.9 release.
--
open-terminal doesn't create a shell over ssh properly
https://bugs.launchpad.net/bugs/90880
You received this bug notification because you are a member of Ubuntu
Bugs, which is
wait, isn't that in the 0.9 release, not 0.8?
http://blogs.gnome.org/cneumair/2008/02/28/nautilus-open-terminal-release/
--
open-terminal doesn't create a shell over ssh properly
https://bugs.launchpad.net/bugs/90880
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package nautilus-open-terminal - 0.8-1ubuntu2
---
nautilus-open-terminal (0.8-1ubuntu2) hardy; urgency=low
* debian/patches
- pkg_config_ext_dir.patch - Get nautilus extension directory from
pkg-config to make sure this extension is installed
When i launch a terminal over ssh via nautilus it works fine but I allways need
to type my password and i endup in my home directory.
Is it possible to use the password memorised by nautilus and follow the actual
path?
thks
--
open-terminal doesn't create a shell over ssh properly
Well, Roch, the best way to keep ssh from asking for your password is to
generate ssh keys, add the private key to your ssh key agent (press
Alt-F2 and run ssh-add), and copy the public key to the remote machine
using ssh-copy-id.
--
open-terminal doesn't create a shell over ssh properly
Still here in up-to-date gutsy.
--
open-terminal doesn't create a shell over ssh properly
https://bugs.launchpad.net/bugs/90880
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
We I wrote this patch I didn't find any way to properly do that. I
choose this one because it worked fine with my personnal use case.
If anyone know a better way, please tell it.
--
open-terminal doesn't create a shell over ssh properly
https://launchpad.net/bugs/90880
--
ubuntu-bugs mailing
Good question. But using /bin/sh with bash extension is just a bad idea.
So why not just use /bin/bash? On any system where /bin/bash doesn't
exist, /bin/sh is probably not going to be linked to it anyway (thinking
solaris).
--
open-terminal doesn't create a shell over ssh properly
BTW: Here's my symptom. When I right click on an ssh location and select
open-in-terminal, I get a terminal that pops up displays this message for a
split second before disappearing:
sh: Illegal option -l
--
open-terminal doesn't create a shell over ssh properly
Christian, i confirm this issue.
** Changed in: nautilus-open-terminal (Ubuntu)
Importance: Undecided = Low
Status: Unconfirmed = Confirmed
--
open-terminal doesn't create a shell over ssh properly
https://launchpad.net/bugs/90880
--
ubuntu-bugs mailing list
We've had no complaints so far on this issue, possibly because most
people use bash. I'm subscribing Guillaume Desmottes [EMAIL PROTECTED]
who implemented SFTP support back in 2005.
Back in those days the problem was that we could either omit the command
and let the ssh client allocate a tty for
Hmm... I'm a little surprised that nobody else is having trouble. After
all, Ubuntu switched to dash a little while back.
I supposed there would be a couple of ways to proceed. One is to simply
use /bin/bash, rather than /bin/sh. Of course this could be problematic
on machines that put bash
12 matches
Mail list logo
