** Changed in: openssh (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage
** Changed in: openssh (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openssh (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
** Tags added: fr-78
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage notifications about this bug go to:
https://bug
This bug was fixed in the package pam - 1.1.8-3.2ubuntu2.3
---
pam (1.1.8-3.2ubuntu2.3) xenial; urgency=medium
* Move patch fixing LP: #1666203 from debian/patches to
debian/patches-applied so it actually gets applied.
* debian/libpam-modules.postinst: Add /snap/bin to $PATH i
And verified on xenial:
(client-server-5)mwhudson@anduril:~/src/subiquity$ ssh ubuntu@10.187.142.193
"sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd641.1.8-3.2ubuntu2.1
go: not found
(client-server-5)mwhudson@anduril:~/src/subiquity$ lxc exec lp1659719-xenial --
apt insta
Hello Leo, or anyone else affected,
Accepted pam into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu2.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
The fix for this in the queue for Xenial is help up by the verification
of bug 1666203.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the f
** Changed in: openssh (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: openssh (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: openssh (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This bug was fixed in the package pam - 1.3.1-5ubuntu4.1
---
pam (1.3.1-5ubuntu4.1) focal; urgency=medium
* debian/libpam-modules.postinst: Add /snap/bin to $PATH in
/etc/environment. (LP: #1659719)
-- Michael Hudson-Doyle Wed, 22 Jul 2020
11:30:44 +1200
** Changed in: pam
If kopanocore is known to be flaky on armhf please add a hint for it to
https://code.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-focal/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.2
---
pam (1.1.8-3.6ubuntu2.18.04.2) bionic; urgency=medium
* debian/libpam-modules.postinst: Add /snap/bin to $PATH in
/etc/environment. (LP: #1659719)
-- Michael Hudson-Doyle Wed, 22 Jul 2020
11:40:59 +1200
**
And bionic:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.63 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.1.8-3.6ubuntu2.18.04.1
go: not found
mwhudson@anduril:~$ lxc exec test-pam-bionic -- apt install -y
libpam-modules/bionic-proposed
Reading package lists... Done
Bui
The focal autopkgtest failures are in cyrus-imapd:
Mail::JMAPTalk version 0.15 required--this is only version 0.13 at
./Cassandane/Cyrus/JMAPCore.pm line 47.
BEGIN failed--compilation aborted at ./Cassandane/Cyrus/JMAPCore.pm line 47.
This seems very unlikely to be due to pam, and it happens wit
Verified on focal:
mwhudson@anduril:~$ ssh ubuntu@10.187.142.128 "sh -c 'dpkg-query -W
libpam-modules; type go '"
libpam-modules:amd641.3.1-5ubuntu4
go: not found
mwhudson@anduril:~$ lxc exec test-pam-focal -- apt install -y
libpam-modules/focal-proposed
Reading package lists... Done
Buildin
Hello Leo, or anyone else affected,
Accepted pam into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Leo, or anyone else affected,
Accepted pam into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pam/1.3.1-5ubuntu4.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu
** Description changed:
- ssh can't call a binary from a snap, it will only work using the full
- path.
+ [impact]
+ ssh can't call a binary from a snap, it will only work using the full path.
+
+ [test case]
+ Create a container. Install the go snap (and make sure golang-go is not
installed). R
This bug was fixed in the package pam - 1.3.1-5ubuntu5
---
pam (1.3.1-5ubuntu5) groovy; urgency=medium
* debian/libpam-modules.postinst: Add /snap/bin to $PATH in
/etc/environment. (LP: #1659719)
-- Michael Hudson-Doyle Fri, 10 Jul 2020
08:35:49 +1200
** Changed in: pam (Ub
** Changed in: openssh (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage notifi
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Ti
** No longer affects: snapd (Ubuntu)
** No longer affects: snapd (Ubuntu Groovy)
** Also affects: pam (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Xenial)
I've filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
about the pam ordering issue.
** Bug watch added: Debian Bug tracker #964580
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Here's a better patch that I've tested this time. I dropped the code
around adding /usr/local/games to PATH as that was in trusty.
** Changed in: pam (Ubuntu Groovy)
Status: Confirmed => In Progress
** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
https://bugs.launchpad.net/sn
The inconsistency between login and openssh session module ordering is
still an issue. Reopening.
** Changed in: openssh (Ubuntu Groovy)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Given Colin's comment 12, it doesn't look like there are any plans to
change this in openssh packaging so I'll mark this Won't Fix.
** Changed in: openssh (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That won't be too different from /usr/local/sbin and /usr/local/bin
being in the PATH but empty I think. I am not aware of any problem or
annoyance caused by nonexisting directories being in the PATH.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage notifications about this bug go to:
https://bug
It's easy enough to unconditionally add /snap/bin to path, see attached,
but I can't really see a clean way to only have it present in the $PATH
when snapd is installed (without code changes to pam_env, anyway).
** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
https://bugs.launchpad.n
** Tags added: id-5ec69c5a5bc4156ecefb75a0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage notifications about this
** Changed in: pam (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manag
** Also affects: pam (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: openssh (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: livecd-rootfs (Ubuntu Groovy)
Importance: Medium
Assignee: Oliver Grawert (ogra)
Status
** Changed in: livecd-rootfs (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a bin
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
To manage notifications about this bug go to:
h
+1, tweaking /etc/environment makes it work. It seems that this has to
be fixed in the libpam-modules postinst script then.
** Changed in: pam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I know that work was done to ensure /snap/bin was in the default path
for systemd itself and that this should be inherited now by all units.
'systemd-path | grep search-binaries:' shows that it's there on my focal
system. 'sudo ps axe | grep sshd' also shows that it's set in the
PATH environme
It looks like the likely cause here is that sshd loads pam, which calls
pam_env, which reads /etc/environment, which has a different PATH than
the default one provided by systemd.
We should fix this to be aligned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple release
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ss
I'm very reluctant to reconfigure openssh for this; it feels like a
layering violation, and a regression of all the work we did way back
when to avoid having to change umpteen packages when we want to change
the default command search path.
How about something like adding a pam_snap session module
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh
Adding a task against the Ubuntu snapd package for the non-interactive
shell case (eg. ssh), since this still affects Ubuntu the distribution
on this point.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Yes it obviously works for login shells.
To make it work for non-login shells /etc/environment would need to
include /snap/bin -- an issue for foundations to decide upon.
Thanks for the insight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
this has been fixed long ago and you should have an /etc/profile.d/apps-
bin-path.sh file that adds /snap/bin to your PATH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call
Still hitting this with...
jenkins@juju-6f7422-solutions-qa-integration-1:~$ snap version
snap2.27.6
snapd 2.27.6
series 16
ubuntu 16.04
kernel 4.4.0-83-generic
jenkins@juju-6f7422-solutions-qa-integration-1:~$ snap list
Name VersionRev DeveloperNotes
conjure-up 2.3.1
so with todays edge core snap it now looks like:
$ ssh 192.168.2.76 env |grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: snappy
Status: New => Confirmed
** Changed in: snappy
Importance: Undecided => Medium
** Changed in: snappy
Assignee: (unassigned) => Oliver Grawert (ogra)
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: livecd-roo
47 matches
Mail list logo
