** Changed in: cloud-init (Ubuntu)
Status: Confirmed => 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/1759406
Title:
sru cloud-init (17.2-35-gf576b2a2-0ubuntu1~16.04.1 update to
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
* cc_apt_pipelining: stop disabling pipelining by
** Summary changed:
- cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-44-g7c07af28-0ubuntu1
+ cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 -> 18.5-45-g3554ffe8-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When debugging a netplan configuration issue, I wanted debug output so I
ran `netplan apply --debug`; this produced no output and apparently
applied my configuration. (It turns out, of course, that what I wanted
to run was `netplan --debug apply`.)
I would expect either to
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
-*
+* cc_apt_pipelining: stop disabling
This version is in disco-proposed, so marked that 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/1819067
Title:
cloud-init SRU: 18.5-21-g8ee294d5-0ubuntu1 ->
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
*
See the changelog entry below for a full list of changes and
Thanks Steve!
We're going to use block-proposed on this bug to hold cloud-init in
-proposed whilst we perform the manual SRU testing process.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When building the latest cloud-init package, lintian reports:
W: cloud-init: package-installs-into-obsolete-dir etc/bash_completion.d/ :
^etc/bash_completion.d/ -> usr/share/bash-completion/completions Ensure new
filename matches stricter requirements (see
The full list of changes, generated from the git log:
- Support locking user with usermod if passwd is not available. [Scott Moser]
- Example for Microsoft Azure data disk added. [Anton Olifir]
- clean: correctly determine the path for excluding seed directory
(LP: #1818571)
-
Public bug reported:
We would like to upload a new upstream snapshot of cloud-init to disco.
This includes a number of desirable bug fixes, in particular:
* clean: correctly determine the path for excluding seed directory (LP:
#1818571)
* azure: Filter list of ssh keys pulled from fabric
* EC2:
(Project task dropped because this is only an issue in the Ubuntu
packaging.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813667
Title:
Update netplan dependency package
To manage notifications
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813667
Title:
Update netplan dependency package
To manage notifications about this bug go to:
cloud-init does now support vendor-data.
** Changed in: cloud-init
Status: Triaged => Fix Released
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the speedy fix, Alberto!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818748
Title:
`ubuntu-drivers install --gpgpu` is strangely permissive about input
with version numbers
To
Public bug reported:
It would be good if:
```
$ ubuntu-drivers install --gpgpu amd
No drivers found for installation.
```
listed the available drivers (if any) and:
```
$ ubuntu-drivers install --gpgpu nvidia:370
No drivers found for installation.
```
listed the available versions for the
Public bug reported:
When trying to work out what the correct input format for installation
was (cf. bug 1818746), I discovered that `install --gpgpu` is extremely
permissive with what strings it will accept when a version number is
given:
```
# The correct invocation (AIUI)
$ ubuntu-drivers
Public bug reported:
As a user, I would like to decide on one of the drivers available to me
and then install it. So I list my options:
```
$ ubuntu-drivers list
nvidia-driver-410
nvidia-driver-390
```
Great, I'll install 410:
```
$ ubuntu-drivers install --gpgpu nvidia-driver-410
No drivers
I'm actually being generous above; a user is much more likely to do:
```
$ ubuntu-drivers install nvidia-driver-410
usage: ubuntu-drivers [-h] [--package-list PATH]
[--gpgpu [driver[:version][,driver[:version
[]
ubuntu-drivers: error: unrecognized
Hi Matti,
That sounds like a separate bug from this one. Could you file a new bug
(with the output of `cloud-init collect-logs` from a failing instance
attached), please?
Thanks!
Dan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this still an issue that needs cloud-init work?
** Changed in: cloud-init
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/1732522
Title:
[2.3] Ephemeral boot
** Changed in: cloud-init
Status: Triaged => Fix Released
** Changed in: cloud-init
Milestone: 0.7.2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1118815
Title:
Remove
** Changed in: cloud-init
Status: New => Triaged
** Changed in: cloud-init
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724128
Title:
Need a Success /
Public bug reported:
do-release-upgrade launches a screen if `screen` is available, but it
doesn't Recommend it so it isn't clear from an archive perspective that
it uses it.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: cloud-init
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/1619420
Title:
snappy removal of dpkg-query breaks lsb_release --all
To manage notifications
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571822
Title:
Azure: cloud-init will not set password on existing user
To manage notifications about this bug go to:
It's not totally clear to me what the required cloud-init changes here
are, please feel free to move the task back to New with some
clarification.
** Changed in: cloud-init
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Hamish,
Do you know how grub-legacy-ec2 ended up on your system? What
environment is this system running in?
Thanks!
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Whit,
Thanks for filing this bug. The OpenStack and ConfigDrive data sources
aren't the same, but they are closely related; OpenStack uses the
OpenStack network metadata source to fetch configuration whereas
ConfigDrive uses a locally-mounted drive to fetch configuration.
Could you run
** Package changed: cloud-init (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761471
Title:
impossible to install bionic crypt on usb support
To manage notifications about this
Hi Nathaniel,
Thanks for using cloud-init and for filing this bug! Can you please run
`cloud-init collect-logs` in a failing instance and attach the output to
this bug?
Thanks!
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
(I've added lxd to the bug, as it's also a component in the issue.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665943
Title:
Home directory has wrong ownership if created by lxd in arranging a
Dropping this from the cloud-init Ubuntu package so we're just tracking
it in one place.
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704402
Title:
I've just been able to reproduce this by following these steps:
```
$ lxc init ubuntu:x c1
$ lxc config set c1 raw.idmap "both 1000 1000"
$ lxc config device add c1 foo disk path=/home/ubuntu/foo
source=/home/daniel/jjl
$ lxc start c1
$ lxc exec c1 -- ls -lah /home/ubuntu
total 16K
drwxr-xr-x 4
** No longer affects: virtualbox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815409
Title:
18.04 Vagrant Box long boot time
To manage notifications about this bug go to:
Hi Coury,
Thanks for filing this bug, and for using Ubuntu! Could you clarify
what platform you're using when you're seeing these issues? If the host
isn't Ubuntu, then you'll need to file a bug with whoever provided you
with that version of Virtualbox (presumably Virtualbox upstream?).
** 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/1777827
Title:
remove log from Vagrantfile
To manage notifications
** Changed in: walinuxagent (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/1806972
Title:
walinuxagent no longer ships
It turns out there was an issue with the way that Microsoft was testing
these images, which has now been resolved. These packages have been
signed off on.
** Tags removed: verification-failed-bionic verification-failed-cosmic
verification-failed-trusty verification-failed-xenial
** Tags added:
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809408
Title:
weather applet crashes on logout
On Wed, Dec 19, 2018 at 04:10:45PM -, Joseph Salisbury wrote:
> Are you able to manually able to start the daemon after seeing that the
> file exists?
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yep, I have now done so:
$ ls -la /dev/vmbus/hv_kvp
crw--- 1 root root 10, 55 Dec 18 22:31 /dev/vmbus/hv_kvp
Joe, I've also imported your SSH keys in to ubuntu@test-
slgyvlgaldgcyzqkzuoz.cloudapp.net if there's any other poking around you
want to do.
--
You received this bug notification
This was from our test suite, so I don't have direct access to an
instance, but using the manifest, it is:
$ grep tools ~/manifest.txt
bcache-tools 1.0.8-3
dosfstools 4.1-2
initramfs-tools 0.131ubuntu15
initramfs-tools-bin
** Description changed:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to
Public bug reported:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to sign the
On disco, we're seeing the following in the cloud image testing:
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft KVP: KVP starting; pid is:204
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft KVP: open /dev/vmbus/hv_kvp failed;
error: 2 No such file or directory
Dec 17 19:37:43 jenk-ituzztgzwdxjesafyoft
Public bug reported:
The default key format used by OpenSSH changed in version 7.8[0] to the
openssh format (rather than the previous "pem" format). (disco is the
first Ubuntu version to include an OpenSSH version later than 7.8; it's
currently at 7.9p1.)
paramiko doesn't have full support for
For clarity, I absolutely agree that this is a different type of
support, and therefore would need to be a distinct field in the data
(and perhaps would need to be just a boolean, as I don't believe
Canonical has committed to a particular timeframe for ESM for precise,
trusty or xenial?). It
Public bug reported:
ubuntu-distro-info is an important source of information about the
current support state of the various Ubuntu releases. Currently,
however, it provides no information about the status of Extended
Security Maintenance for Ubuntu releases, which is an important aspect
of
>From the cloud image publication, we currently use distro-info-data to
determine whether a particular image is valid for a variety of reasons;
we currently have to perform manual steps for precise. When looking at
automating this, it became apparent to me that we won't be the only
Ubuntu
Hi Aaron,
I don't believe this is a cloud-images bug; I'm not 100% sure what the
correct component is, so I'll just assign it to Ubuntu as a whole.
Thanks,
Dan
** Also affects: ubuntu
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => Invalid
--
Hi Robie,
Thanks for the reminder. I already have marked the SRU bug as
verification-*-failed[0]; I filed this due to it also affecting disco.
However, it has been pointed out to me that this file has actually been
absent for several releases, so probably isn't the root cause of the
issue we're
Microsoft's testing has turned up
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1806972 as
an issue in the latest version of walinuxagent, which will need
addressing before we can SRU it.
** Tags removed: verification-needed-bionic verification-needed-cosmic
Public bug reported:
This file was previously shipped by walinuxagent to unambiguously
configure cloud-init to use the Azure data source. It is no longer
present in the latest version in disco, or the versions in
{trusty,xenial,bionic,cosmic}-proposed.
This file should be restored, so that
** Changed in: livecd-rootfs (Ubuntu Xenial)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776706
Title:
clean_loops can't be called multiple times with set -u
To
Public bug reported:
Even once bug 1804709 is addressed and the hook can run at all, it still
won't work on default Ubuntu installations (which don't have Python 2)
because the shebang points at /usr/bin/python.
** Affects: gnome-screenshot (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
As you can see here:
```
$ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py
ubuntu/devel [ 17:38:44 ]
+#!/usr/bin/python
+
'''Apport package hook for
** Tags added: verification-needed-bionic verification-needed-cosmic
verification-needed-trusty verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799498
Title:
New Microsoft
On Tue, Oct 16, 2018 at 12:20:21PM -, John Patrick wrote:
> Cheers all,
> Just updated myself and picked up '20181015.0.0' and vagrant up works cleanly.
> John
Great, thanks for the confirmation!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi John,
I've just tested with the latest Vagrant box, and this looks good to me
now:
$ vagrant box update
==> default: Checking for updates to 'ubuntu/cosmic64'
default: Latest installed version: 20181008.0.0
default: Version constraints:
default: Provider: virtualbox
==> default:
** Changed in: livecd-rootfs (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/1797170
Title:
xenial cloud image builds fail due to /lib/modules
On Fri, Oct 12, 2018 at 07:18:51AM -, Georgi Georgiev wrote:
> Any reason why the executable bit of diff-highlight is stripped?
>
> If I run `sudo make -B -C /usr/share/doc/git/contrib/diff-highlight
> diff-highlight` the generated file is executable, but the one shipped
> with the package is
Public bug reported:
I use more than one browser profile, only one of which is logged in to
Launchpad. When using ubuntu-bug to report a bug, it will open the page
in whichever one happened to be focused last. If this browser profile
isn't logged in to Launchpad, it will redirect me to a login
Public bug reported:
>From time-to-time, when using cosmic, my keyboard presses will no longer
register. This applies to both the internal laptop keyboard and my
external keyboard. I haven't identified any particular trigger of this.
The one workaround I have found is to use the mouse (which
Is there anything specific that I can do to capture more information
when this happens again? Browsing through the systemd journal didn't
reveal anything obvious, but I don't necessarily know what to look for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
build of the ubuntu-cpc project; it will fail without a
fix, and pass with a fix.
[Regression Potential]
The fix is to modify the `mkdir` to `mkdir -p`, so the potential for
regression is very low.
** Affects: livecd-rootfs (Ubuntu)
Importance: Critical
Assignee: Dan Watkins (daniel
: (unassigned) => Dan Watkins (daniel-thewatkins)
** 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.
https://bugs.launchpad.net/bugs/1797170
Title:
xenial cloud im
>From a pre-LXD-seeding instance, the plot is at
http://people.canonical.com/~dwatkins/1796137-before.svg and the `snap
change` output is:
$ snap change --abs-time 1
Status Spawn Ready Summary
Done2018-10-09T20:41:32Z 2018-10-09T20:41:33Z Ensure
Public bug reported:
Currently, one has to run (multiple) snap commands to get the "logs" of
what snapd has done on a system. This is not only annoying (because the
commands one has to run are dynamic based on change IDs, so it requires
scripting), but also means that normal methods of collating
Further to this, I believe snapd drops its record of old changes at some
point, with no way of understanding what happened before its oldest
recorded change. If these changes were logged, regular log
rotation/retention would retain this information.
--
You received this bug notification because
The box certainly needs to be fixed.
(In the meantime, a workaround if you _really_ need a cosmic box is
probably to manually install the virtualbox-guest-dkms package; I
haven't tested this locally though.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Some more details about what's happening inside snapd:
$ snap changes --abs-time
ID Status Spawn Ready Summary
1Done2018-10-09T20:35:36Z 2018-10-09T20:35:47Z Initialize system state
2Done2018-10-09T20:35:36Z 2018-10-09T20:35:38Z Initialize
As requested on IRC:
$ systemctl cat snap.lxd.daemon.unix.socket
# /etc/systemd/system/snap.lxd.daemon.unix.socket
[Unit]
# Auto-generated, DO NOT EDIT
Description=Socket unix for snap application lxd.daemon
Requires=snap-lxd-9010.mount
After=snap-lxd-9010.mount
X-Snappy=yes
[Socket]
http://people.canonical.com/~dwatkins/1796137.svg is a `systemd-analyze
plot` run on the instance with lxd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796137
Title:
huge and slow image 20181002
This is from a cosmic GCE instance _after_ the lxd snap has been seeded:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @23.527s
This is from a cosmic GCE instance _before_ the lxd snap was seeded
(i.e. with just the google-cloud-sdk snap seeded):
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+"
My understanding of the issue after an IRC conversation with sforshee is
that the modules were intentionally dropped from the kernel packages,
but the corresponding Provides of virtualbox-guest-modules was _not_
dropped from the kernel packaging. This means that when we install
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199151/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199150/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199143/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199145/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 9 16:18 seq
crw-rw 1 root audio 116, 33 Oct 9 16:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199149/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199146/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199144/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199148/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199147/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ In bionic, the vboxsf module was included in linux-modules-...-generic:
+
+ $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep
vboxsf.ko
+ -rw-r--r-- root/root 63238 2018-09-24 10:08
I was able to SSH in before the service completed, so I don't think it's
just a lack of network connectivity.
http://paste.ubuntu.com/p/pSrJJVD8zt/ is the full journalctl output from
the (GCE) instance.
(I'm not 100% sure if this is relevant to the second part of your
comment, Dimitri, but this
This is now fixed.
** Changed in: cloud-images
Status: Confirmed => 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/1585233
Title:
Provide -root.tar.xz for bionic and later
To
** Changed in: cloud-images
Status: Confirmed => 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/1726818
Title:
vagrant artful64 box filesystem too small
To manage notifications
** Changed in: cloud-images
Status: New => Confirmed
** 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/1787506
Public bug reported:
$ sudo apt-get remove -y sendmail-base
100 [ 09:37:15 ]
Reading package lists... Done
Building dependency tree
http://cloud-images.ubuntu.com/cosmic/20180906/unpacked/cosmic-
daily.changelog outlines the changed packages between the two images. I
strongly suspect that the root cause of this is the systemd environment
generator added in the latest version of snapd, so I've added snapd to
this bug.
The
As nobuto notes, the man page says "list of all supported stable
versions"; so either the functionality or the man page needs to be
updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727751
Public bug reported:
When booting an instance with it installed, I see the following in the
log:
Aug 23 20:37:29 ubuntu systemd[1]: nova-agent.service: Found ordering cycle on
basic.target/start
Aug 23 20:37:29 ubuntu systemd[1]: nova-agent.service: Found dependency on
sockets.target/start
Aug
Attached is a tar file that can be used to reproduce the issue.
** Attachment added: "reproducer.tar"
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1788231/+attachment/5178839/+files/reproducer.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have filed this upstream at https://gitlab.gnome.org/GNOME/file-
roller/issues/11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788231
Title:
Silently discards tar contents after a file with
When I attempt to extract the file, I get an "Ignoring malformed pax
extended attribute" error message (screenshot attached).
** Attachment added: "lolpax.png"
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1788231/+attachment/5178727/+files/lolpax.png
--
You received this bug
Public bug reported:
Steps to reproduce:
1) Create a tar file containing /usr/bin/mtr-packet (which has xattrs) (and a
file before and after to confirm the behaviour):
$ tar -C / --xattrs --xattrs-include=\* etc/adduser.conf
usr/bin/mtr-packet etc/aliases -cf reproducer.tar
2) Confirm
401 - 500 of 1128 matches
Mail list logo
