Fixed in https://bugs.launchpad.net/bugs/1179202.
** Changed in: openssh (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1179344
Thanks for the confirmation!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1179344
Title:
ssh doesn't get pty; says inappropriate ioctl for device
To manage notifications about
** Changed in: openssh (Ubuntu)
Status: New = Confirmed
** Changed in: openssh (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1179344
You might find useful log information in /var/log/auth.log.
I suspect that this may be a consequence of bug 1179202.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1179344
Title:
** Changed in: openssh (Ubuntu)
Importance: Low = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1179344
Title:
ssh doesn't get pty; says inappropriate ioctl for device
To
@cjwatson, you're correct that the bugs seem related. For example:
May 13 09:45:42 emu sshd[12679]: Accepted publickey for codegnome from
192.168.1.127 port 50803 ssh2
May 13 09:45:42 emu sshd[12679]: pam_unix(sshd:session): session opened for
user codegnome by (uid=0)
May 13
Given that the nature of the other bug messes quite thoroughly with
sshd's ability to communicate between bits of itself, including the
protocol that allows it to set up a session properly, I don't think it's
fair to consider the TERM/pty/login-shell issues as unrelated. If
1:6.2p1-3 fixes this
