a) The problem was everywhere, but released everywhere else as part of
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2104165 . In the
course of that SRU, we were told not to SRU that changeset to Focal, but SRUing
a targeted fix to Focal might be more acceptable. Hence this bug.
b) I
I went through the procedures mentioned in both the description of this
issue, and the procedure laid out by Andreas in a previous comment. Both
succeed using the proposed version.
The scripts used as well as their output are in the attached tarball.
** Attachment added: "results.tar.gz"
http
** Description changed:
[ Impact ]
Cloud-init 25.1.2 changed installation of systemd-related packaging from
/lib to /usr/lib, which was suggested by lintian packaging warnings.[1]
- This change though is incompatible with debhelper version 13.6ubuntu1 in
- Jammy which now no longer "se
** Description changed:
- Does not affect: Noble, Oracular, Questing
+ [ Impact ]
- In cloud-init 25.1.2, changed systemd-related packaging from /lib TO /usr/lib
- which was suggested by lintian packaging warnings.[1]
+ Cloud-init 25.1.2 changed installation of systemd-related packaging from
+
Integration testing results are attached. Tests were run against EC2,
GCE, LXD containers, and LXD VMs. Reasons for failures are described in
failures.txt. Any necessary local reruns are captured in the *-rerun.txt
files.
** Attachment added: "jenkins_results.tar.gz"
https://bugs.launchpad.net
In an email on May 29, 2025, Christopher Patterson gave a +1 from
Azure's testing.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble verification-needed-oracular
verification-needed-plucky
** Tags added: verification-done verification-done-jammy
verificati
** Summary changed:
- sru cloud-init (25.1.1 update) to focal, jammy, noble, oracular, and plucky
+ sru cloud-init (25.1 update) to focal, jammy, noble, oracular, and plucky
** Changed in: cloud-init (Ubuntu Focal)
Status: In Progress => Won't Fix
** Summary changed:
- sru cloud-init (25
** Description changed:
+ [ Impact ]
+
+ Deployments of images using cloud-init 24.04.1 are stuck at "rebooting"
+ if you use a bonded interface on the network that is used for the MAAS
+ management.
+
+ This happened because the MAAS datasource isn't often ready when cloud-
+ init starts sendin
I managed to trace the source of this issue, at least in my case, to a
missing package "mokutil". Installing this automatically ran the
postinst script again and it now works fine. Hopefully this will help
someone else.
--
You received this bug notification because you are a member of Ubuntu
Bugs
@juergh I have been having issues getting Wi-Fi working on my new laptop
- same card, Lenovo Thinkpad. I can confirm that downloading the new
firmware and adding to /lib/firmware solved my issue, Wi-Fi now detected
and working as expected. Thank you so much, I was tearing my hair out!
--
You rece
This fix in 25.2~1g7a0265d3-0ubuntu1 is currently only available in
devel (questing).
For other stable Ubuntu releases, cloud-init has to be released through
the SRU process. This will be SRUed as 25.1.2. These have been uploaded
and are waiting for acceptance into the '-proposed' pockets. Once th
** Summary changed:
- sru cloud-init (25.1.2 update) to focal, jammy, noble and oracular
+ sru cloud-init (25.1.1 update) to focal, jammy, noble, oracular, and plucky
** Changed in: cloud-init (Ubuntu Plucky)
Status: Fix Released => In Progress
** Also affects: cloud-init (Ubuntu Questing
** Summary changed:
- sru cloud-init (25.1.1 update) to focal, jammy, noble and oracular
+ sru cloud-init (25.1.2 update) to focal, jammy, noble and oracular
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
Thanks for the context Dave. I'll go ahead and remove the deprecation
message and file something in cloud-init upstream about better
supporting or documenting this use case.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you
This is for identifying the filesystem that contains cloud-init metadata
at its root. Traditionally, cloud-init has used 'cidata' for this label.
Not using 'cidata' was recently deprecated because cloud-init's
generator only looks for the 'cidata' label. This can result in the
generator failing to
See https://github.com/canonical/cloud-init/pull/6167 for cloud-init
fix.
** Project changed: cloud-init => cloud-init (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Importance: Unknown => Undecided
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => New
** Changed in: cloud-init
Seems like the same issue on a Dell Latitude 7420.
If anyone triages this, let me know what logs you need and I'll try to
provide them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091130
Title:
The python bug was rolled back so I was able to get a successful build on focal:
https://launchpad.net/ubuntu/+source/cloud-init/24.4.1-0ubuntu0~20.04.2/+build/30422169
We should now be able to test focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Oracular upgrading cloud-init 24.4.1-0ubuntu0~24.10.2 to
24.4.1-0ubuntu0~24.10.3:
- No errors on upgrade
- No errors on reboot
- `dpkg -l | grep cloud-init` shows no cloud-init-base, though `apt install
cloud-init-base` reports `Note, selecting 'cloud-init' instead of
'cloud-init-base'. cloud-in
** Description changed:
[ Impact ]
Cloud-init is currently broken on `do-release-upgrade` to plucky. In
plucky, cloud-init's packaging has been broken out into multiple binary
packages:
- cloud-init-base contains almost all of what used to be cloud-init
- minus some dependencies tha
If I inject libfreetype 2.10.1 and libfontconfig 2.13.1 from the Focal
archive via LD_LIBRARY_PATH, it clears up the font rendering problems
with variable fonts.
So upgrading those libraries in the gnome-3-28-1804 snap would likely
solve the problem. There is still the possibility it would introdu
So the walc snap is using gnome-3-28-1804 content snap, which provides
Freetype 2.8.1.
Looking at the Freetype website, they specifically call out fixes for
OpenType variation fonts in Freetype 2.9 ("If you are going to use
variation fonts, please update to this version since it comes with some
im
Plucky, oracular, and noble packages have been uploaded.
** Changed in: cloud-init (Ubuntu Plucky)
Status: Triaged => Fix Committed
** Changed in: cloud-init (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu Focal)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu Jammy)
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/2092333
Tit
** Attachment added: "System Dmesg"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2104054/+attachment/5868346/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Description changed:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
** Description changed:
+ [ Impact ]
+
+ Cloud-init is currently broken on `do-release-upgrade` to plucky. In
+ plucky, cloud-init's packaging has been broken out into multiple binary
+ packages:
+ - cloud-init-base contains almost all of what used to be cloud-init
+ minus some dependencies tha
*** This bug is a duplicate of bug 2092333 ***
https://bugs.launchpad.net/bugs/2092333
** This bug has been marked a duplicate of bug 2092333
package cloud-init-base 24.4-0ubuntu1 failed to install/upgrade: Versuch,
»/etc/cloud/cloud.cfg« zu überschreiben, welches auch in Paket cloud-init
** Changed in: nvidia-graphics-drivers-550 (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/2103957
Title:
Black screen after login, workaround: TTY switch
FWIW this should be renamed, this isn't an incompatibility, it's a
regression in IPv6 firewall capabilities.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104282
Title:
iptables incompatibility
To
> the effect being slightly different on Noble than on plucky?
Why is the effect different?
Agreed though. The change in 2104238 should also address this issue.
Cloud-init has removed DSA support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
** Description changed:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
** Bug watch added: Debian Bug tracker #1082371
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082371
** Also affects: libzip (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082371
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
Public bug reported:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
This issue b
** Description changed:
The main symptom is that, after the system boots up fine, reaches GDM,
and the user logs in, the screen turns black before the Gnome Desktop
appears. Switching to a text-based TTY and back to the Desktop works
around it, making the Desktop show and work normally.
Great post. It was much needed. Love your simplistic style of explanation.
https://www.loweskidsworkshop.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540507
Title:
linux: 3.2.0-98.138 -propo
Zachary, are you saying they're breaking while using the cloud-init
currently in proposed (24.4.1-0ubuntu0~.2)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAA
At the very least, this will result in IPv6 openstack instances failing to boot:
https://github.com/canonical/cloud-init/blob/main/cloudinit/sources/DataSourceOpenStack.py#L78
I think this needs to be treated as a critical issue.
--
You received this bug notification because you are a member of
It looks like the cause of our build failure is due to a recent change
in Focal's python.
https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/2103454
Does that mean our package needs to wait until that can be fixed?
--
You received this bug notification because you are a member of Ubuntu
B
f:fe23:4567:890a%25eth0]/')
But now, we get:
(focal-amd64)james@cow:/build/cloud-init-M2qWdO/cloud-init-24.4.1$ dpkg -l |
grep python3.8
ii libpython3.8-minimal:amd64 3.8.10-0ubuntu1~20.04.16 amd64
Minimal subset of the Python language (version 3.8)
ii libpython3.8-stdlib:
I'm looking into the problem. Something appears to have changed in the
sbuild environment (or deps) that is causing some unrelated
failures...it now also fails when I try to build the previous release
that succeeded previously.
--
You received this bug notification because you are a member of Ubu
probleme resolu pour moi, Merci!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097945
Title:
backport-iwlwifi fails to build against 6.11 HWE
To manage notifications about this bug go to:
https:
This bug isn't really the package's or APT's fault.
It happens because your terminal emulator needs to decide where the URL
ends. Because it's common to use URLs at the end of sentences, it
intentionally removed the trailing dot.
I'm not sure we can do much about this. If the trailing dot was inc
** Description changed:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
t
The upstream project still builds with 1.17 so don't see 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/2097790
Title:
--formatter json broken
To manage notifications about this bug go to
** Changed in: cloud-init (Ubuntu Plucky)
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/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To
** Description changed:
+ [Impact]
+
+ Cloud-init 24.4.1 included a change[1] that results in a traceback on MAAS
systems. This is because the cloud-init MAAS datasource code wraps behavior
provided by the readurl() helper function, so because the readurl() helper
function signature changed bu
Unfortunately, no, I have no ETA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To manage notifications about this bug go to:
https://bu
@athos-ribeiro, what information do I need to attach here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100621
Title:
Overlayroot: Keyboard and mouse unresponsive after resume after
enabling ove
Updated, thanks for the help but its not for me now as I have since
uninstalled as I am not using this in a critical environment but other's
may, but I could still help.
** Also affects: cloud-initramfs-tools
Importance: Undecided
Status: New
** No longer affects: cloud-initramfs-tools
networkctl output:
root@ip-192-168-11-242:/home/ubuntu# networkctl status
● Interfaces: 1, 2, 3
State: routable
Online state: online
Address: 192.168.11.242 on ens5
192.168.12.6 on ens6
** Description changed:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
t
networkd debug logs attached from after reboot on plucky
** Attachment added: "networkd_debug_plucky"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2101860/+attachment/5864048/+files/networkd_debug_plucky
--
You received this bug notification because you are a member of Ubuntu
Bu
Also adding netplan and systemd here as the rendered networkd config
doesn't change, and the netplan apply call is racy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2101860
Title:
Different networ
networkd debug logs attached from after reboot on oracular
** Attachment added: "networkd_debug_oracular"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2101860/+attachment/5864049/+files/networkd_debug_oracular
** Also affects: systemd (Ubuntu)
Importance: Undecided
Stat
It appears Plucky is missing the proper rule:
root@ip-192-168-11-242:~# ip rule
0: from all lookup local
32765: from 192.168.15.230 lookup 101 proto static
32766: from all lookup main
32767: from all lookup default
Compared to Oracular:
root@ip-192-168-1-227:/usr/lib/systemd/network# ip ru
Public bug reported:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
two (total) I
> When removing the "use-routes" dhcp-overrides for ens6 and running
"netplan apply" it seems to be working.
The default for this is true, so unless the documentation is wrong, I
don't think that changing this is actually doing anything.
There is certainly some racy behavior though. Using a scrip
Plucky routes:
ubuntu@ip-192-168-11-242:~$ ip route
default via 192.168.0.1 dev ens5 proto dhcp src 192.168.11.242 metric 100
default via 192.168.0.1 dev ens6 proto dhcp src 192.168.12.6 metric 1003 mtu
9001
192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.11.242 metric 100
192.168.0
I created a file at:
/etc/apt/sources.list.d/noble.sources.list
with the contents:
deb http://ports.ubuntu.com/ubuntu-ports noble main restricted universe
multiverse
deb http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe
multiverse
deb http://ports.ubuntu.com/ubuntu-p
Yes, we'll get it backported ASAP.
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because y
** Changed in: rabbitmq-server (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/2085277
Title:
Merge rabbitmq-server from Debian unstable for pluck
Public bug reported:
Screen randomly freezes. I can move the mouse but not click on anything.
Works again after a hard reset.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11
Uname: Linux 6.11.0-19-generic
This issue was caused by a conflict between the new JSON module in
elixir 1.18.0 and the vendored JSON module in the rmq source.
My fix is a workaround that renames the vendored module to JSONOLD to
avoid this conflict - the Elixir version is not a drop in replacement
for the built in version.
**
ntu)
Importance: Undecided => High
** Changed in: rabbitmq-server (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed in: rabbitmq-server (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
During a routine software update:
dpkg: error processing archive
/tmp/apt-dpkg-install-94wGea/06-avldrums.lv2-data_5%3a0.4.1_all.deb (--unpack):
trying to overwrite '/usr/lib/lv2/avldrums.lv2/Black_Pearl_4_LV2.sf2', which
is also in package avldrums.lv2-soundfont 0.7.2-1bu
+1 for backporting 'Support persistent headless sessions' to 24.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072130
Title:
RDP doesn't keep sessions alive in Ubuntu 24.04 after disconnectin
Only Noble and Oracular will have had the snapshot version that caused
this problem so no need to fix in Plucky.
** Also affects: ceph (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: ceph (Ubuntu Plucky)
Importance: Undecided
Assignee: Maksym Medvied (medvie
** Also affects: ceph (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ceph (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: ceph (Ubuntu Plucky)
Importance: Undecided
Assignee: Luciano Lo Giudice (lmlogiudice)
Status: Confir
Is it possible to get the resulting tarball from `cloud-init collect-
logs`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100620
Title:
cloud-init not importing ssh keys
To manage notifications a
Rejecting focal target; 17.2.x is only found in Jammy in Ubuntu
There are however Cloud Archive targets that focal.
** Changed in: ceph (Ubuntu)
Status: New => Invalid
** Changed in: ceph (Ubuntu Jammy)
Status: New => Triaged
** Changed in: ceph (Ubuntu Focal)
Status: New =
** Changed in: openvswitch (Ubuntu)
Assignee: James Page (james-page) => (unassigned)
** Changed in: openvswitch (Ubuntu Bionic)
Assignee: James Page (james-page) => (unassigned)
** Changed in: openvswitch (Ubuntu Eoan)
Assignee: James Page (james-page) => (unassigned)
To add, Daniel seems to be tagging a different issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079799
Title:
Restarting Gnome Shell with Alt-F2 R freezes Gnome in Xorg
To manage notifications
I confirm that LTS 24.04.2 has resolved 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/2079799
Title:
Restarting Gnome Shell with Alt-F2 R freezes Gnome in Xorg
To manage notifications ab
Public bug reported:
Overlayroot: Keyboard and mouse unresponsive after resume after enabling
overlayroot
** Affects: xorg-server
Importance: Undecided
Status: New
** Affects: cloud-initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Package changed: ubuntu
** Also affects: python-openstackclient (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: python-openstackclient (Ubuntu)
Status: New => Invalid
** Changed in: python-openstackclient (Ubuntu Oracular)
Status: New => Triaged
** Changed in: python-openstack
** Changed in: neutron
Assignee: James Page (james-page) => (unassigned)
** Changed in: neutron
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831986
Hello Eric, or anyone else affected,
Accepted cinder into dalmatian-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-a
In addition to the regression tests posted above, tests for this
particular feature were tested on package build against a fake IMDS.
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
** Tags added: veri
Regression test results on EC2. Jammy failures are due to test changes
for netplan that haven't yet been SRUed.
** Attachment added: "test_results_2094858.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094858/+attachment/5860861/+files/test_results_2094858.tar.gz
--
You r
This should be fixed in cloud-init version 25.1-0ubuntu2 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098988
Title:
cloud-init datasource failure on Azure
To manage notifications about this bug
** 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.
https://bugs.launchpad.net/bugs/2098988
Title:
cloud-init datasource failure on Azure
To manage notifications
** Changed in: libsass-python (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095581
Title:
[MIR] libsass-python
To manage notifications about this bug go t
** Changed in: libsass (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095582
Title:
[MIR] libsass
To manage notifications about this bug go to:
https://bug
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-done-noble verification-done-oracular
--
You received thi
Test results
** Attachment added: "test_results_2097319.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2097319/+attachment/5860234/+files/test_results_2097319.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-neede
Test results
** Attachment added: "test_results_2094179.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094179/+attachment/5860136/+files/test_results_2094179.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-neede
I confirm this issue, this issue is due to mutter which was fixed on:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3908?diff_id=1187609&start_sha=c3365ccbb2d1533e45622a75d065bdbb4671d507
Its milestone is part of Gnome 46. When will this be in the updates?
This is a critical stability iss
Test results attached
** Attachment added: "test_results_2094208.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094208/+attachment/5859269/+files/test_results_2094208.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verificat
Thanks for the offer to cloud-init! We'll likely take you up on that
soon.
It looks like your bug was something introduced in the last release, but it was
a particularly instance of a more general change in cloud-init. Cloud-init will
exit 2 when it hits recoverable errors. This is new behavior
I did a bit of general package hygiene:
libsass (3.6.6-0ubuntu1) plucky; urgency=medium
* New upstream point release which == 3.6.5+20231221.
* d/libsass1.symbols: Refactor to only care about symbols that
are part of the libsass1 ABI.
* d/rules: Enable hardening.
-- James Page Fri
bsass (Ubuntu)
Status: Incomplete => New
** Changed in: libsass (Ubuntu)
Assignee: James Page (james-page) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095582
Title:
[M
I dug into the LTO for this package - it was fixed in a later package
update after impish:
libsass (3.6.5+20231221-1) experimental; urgency=high
[ upstream ]
* new development snapshot
+ fix most urgent issues in 2023;
closes: bug#1051893, #1051894, #1051895;
CVE-2022-26592 CV
coverage
* set urgency=high due to security bugfixes
* enable link-time optimization;
closes: bug#1015519, thanks to Matthias Klose
-- Jonas Smedegaard Thu, 21 Dec 2023 19:57:09 +010
** Changed in: libsass (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
** Changed
Added bug subscription for ubuntu-openstack team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095582
Title:
[MIR] libsass
To manage notifications about this bug go to:
https://bugs.launchpad.net/
I've added autopkgtests to this package with my most recent upload -
this executes sasstests.py using pytest against the installed packages.
** Changed in: libsass-python (Ubuntu)
Status: Incomplete => New
** Changed in: libsass-python (Ubuntu)
Assignee: James Page (ja
Test results ensure /var is mounted are attached for each series.
** Attachment added: "test_results_2097441.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2097441/+attachment/5859141/+files/test_results_2097441.tar.gz
** Tags removed: verification-needed verification-neede
Test results attached. Tested cases where bootcmd are included and not
included in user data representing the cases that previously resulting
in waiting vs not waiting.
** Attachment added: "test_results_2094149.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094149/+attachm
** Description changed:
[ Impact ]
There was an upstream change that moved
`RequiresMountsFor=/var/lib/cloud` from cloud-init-local.service to
cloud-init-main.service. Since cloud-init-main.service was patched out
of stable downstreams, this `RequiresMountsFor` line was accidentally
1 - 100 of 18475 matches
Mail list logo
