Promotion from -proposed sure would be nice. I see verification has
been done but a update excuses shows an netplan.io regression[1]. I'm
not sure if the test is flaky but I see that seb retried it a few
times[2] last week and it failed consistently, so maybe not.
I'm just curious if there's
Thank you Seb, I had the issue reported in this bug in a WeWork today
(first time connecting since updating to Jammy) and the package in
-proposed resolved the issue for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Could you add some clarifying output in the postinst around pypy3compile
failures to give context to an end user? The errors as they stand don't
indicate that this is pyp3 specific and can be concerning (they also
give the impression that QA isn't catching basic python bugs
Where are you expecting to ship these images from? I'm concerned about
the hard-coded password and I want to ensure people know what they're
getting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The autopkgtest regression noted in comment #17 was due to an ephemeral failure
trying to reach people.canonical.com for seeds:
! Could not open (any of):
!
http://people.canonical.com/~ubuntu-archive/seeds/ubuntu.focal/desktop-minimal-zh
!
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Milestone: None => ubuntu-21.04
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've left a comment in the upstream bug https://github.com/aws/aws-ec2
-instance-connect-config/issues/28#issuecomment-816650597 regarding my
SRU test feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have tested in AWS local zone us-west-2-lax-1a
xenial:
image: ami-008b09448b998a562
build serial: 20201014
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~16.04.2
bionic:
image: ami-02701bcdc5509e57b
build serial: 20210224
ec2-instance-connect 1.1.12+dfsg1-0ubuntu3~18.04.2
focal:
image:
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-xenial
** Tags added: verification-failed verification-failed-focal
verification-failed-groovy verification-failed-xenial
--
You received this bug notification because you are a member
This is fixed in devel in changes that span multiple commits and this
bit was omitted from the backport of those changes (which broke focal
images)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@gjolly,
I've taken a look at the 'Where problems could occur' section of the SRU
template and I'm concerned about the risk of regression for users
altering mount options for the root file system.
My concerns involve the root filesystem line alone. I think 'discard'
is nice-to-have but not
** Description changed:
[Impact]
* In cloud images, the ESP is currently mounted with default (0755)
permissions. This means anyone can read the ESP partition. This can
cause security issues as sensitive data might be put in this
partition[0]
* The root filesystem
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
You received this bug notification because you are a member of
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed:
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$
I'm using xorg because wayland has bug #1918189 (can't share terminals
in Google Meet) blocking me from using wayland as a daily driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917926
Title:
Public bug reported:
When running xwayland in Hirsute I am unable to share gnome-terminal
windows from Google Meet. In Google Meet running in Chrome
v89.0.4389.82 when I select the share a window I do not see my gnome-
terminal windows listed as an option to share.
Here is what I am running
Wavelength zones are described @
https://aws.amazon.com/wavelength/features/#Locations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915345
Title:
eic_harvest_hostkeys fails in local zones
To
And I haven't tested, but this would also fail in Wavelength zones with
names in the form `us-east-1-wl1-bos-wlz-1`. Even if instance connect
isn't supported in wavelength zones I rather not have the service fail
and mark the system status as degraded.
--
You received this bug notification
** Bug watch added: github.com/aws/aws-ec2-instance-connect-config/issues #28
https://github.com/aws/aws-ec2-instance-connect-config/issues/28
** Also affects: ec2-instance-connect via
https://github.com/aws/aws-ec2-instance-connect-config/issues/28
Importance: Unknown
Status:
This is a problem with "# Validate the zone" logic @
https://git.launchpad.net/ubuntu/+source/ec2-instance-
connect/tree/src/bin/eic_harvest_hostkeys?h=applied/ubuntu/hirsute#n92
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
ec2-instance-connect breaks during host key harvesting for instances
launched in local zones[1]. Here are is the relevant debug data:
$ systemctl is-system-running
degraded
$ systemctl list-units --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Based on my prior reply I've marked this as "Won't Fix" as it doesn't
match with our plans for the unminimized script per policy on
'recommends'.
** Changed in: cloud-images
Status: New => Won't Fix
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Won't Fix
--
You received
I've discussed this issue in #ubuntu-devel on IRC[1] and the feedback is
that recommends, by policy, are installed for a reason and overriding
that should not be part of the unminimize tool. But for your use case
there is a solution that could meet your needs. You can set the
following in
I've moved this to the livecd-rootfs project which builds the images and
contains the unminimize script code.
Background: Ubuntu images themselves do install recommends for packages
in the base, so re-installing recommends was seen as appropriate to make
a stock minimized image look like the
Adding the cloud-images project so that a test can be added once this
change lands in livecd-rootfs
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With snapd 2.48 in the store and in the archive we have built test
images from the ubuntu-cpc project and verified that snaps are preseeded
in the image resulting in reduced seed times during first boot. I'm
removing the block and marking this as verification done.
** Tags removed:
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects:
** Description changed:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from
** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #84
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
** Also affects: google-guest-agent via
https://github.com/GoogleCloudPlatform/guest-agent/issues/84
Importance: Unknown
Status: Unknown
--
You
Public bug reported:
We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run. That test is failing and investigation shows
that we have a functional regression from
@chad.smith I have used the cloud-utils in your ppa to build Xenial
maas-images on a bionic host to confirm that things are working now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493188
Title:
With the move to Bionic host kernels on the builders, the Xenial MAAS
images fail to build. This is because cloud-utils mount-image-callback
remains unfixed in Xenial while the Bionic kernel does not have the
overlayfs kernel module. The following patch at minimum is required in
Xenial:
Thank you for the bug report. I have confirmed this issue and flagged
the correct project, livecd-rootfs, for this work.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: livecd-rootfs (Ubuntu)
So we need to fix livecd-rootfs to correctly add the tools version field
to the vmdk header *and* add a check that it got there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893898
Title:
But that function is sed'ing the file created by python3-vmdkstream so
we'll look into it. The vmdk-stream-converter source package has had a
minor change between focal and groovy but it doesn't explain this issue.
** Also affects: cloud-images
Importance: Undecided
Status: New
--
Okay, the vmdk lacks the version in bionic, focal, and groovy. The
ddb.comment field that toolsVersion uses is missing:
# Disk Descriptor File
# Created by VMDKstream
version=1
CID=7e5b80a7
parentCID=
createType="streamOptimized"
# Extent description
RDONLY 20971520 SPARSE
The OVA we're providing[1] is built with this[2] binary hook in livecd-
rootfs which wraps up the VMDK created using the create_vmdk[3]
function. That function calls modify_vmdk_header to set the tools
version; this code is unchanged from when it was added in early 2017.
[1]
A backport of https://github.com/hashicorp/vagrant/pull/9338 could
resolve this and allow bionic to launch Focal and later vagrant boxes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738400
Title:
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889470
Title:
snap seed with channel breaks ubuntu-cpc:minimized builds on focal
To manage notifications about
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
@marin-n & @hggdh2,
I see that you have both reported failures on Azure. @marin-n, from
your grub versions it looks like you're on focal. I'd like to learn
more so I can recreate and get this addressed.
I would like to find out:
- which image release and build you are running:
$ cat
My recreate is with an AWS EC2 instance with an NVMe root device as that
is one known way to trigger an error in cloud-init cc_grub_dpkg so that
it does not write a valid debconf for grub-pc install_devices, however
this is broader than NVMe root with cloud-init.
--
You received this bug
*** This bug is a security vulnerability ***
Public security bug reported:
Failure to install new grub core to the specified device does not
correctly prevent upgrade to incompatible modules (LP: #1889509)
$ sudo debconf-get-selections |grep sda
grub-pc grub-pc/install_devices_disks_changed
I'm attaching a full log from the recreate that shows additional details
** Attachment added: "grub_bug_log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397176/+files/grub_bug_log
** Description changed:
Failure to install new grub core to the specified
** Merge proposal linked:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/388320
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889470
Title:
snap seed with channel
** Description changed:
+ [Impact]
+
+ * Focal ubuntu-cpc:minimized builds fail (see Original Description)
+
+ [Test Case]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+package to reproduce the bug and
Public bug reported:
[Impact]
* Focal ubuntu-cpc:minimized builds fail (see Original Description)
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated
Adding 'grub' project to verify and provide assistance.
--
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 notifications about this
@xnox wrote:
> It sounds like we must remove seeded snaps from our LXD images, and not
> install
> any seeded snaps inside our container. And like only install the lxd stub deb.
> Cause it looks like seeding snaps is not supported inside classic lxd
> containers.
Let's remember that these
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an
I've opened a track for livecd-rootfs where the minimal image is defined
and I'm going to close the cloud-images portion.
But I will add that the images themselves set the expectation about what
it is to be considered minimal as:
"This system has been minimized by removing packages and content
I added a -d flag to the invocation of perl in the shebang line of
/usr/share/lintian/frontend/dplint Here is what I got:
# lintian --help
Loading DB routines from perl5db.pl version 1.55
Editor support available.
Enter h or 'h h' for help, or 'man perldebug' for more help.
I'm moving this from cloud-images to lintian, this is not an issue
specific to the image itself.
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Eoan arm64 container on focal amd64 host does not recreate this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881217
Title:
arm64v8 focal: lintian will get stuck with it
To manage
** No longer affects: cloud-images/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant username and
password
To manage
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images
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/1875068
Title:
** Changed in: cloud-images
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/1875882
Title:
debconf attempts interactive configuration; breaks Docker image builds
To
On Thu, Apr 30, 2020 at 2:50 PM Steve Langasek
wrote:
> On Thu, Apr 30, 2020 at 05:27:49PM -, Dimitri John Ledkov wrote:
> > Looking at seeds, it seems like maybe "cloud-image" should have fdisk
> > seeded in both focal & groovy.
>
> I think this belongs in the server seed, not just
Built ubuntu-cpc images and tested that images with core or core18 based
snaps build as expected. The core snap was pulled in for snaps without
an explicit base while core18 & snapd were pulled in for snaps with an
explicit core18 base, and were there were both we have core and core18
without
I've looked at the ubuntu-image autopkgtest failure on ppc64el. The
failure was a network timeout on a 'pip' command. Re-running the test
has passed and this seems acceptable. I will continue testing the SRU
per the testcase in the template and update this bug.
--
You received this bug
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Xenial)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Description changed:
- A xenial image that preseeds a snap based on core18 will end up with
- core instead and preseeding on boot will fail.
+ [Impact]
+
+ * A xenial image that preseeds a snap based on core18 will
+end up with core instead and preseeding on boot will fail.
+
+
+ [Test
Public bug reported:
A xenial image that preseeds a snap based on core18 will end up with
core instead and preseeding on boot will fail.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Drat, I see that now in sshd_config. I think I tried searching for
"first" and maybe by that point I was just looking at sshd's man page.
Okay, well then this is fine for me It's documented and stable. We
can comfortably make this change for cloud-images. Thanks Colin!
** Changed in:
@colin-king, Can we get that config option added for this kernel?
** Also affects: linux-kvm (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/1873809
I have used livecd-rootfs 2.620.2 from proposed to build ec2 and gce
images. EC2 currently has a mix of core and core18 based snaps while
GCE has only core18 based snaps. I confirmed that snapd was seeded when
core18 was the only core snap present. Boot testing each of these
images confirmed
Public bug reported:
I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
for use in Ubuntu cloud images. I wanted to add a config file and see
if I had done things correctly. I assumed that the files were sourced
lexographically (based on use of glob() in readconf.h) so that
This is great and I'd love to see us move to this from what we are
doing. Parallel builds for the ubuntu-cpc project have an absolute
requirement for cohort support; so that requirement will need to be
driven with snapd.
--
You received this bug notification because you are a member of Ubuntu
** Also affects: livecd-rootfs (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Eoan)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu Eoan)
Status: New => In Progress
--
You received th
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863024
Title:
SRU: bootable buildd images for all releases
To manage
** Description changed:
[Impact]
- * Building an ubuntu-cpc minimal image by default would have no snaps
+ * Building an ubuntu-cpc minimal image by default would have no snaps
installed. When a binary hook seeds a snap that has a core18 base
the build will fail when calling 'snap
** Description changed:
+ [Impact]
+
+ * Building an ubuntu-cpc minimal image by default would have no snaps
+ installed. When a binary hook seeds a snap that has a core18 base
+ the build will fail when calling 'snap debug validate-seed' because
+ the snapd snap is missing.
+
+ *
** Tags removed: verification-needed
** Tags added: 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/1863024
Title:
SRU: bootable buildd images for all releases
To manage
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:
Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
pciutils,
virtualbox-guest-dkms (=
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872485
Title:
virtualbox-guest-utils fails to install on 20.04
To manage notifications about this bug go to:
** Summary changed:
- explicit key offered after all agent keys, auth fails before explicit key used
+ explicit key offered after all agent keys, auth can fail before explicit key
used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A user creates an ssh key and specifies it on the cmdline with 'ssh -i
new_key user@host'. The connection fails with the message "Too many
authentication failures" displayed to the user.
This would lead the user to believe that they failed to put the public
portion of the
** Changed in: livecd-rootfs (Ubuntu)
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/1871919
Title:
images with only core18-based snaps fail to build
To
This would be an issue for the package, I will close the track for
cloud-images.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: chromium (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/1869963
Title:
Unable to install chromium-browser 20.04
To manage
for each snap
and seed the appropriate base. There should be no reason to explicitly
seed the 'core' snap and with snaps moving to 'core18' this will add
'core' without need.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Robert C Jennings (rcj)
Status
:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/382041
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification becau
*** This bug is a duplicate of bug 1871919 ***
https://bugs.launchpad.net/bugs/1871919
** This bug has been marked a duplicate of bug 1871919
images with only core18-based snaps fail to build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: simplestreams
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/1833435
Title:
RFC: Add url/urls/mirrors attribute for product items
To manage
@raharper,
Your statement that this will be opt-in (disabled by default) does not
reflect our intentions with this package. Upon review, my earlier
statement was not as clear as I wish it was. In comment #31 I said:
> CPC (public cloud team) will continue with our baseline testing and for
>
** Changed in: livecd-rootfs (Ubuntu Bionic)
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/1863024
Title:
SRU: bootable buildd images for all releases
Please provide details on the steps needed to recreate including AMI-
id/region and package version for ec2-hibinit-agent.
Once you have recreated please collect logs with 'sosreport -a' and
attach the result. Thank you.
** Changed in: ec2-hibinit-agent (Ubuntu)
Status: New =>
** Changed in: livecd-rootfs (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/1863024
Title:
SRU: bootable buildd images for all releases
To manage
** No longer affects: livecd-rootfs (Ubuntu Eoan)
** Merge proposal unlinked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378931
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378975
**
This has been verified using 2.408.58 in xenial-proposed.
I have built the qcow2 image target of the ubuntu-cpc project with and
without a cohort key.
I added the following to the qcow2 binary hook:
. /build/config/binary
mkdir qcowmp
mount_disk_image binary/boot/disk-uefi.ext4 qcowmp
Dave, using the latest focal daily lxd container (serial 20200313) I can
remove and install flash-kernel to see the "flash-kernel: /boot/vmlinuz-
or /boot/initrd.img- missing; expecting future run" failure and confirm
that installing from the ppa (3.98ubuntu12~ppa1) gives the same output
as above
I have a questionable recreate and maybe Stephan Fabel can confirm if
this is what he's seeing.
I have launched an arm64 VM on AWS and on that VM I have started an 18.04
container from the 'ubuntu:' remote. The container has a build serial of
20190307.
Running 'apt update; apt upgrade -y'
If that is the issue that Stephan is seeing then I have not seen the
issue with the bionic package in Dave's PPA:
$ lxc launch ubuntu:08e14ca27965 b
$ lxc shell b
$ apt-add-repository ppa:waveform/flash-kernel
$ apt install -y flash-kernel
Reading package lists... Done
Building dependency tree
For others that would like to attempt a recreate, the image I'm using
is:
$ lxc image info ubuntu:08e14ca27965
Fingerprint: 08e14ca2796594a0a52f62a1974774db6f4ecfbb2a3da7f3a5c1e2e0abff7362
Size: 161.48MB
Architecture: aarch64
Public: yes
Timestamps:
Created: 2019/03/07 00:00 UTC
Uploaded:
On the topic of testing raised in earlier comments. CPC will continue
with our baseline testing and for releases earlier than focal where we
will be pre-installing the package in AWS images with the service
disabled (opt-in) we will test that the service is correctly disabled.
This testing is
Attaching the 2nd display via DisplayPort rather than DVI allows me to
use it again, so I happen to have a solution, but not everyone may be so
lucky.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The 2nd display (attached to DVI) has stopped being detected but is used
by bios and grub (output ceases once the spinning boot animation
starts). I was away for a week but it was working prior to leaving.
I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd
1 - 100 of 764 matches
Mail list logo
