[Bug 1783129] Re: Only "main" component enabled after install
Rob Thomas
1783129 at bugs.launchpad.net
Mon Aug 20 22:27:53 UTC 2018
This just happened to me, and reading through, I noticed this is
triggered by cloud-init.
Is it possible that it's only biting people who install SSH keys with
cloud-init, as I was mildly surprised to see it running as part of boot.
(Screenshot:
https://s3.amazonaws.com/uploads.hipchat.com/190176/1597809/1iuhppYcWkjRHm7/upload.png
)
For people looking for a one-line fix, here it is:
curl https://pastebin.freepbx.org/view/raw/fca35292 > /etc/apt/sources.list && apt-get update
That paste is a mirror of the paste in #16 without the requirements to login.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1783129
Title:
Only "main" component enabled after install
Status in subiquity:
Confirmed
Status in livecd-rootfs package in Ubuntu:
In Progress
Status in livecd-rootfs source package in Bionic:
Confirmed
Bug description:
Maybe this is on purpose, and I also don't remember how the classic
server installer behaved, but after I booted my system installed with
subiquity, only the main component was enabled in
/etc/apt/sources.list. There was no "restricted", "universe" or
"multiverse" there.
Feel free to mark this as invalid, if this is the intended behaviour.
I wasn't sure so decided to file this bug just in case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1783129/+subscriptions
More information about the foundations-bugs
mailing list