** Description changed:
Which is bad now that the ubuntu-server metapackage depends on it.
+
+ Setting up multipath-tools (0.7.4-2ubuntu4) ...
+ Created symlink /etc/systemd/system/multipath-tools.service →
/lib/systemd/system/multipathd.service.
+ Created symlink /etc/systemd/system/sysinit.t
Going forward openssh-server is not present in the install image at all.
If you install it, keys will be generated as usual.
** Changed in: subiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
On Thu, 10 Oct 2019, 23:41 Dimitri John Ledkov,
wrote:
> This has now added
> lxd:x:101:
>
> Into ubuntu-base tarballs http://cdimage.ubuntu.com/ubuntu-
> base/daily/pending/ which is a bit problematic.
>
> Was that intended?
>
I think it was sort of known, vs actively intended.
core20 snap bui
Argh I was worried that might happen :( Are you in a postition to test
the attached patch? (I realize testing installer patches like this isn't
the easiest thing)
** Patch added:
"0001-only-suppress-the-installation-media-for-some_device.patch"
https://bugs.launchpad.net/ubuntu/+source/partma
Argh you're right of course. Have to run now, don't have time to make a
better patch.
And yes, I was assuming your recipe doesn't use some_device -- the
intent of my change was essentially to restrict the logic xnox added to
some_device and not the others (we should also probably add some
filterin
Yeah, I have a similar config in my laptop, and:
(master)mwhudson@anduril:~/src/probert$ sudo multipathd show paths
hcildev dev_t pri dm_st chk_st dev_st next_check
0:1:1:1 nvme0n1 259:0 1 undef undef unknown orphan
(master)mwhudson@anduril:~/src/probert$ sudo multipathd show maps
Ah so curtin takes DM_MULTIPATH_DEVICE_PATH being set at all as an
indication of a multipath device, but per the follow up to
https://www.spinics.net/lists/dm-devel/msg35965.html that's wrong: only
a value of "1" indicates a multipath device.
--
You received this bug notification because you are
This is fixed in the stable/ubuntu-19.10 channel now. If you boot an
eoan daily (up to and including 20191014, the next one will contain the
fix), it will offer to update you to 19.10.2 which should then be able
to complete the install.
** Changed in: subiquity
Status: New => Fix Committed
This got fixed I think?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847852
Title:
lxd group is added to too many products
To manage notifications about this bug go to:
https://bugs.launchpad.net
I was hoping Debian would upload cargo 0.38 but they haven't so I guess I
get the fun of doing the upstream update myself. Yes, I should start work
on this soon.
On Wed, 16 Oct 2019 at 01:35, Rico Tzschichholz <1843...@bugs.launchpad.net>
wrote:
> @mwhudson Are you planning to start on that?
>
>
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860412
Title:
Lubuntu 18.04.4 QA-test install; just stops (circling pointer)
To manage notifications about this bug go
Finally tested this with a bionic daily and it passed (screenshot
attached). Sorry for taking so long over this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848880
Title:
installing ubiquity on e
** Attachment added: "Screenshot from 2020-01-30 10-41-20.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848880/+attachment/5323927/+files/Screenshot%20from%202020-01-30%2010-41-20.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Is this still an issue? We reprobe on udev events now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849537
Title:
19.10 subiquity installation on s390x with FCP/SCSI disk storage got
stuck
To m
So I've been handed the job of moving this bug forward this iteration.
Having just re-read all the comments again and read some source code
while listening to loud techno music my observations/questions are
these:
1) this is a doozy
2) I would really like to see complete udevadm monitor and inot
Ah, no I think this might be along right lines: udev is calling blkid on
the _partition_ of course, so it can probe for filesystem etc without
looking at the partition table. After it's done that, it does look for
the partition table so it can read the ID_PART_ENTRY_* values from it,
but if it fail
Oh yeah and one other thing I don't understand: why udev is processing
the partition while sgdisk is still running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart r
Hi, could someone prepare an image with
https://paste.ubuntu.com/p/HYGv6m8gCc/ at /etc/systemd/system/systemd-
udevd.service.d/udevd-debugging.conf, boot it on azure until it fails
and put the journalctl output (probably a few megs) somewhere I can read
it? Output from a successful boot would also
On another tangent, I wonder if the change that brought this to light
was the switch to booting without initrd. The timing is about right, and
fits with the fact that it doesn't occur with the generic kernel (which
cannot boot without initrd in Azure). So if someone has an excess of
time to test ,
I managed to reproduce this, although I don't think I was being offered
the autoresize option but rather it was trying to install "alongside"
the "install" that was on the install media. (certainly, sdb was the
install media for me, and I got the same message)
--
You received this bug notificatio
Here's /var/log from a failed install attempt with debug-ubiquity on the
kernel command line.
** Attachment added: "lp-1861912.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861912/+attachment/5325423/+files/lp-1861912.tgz
--
You received this bug notification because you are
** Changed in: ubiquity (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/1861912
Title:
file system creation in partition failed in auto-resize install
18.04.
> Ah, no I think this might be along right lines: udev is calling blkid
> on the _partition_ of course, so it can probe for filesystem etc without
> looking at the partition table. After it's done that, it does look for
> the partition table so it can read the ID_PART_ENTRY_* values from it,
> but
So the status here is that containerd 1.3.1 is in focal-proposed but is
stuck there because the docker autopkgtests are hanging:
http://autopkgtest.ubuntu.com/packages/d/docker.io/focal/amd64
I have no idea what is going on. It doesn't happen in my machine. I
guess the next step is to get someone
Hi, this sounds strange and fairly serious. The install media you used
should have logs copied to it -- they'll be on the filesystem with label
casper-rw. Can you tar up and attach the logs for the install that
failed to boot?
--
You received this bug notification because you are a member of Ubun
If you could also try a focal daily, that would be great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857789
Title:
Ubuntu Server 19.10 Installer immediately boots to GRUB rescue prompt.
To mana
I'm surprised the install doesn't fail in this situation :(
I'm a bit leery of doing too much ahead of time validation of the mirror
but I guess we could at least do a HEAD request for the Release file or
something, would weed out most typos and silly mistakes.
** Package changed: subiquity (Ubun
snapd itself does not have any concept of newer/older revisions, if the
snap in the channel is different to the one installed it will be offered
as a refresh candidate. I don't really want to work around that in
subiquity.
I think what happened here was that the stable/ubuntu-20.04 branch
autoclos
** Changed in: subiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840734
Title:
i am testing apport integration
To manage notifications about this bug g
** Also affects: subiquity
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/1839529
Title:
Live-server installation fails to install on Samsung NVME
To mana
The package in bionic-proposed lacked the executable bit on the new
script. Have reuploaded it with that bit set.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bug
Yes I wondered if that might be your response. Hopefully the next person
who runs into this will not actually need to use the server immediately
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857789
Um what? We have the same version of containerd everywhere (well apart
from powerpc maybe but I'm sure you don't care about that). Where are
you seeing older versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
That one works better, picture attached.
** Attachment added: "Screenshot from 2020-01-23 22-04-14.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1853912/+attachment/5322306/+files/Screenshot%20from%202020-01-23%2022-04-14.png
** Tags removed: verification-needed verification-need
Huh that is strange. It's wrong though, for example:
(ubuntu/devel)mwhudson@anduril:~/src/pkg/python-jsonschema$ rmadison containerd
containerd | 0.2.5-0ubuntu2 | bionic/universe | source,
amd64, arm64, armhf, i386, ppc64el, s390x
containerd | 1.2.6-0ubuntu1~16.04.3 | xenial-se
** Changed in: containerd (Ubuntu)
Status: New => Won't Fix
** Changed in: containerd (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860639
Title:
ZFS support is not going to happen for 20.04. Did you get the impression
it would from somewhere?
** Changed in: subiquity (Ubuntu)
Status: New => Triaged
** Changed in: subiquity (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member
This is because "lsb_release -d" does not contain "LTS" yet on focal.
When it does, the text used here follows this template:
Welcome to the Ubuntu Server Installer!
The most popular server Linux in the cloud and data centre, you can
rely on Ubuntu Server and its five years of guaranteed free upg
Maybe we should add different text when the description says
"development version"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860848
Title:
focal server installer says nine month support period
Public bug reported:
libbde ftbfs because it depends on removed packages, debian has an
upload fixing this in DELAYED/15 which should migrate around Feb 3.
** Affects: libbde (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification
** Description changed:
- libbde ftbfs because it depends on removed packages, debian has an
- upload fixing this in DELAYED/15 which should migrate around Feb 3.
+ libbde and libfsapfs ftbfs because they depends on removed packages,
+ debian has uploads fixing these packages in DELAYED/15 which s
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860944
Title:
ftbfs with gcc-9
To manage notifications about this bug go to:
https://bugs
Public bug reported:
Apparently the 0.2.3 release fixes this.
** Affects: libopenshot (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Bug watch added: Debian Bug tracker #925754
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
--
You received thi
** Changed in: casper (Ubuntu)
Status: New => Incomplete
** Changed in: casper (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-power-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
My gut says this is more likely to be systemd or the kernel but we
should look into it further indeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856083
Title:
autopkgtest fails with Go 1.13
To
Oh, I hadn't realized that you were running in the lxd backend. I'm not
super surprised that fails. It might work in a privileged container
maybe? We should probably add isolation-machine or whatever the
restriction is to d/tests/control.
--
You received this bug notification because you are a m
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: livecd-rootfs (Ubuntu Trusty)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Verification complete on trusty:
1) I started two trusty ubuntu-base livefs builds:
$ start-livefs-build
--livefs=~mwhudson/+livefs/ubuntu/trusty/docker-ubuntu-core-tests --pocket
Updates --metadata project='"ubuntu-base"' --metadata image_format='"plain"'
https://launchpad.net/~mwhudson/+livef
Is there somewhere to upload these versions to? rust-next is still
behind rust-updates, so if I upload to rust-updates the version
currently there will be lost (not that I'm sure I'm going to have
packages to upload before I go on leave for four weeks; someone else
might have to drive this).
** Ch
Ah OK that makes sense. I don't think it'll make bootstrapping any worse
than it already is ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856851
Title:
rustc 1.39 and cargo 0.40 required by fire
** Description changed:
[impact]
This breaks apt update in a trusty docker image that does not have ESM
enabled.
[test case]
- Build a livefs with image_format=plain, project=ubuntu-base. Unpack it, do
the usual pre-chroot setup dance (copy resolv.conf, bind mount proc and dev)
chroot
The autopkgtests for the update in both xenial and bionic passed, which
is all the verification we can sensibly do at this stage.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial
--
You re
I wonder if this was the same problem as
https://bugs.launchpad.net/subiquity/+bug/1868817
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
Subiquity on Focal Live Server (current daily-
Ah yes, you could try the process described in
https://discourse.ubuntu.com/t/how-to-test-the-latest-version-of-
subiquity/12428, that would actually be very useful.
FWIW, fix committed does not mean it will be on the next ISO, that's
more what fix released means in this project. But we've not bee
Hm, is it possible to attach an error report to this bug? By design it's
not possible to get from an error report in the tracker back to a user.
If that's not easy, can you look in the .meta file in /var/crash? It
should have an oops_id which will let me find the report reliably.
--
You received
** Also affects: quassel (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags added: regression-update
** Changed in: quassel (Ubuntu Xenial)
Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco)
--
You received this bug notification because you are a member
Ah the traceback is this:
Traceback:
Traceback (most recent call last):
File
"/snap/subiquity/1581/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 145, in _probe
self._probe_once_task.task, 15.0)
File "/snap/subiquity/1581/usr/lib/python3.6/asyncio/tasks.py", l
Pretty sure it's initramfs-tools that is putting the mac addresses in
the netplan. That probably needs to grow a little platform-dependent
behaviour around this.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because yo
So I think Paride is more or less right in #10: One of the subiquities
starts the install. One of the subiquities then segfaults (doesn't
matter which one). Systemd restarts this subiquity, which then unmounts
/target, so the subiquity running the install just copies
filesystem.squashfs to RAM and
Ah wait, subiquity is segfaulting when curtin is in net-meta auto. That
makes me very much suspect the crash is inside probert. Did libnl3
change recently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
It would be amazingly strange, but it's possible that
https://github.com/CanonicalLtd/subiquity/pull/670 will make the crash
go away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
foc
In any case, can someone who can reproduce this try with edge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865027
Title:
focal-arm64 install fails. No space left on device on /target
To manage n
Argh sorry I've been meaning to look into this but other things keep coming
up. To be clear: an existing casper-rw partition *should* be being used.
It's a bug that it is not.
On Fri, 28 Feb 2020, 21:25 sudodus, <1863...@bugs.launchpad.net> wrote:
> > I noticed that the version of casper has chan
So I tried to reproduce this in a VM and failed. This is what I did:
$ cd ~/isos/
$ zsync
http://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/focal-live-server-amd64.iso.zsync
[...]
$ cd ~/images/
$ truncate -s 1G casper-rw.img
$ truncate -s 1G root.img
$ parted --script --align optimal ca
Yes, so roughly speaking it works on faster machines and fails on slower
machines. (I also tested your steps on my laptop, and it worked there --
but my laptop is a t480s with nvme so that's consistent). I do have a
slower machine that I use for testing but I'm travelling and so don't
have access t
This seems to occur when an executable that has been deleted crashes --
the apport hook is called with the executable name set to "/path/to/exe
(deleted)" and somehow this is being split on spaces and the extra
(deleted) argument causes this crash. But simple attempts at reproducing
this scenario f
subiquity end of this needs fixing in the image build
** Also affects: livecd-rootfs (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/1863887
Title:
Can someone from CPC confirm that this has fixed the issues in the Azure
tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
To manage notificatio
There aren't any such packages (unless I'm missing something). I'm not
updating the default version of Go in trusty, but rather the special
golang-1.6 packages that was uploaded to allow juju to use it -- but
juju has not used it yet.
--
You received this bug notification because you are a member
** Changed in: golang-1.6 (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567096
Title:
Docker doesn't work since Containerd integration
To manage n
** Changed in: lxd (Ubuntu)
Status: Triaged => In Progress
** Changed in: dh-golang (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508122
Ti
** Also affects: php7.0 (Ubuntu Xenial)
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/1596578
Title:
zabbix issues with current php version
To manage not
I've uploaded this to the xenial unapproved queue now. The only change I
made was that I set the version number to 7.0.8-0ubuntu0.16.04.1.
** Changed in: php7.0 (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
FWIW, https://launchpad.net/bugs/1596735 is about uploading the same
upstream version to Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569609
Title:
[SRU] microrelease exception for src:ph
Huh. Can you test yakkety too? I was fairly sure that it worked, but maybe
i confused myself.
On 2/07/2016 4:01 am, "dann frazier" wrote:
> With the -proposed version, I'm seeing failures on arm64, apparently due
> to the new dependency on containerd.
>
> Starting Docker Socket for the API.
> Lis
*** This bug is a duplicate of bug 1766391 ***
https://bugs.launchpad.net/bugs/1766391
** This bug has been marked a duplicate of bug 1766391
package shim-signed (not installed) failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
*** This bug is a duplicate of bug 1766391 ***
https://bugs.launchpad.net/bugs/1766391
** This bug has been marked a duplicate of bug 1766391
package shim-signed (not installed) failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
** Changed in: subiquity
Status: Triaged => Fix Released
** Changed in: debian-cd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625211
Title:
"invalid" is a bit strong, more like "unlikely to be correct". Part of
the fun here is that subiquity currently doesn't ask for a country at
all, I guess we should, although I suppose that doesn't matter much for
Polish...
--
You received this bug notification because you are a member of Ubuntu
B
** Package changed: subiquity (Ubuntu) => subiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767054
Title:
Invalid default keyboard selected during installation
To manage notifications about
Oh sigh debian has already been through this: https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=846200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700696
Title:
ftbfs in artful due to DT_RPATH/D
Public bug reported:
elektra fails to build in artful with tests failing like this:
Traceback (most recent call last):
File "/<>/src/bindings/swig/python/tests/test_kdb.py", line 61,
in tearDownClass
with kdb.KDB() as db:
File "/<>/obj-x86_64-linux-gnu/src/bindings/swig/python/kdb.py",
; Invalid
** Changed in: golang-1.6 (Ubuntu Xenial)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: golang-1.6 (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Description changed:
+ == SRU template for golang-1.6 ==
+
+ [Impact]
+ The kernel bug reported below means that occasionally (maybe 1 in 1000 times)
the snapd -> snap-confine exec that is part of a snap execution fails to take
the setuid bit on the snap-confine binary into account which mea
** Changed in: golang-1.6 (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672819
Title:
exec'ing a setuid binary from a threaded program sometimes fa
Public bug reported:
To allow ISO testing to test a live-server install without modifying the
ISO, one thing that's necessary is a way for the installer to suppress
the "remove installation medium" message. The best idea so far is to
have casper-stop skip the prompt if /run/casper-no-prompt has be
It would be technically easy to fix this bug, i.e. restart the docker
daemon on package upgrade.
The impact of this is that the docker containers will be restarted when
the package is upgraded.
We need to decide if this impact outweighs the benefit.
--
You received this bug notification because
Yes, probably. Curtin copies its log to /root/curtin-install.log too,
maybe that should be /var/log/installer/curtin-install.org too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738199
Title:
sho
Python 3.6 is not part of 16.04 and so no package that contains
extension modules has them built for python 3.6. 17.10 has everything
built for 3.6 and obviously 18.04 will too.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
The offending version of libseccomp2 is still in xenial-proposed, but
snapd on most architectures statically links against it. Unfortunately
the bug for the libseccomp2 SRU is still in verification-needed:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1682102.
The two fixes that spring
We run full autopkgtests on all architectures now so closing.
** Changed in: runc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658150
Title:
adt
Doko asked me to look at the package and it seems OK to me on a quick
glance. (Only spent a few minutes, let me know if you'd like a deeper
review!)
On the packaging side, I'm a bit surprised at the use of go:generate to
create the shared lib but it works I guess. Another thing that's more on
the
I've noticed the delay on switching to another vt. You don't need to
press enter btw, it appears by itself eventually, but I didn't know what
was causing the wait. I'd prefer to have the shell appear instantly than
having text that says you need to wait!
After digging, this is an obscure systemd t
** Changed in: subiquity
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738199
Title:
should copy live system journal into installed system
/var/log/installer
T
** Changed in: subiquity
Status: New => Fix Released
** Changed in: probert (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743631
Title:
Ins
Public bug reported:
I think this is covered by this special case on
https://wiki.ubuntu.com/MainInclusionProcess:
If a new source package contains only code which is already in main
(e.g., the result of a source package split or rename, or source
packages with a version in the name), it may not
Ah yes, I think this is fixed in git but not in the latest ISOs. Thanks
for the report!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751656
Title:
Installing 18.04 LTS on existing Partition
To ma
*** This bug is a duplicate of bug 1750819 ***
https://bugs.launchpad.net/bugs/1750819
** This bug has been marked a duplicate of bug 1750819
Impossible to install without network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ssh-import-id (Ubuntu Bionic)
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/1770302
Title:
ssh-import-id gh:$missing-user does not flush
201 - 300 of 2201 matches
Mail list logo
