** 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/1770305
Title:
ssh-import-id lp:$missing-user attempts to par
"This then causes the install to fail." what do you mean by this? The
screenshots you've posted look fine to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768632
Title:
installer static IPv4 DN
Ah so I think what's happening here is that when you select "use
DHCPv6", the nameservers configured when you configured IPv4 are
forgotten. If you configure DHCPv6 first and then configure IPv4 does
that work?
This clearly isn't sensible behaviour.
--
You received this bug notification because
Thanks for checking. I wasn't meaning to propose what you did as a
solution, although it just about qualifies as a workaround I guess, but
by doing that you confirmed my suspicions as to what the problem was!
** Changed in: subiquity
Status: Incomplete => Triaged
** Summary changed:
- ins
** Description changed:
+ [Impact]
+ Invoking ssh-import-id gh:$missing_user in a non-interactive context produces
no output.
+
+ [Test case]
+ "ssh-import-id gh:mwhudso 2>&1 | cat" should output "no such user" or some
similar helpful messsage, not nothing at all.
+
+ [Regression potential]
+
** Description changed:
+ [Impact]
+ Invoking ssh-import-id lp:$missing_user produces unhelpful, noisy error.
+
+ [Test case]
+ "ssh-import-id lp:mwhudso" should output "no such user" or some similar
helpful messsage, not pages of complaints about a file in /tmp not being a
public key file.
+
** 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/1570997
Title:
fail if HOME environment variable is not set
** Description changed:
[Impact]
Invoking ssh-import-id lp:$missing_user produces unhelpful, noisy error.
I want to change subiquity to invoke ssh-import-id directly and helpful
error messages are important in giving useful feedback to the user.
[Test case]
"ssh-import-id lp:mwhu
Verification completed, I tested this version:
$ dpkg-query -W ssh-import-id
ssh-import-id 5.7-0ubuntu1.1
on my bionic install, I tested importing keys from an non-existing
username
$ ssh-import-id mwhudso
2018-05-20 22:17:21,328 ERROR Launchpad user not found. status_code=404
user=mwhudso
a
Verification done on bionic.
$ dpkg-query -W ssh-import-id
ssh-import-id 5.7-0ubuntu1.1
$ ssh-import-id gh:mwhudso 2>&1 | cat
2018-05-20 22:47:00,209 ERROR Username "mwhudso" not found at GitHub API
$ ssh-import-id gh:mwhudson 2>&1 | cat
2018-05-20 22:47:03,645 INFO Already authorized ['1024',
We're planing to have version 17.12 for bionic.
On 13 March 2018 at 06:58, xantares wrote:
> Public bug reported:
>
> Hello maintainer,
>
> The docker version 17.03 (bionic) in ubuntu doesn't allow the statx
> syscall which is needed to build qt >=5.10 applications:
> https://github.com/docker/f
** Bug watch added: github.com/docker/for-linux/issues #208
https://github.com/docker/for-linux/issues/208
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755250
Title:
backport statx syscall whit
** 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/1750873
Title:
Long delay on boot without any feedback is disconcert
I guess we could be totally unsubtle and do this:
https://code.launchpad.net/~mwhudson/livecd-
rootfs/lp-1743643/+merge/341440
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743643
Title:
Install to
** Changed in: casper (Ubuntu)
Status: Confirmed => 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/1743643
Title:
Install to dirty disk with swap fails
To manage notifications abo
** Changed in: casper (Ubuntu)
Status: In Progress => Invalid
** 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/1
For the record, the plan for the live server installer is to run “snap
set core refresh.hold=$(date --date=now+60days --iso-8601=seconds)”
fairly early on. If people leave their live sessions going for 60 days,
so be it…
--
You received this bug notification because you are a member of Ubuntu
Bug
On 21 March 2018 at 22:23, Iain Lane wrote:
> On Wed, Mar 21, 2018 at 08:13:23AM -0000, Michael Hudson-Doyle wrote:
> > For the record, the plan for the live server installer is to run “snap
> > set core refresh.hold=$(date --date=now+60days --iso-8601=seconds)”
> > fairl
I should have commented here before, I'm waiting for slangasek or
infinity to review this one. There should be an artful upload yes but
that can wait for a bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I had a quick look at unbound, it seems quite difficult. People who
install unbound probably want it so they can have DNSSEC supported in
their local resolver which we can't really do by integrating with
resolved. OTOH, if installing unbound replaces (in some sense) resolved
and everything else int
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The code in 05localechooser assumes that if grep -q ^LANG=
/target/etc/default/locale succeeds it's managed to configure the
locale. But that file defaults to LANG=C.UTF-8 now and so localechooser
never sets the locale.
** Affects: localechooser (Ubuntu)
Importance: High
I wasn't planning on doing the xenial back port myself, but I can if you
want...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759003
Title:
cloud-init fails for minimal images (can't find locale-g
If you used ubuntu-18.04-server-amd64.iso this isn't a bug in subiquity
but some part of d-i.
** Project changed: subiquity => debian-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
if this was a live-server install, would it be possible to see the
contents of the /var/log/installer directory from the live session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768617
Title:
In
** Project changed: subiquity => debian-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768171
Title:
Manual partitioning with encrypted root and unencrypted swap gets
stuck
To
I have verified the fix for bionic and disco by doing netinstalls with
apt-setup/proposed=true on the kernel command line with disk images that
had had a raid6 with 0.90 metadata created on them and watching the
output of wipefs $image outside of the VM. Immediatly before selecting
the "write chang
Public bug reported:
will close this soon
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: subiquity (not installed)
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20
I've now done the testing asked for in comment #10, verifying that
additional disks are not touched by installing to one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828558
Title:
installing ubun
Public bug reported:
In an eoan armhf container on a disco arm64 vm:
root@helped-oyster:~# gdb /bin/true
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
...
(gdb) r
Starting program: /usr/bin/true
Program received signal SIGSEGV, Segmentation fault.
0xf7fc8ee0 in ?? () from /lib/ld-linux-armhf.so.3
It happe
I don't really know what is happening here but I suspect pretty strongly
it's related to systemtap static probes, because if I do this:
root@helped-oyster:~# cp /lib/ld-linux-armhf.so.3 .
root@helped-oyster:~# objcopy -R .note.stapsdt ld-linux-armhf.so.3
ld-linux-armhf.so.3-nostap
root@helped-oy
No.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841006
Title:
gdb reports a segfault in ld-linux.so.3 on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
I've just uploaded the patch to the disco, bionic and xenial in ppa
:ubuntu-mozilla-security/rust-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841191
Title:
"error: failed to acquire packa
I don't see how this could be p9 specific? And I thought this got fixed
fairly recently...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846254
Title:
subiquity netboot allowed booting missmatched
Oops, sorry for the disruption. Yes, having "nopersistent" suppressing
this behaviour makes sense to me.
Is there any way we could have found out about this breaking your use
case earlier? casper has tests now, so if you can describe other use
cases sufficiently precisely we can make sure we keep
I've uploaded a fix to eoan UNAPPROVED.
** Changed in: casper (Ubuntu Eoan)
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/1846762
Title:
automatic creation of casp
> Let's add a livecd-rootfs task, as livecd-rootfs marks it as
automatic.
But that's fine though, it's the installer that should mark the required
if they are in fact being used by the particular install configuration
the user selects.
** Changed in: livecd-rootfs (Ubuntu Eoan)
Status: Tri
That said, it does seem attempts have been made to fix it in livecd-
rootfs before. I wrote this https://git.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-
rootfs/commit/?id=b235dfb718730a0a83fec0a1b366ddef8468a0b5 but I'm not
sure about landing this in the space between now and release unless
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-
rootfs/+merge/373789
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received th
I downloaded the squashfses for all the flavours and none of them are
affected by this bug (either cryptsetup is not marked automatically
installed or a metapackage depends on it and will keep it installed) so
I don't think this is super critical for release.
--
You received this bug notification
Following a hint from Adam, I propose this change
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373794
which should fix the bug properly (not tested though).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
That didn't quite work so I had another go:
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/373809
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841672
Title:
CryptSetup packages
The reason that I argued for the importance to be lowered is that I'm
not super confident about fixing it on a short turnaround without
causing other problems. In disco and before, casper would mount the
entire device (say /dev/sdb) containing the installation media (i.e.
mount /dev/sdb not /dev/sd
I fixed this in grub recently, although only for multipath, not other uses
of device mapper. grub-mkconfig and whatever makes fstab files should be
consistent I guess...
On Thu, 10 Oct 2019, 11:25 Dimitri John Ledkov,
wrote:
> And given that we have identical stock VG and LV names across all
> i
In what follows, the ubuntu-${series}-core-cloudimg-amd64-root.tar.gz
tarball is the current tarball from https://partner-
images.canonical.com/core/ and livecd.ubuntu-
base.rootfs-${series}.tar.gz is a test build I made with -proposed
enabled (see build pages at
https://launchpad.net/~mwhudson/+li
Well ok but those are currently deleted downstream anyway by
https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh#L91.
Do you want to submit a patch there and then we can patch it here too? In
the mean time I still would like to release this change.
On Fri, 10 May 2019, 19:30 Ju
I'm glad you got your system working again. Not a bug in the docker.io
package though.
** Changed in: docker.io (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/182
Can you filter that list to source packages that build non-arch-all
binary packages? They are the ones that will need to be rebuilt once the
go.crypto has been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
The runc currently in xenial is too old for the new version of
containerd, so I need to upload containerd with a more appropriate
dependency.
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
** Changed in: containerd (Ubuntu Xenial)
Status: Fix Committe
Ah sorry for imprecision, I was indeed only referring to the apt bits.
On Thu, 16 May 2019, 18:25 Christian Ehrhardt , <1829...@bugs.launchpad.net>
wrote:
> FYI: /usr/share/locales have 7MB in ubuntu:latest as of 15th of May
>
> --
> You received this bug notification because you are a member of
Ugh.
I don't see what subiquity can do differently here, we're just making
snapd api calls, it seems to me (and I don't just want to be seen as
passing the buck) that snapd is the right place to solve this (or even
the store: it could detect the request is coming from an internal IP and
not return
Hm so it sounds like snapd's behaviour is what Dimitri is asking for
here? Has this changed in snapd recently (note that this behaviour was
observed during the disco release sprint, so April 2019).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: partman-base (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: partman-base (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:/
** Description changed:
- 18.04 is installed using GUI installer in 'Guided - use entire volume'
- mode on a disk which was previously used as md raid 6 volume. Installer
- repartitions the disk and installs the system, system reboots any number
- of times without issues. Then packages are upgrade
I had a stab at this
https://code.launchpad.net/~mwhudson/ubuntu/+source/grub2/+git/grub2/+merge/370896
-- all comments welcome! (my brain now hurts)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14293
** Changed in: grub2 (Ubuntu)
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.net/bugs/1429327
Title:
Boot from a unique, stable, multip
hanged in: partman-base (Ubuntu Bionic)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: partman-base (Ubuntu Disco)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Bu
Turns out my fix is wrong: it is clearing the superblocks in NEW_LABEL,
but really the disk should not be touched until COMMIT.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco
** Tags added: verification-failed verification-failed-bionic
verification-fai
** Changed in: partman-base (Ubuntu)
Status: Fix Released => 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/1828558
Title:
installing ubuntu on a former md raid volume makes system
** Changed in: partman-base (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/1828558
Title:
installing ubuntu on a former md raid volume makes system
I had a look at this and got pretty confused! Feels more like a kernel
problem than a casper one, somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840122
Title:
System fails to reboot from li
Verification done on bionic and cosmic; xenial needs another fix for
runc which is currently in UNAPPROVED.
There are autopkgtest failures for ubuntu-fan on bionic but these are
only because of systemd messages on stderr that are ignored in cosmic
and up.
** Tags removed: verification-needed-cosm
** Also affects: livecd-rootfs (Ubuntu Disco)
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/1829944
Title:
magic-proxy does not send along headers for err
OK everything looks good on Xenial too now, all autopkgtests green.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
So I think what's happening here is that finalrd.sh is getting killed
because it's running for more than 90s and so the hooks don't get to
copy all needed libraries to /run/initramfs (maybe this was obvious, but
it wasn't to me). The open-iscsi tests boot an image in system emulation
without any kv
** Also affects: cargo (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: cargo (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Xenial)
Importa
** Changed in: cargo (Ubuntu)
Status: New => Fix Released
** Changed in: rustc (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/1852982
Title:
rustc
I am still reading this (although busy, hence the delay). I quite
strongly don't want to change the default but maybe we can make it
easier to disable than applying sed to the entire ISO (!). Probably the
forums or discourse.ubuntu.com would be a better place to discuss this.
--
You received this
I finally got around to reporting this upstream as
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
** Bug watch added: Sourceware.org Bugzilla #25215
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Oh good spot. So the issue is that the install of oem-config-debconf at
the end of the install fails because ubiquity's recommends did not get
updated to care about the split of grub-efi into grub-efi-amd64 and
grub-efi-arm64. We can fix this in ubiquity I think.
** Package changed: debian-install
In general I would prefer to do more things in livecd-rootfs and fewer
in casper, but if you need the device serial then yeah, I guess we need
to do this in casper.
** Changed in: casper (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubun
** Also affects: ubiquity (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I think this got fixed in ubuntu11, but there are more test failures
yet, see bug 1854237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853383
Title:
autopkgtest regression in test_add_proc_info
T
** Changed in: rustc (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: rustc (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: rustc (Ubuntu Disco)
Status: New => Fix Released
** Changed in: rustc (Ubuntu Eoan)
Status: New => Fix Released
** Changed
subiquity should definitely reprobe on udev events. The only question in
my mind is whether we should do a full reprobe on each event (or, well,
group of events, let's not be daft) or try to be clever and more
incremental, e.g. only probing for each new device as it appears. I
guess we can implemen
** Also affects: cargo (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: cargo (Ubuntu)
Status: New => In Progress
** Changed in: rustc (Ubuntu)
Status: New => Fix Released
** C
** Changed in: cargo (Ubuntu Xenial)
Status: New => In Progress
** Changed in: cargo (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cargo (Ubuntu Disco)
Status: New => In Progress
** Changed in: cargo (Ubuntu Eoan)
Status: New => In Progress
--
You receiv
** Changed in: rustc (Ubuntu Disco)
Status: In Progress => Fix Released
** Changed in: rustc (Ubuntu Bionic)
Status: In Progress => Fix Released
** Changed in: rustc (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: rustc (Ubuntu Xenial)
Status: Fix
This is a bit strange. FWIW, this test has never passed properly on
focal, the test doesn't really test anything until the cloud images
appear and they weren't there for the first couple of tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
This is the failure:
(initramfs) losetup -f
loop: can't get info on device /dev/loop1: No such device or address
And it reflects behaviour in the focal live-server images too, i.e. they
are completely broken. Fun.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
So this was somehow caused by the ftbfs fix for klibc. On my eoan
system:
mwhudson@anduril:~/images$ sudo /usr/lib/klibc/bin/losetup -f
loop: can't get info on device /dev/loop30: No such device or address
mwhudson@anduril:~/images$ sudo apt install klibc-utils=2.0.6-1ubuntu1
libklibc=2.0.6-1ubun
We found the issue -- I think xnox is going to report it via proper
channels. But basically it's this:
sizeof(dev_t) = 4 sizeof(__kernel_old_dev_t) = 8
This makes the kernel's loop_info 8 bytes bigger than klibc's and so the
kernel is writing past the end of the loopinfo on the stack, which unti
Public bug reported:
I have no further information, sadly. The boot stops at the message "EFI
stub: UEFI Secure Boot is enabled". Disabling secure boot or selecting
an older kernel both work fine.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received
mwhudson@anduril:~$ apport-collect 1843860
dpkg-query: no packages found matching linux
** Changed in: linux (Ubuntu)
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/b
Update: disabling TPM is enough to allow boot.
>From dmidecode:
Handle 0x000C, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 20L8S7X100
Version: ThinkPad T480s
Serial Number: xxx
UUID: xxx
Wake-up Type: Power Switch
*** This bug is a duplicate of bug 1844101 ***
https://bugs.launchpad.net/bugs/1844101
Yes, I assume it's the same bug. Julian and I were actually sitting next
to each other yesterday trying to diagnose things. As the other bug has
logs, let's mark this a duplicate of the other.
** This bug h
** Also affects: cargo (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: cargo (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: rustc (Ubuntu Xenial)
Importa
rustc uploaded to eoan now but debian doesn't have the new cargo yet so
going to wait and see if they do that before I have to do it myself...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843765
Tit
The brain dead fix would be to paste the definition of try_mount into
lupin-helpers I guess. The more elegant thing would be to fix the issue
that was the reason I removed try_mount: you can end up unmounting
previously mounted filesystems.
It has to be said, the description of the lupin-casper pa
** Package changed: efibootmgr (Ubuntu) => efivar (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844320
Title:
efibootmgr -v UiAppCould not parse device path
To manage notifications about
Thanks for the report, and congratulations on figuring out what was
going on! I can see why the behaviour is as described on a very shallow
level: xenial postrm masks both the service and socket units but the
bionic postinst just unmasks the socket. Deeper than that, I really
don't know. The way th
try_mount got readded to casper in 1.418 so this is fixed now.
** Changed in: casper (Ubuntu)
Status: New => Fix Released
** Changed in: lupin (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is the same bug as bug 1844101 I think? If it is, it doesn't
reproduce with secure boot off and we'll need a signed kernel to test.
I'm happy to enrol whatever key in my firmware to test a self-signed
kernel...
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
I guess this is actually a bug in some partman component, but well. In
both the desktop and ubuntu studio installers for eoan beta, I was
offered the installation media as a target disk. This seems unlikely to
be correct.
** Affects: ubiquity (Ubuntu)
Importance: Undecid
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
** This bug is no longer a duplicate of bug 1844101
5.3.0-10 crashes immediately in init_tis -> ... -> tpm_init -> ... ->
tpm_tis_core_init.cold -> ... (never boots)
** This bug has been marked a duplica
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
Bug 1845454 was filed later but has more useful comments, so I'm going
to mark this a duplicate of that.
** This bug has been marked a duplicate of bug 1845454
Kernel panic with 19.10 beta image
--
You
*** This bug is a duplicate of bug 1845454 ***
https://bugs.launchpad.net/bugs/1845454
** This bug is no longer a duplicate of bug 1844101
5.3.0-10 crashes immediately in init_tis -> ... -> tpm_init -> ... ->
tpm_tis_core_init.cold -> ... (never boots)
** This bug has been marked a duplica
It's on the roadmap for 19.04. I'll make sure to update this bug when
there is stuff to test via snap refresh!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680245
Title:
subiquity does not take in
Hm the installer is definitely *meant* to restart on the serial line
after refresh but I haven't tested this in a while. Logs should have
been written to the USB stick, can you attach them to this report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
301 - 400 of 2201 matches
Mail list logo
