On Wed, 21 Nov 2018 at 06:41, Nick Zaccardi <1803...@bugs.launchpad.net>
wrote:
> Hi Michael,
>
> I am now noticing that the installer is indeed throw an error. I am not
> sure if that was happening previously, I certainly didn't notice it in
> any case. The attached log is from /var/log/curtin/in
I have tested that this change works as designed, a system installed
with the current bionic live server daily has the expected contents of
/etc/apt/sources.list.
I haven't explicitly tested that all other bionic images are still
working as designed and I'm not really sure how to. All the automate
I tested this by booting a live-server ISO, running systemd-cat -t
testing seq 1 and checking that all 10001 lines of output ended up
in the journal.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this
I'm not incredibly happy about this approach (doing it in pam_env.so
would be best I think) but it does the job for now. I verified this in a
minimal bionic image with and without base-files from proposed and the
behaviour was as expected.
** Tags removed: verification-needed verification-needed-b
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/1789920
Title:
Installation in OEM mode broken on bionic
To manage notifications about this bug
Oh wait no it does boot, it just takes a very very long time. Dariusz,
how long did you wait for it to boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Installation in OEM mode br
nee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Also affects: probert (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/1797342
Title:
c
ial for
regression.
** Changed in: probert (Ubuntu Bionic)
Status: New => In Progress
** Changed in: probert (Ubuntu Bionic)
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: probert (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received th
** Description changed:
[Impact]
Without this fix we end up creating /var/log/opal-prd.log file with root
user. Hence rsyslogd will not be able to write data to this file. Hence we will
not have enough opal-prd logs for debugging.
[Test Case]
- - Installed fixed version of opal-prd pack
Ahh silly me 1.34.1 added the fix to debian/patches but it's a native
package.
** Changed in: dh-golang (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed verification-failed-bionic
--
Yo
snapd built successfully with the golang-1.10 from bionic-proposed here:
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=snapd&field.status_filter=published&field.series_filter=bionic
I ran through the smoke test as well:
mwhudson@ringil:/tmp$ PATH=/usr/lib/go-1
Ah, thanks for the improved test case. I've been through the steps
(boring transcript below) and also verified the fix.
ubuntu@dradis:~$ systemctl status opal-prd
● opal-prd.service - OPAL PRD daemon
Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor
preset: enabled)
Acti
Verification done on Xenial:
root@xenial:~# PATH=/usr/lib/go-1.10/bin:$PATH
root@xenial:~# go version
go version go1.10.4 linux/amd64
root@xenial:~# cat > trivial.go
package main
func main() {}
root@xenial:~# go run trivial.go
root@xenial:~# cat > trivialcgo.go
package main
import "C"
func main()
And trusty:
root@trusty:~# PATH=/usr/lib/go-1.10/bin:$PATH
root@trusty:~# go version
go version go1.10.4 linux/amd64
root@trusty:~# cat > trivial.go
package main
func main() {}
root@trusty:~# go run trivial.go
root@trusty:~# cat > trivialcgo.go
package main
import "C"
func main() {}
root@trusty:~#
Public bug reported:
[impact]
elfutils ftbfs on sid on arm64 currently:
FAIL: run-backtrace-dwarf.sh
0xb3c5373c raise
0xb3c418e8 abort
/<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null)
dwarf: no main
FAIL run-backtrace-dwarf.sh (exit status: 1)
FAIL
** Also affects: elfutils (Ubuntu Cosmic)
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/1798700
Title:
ftbfs on arm64
To manage notifications about this
** Also affects: docker.io (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: docker.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: docker.io (Ubuntu Xenial)
** Also affects: docker.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: docker.io (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu Xenial)
Status: New => Triaged
** Changed in: docker.io (Ubuntu Bionic)
Sta
** Description changed:
- I have downloaded the 18.04.1 iso with alternative (legacy) installer.
+ [impact]
+ Users booting a device for customization in OEM mode have to switch to
another vt to log in (and it's not very obvious at all that you can do this)
+ [test case]
I took the following
As above, the build passing is a sufficient test for this.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
mod (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: kmod (Ubuntu Bionic)
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
** Description changed:
+ [impact]
+ installation of docker can fail trying to create the docker group if it
already exists
+
+ [test case]
+ # addgroup docker
+ # apt install docker.io
+
+ [regression potential]
+ The change to fix this but is small and clear:
https://github.com/tianon/debian
** Description changed:
+ [impact]
+ docker.io now prompts on upgrade as to whether to restart, which is an
improvement, but there is no way to decide ahead of time for a non-interactive
upgrade.
+
+ [test case]
+ # apt install docker.io
+ # dpkg-reconfigure docker.io
+ < this will only ask a
** Description changed:
[impact]
docker.io now prompts on upgrade as to whether to restart, which is an
improvement, but there is no way to decide ahead of time for a non-interactive
upgrade.
[test case]
- # apt install docker.io
- # dpkg-reconfigure docker.io
+ # apt-get install docke
I've completed verification for this bug (i.e. checked the autopkgtests
ran ok) and also verified the fixes for bug 1784602 and bug 1769911
which I really ought to have mentioned in the changelog entry. I'm going
to give the k8s team a few days to raise objections though.
--
You received this bug
verified in a lxd bionic image on my dragonboard running ubuntu core 16:
root@fit-ape:~# dpkg -l probert
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
** 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/1800103
Title:
Static IP address validation bug
To manage notifications about th
Public bug reported:
If you attempt a OEM install under UEFI, oem-config will fail to be
installed, because installing oem-config installs ubiquity which
recommends "grub-pc | grub | grub-efi". Back in the day, grub-efi would
have been installed but it seems that this has now split into grub-efi-
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Installation in OEM mode broken o
(forgot to hit the "post comment" button)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Installation in OEM mode broken on bionic
To manage notifications about this bug go to:
https:
I verified the fix using the ISO with .disk/info "Ubuntu-Server 18.04.1
LTS "Bionic Beaver" - Release amd64 (20181030)".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Installation in
Public bug reported:
Hi, youkey-assistant fails to build in disco:
https://launchpad.net/ubuntu/+source/youker-assistant/3.0.0-0ubuntu2
This is the error message:
../../component/alertdialog.cpp: In member function ‘virtual void
AlertDialog::paintEvent(QPaintEvent*)’:
../../component/alertdial
** Description changed:
[impact]
To enable packages that are backported wholesale to all releases of Ubuntu
(i.e. snapd) to stop depending on what is now a fairly ancient version of Go,
we are going to upload 1.10 (the version of Go in 18.04 LTS) to xenial and
trusty as well. This is an unu
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749289
Title:
Installer stops
So I think this patch (to ubiquity):
(master)mwhudson@ringil:/opt/opensource/ubiquity$ git diff
diff --git a/finish-install.d/01oem-config-udeb
b/finish-install.d/01oem-config-udeb
index afb94f4b3..16940ff2b 100755
--- a/finish-install.d/01oem-config-udeb
+++ b/finish-install.d/01oem-config-udeb
https://code.launchpad.net/~mwhudson/ubiquity/+git/ubiquity/+merge/355896
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789920
Title:
Installation in OEM mode broken on bionic
To manage notificati
** Also affects: dh-golang (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gcc-8 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: dh-golang (Ubuntu)
Status: New => Incomplete
** Changed in: dh-golang (Ubuntu)
Status: Incomplete
** Description changed:
+ [Impact]
+ Without this fix we end up creating /var/log/opal-prd.log file with root
user. Hence rsyslogd will not be able to write data to this file. Hence we will
not have enough opal-prd logs for debugging.
+
+ [Test Case]
+ - Installed fixed version of opal-prd pack
** Package changed: opal (Ubuntu) => skiboot (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785026
Title:
[LTCTest][OPAL][OP920] OPAL PRD generated logs is not available in
/var/log/opal-
While I entirely support the idea of snapd no longer caring about gccgo,
this report does indicate a clear bug so I've uploaded a fix for dh-
golang to the SRU queue.
** Description changed:
- We see this kind of error in recent runs of snapd tests when using
- bionic updating gccgo 4:8.2.0-1ubun
** Changed in: skiboot (Ubuntu Bionic)
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/1785026
Title:
[LTCTest][OPAL][OP920] OPAL PRD generated logs is not available
> The dh-golang SRU needs a proper Regression Potential section please.
Done.
** Description changed:
[impact]
Packages that use gccgo-go to build fail to build. There aren't really any
such packages in Ubuntu today, but it's still a broken situation.
[test case]
$ apt source golang-
** Description changed:
+ [impact]
we should update docker to the 18.06 release
+
+ [test case]
+ The autopkgtests per https://wiki.ubuntu.com/DockerUpdates.
+
+ [regression potential]
+ https://wiki.ubuntu.com/DockerUpdates again.
--
You received this bug notification because you are a memb
** Also affects: jtreg (Ubuntu Cosmic)
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/1803628
Title:
jtreg fails to run under openjdk-8 due to api incompat
If you can reproduce this, could you run cloud-init collect-logs (as
root) and attach the resulting tarball to this report?
The user definitely does get created under normal circumstances...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Tags removed: verification-needed 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/1784602
Title:
No option to configure docker.io
The .2 with the increased timeouts passed its autopkgtests first time.
Some ubuntu-fan tests failed but they are flaky in release and the
developers are aware.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notific
That worked better:
root@bionic:~# apt source golang-petname
Reading package lists... Done
NOTICE: 'golang-petname' packaging is maintained in the 'Bzr' version control
system at:
https://code.launchpad.net/petname/petname/trunk
Please use:
bzr branch https://code.launchpad.net/petname/petname/tr
Public bug reported:
[impact]
The tests, both during build and in autopkgtest, tend to time out on slow
machines (e.g. when all builders are busy). The autopkgtest failures in
particular interfere with updating Python in Bionic and Cosmic.
[test case]
Just that the builds and autopkgtests compl
Turns out the package in release ftbfs too. I guess I get to fix that
too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801184
Title:
tests time out on arm64 and armhf
To manage notifications abo
** Tags removed: verification-needed 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/1769911
Title:
docker.io install fails when dock
** Tags removed: verification-needed 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/1784602
Title:
No option to configure docker.io
Hi, thanks for testing so quickly! Some autopkgtest failed but I suspect
they're just being flaky. Will retry before I mark verification-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794396
Tit
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Also affects: kmod (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: kmod (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you
Hi, thanks for the report. The fix seems to be simple, we just need to
have libsystemd-dev installed during the build. I'm building a fix for
that in my ppa:
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages
Which I'll test later, but you could also grab the deb from there if you
w
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798509
Title:
rustc upload not intended for cosmic
To manage notifications about this bug go to:
https://bugs.launchpa
Thanks for the report. I'm a bit confused though, because although
you're right that the call to chown will probably fail, I can't see how
that failure will result in networking not being configured. Can you
post the console log of networking failing to be configured?
--
You received this bug not
Well the missing chown is not going to be a problem because there is
only one user in the initramfs (root!). The chmod failing might be a
problem but it seems a bit unlikely.
I think this code can only be executed if two DHCP leases are accepted.
Are you doing both DHCP4 and DHCP6 or something lik
With that in mind I'm removing the regression-update tag and setting the
bug to incomplete. I presume you've updated your scripts by now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790003
Title:
This was an upstream change in 2.02-beta3, which first appeared in
Ubuntu in 17.04. I'm pretty sure it's not a change introduced by a SRU.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
** Tags removed: regression-update
--
You received this bug notification because you are a me
Oh, I misread the bug report, I thought that the system wasn't booting
at all :(
The good news is that I can reproduce your issue now I understand what
it actually is! The bad news is that I don't really know what to do
about it. getty@tty1.service is being prevented from running by
ubiquity.servi
Using the workaround of switching to tty2 to be able to log in as oem,
clicking cancel on the select language screen now reboots the system and
drops me into grub. Is that expected? (the test case doesn't really
explain the expected behaviour). It seems vaguely reasonable to me...
--
You received
** Changed in: groovy (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/1794135
Title:
Please merge groovy 2.4.15-3 from Deb
Public bug reported:
[impact]
To enable packages that are backported wholesale to all releases of Ubuntu
(i.e. snapd) to stop depending on what is now a fairly ancient version of Go,
we are going to upload 1.10 (the version of Go in 18.04 LTS) to xenial and
trusty as well. This is an unusual "S
Public bug reported:
we should update docker to the 18.06 release
** Affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
** Affects: docker.io (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: docker.io (Ubuntu Bionic)
Importance: Undecided
I have test builds here
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages (they
keep failing on intel because builder performance is so bad currently
:()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
So can we call this verification-done-xenial then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749289
Title:
Installer stops after pressing Cancel on Select a language screen
during OEM install
Would it be possible for one of the subscribers to this bug to update it
with the impact/test case/regression potential per
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?
** Also affects: opal (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: opal (Ubuntu
On Fri, 28 Sep 2018, 20:20 John Lenton,
wrote:
> What can we do about architectures that need gccgo?
>
To be clear, the only such architecture is powerpc on xenial.
For snapd, my understanding is having snapd there does not offer anyone
anything - there has never been a core snap published for
Should SRU the new dh_golang I guess. Although why do you care about
buildability with gccgo?
On Fri, 28 Sep 2018, 20:20 William Grant, wrote:
> ** Package changed: gcc-defaults (Ubuntu) => gcc-8 (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to dh-
> golang in U
Glad it's working now and that's for coming back to report it.
** Changed in: docker.io (Ubuntu)
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/1821540
Title:
do
Hi Marc, do you happen to know how to install security updates only via
apt?
** Changed in: subiquity
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817049
Title:
Su
** Changed in: subiquity
Importance: High => Critical
** 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.net/bugs/1
** Changed in: subiquity
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/1750645
Title:
support encrypted block devices
To manage notifications about this b
** 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/bugs/1816954
Title:
Unable to show Info nor Set static IP during install
To manage not
Certainly just installing all updates would be easier (very easy in
fact). Maybe we should just do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817049
Title:
Subiquity should install securit
** Changed in: subiquity
Status: Triaged => 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/1780867
Title:
hostname unchangeable / some daemon changes and resets /etc/hostname
T
https://github.com/CanonicalLtd/subiquity/pull/451 has an implementation
(and asciinema video) of opportunistically downloading/installing
updates.
** Changed in: subiquity
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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/1817049
Title:
Subiquity should install security updates before first login
To man
Public bug reported:
We should upgrade to docker.io 18.09.5 in xenial+, this now means
updating containerd and runc.
[test case]
autopkgtests per https://wiki.ubuntu.com/DockerUpdates
[regression potential]
As per usual, we don't mind if the updated packages regress in some sense,
that's all pa
** Changed in: containerd (Ubuntu)
Status: New => Fix Released
** Changed in: runc (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/1824461
Title:
up
Public bug reported:
I forgot to mention it in the changelog but the runc update fixes
CVE-2019-19921.
The containerd update to 1.3.1 is being tracked in bug 1854841.
[test case]
per https://wiki.ubuntu.com/DockerUpdates, our test case is the autopkgtests
[regression potential]
As usual, we del
** Changed in: docker.io (Ubuntu)
Status: New => Fix Committed
** Changed in: runc (Ubuntu)
Status: New => Fix Committed
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hmm. You're almost certainly right that it was the casper upload that
caused this.
I changed casper so that it creates a filesystem with the label
"writable" but it should still mount a pre-existing filesystem with
label "casper-rw" (and there are autopkgtests that it does this). There
could be a
I bet it's a race and sometimes it works and sometimes it doesn't with
the new casper (which of course can drive anyone trying to figure out
what is going on crazy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
"Warning: Unable to find the persistent medium" is the message
indicating failure.
Do you know how to make changes to the initramfs? (I know it's not the
simplest procedure)
If you do, can you insert "ls -l /dev/disk/by-label/" just above the "if
[ ! -e "/dev/disk/by-label/${root_persistence}" ]
Good enough for me.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
As it happens I uploaded 1.0.0-rc10 to bionic UNAPPROVED a few days ago,
which should fix this. I'll try to remember to update this bug when that
gets into proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1862478 ***
https://bugs.launchpad.net/bugs/1862478
** This bug has been marked a duplicate of bug 1862478
gnome-system-monitor can't measure network transfer rate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I fixed this upstream https://gitlab.gnome.org/GNOME/gnome-system-
monitor/-/commit/c031de0a3469faf5020768de506c6169e1e71ac0, not sure if
there will be a release before focal or if this should be cherrypicked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fairly sure the problem is this line from
https://git.launchpad.net/ubuntu/+source/sg3-utils/tree/scripts/55-scsi-
sg3_id.rules?h=applied/1.44-1ubuntu1#n48:
ENV{ID_SERIAL}!="?*", ENV{SCSI_IDENT_LUN_NAA_EXT}=="?*",
ENV{ID_BUS}="scsi", ENV{ID_SERIAL}="3$env{SCSI_IDENT_LUN_NAA}",
ENV{ID_SERIAL_SHORT}
** Also affects: sg3-utils (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: sg3-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
- 1.
- root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info
+ [impact]
+ ID_SERIAL in udev for scsi
** Description changed:
[SRU justification]
The ubuntu-dev-tools package is primarily of interest to Ubuntu developers,
providing tools for interacting with the Ubuntu archive and Ubuntu
developer-centric services. Developers should have consistent behavior from
these tools, regardless of
** Also affects: ubuntu-dev-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan
** Changed in: runc (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: docker.io (Ubuntu)
Status: Fix Committed => Fix
Hi, this works for me in very simple testing. Can you post a full
reproducer?
** Changed in: docker.io (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821540
This is fixed now I think? I guess the livecd-rootfs change needs to go
back to bionic?
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: subiquity
Status
It's fixed in the installer code but not in any released media yet. If
you switch to tty2 and run "snap refresh subiquity" you'll get a version
of the installer with this bug fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
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.target.wants/m
101 - 200 of 2201 matches
Mail list logo
