Snapd errors when init isn't systemd


#1

i have the same problem except that the systemctl command does not work


Snap cannot communicate with server
#2

Which is, exactly, your problem, and in what way does systemctl not work?


#3

it says, “System has not been booted with systemd as init system (PID 1). Can’t operate.”


#4

that’s a completely different problem: snapd needs systemd to be your init.


#5

how do i do that…


#6

I don’t know: how do you not have systemd as your init? These days that’s got to be a conscious effort on your part.


#7

i didn’t do anything


#8

What distribution are you using?


#9

im sorry i dont know what your talking about.
my terminal says xenial before the local host name does that help?


#10

i think im in 64 bit as well


#11

Please, what is the output of snap version?


#12

snap 2.37.4+18.04.1
snapd unavailable
series -


Snap cannot communicate with server
#13

How did you install this system?


#14

through dev console and ubuntu download


#15

Is this a virtual machine hosted by another party? Not a machine in your personal control?


#16

not that i know of…


#17

It’s a physical machine sat in front of you?


#18

im pretty sure i dont think its a hologram


#19

Ok, we’re going to need some more details if we’re going to debug this.

How exactly was this installed? Off a USB stick? Where did the ISO come from?
What’s the output of the following commands:-

lsb_release -a

and

uname -a


#20

lsb_release -a =
No lLSB modules are available
Distributor ID: Ubuntu
description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

uname -a=
Linux localhost 3.18.0-18747-gdea8d908bd77 #1 SMP PREEMPT Sun Mar 3 22:37:23 PST
2019 x86_64 x86_64 x86_64 GNU/Linux