** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: cloud-images
Assignee: (unassigned) => Gauthier Jolly (gjolly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now in noble unapproved queue
https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064280
Title:
Hyperv desktop images no
Now in noble unapproved queue
https://launchpad.net/ubuntu/noble/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066905
Title:
LXD snap no longer seeded in
** Description changed:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic related to LXD snap @
https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108
is no longer required.
lxd-installer can remain
** Description changed:
The LXD snap is no longer seeded in any images since Noble+ so the
unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live-
build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
** Description changed:
The LXD snap is no longer seeded in any images since Noble+ so the
unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live-
build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
For context the image @jibel tested was https://partner-
images.canonical.com/hyper-v/desktop/oracular/20240522/
@jibel I will start SRU to noble now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic in https://git.launchpad.net/livecd-
rootfs/tree/live-build/auto/build?h=ubuntu/noble#n290 and
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
Public bug reported:
The LXD snap is no longer seeded in non minimal images since Noble+ so
the unminimize logic related to LXD snap @
https://git.launchpad.net/ubuntu/+source/unminimize/tree/unminimize?h=applied/ubuntu/noble#n108
is no longer required.
lxd-installer can remain installed.
This
@sdeziel thank you for debugging.
+1 on moving to `/usr/sbin/lxd` instead of `/sbin/lxd` if possible thus
removing the need for any livecd-rootfs changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jammy livecd-rootfs 2.765.42 has now been uploaded to SRU queue @
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062929
Mantic livecd-rootfs 23.10.60 has now been uploaded to SRU queue @
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062929
Full failing build log @
https://launchpadlibrarian.net/731241044/buildlog_ubuntu_noble_amd64_ubuntu-
server-live_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
The changes proposed here in Noble lxd-installer 4ubuntu0.1 have caused
server builds to fail
```
Invoking LXD so that it can be installed by the lxd-installer's script..
Unable to trigger the installation of the LXD snap.
Please make sure you're a member of the 'lxd' system group.
```
This is
** Changed in: livecd-rootfs (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/2052789
Title:
AppArmor profiles missing in kernel 5.15.0-1051+
The xenial and bionic target is the ESM repos
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064580
Title:
Please update the package to 20240320.00
To manage notifications about this bug go to:
Public bug reported:
Following on from previous similar package update requests @ LP:
#2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a
request to update the google-osconfig-agent to the upstream version
`20240320.00` @
oem-config to the new provisioning
stack but this is out of scope of this bug.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
** Affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: New
** Also
Verification done for Mantic now.
* Successfully built image with LXD preseeded with these changes
* confirmed LXD is preseeded/installed and works as expected.
* Confirmed that preseeding other snap like google-cloud-cli for example in
the GCE images continues to preseed as expected.
**
This issue affects Oracular/24.10 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061121
Title:
Mantic preseeding of LXD using incorrect track/channel
To manage notifications about this bug go
Public bug reported:
The recent change in Ubuntu 24.04 and needrestart which results in
services being restarted automatically , details @
https://discourse.ubuntu.com/t/noble-numbat-release-
notes/39890#services-restart-on-unattended-upgrade-26, has resulted in
unexpected behaviour on Google GCE
** Also affects: linux-gcp (Ubuntu Noble)
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/2063315
Title:
Suspend & Resume functionality broken/timesout in
** Changed in: snapd (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu Noble)
Status: New => Fix Released
I have removed references to desktop FDE from the description. Thank you
for testing.
** Description changed:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included the vendoring of snapd 2.62.
This is a 24.04 release blocking bug as it is a regression and results
in a failure to boot for TPM backed FDE instances.
** Description changed:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included
Public bug reported:
Azure testing has reported an issue following update of the nullboot
package from 0.5.0-0ubuntu3 to 0.5.1-0ubuntu1 which I am informed
included the vendoring of snapd 2.62.
This has caused a regression and TPM backed FDE instances no longer boot
as expected.
There are
** Changed in: livecd-rootfs (Ubuntu)
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/2062024
Title:
armhf doesn't build disk-image-uefi
To manage
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrony (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance:
Public bug reported:
* Canonical Public Cloud discovered that `chronyc -c sources` now fails with
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in
linux-azure and linux-gcp kernels (6.8.0-1005.5)
* Disabling AppArmor (`sudo systemctl stop apparmor`) completely results
This does not affect Noble as we no longer preseed LXD in >=Noble
** Also affects: livecd-rootfs (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Mantic)
Assignee: (unassigned) => Philip Roche (philroche)
** Description changed:
Public bug reported:
Recent Mantic cloud image builds fail - see
https://launchpad.net/~cloudware/+livefs/ubuntu/mantic/cpc/+build/604087
build log for an example.
```
+ UBUNTU_STORE_ARCH=amd64 SNAPPY_STORE_NO_CDN=1 snap download
Assignee: Catherine Redfield (catred)
Status: New
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Noble)
Assignee: (unassigned) => Philip Roche (philroche)
** Changed in: livecd-rootfs (Ubuntu No
Verified Focal:
This exact proposed version of livecd-rootfs has been used in cloud
image build for many weeks now and has met all of the steps listed in
the test plan.
GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405``
being one such image with snaps and built using this
Verified Focal:
This exact proposed version of livecd-rootfs has been used in cloud
image build for many weeks now and has met all of the steps listed in
the test plan.
GCE daily minimal image daily-ubuntu-minimal-2004-focal-v20240405``
being one such image with snaps and built using this
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
MP with catred's proposed changes @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/463488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor
MP with catred's proposed changes @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/463488
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059730
Title:
Focal 5.15
Now uploaded to Jammy queue @
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor profiles missing in
** Also affects: google-guest-agent (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: google-guest-agent (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: google-guest-agent (Ubuntu Mantic)
Importance: Undecided
Status: New
**
@holmanb
> google-startup-scripts.service starts well after the network is online
You are correct. I have updated the bug description now.
> due to configuration via cloud-init not being fully completed, apt
sources for example, when startup scripts are run
** Description changed:
- New GCP
Test plan updated for Jammy too
** Description changed:
After the kernel roll to linux-gcp-5.15 to version
5.15.0-1051.59_20.04.1 the public cloud team pre publication test were
failing on our snap_preseed_optimized test which checks to ensure that
snaps are preseeded correctly
This
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: update-manager (Ubuntu Noble)
Importance: Wishlist
Assignee: Calvin Mwadime Makokha (calvinmwadime)
Status: Triaged
--
You received this bug notification because you are a
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: wsl-pro-service (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Subscribing ubuntu-release as per FFE policy. This bug will block noble
cloud image release
** Also affects: livecd-rootfs (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[ Impact ]
* It is not possible to upgrade or re-install python-apt using pip from
the git+ssh://git.launchpad.net/ubuntu/+source/python-apt git repo if
already installed and if wheel installed too.
* On initial install it also is assigned version `0.0.0` which is
Jammy fix is still awaiting review @
https://code.launchpad.net/~philroche/livecd-rootfs/+git/livecd-
rootfs/+merge/460929
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052789
Title:
AppArmor
As verification I have successfully built and published Ubuntu 21.10
Impish armhf cloud images with this patch applied as in -proposed.
http://cloud-images.ubuntu.com/impish/20211208.1/
Note that armhf downloads are present and have passed all available
testing.
** Tags removed:
** Description changed:
[Impact]
- * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
+ * Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
on device' errors. See attached build log snippet for details on the
disk space errors.
- * The fix
Test build with this patch was successful - see private build
https://launchpad.net/~cloudware/+livefs/ubuntu/impish/cpc/+build/314665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953609
Title:
MP now created https://code.launchpad.net/~philroche/livecd-
rootfs/+git/livecd-rootfs/+merge/412892
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953609
Title:
[SRU] Bump disk image size for amhf
Public bug reported:
[Impact]
* Unable to build armhf Ubuntu 21.10 cloud images due to 'No space left
on device' errors. See attached build log snippet for details on the
disk space errors.
* The fix has landed upstream in the livecd-rootsfs master branch
https://git.launchpad.net/livecd-
@sil2100 We have now successfully tested reboot with grub-efi-
amd64-signed 1.167~16.04.2+2.04-1ubuntu44 from xenial-proposed with
image ubuntu-1604-xenial-v20200429 in GCE
And I confirmed the bug with grub-efi-amd64-signed
1.66.23+2.02~beta2-36ubuntu3.23 prior to testing
Marking
I also verified the fix with a python2 virtualenv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912248
Title:
virtualenv on xenial: easy_install syntax error
To manage notifications about this
I have verified fix in amd64 xenial VM.
Test case:
* `sudo apt install python3-virtualenv virtualenv python-virtualenv`
* Confirm that any `pip` operations fail as per bug description
* `virtualenv -p /usr/bin/python3 venv/py3 --verbose`
* `source ./venv/py3/bin/activate`
* `pip list`
*
@stefanor
Thanks for the explanation.
I have a one liner workaround now:
```
virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-download && .
venv/py3/bin/activate && python3 -m pip install --upgrade 'setuptools;
python_version >= "3.6"' 'setuptools<51.3.0; python_version < "3.6" and
I have found the following workaround on Ubuntu 16.04 Xenial
Do not install setuptools on virtualenv creation:
`virtualenv -p /usr/bin/python3 venv/py3 --verbose --no-setuptools`
Install a supported setuptools version after virtualenv creation and
activation:
`python3 -m pip install --upgrade
This is being tracked in setuptools upstream too
https://github.com/pypa/setuptools/issues/2541
The cause is that python-virtualenv is pulling in setuptools 51.3.3
`virtualenv -p /usr/bin/python3 venv/py3 --verbose`
```
snip...
Installing setuptools, pkg_resources, pip, wheel...
** Also affects: grub (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/1885571
Title:
Can't set boot kernel in GRUB on focal image
To manage
CPC are seeing this issue in _all_ minimal cloud images testing with LXD
snap version 4.2 or greater. This blocks promotion of all minimal cloud
download images and blocks build and publication of both daily and
release cloud images.
--
You received this bug notification because you are a member
Verification of livecd-rootfs 2.664.2 in focal -proposed completed.
The following verification was completed.
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it boots
* Confirm there is no boot speed regression
* Confirm that running `sudo
Verification of livecd-rootfs 2.620.3 in eoan -proposed completed.
The following verification was completed.
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it boots
* Confirm there is no boot speed regression
* Confirm that running `sudo
debdiff for eoan SRU rev2. Building package without extraneous contents
as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html
#build-noextra
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-eoan-rev2.debdiff"
debdiff for focal SRU rev2. Building package without extraneous contents
as per https://www.debian.org/doc/manuals/debmake-doc/ch05.en.html
#build-noextra
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-focal-rev2.debdiff"
debdiff for eoan SRU
** Patch added:
"lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375695/+files/lp-1880170-kvm-revert-of-initramfs-package-removal-eoan.debdiff
--
You received this bug
debdiff for focal SRU
** Patch added: "lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1880170/+attachment/5375692/+files/lp-1880170-kvm-revert-of-initramfs-package-removal.debdiff
--
You received this bug notification
** Description changed:
- We want to the revert of initramfs package removal in KVM image.
+ No packages marked for auto-removal should be present in a published
+ cloud image.
+
+ The current kvm binary hook in livecd-rootfs removes the packages
+ `initramfs-tools` and `busybox-initramfs`. This
Public bug reported:
We want to the revert of initramfs package removal in KVM image.
[Impact]
* We don't want any packages marked for auto-removal on a published kvm
cloud image.
[Test Case]
* Perform livefs build with project ubuntu-base
* Boot *-disk-kvm.img using kvm
* Confirm it
This does not appear to be docker specific but the chromium package has
moved to a snap package.
What is your host OS and kernel version?
Is the snapd service running in the container?
We have added the chromium package to this bug so they can investigate.
** Changed in: cloud-images
It appears that a bug was already filed against netcat
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861704
Title:
ubuntu-fan
Public bug reported:
Following some debug of the docker.io package in universe, we (Canonical
CPC) discovered that the ubuntu-fan package from main and the netcat-
traditional package from universe were being installed.
This was due to the following dependency/recommends tree:
* docker.io (in
We (CPC) are seeing this issue too when trying to build Trusty non
amd64/i386 images.
When we hit this yesterday Security team confirmed that ESM doesn't
support other arches but we shouldn't block builds because of this
change.
--
You received this bug notification because you are a member of
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840135
Title:
Request for new Eoan build of python-simplestreams
To manage notifications about this bug go to:
Public bug reported:
Following the merge of MP
https://code.launchpad.net/~philroche/simplestreams/+git/simplestreams/+merge/369682
would it be possible to get a new build of simplestreams published to
Eoan?
This change might not be SRUable as it could change behavior that
current users are
On guidance from raharper I have opened new bug for this @
https://bugs.launchpad.net/cloud-init/+bug/1822353
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766287
Title:
18.04 minimal images on
I'd like to reopen this following Disco minimal images failing to set up
networking due to similar reasons to this bug with the only difference
being that no nic was found.
A workaround was found to set up cloud-init service config:
/etc/systemd/system/cloud-init-local.service.d/gcp.conf
```
Verification is complete and GCE have given +1 on 20190124 packages
migrating to -updates
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-bionic
Myself and @kamalmostafa spoke and the issue is not obvious especially
as linux-azure is installed in the base image too which does not exhibit
the issue.
Although not obvious @kamalmostafa did suspect the issue to lie
somewhere with random number generation and a related package/kernel
patch.
@kamalmostafa @mhcerri
I noticed that linux-azure 4.18.0.1003.3 was uploaded to cosmic-proposed
so I built a new test image.
For convenience I have imported your SSH keys to 'ssh
ubuntu@51.140.217.58'.
All logs and VHD etc. have been uploaded to https://private-
** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1002.2 (from
cosmic-proposed) boot log"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5195337/+files/chohv4Va7Ahx7-vm-imagedebug-boot.log
--
You received this bug notification because you are
On request on IRC I have tried a new image with linux-azure
4.18.0.1002.2 from cosmic-proposed.
This too exhibited the slow boot
5min 19.070s (kernel) + 41.724s (userspace) = 6min 794ms
Full logs @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20181001/
--
You received this
Public bug reported:
Hi,
We're planning to share a new Cosmic minimal image for Azure including
the linux-azure custom kernel.
I have found boot speed increase from ~55s in non minimal image to over
6mins for minimal image.
I have gathered boot log, systemd logs and cloud-init logs for this
I have verified xenial using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/xenial/
[2]
I have verified xenial using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/xenial/
[2]
I have verified bionic using a locally created test image.
Test image [1] was created using ubuntu-old-fashioned [2] and the
proposed branch of livecd-rootfs.
[1]
https://private-fileshare.canonical.com/~philroche/unminimize-verification-20180704/bionic/
[2]
The meta-packages have been rolled back and the fix is in progress of
being applied and uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779961
Title:
Boot delays with 4.15.0-24 based
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770650
Title:
Update google
Trusty image with gce-compute-image-packages
20180510+dfsg1-0ubuntu3~14.04.3 now published as "daily-ubuntu-gceip-
ppa-1404-trusty-v20180611" in project "ubuntu-os-cloud-devel". All
automated tests and manual tests passed.
@GCE-team, please can you verify these images before we proceed with
Trusty image with gce-compute-image-packages
20180510+dfsg1-0ubuntu3~14.04.2 now published as "daily-ubuntu-gceip-
verify-1404-trusty-v20180530a" in project "ubuntu-os-cloud-devel". All
automated tests and manual tests passed.
In summary:
The following test images have been created with the
The following test images have been created with the proposed version of
gce-compute-image-packages:
daily-ubuntu-testing-1804-bionic-v20180525 in project ubuntu-phil
daily-ubuntu-testing-1604-xenial-v20180529 in project ubuntu-phil
daily-ubuntu-testing-1710-artful-v20180529 in project
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu3~17.10 in artful.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu3~16.04 in xenial.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have verified gce-compute-image-packages version
20180510+dfsg1-0ubuntu4~18.04 in bionic.
All automated tests and manual tests passed.
Tests confirm expected services are running too.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this
Given https://gitlab.gnome.org/GNOME/glib/commit/0d69462 referred to
above it does look like an intentional change and nothing to do with
udisks2. Please close if this is the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also refer you to https://gitlab.gnome.org/GNOME/glib/commit/0d69462
which seems to be the cause.
https://gitlab.gnome.org/GNOME/nautilus/issues/312 refers to this too
but I have experienced this in Caja too, not just nautilus.
--
You received this bug notification because you are a member of
Public bug reported:
Apologies if this is not the correct package to file this bug/regression
against.
On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting
network shares (SMB and NFS) they no longer appear under Devices in file
manager (Nautilus or Caja), the mounts do
1 - 100 of 179 matches
Mail list logo
