** Also affects: probert
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/2007510
Title:
probert resize tool output not logged on failure
To manage notifica
** Changed in: probert (Ubuntu)
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/1811279
Title:
probert --network throws stacktrace
To manage notifications about thi
*** This bug is a duplicate of bug 1811279 ***
https://bugs.launchpad.net/bugs/1811279
** This bug has been marked a duplicate of bug 1811279
probert --network throws stacktrace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** No longer affects: probert (Ubuntu)
** No longer affects: probert (Ubuntu Noble)
** No longer affects: probert (Ubuntu Plucky)
** Also affects: probert
Importance: Undecided
Status: New
** Changed in: probert
Status: New => Fix Committed
--
You received this bug notificati
** No longer affects: probert (Ubuntu)
** No longer affects: probert (Ubuntu Noble)
** No longer affects: probert (Ubuntu Plucky)
** Also affects: probert
Importance: Undecided
Status: New
** Changed in: probert
Status: New => Fix Committed
** Changed in: subiquity (Ubuntu Nob
> Is this something we still need to fix in probert itself? I see that
https://github.com/canonical/probert/pull/152 was closed. Is this a case
where the fix makes sense, but verification is hard?
Actually, probert is no longer in the archive so there is no testing to
be done at the archive level.
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: subiquity
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/bug
** Changed in: subiquity (Ubuntu Noble)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: subiquity (Ubuntu Noble)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that when installing Ubuntu with LVM + multipath, curtin adds a
filter for LVM. This allows the target system to avoid the situation
where LVM "steals" /dev/sdN devices that would normally be used by
multipath.
$ grep filter /target/etc/lvm/lvm.conf
filter = [ "a|/dev/disk/by-id/dm-uuid
I did further analysis on amd64 + qemu today.
I figured that the EBUSY error is caused by LVM creating a DM entry
(e.g. ubuntu--vg-ubuntu--lvm on a typical install) using paths such as
/dev/sda and /dev/sdb - before multipathd has a chance to start and
create the /dev/mapper/mpatha device.
After
For some reason, running the above steps without involving LVM (i.e., [
] Set up this disk as an LVM group) allows the disk to be detected
properly during the second installation ; and then it succeeds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: subiquity (Ubuntu Noble)
Milestone: None => ubuntu-24.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081778
Title:
storage probe validation fails for Windows dynamic disks "C
I run the same steps as Christian did and observed the same symptoms.
However
> [...] the installer properly detected the disk state.
Only on actually going to deployment did it crash.
Yes, it crashes but the state of the disks were not correctly detected
during the second install.
Instead of a
** Description changed:
Several users in private bugs have run into a common problem, where
curtin fails to parse the initial storage configuration with the
following error:
File
"/snap/ubuntu-desktop-installer/939/bin/subiquity/subiquity/server/controllers/filesystem.py",
line 852,
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a memb
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
Status: Fix Committed => Fix Released
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
** Changed in: subiquity (Ubuntu Plucky)
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/2095141
Title:
For OEM factory reset, reset GRUB option is not gen
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
Status: Fix Committed => Fix Released
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
Status: Fix Committed => Fix Released
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
Status: Fix Committed => Fix Released
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: subiquity
Status: New => Fix Released
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committe
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification beca
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
** Changed in: subiquity (Ubuntu Plucky)
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/2104310
Title:
Plucky arm64 desktop: boot console showing on seria
The fix is included in Subiquity 25.04
https://github.com/canonical/subiquity/releases/tag/25.04
** Changed in: subiquity
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.launch
** Changed in: ubuntu
Status: Fix Committed => Fix Released
** Changed in: subiquity (Ubuntu)
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/2107381
** Attachment added: "binary_bios_measurements-after-reboot"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872331/+files/binary_bios_measurements-after-reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "490995999_685386237521061_4162562558058417091_n.jpg"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872332/+files/490995999_685386237521061_4162562558058417091_n.jpg
--
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "490992766_1361809688361599_7545049647696778749_n.jpg"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872333/+files/490992766_1361809688361599_7545049647696778749_n.jpg
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "binary_bios_measurements-live-installer"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872330/+files/binary_bios_measurements-live-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello Mate, hello Chris,
I did another install and tried booting the target system from the exact
same menu but it still asked me for the recovery key.
Quickly after powering on the laptop, I hit F12 - "One-Time Boot
Settings" then select the USB media if I want to boot the installer - or
select
Reproduced by creating a VM using virt-manager on a plucky amd64 host.
After selecting "Reboot now", only a blinking cursor was visisble.
Switching to the serial console and pressing enter actually started the
shutdown sequence.
--
You received this bug notification because you are a member of U
Same result when installing 24.10 - so not a regression in that sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107457
Title:
Can't boot after installation with TPM backed FDE on xps9320
To m
Same result if I skip the "passphrase" screen during the installation.
** Description changed:
- I tried on two different XPS 9320 units.
+ I tried installing Ubuntu 25.04 desktop with TPM backed FDE on two
+ different XPS 9320 units.
The installation seems to succeed.
However, on first
Logs from second install
** Attachment added: "install-logs-2025-04-16.1.txz"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872093/+files/install-logs-2025-04-16.1.txz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Logs from first install
** Attachment added: "install-logs-2025-04-16.0.txz"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2107457/+attachment/5872092/+files/install-logs-2025-04-16.0.txz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
I tried on two different XPS 9320 units.
The installation seems to succeed.
However, on first boot, it is asking me for a recovery key.
Please enter the recovery key for volume ubuntu-data-a2b3ba2e-2555-4957-a47b-948
04d4c119 for device /dev/disk/by-uuid/6bdc5a11-5d7d-4d64-
** Changed in: subiquity
Status: In Progress => Fix Committed
** Changed in: ubuntu
Status: In Progress => 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/2107381
Title:
z
Hello,
It is not obvious to me yet that this is an installer bug. Did it happen
while installing Ubuntu?
Here's what the DpkgTerminalLog says:
Processing triggers for linux-image-6.11.0-21-generic (6.11.0-21.21) ...^M
/etc/kernel/postinst.d/initramfs-tools:^M
update-initramfs is disabled since r
** Also affects: subiquity
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin
Status: In Progress => Fix Committed
** Changed in: subiquity
Status: New => In Progress
--
You received th
** Changed in: subiquity (Ubuntu)
Status: In Progress => 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/2107381
Title:
zfs + encryption fails with plucky iso dated 20250415 - Re
Pull request for main (includes other changes):
https://github.com/canonical/subiquity/pull/2195
Pull request for plucky (single commit):
https://github.com/canonical/subiquity/pull/2196
** Changed in: subiquity (Ubuntu)
Status: New => In Progress
--
You received this bug notification
The guided TUI bits (at least when it comes to offering the installation
media as the target disk) should be addressed by
https://github.com/canonical/subiquity/pull/2194. This won't prevent
further use of the installation media in the manual partitioning screen
though.
--
You received this bug n
IIRC, the order of disks in the list is determined by their size (i.e.,
the largest disk comes first).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106499
Title:
Installation fails with 'OSError:
I guess we could read the MMC_TYPE [1] variable and add it to the label
somehow. But that would be very much specific to MMCs.
IMO, we should start by removing the installation media from the list
(or graying it out).
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/dri
Using the probe-data from bug 2107318:
$ jq '.blockdev[] | select(.DEVTYPE | test("disk")) | {DEVNAME, ID_SERIAL,
MMC_TYPE}' probe-data.json
{
"DEVNAME": "/dev/mmcblk0",
"ID_SERIAL": "0xc64a48e1",
"MMC_TYPE": "MMC"
}
{
"DEVNAME": "/dev/mmcblk0boot0",
"ID_SERIAL": "0xc64a48e1",
"MMC_TY
** Changed in: subiquity (Ubuntu Plucky)
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/2104087
Title:
segfault at 1 ip 761167255720 sp 7ffd725da1
** Changed in: subiquity (Ubuntu Plucky)
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/2099893
Title:
[FFE] Support reading the GPT partition name in Sub
** Changed in: subiquity (Ubuntu)
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/2084012
Title:
Network disconnect when booting the NVMe/TCP installed sys
** Changed in: subiquity (Ubuntu Plucky)
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/1941889
Title:
[FFE] Enhancing 'autoinstall-user-data' with s390x
** Changed in: subiquity (Ubuntu Plucky)
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/2045688
Title:
RAID configuration list looks empty when disk label
** Changed in: subiquity (Ubuntu Plucky)
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/2060894
Title:
dialogue won't start, high cpu usage
To manage not
** Changed in: subiquity (Ubuntu)
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/2104267
Title:
autoinstall fails to execute zdevs entries, reports ZdevCo
** Changed in: subiquity (Ubuntu)
Milestone: ubuntu-25.04 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104249
Title:
Subiquity installer crashed NotExclusiveError
To manage notificati
** Changed in: subiquity
Status: Triaged => Fix Committed
** Changed in: subiquity (Ubuntu)
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/2084012
Title:
N
Marking invalid for ubuntu-desktop-provision since we disabled the WLAN
listener on desktop.
** Changed in: ubuntu-desktop-provision
Status: New => Invalid
** Changed in: probert (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: subiquity (Ubuntu Noble)
Status: In P
** Changed in: subiquity (Ubuntu Noble)
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/2045688
Title:
RAID configuration list looks empty when disk label is too long
Reading the logs again for this bug report, it looks similar to LP:
#2106499, where the block device selected as the target contains the
installer.
The difference here is that mmcblk0 is present - but for some reason not
selected.
--
You received this bug notification because you are a member of
** Summary changed:
- Installation fails with 'OSError: [Errno 16] Device or resource busy:
'/dev/mmcblk1p3''
+ Installation fails with 'OSError: [Errno 16] Device or resource busy:
'/dev/mmcblk1p3'' (target device contains the installer)
--
You received this bug notification because you are a
** Changed in: subiquity (Ubuntu Noble)
Status: In Progress => 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/2045688
Title:
RAID configuration list looks empty when disk label i
I suppose so, we had to relax these checks to make it possible to
install from a recovery partition. But it made the TUI worse for more
standard scenarios.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
After further discussion, it appears that only mmcblkp1 (the SD-card)
was detected by the installer - so was the only option for installation.
Begin: Loading essential drivers ... [7.554515] mmc0: Failed to
initialize a non-removable card
--
You received this bug notification because you are
Hello Heinrich,
Looking at the probe-data, it looks like mmcblk1 is flashed with the
installer ISO. I assume we won't be able to use it as the target if
that's where the installer is loaded from?
Is it possible on this board to have the installer loaded on a different
device than the MMC - assumi
Hello @anaghk-dos
> Would it be possible to also backport this for 22.04 please? It's
still in the standard support window and that's where the bug was
originally reported from.
We're managing 22.04 and 24.04 slightly differently. We don't have a dedicated
subiquity snap track for 22.04, like we
Backport PR to noble: https://github.com/canonical/subiquity/pull/2192
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045688
Title:
RAID configuration list looks empty when disk label is too long
T
** Changed in: subiquity
Status: In Progress => Fix Committed
** Changed in: subiquity (Ubuntu Noble)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: subiquity (Ubuntu Plucky)
Status: In Progress => Fix Committed
** Changed in: subiquity (Ubu
ity
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: subiquity
Status: Triaged => In Progress
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in:
** Description changed:
- TBD
+ The move from core22 to core24 broke the network TUI screen in two ways:
+
+ * After moving from "disabled" to DHCP, the IP will not be visible once the
lease has been acquired. This is because of a mismatch between Subiquity's Link
instance and the one that prob
** Changed in: subiquity (Ubuntu)
Status: New => Fix Committed
** Changed in: subiquity
Status: In Progress => 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/2105510
Title:
https://github.com/canonical/probert/pull/154
** Also affects: probert (Ubuntu)
Importance: Undecided
Status: New
** Changed in: probert (Ubuntu)
Status: New => In Progress
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity
** Changed in: subiquity
Status: In Progress => Fix Committed
** Changed in: subiquity (Ubuntu)
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/2104087
Title:
** Also affects: probert (Ubuntu Plucky)
Importance: High
Status: Fix Committed
** Also affects: subiquity (Ubuntu Plucky)
Importance: High
Status: Fix Committed
** Also affects: probert (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: subiquity (Ub
** Changed in: probert (Ubuntu)
Status: New => Fix Committed
** Changed in: subiquity
Status: Incomplete => 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/2060894
Title:
di
For testing, I used kvm-test:
$ scripts/kvm-test.py --install --iso /srv/iso/plucky-live-server-
amd64.iso --recreate-target --nic user,model=virtio-net-
pci,hostfwd=tcp::-:22,net=10.0.2.0/24 --nic user,model=virtio-net-
pci,net=10.0.3.0/24
I am requesting two network interfaces because I wan
It is a bit annoying.
If we want the ability to install such packages before first boot, we'd
need a way to run snapd in the target system.
Otherwise, the option is probably to install packages on first boot,
like we do with snaps.
I suspect listing the packages in autoinstall.user-data.packages
Backport for noble:
https://github.com/canonical/subiquity/pull/2189
** Also affects: probert (Ubuntu Plucky)
Importance: Undecided
Status: Fix Committed
** Also affects: subiquity (Ubuntu Plucky)
Importance: Undecided
Status: Fix Committed
** Also affects: probert (Ubuntu N
Backport for noble:
https://github.com/canonical/subiquity/pull/2189
** Also affects: probert (Ubuntu Plucky)
Importance: Undecided
Assignee: Olivier Gayot (ogayot)
Status: Fix Committed
** Also affects: subiquity (Ubuntu Plucky)
Importance: Undecided
Status: Fix
** Changed in: subiquity (Ubuntu)
Status: New => Fix Committed
** Changed in: subiquity
Status: In Progress => 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/2060894
Title:
** Changed in: probert (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: subiquity
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/2105510
Title:
n
** Changed in: probert (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: probert (Ubuntu)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Milestone
** Changed in: subiquity
Importance: Undecided => High
** Changed in: probert (Ubuntu)
Importance: Undecided => High
** Changed in: subiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: subiquity
Status: In Progress => Fix Committed
** Changed in: subiquity (Ubuntu)
Status: In Progress => 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/2104267
It is a bit of a blind guess, but I think the below PR could fix the
issue:
https://github.com/canonical/probert/pull/153
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060894
Title:
dialogue won't
*** This bug is a duplicate of bug 2104087 ***
https://bugs.launchpad.net/bugs/2104087
** This bug has been marked a duplicate of bug 2104087
segfault at 1 ip 761167255720 sp 7ffd725da1a0 error 4 in
_nl80211.cpython-310-x86_64-linux-gnu.so
--
You received this bug notification be
** Also affects: probert (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/2104087
Title:
segfault at 1 ip 761167255720 sp 7ffd725da1a0 error
** Summary changed:
- Subiquity installer crashed
+ Subiquity installer crashed NotExclusiveError
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104249
Title:
Subiquity installer crashed NotExclusi
*** This bug is a duplicate of bug 2104249 ***
https://bugs.launchpad.net/bugs/2104249
** This bug has been marked a duplicate of bug 2104249
Subiquity installer crashed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: subiquity
Status: New => In Progress
** Changed in: subiquity
Assignee: (unassigned) => Olivier Gayot (ogayot)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 2104249 ***
https://bugs.launchpad.net/bugs/2104249
** This bug has been marked a duplicate of bug 2104249
Subiquity installer crashed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I opened https://github.com/canonical/subiquity/pull/2183 as a tentative
to fix this issue. Will need to be tested on real hardware though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104267
Title:
** Changed in: subiquity (Ubuntu)
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/2104267
Title:
autoinstall fails to execute zdevs entries, reports ZdevControlle
The code that sets ZdevController.zdevinfos is only run in dry-run mode.
When running an actual installation, we should either initialize
ZdevController.zdevinfos using `lszdev()` or not rely on zdevinfos at
all.
** Changed in: subiquity (Ubuntu)
Status: New => Triaged
** Changed in: subi
Hello Heinrich,
Just to be sure I understand the problem. Are we only talking about end0
(which appears to be running DHCP but doesn't show its IP address - even
though it supposedly has one. Or are we talking about end1 which is
marked as "autoconfiguration failed"?
--
You received this bug not
With Nick's upload of systemd (thanks Nick!) + the subiquity patch from
https://github.com/canonical/subiquity/pull/2182, I think we're just
waiting for new dailies now.
** Changed in: subiquity
Status: New => Fix Committed
** Changed in: subiquity (Ubuntu)
Status: In Progress => Fi
1 - 100 of 503 matches
Mail list logo
