Some aspects of this don't make much sense to me. /dev/sda1 is not
managed by udev, it's created by the kernel / devtmpfs. If it's not
there on the filesystem something really wacky is going on. But it
pretty clearly isn't in the udev database, which is almost as strange...
--
You received this b
I'm afraid I don't really understand this report. If you still have
access to the system can you attach the contents of /var/log from the
live session to this report?
** Changed in: subiquity
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
** Changed in: subiquity
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893818
Title:
Several blockprobe errors if trying to install the groovy daily live
on LPAR
To
Well OK I guess I understand that much -- but without logs I cannot do
anything useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897515
Title:
Ubuntu server 20.04.1 Subiquity running from DVD
OK, I was wrong /dev/sda1 (and similar) is really not present. If I run
"partprobe /dev/sd*" things start behaving but that should in no way be
needed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
OK some more clues: if i deactivate and reactivate the zdevs, the nodes
for the partitions do not appear. If I remove multipath-tools and
deactivate and reactivate the zdevs, the nodes for the partitions *do*
appear. If I install multipath-tools and remove
/lib/udev/rules.d/60-multipath.rules and d
60-multipath.rules is the same between focal and groovy though. Good
night for now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893818
Title:
Several blockprobe errors if trying to install the gr
Aaah so it turns out there has always been a udev rule that should have
removed the /dev/sda1 etc nodes for a drive that is multipathed, but
thanks to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959727 it
didn't work. So I guess probert / curtin need updates to cope with this
new reality but
** Changed in: curtin
Status: New => Confirmed
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893818
Title:
Severa
Well I finally got around to testing this, using kvm -nographic (and
booting with -kernel/-initd/-append console=ttyS0) and it seemed to work
fine. I agree it would be nice to be able to get grub to run on the
serial console but my understanding is that this is harder than it
should be on intel pla
I haven't checked it will help in your situation, but parted has a
--script command line flag which is documented as "never prompts for
user intervention" -- are you using that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
These seem to have both passed on retry...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891486
Title:
vim ftbfs in focal (armhf, ppc64el)
To manage notifications about this bug go to:
https://bug
Looking at this a bit more carefully, I think we can remove the call
that is failing and replace it with some udev checking instead. I'm
actually a bit surprised it fails -- a very similar call was made by
probert earlier in the run and that seems to have worked fine (although
I can't . I wonder if
Uh not sure how I missed this. Currently there are no plans to backport
the changes required to bionic. It's probably possible to make an iso
that does autoinstall by putting an /autoinstall.yaml file in the right
place -- but I haven't tried it.
--
You received this bug notification because you
** Description changed:
[Impact]
- * Golang 1.13 is not available in Bionic and Xenial preventing SRU-ing
+ * Golang 1.13 is not available in Bionic and Xenial preventing SRU-ing
LP: #1911454 and related packages.
[Test Case]
- * Install the package and run go version
+ * Instal
** Also affects: golang-1.13 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: golang-1.13 (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://
ed in: golang-1.13 (Ubuntu Xenial)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: golang-1.13 (Ubuntu Bionic)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
So, just to be clear I should add
https://src.fedoraproject.org/rpms/rust/blob/8148cbf67890e233c779daeddd4a4dfd5557fdf2/f/0001
-Revert-Auto-merge-of-79547.patch to the package and upload?
I'm not sure if it's worth the effort of backporting this to the older
releases at this point, but could be ta
Unfortunately it's going to be a little complicated because the rustc in
hirsute is too broken to build a fixed one :( We'll sort something out
but it's probably going to involve archive admin support...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hi, this seems fine and I'll upload it presently. Can you also send it
upstream to https://github.com/rfrail3/tuptime/pulls? (I also wonder if
the code would match the intent ever-so-slightly closer if you wrote
"chmod o+rx" rather than "chmod 0755" but that's super nit picky)
--
You received thi
** Changed in: subiquity
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the VG name
alre
** Changed in: subiquity
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897515
Title:
Ubuntu server 20.04.1 Subiquity running from DVD doesn't see drive 0
as a
** Also affects: curtin
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/1868177
Title:
/snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_t
** Changed in: curtin (Ubuntu)
Status: New => Invalid
** Changed in: curtin
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/1916325
Title:
Overly strict NAME_REGE
pretty sure this was fixed in 20.04.2.
** Changed in: curtin
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/1901817
Title:
subiquity installation (on s390x
** Changed in: curtin
Status: Fix Committed => 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/1896947
Title:
Release 20.2
To manage notifications about this bug go to:
https://bu
** Changed in: pam (Ubuntu Xenial)
Status: Won't Fix => In Progress
** Changed in: pam (Ubuntu Xenial)
Assignee: Don van der Haghen (donvdh) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Verified the new upload on xenial:
root@xenial-pam-play:~# dpkg -l libpam-modules
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
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
On Tue, 6 Oct 2020 at 22:20, Paride Legovini <1895...@bugs.launchpad.net>
wrote:
> I can't spot what change caused the /efi directory to be included again
> in the ISO filesystem. Does anybody have a pointer?
It was this upload I think:
https://launchpad.net/ubuntu/+source/cd-boot-images-amd64/7
I think the live server installer ISO, at least, is already preseeded?
(not completely sure how you tell, mind)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913758
Title:
let's preseed installer i
Oh so the last crash with LVM was this silly thing:
https://bugs.launchpad.net/subiquity/+bug/1905412. I really need to fix
this.
I think given that this bug report has fixed two real problems and has
resulted in a successful install without LVM, I'm going to close it and
any new problems can be h
Argh. Well in that case I guess you should put net.ifnames=0 on the
kernel command line when booting the install media (after --- so it gets
propagated to the installed system too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Huh this is very strange. I notice that go build -a succeeds so I wonder
if one of the .a files that's part of golang-1.13-go is broken somehow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913852
T
Well here's a funny thing:
root@xenial:~/# go tool pack tv
/usr/lib/go-1.13/pkg/linux_amd64/compress/zlib.a
-rw-r--r-- 0/0 5145 Jan 1 00:00 1970 __.PKGDEF/
-rw-r--r-- 0/0 46655 Jan 1 00:00 1970 _go_.o/
why are there / on the end of the archive names? No
Oh I have dealt with this before: the problem is that debhelper (in
xenial) thinks that "zlib.a" is a static library (it's trying to find
files with names of the form "libXXX.a" but uses a bad regex) and feeds
it to strip as part of the package build, which mangles the file.
--
You received t
** Also affects: golang-1.13 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [impact]
+ Applications that use the "compress/zlib" package fail to build.
+
+ [test case]
+ $ cat > go.mod
+ module github.com/foo/baz
+
+ go 1.13
+ $ cat > main.go
+ package mai
I've uploaded a fix to unapproved. You can also try the version from
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages to see
if it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi, this looks mostly very good! I have some tiny nitpicks:
1) It's good to mention the patches that are being dropped in the changelog
entry.
2) There are some whitespace changes in the bottom of the changelog that you
could drop if you felt like it.
--
You received this bug notification beca
The construction of the iso is buried in https://people.canonical.com
/~ubuntu-archive/cd-build-logs/ubuntu-server/focal/daily-
live-20210209.log, for ppc64el it seems to be:
/usr/bin/mkisofs -r -V Ubuntu-Server\ 20.04.2\ LTS\ ppc64 -o
/srv/cdimage.ubuntu.com/scratch/ubuntu-server/focal/daily-live
Thanks, this looks good to me but out of an abundance of caution (this
is sudo, after all), I'm going to get Marc from the security team to
take a look -- it seems the upstream fixes for the CVE are a bit
different from the ones currently in Ubuntu and I'd like him to verify
that we think upstream
Do you have any idea when this will become a requirement? Just trying to
asses priorities.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915722
Title:
rustc 1.50 and cargo 0.51 will be required by
I don't see how this has anything to do with subiquity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go
Hi, can you try again with suiquity-channel=edge/lp1878041 please? If it
fails, and it's possible, can you attach the .crash file here? Error
reports to the tracker get truncated in ways that make them a bit less
useful for this sort of thing (it is also hard to find a specific
report).
The initra
Thanks for that. The failure is different now (which suggests my changes
have helped):
Running command ['sgdisk', '--new', '2:18432:2424585727', '--typecode=2:8300',
'/dev/mapper/mpathr'] with allowed return codes [0] (capture=True)
An error occured handling 'partition-1': ProcessExecutionError
Actually lets try something simple, can you try suiquity-channel=edge
/mwhudson-hack when this build finishes (probably in about 20 minutes,
but I'm going to bed): https://launchpad.net/~mwhudson/+snap/subiquity-
hack/+build/1267203
Also I'm glad to hear today's hirsute daily works!
--
You recei
mdadm definitely is installed in the installer's live environment. Why
do you think it is not? (It's not part of the apt repository at /pool on
the ISO because it is already installed in filesystem.squashfs)
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mdadm
Hm that's failing in the same sort of way. I've just pushed a new
version (0+git.5ef5b352) to edge/mwhudson-hack, can you try that?
Hopefully that will work better, or at least have more informative logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
It looks like the snap didn't get updated to the version from edge
/mwhudson-hack for that run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878041
Title:
installation fails creating user on large
Yes, it should be subiquity-channel=edge/mwhudson-hack on the kernel
command line
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878041
Title:
installation fails creating user on large multipath sys
This bug is believed to be fixed in curtin in version 21.2. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
** 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/1888062
Title:
autopkgtest became very flaky in Groovy
To manage notifications about this bug go to:
https://bugs.launch
Public bug reported:
The package in release ftbfs with gcc-10.
The package in proposed fails autopkgtests on all arches (and in
Debian), and is the last package preventing json-c from migrating.
It has no reverse depedencies.
So I think we should remove this package for now and see if we get a
Err. Just to check, you are booting with the right initramfs? Can you
share your pxe(linux emulation) config?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890884
Title:
kernel trace of 18.04.5 dai
Thanks, I merged your PRs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890397
Title:
console-conf cannot support canX and crashes
To manage notifications about this bug go to:
https://bugs.launch
Hi, we don't maintain console-conf in the archive any more so no need
for an SRU. You should probably talk to xnox about when it gets to
core20 -- I think we just need to merge main to the core/focal branch,
or cherry-pick the needed commits.
--
You received this bug notification because you are
Public bug reported:
It is obsolete and ftbfs.
** Affects: golang-1.13 (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/1891944
Title:
please
Public bug reported:
It ftbfs with gcc-10, has (as of a few minutes ago) no rdeps and only
ever existed to support installing Ubuntu that was released more than 10
years ago.
** Affects: syslinux-legacy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificati
Hi, is it correct to say that fixing this bug and bug 1882494 just
requires updating the patch we have to the current state of the
https://github.com/madler/zlib/pull/410 pull request? If so, the package
that is currently building at
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?
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
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
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
Great thanks for confirming. Are you able to test the packages mentioned
above? We don't have z15 hardware to test on (also bug 1884514 while
you're here :-p)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I've sponsored both patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887974
Title:
[20.04] Valgrind: PPC sync instruction L field should only be 2 bits
in ISA 3.0
To manage notifications a
I think the guided lvm view does not check it is not using the name of a
vg that already exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902845
Title:
20.10 server installer fails
To manage
So this is more a bug in multipath-tools then? I mean subiquity _could_
grow a feature for disabling multipath but I'd really rather not unless
this breakage is common.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Unfortunately not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this bug go to:
Are you using the 18.04 release? Can you try the most recent point
release instead, or upgrade the snap when you are offered the chance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806022
Title:
First of all, I'm sorry I appear to have been neglecting this bug. It's
hard to debug something you can't see! And I've had lots of other things
on my plate unfortunately.
I don't think anyone can claim with a straight face that casper-rw is
anything other than opaque. We could have an argument ab
Sorry for the slow response and thanks for the offer but I think we have
enough information to go on to debug this. Other things just keep on
coming up! Hopefully I can look at this tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I'll have a conversation with the release team about this. In the mean
time, I've updated https://people.canonical.com/~mwh/casper-initrd.gz
with one that might work better (no need to uncompress it btw).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hmm this is interesting, and maybe points to a bug in initramfs-tools :(
That /dev/disk/by-label directory should be populated by the time init-
top/udev exits.
Can you download and try again (added a bit more logging)? The zip of
all of /run is perfect.
--
You received this bug notification bec
Hi, I've uploaded yet another initrd -- I think this one might fix the
bug, hopefully. It seems that for whatever reason, it takes a long time
for the block device to show up at all in your system (seems it's more
the kernel being slow rather than udev lagging behind which is what I
suspected at fi
Public bug reported:
Usually we make the new version of Go as soon as it is released. This
time I forgot, so here's me asking for permission to do it waaay after
feature freeze.
1.14 has been the default in Debian for a while with no obvious major
problems.
The motivation is (a) RISC-V is only s
Here's the debdiff of my proposed fix
** Patch added: "lp-1863672.diff"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5348574/+files/lp-1863672.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I created https://github.com/CanonicalLtd/probert/pull/86 which is
hopefully a workaround/fix for this
--
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:
block probing fails with KeyError
** Changed in: subiquity
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870408
Title:
casper-md5check should leave a breadcrumb which apport, ubiquity,
subiquit
The crash is now
Traceback (most recent call last):
File
"/snap/subiquity/1999/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 144, in _probe
self._probe_once_task.task, 15.0)
File "/snap/subiquity/1999/usr/lib/python3.6/asyncio/tasks.py", line 358, in
wait_fo
So the udev data for /dev/nvme0n1 is:
/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1
N: nvme0n1
L: 0
S: disk/by-id/nvme-SAMSUNG_MZPLL3T2HAJQ-5_S4CCNE0M300015
S: disk/by-id/nvme-eui.344343304d300015002538450004
E: DEVPATH=/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0n1
E: S
This tiny patch to curtin https://paste.ubuntu.com/p/fbJVRmdBjz/ gets
past this crash. If your expeditious colleague would like to try
patching the subiquity snap with that and trying again, I'd be
interested to hear if that works!
--
You received this bug notification because you are a member of
cute time for each test: 5.8393 sec.
-
- ==
- Worker Balance
- ==
- - Worker 0 (159 tests) => 0:00:01.182108
- - Worker 1 (159 tests) => 0:00:01.607279
- - Worker 2 (159 tests) => 0:00:01.570729
- - Worker 3 (158 tests) => 0:00:01.650056
- make[1]: *** [deb
Thanks for testing the casper-rw fallback. I'll get that uploaded.
I see "ln: /tmp/mountroot-fail-hooks.d/scripts/init-premount/lvm2: No
such file or directory" message sometimes, I think it's harmless
(although I guess someone should look into it).
The superblock stuff does sound a bit worrying
It never ends, the failure is now
+ grub-install --target=x86_64-efi --efi-directory=/boot/efi
--bootloader-id=ubuntu --recheck
Installing for x86_64-efi platform.
grub-install: warning: efivarfs_get_variable:
open(/sys/firmware/efi/efivars/blk0-47c7b225-c42a-11d2-8e57
The crash file from the failed UEFI install is in comment #18, and
contains the probe data.
** Changed in: curtin
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Great, thanks for confirming.
I wonder if we should SRU this. You see it on Eoan I presume? The bug is
theoretically present in Bionic too aiui but if it never crops up I
don't know if it's worth it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** No longer affects: linux-azure (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Also affects: cloud-utils (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug not
They're not on an ISO yet but if you can try with the edge snap, you'll
get a subiquity with these patches. https://discourse.ubuntu.com/t/how-
to-test-the-latest-version-of-subiquity/12428 has a few ways you can do
this.
I would not expect UEFI installs to work yet but hopefully the BIOS
install
Argh. The unusual partition tables on ISOs continue to cause more pain.
I guess we should accelerate the work of not including unreferenced
disks in the curtin config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
So we believe this bug is now fixed but can you confirm Frank?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868246
Title:
No network after subiquity LPAR installation on s390x with VLAN
To manage
PS: I tested the ISO with serial 20200413
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847307
Title:
Install in english with italian keyboard - keyboard not set during
install
To manage notific
I can't reproduce this with the latest focal daily -- I followed the
instructions from comment #2 as closely as I could UEFI, selecting
install from boot menu, french language, french keyboard, custom
partitioning, and the layout was still active in the user creation
screen. It was a VM rather than
** Changed in: glibc (Ubuntu Groovy)
Status: Triaged => 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/1869364
Title:
glibc pwd/test-getpw test failures in autopkgtest
To manage n
attaching the debdiff so it can be included in the next upload
** Patch added: "glibc_2.31-0ubuntu10_2.31-0ubuntu11.patch"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1869364/+attachment/5388568/+files/glibc_2.31-0ubuntu10_2.31-0ubuntu11.patch
--
You received this bug notification b
** Changed in: subiquity (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/1879284
Title:
Cannot access shell in subiquity installer during automatic
in
IIRC one of the reasons console-conf-wrapper is implemented in shell is
because some of our target platforms were too slow / memory constrained
to run python as part of the boot process? Is that still true? Because
this is starting to get a little complicated for shell now...
--
You received this
I think this is fixed now, fwiw. I'll update the bug status in the
morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876942
Title:
rustc 1.43 and cargo 0.44 required by firefox 79
To manage n
** Changed in: subiquity
Status: Confirmed => In Progress
** Changed in: subiquity
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I think https://github.com/CanonicalLtd/subiquity/pull/794 implements
the logic described in comment #6 but I've entirely forgotten how to
test this code!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
There's something I don't understand about this bug though: it must be
that having the lxd snap seeded causes "snap managed" to be "true". That
seems wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Yeah, so I think there's two bugs here:
1) having the lxd snap around should not make `snap managed` be true
(this is a bug in snapd I think, although xnox said this might have been
fixed?)
2) console-conf should never suggest that the user logs in as lxd@
My branch fixes 2). If 1) unexpectedly
401 - 500 of 2201 matches
Mail list logo
