** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with '/usr/bin/snap wait
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in:
root@plis231v:~# ps -o cmd fp 1
CMD
/sbin/init
root@plis231v:~# sudo ls -lah /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart
root@plis231v:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet
root@plis231v:~#
--
You
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap
any suggestion to fix this?
I had tried below command.
root@plis231v:~# sudo dpkg -l | grep systemd
ii libpam-systemd:amd64 229-4ubuntu21.31+esm1
amd64system and service manager - PAM mod
ii libsystemd0:amd64
@gsunipipeline it looks like systemd does not operate correctly in your
system. This is a prerequisite for even accessing the snapd daemon,
since we rely on systemd to provide the socket, then activate snapd
daemon, and the snapd daemon directly interacts with systemd to set up
snaps.
** Also
6 matches
Mail list logo
