mesa (24.0.2-1ubuntu1) noble; urgency=medium
* Merge from Debian.
* radeon-fix-gnome-shell-crash.diff: Fix a regression crashing
gnome-shell. (LP: #2054851)
-- Timo Aaltonen Thu, 29 Feb 2024 09:40:21 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
**
Hello, thanks for the report; note that the fstab(5) and mount(8) man
pages both say "user", singular, not "users", plural. That's probably
why your mount command didn't work when run as a user.
I don't know about the gio or udisksctl tool errors, I'm unfamiliar with
their operation. Maybe they
I suggest talking with the virtualbox devs:
[4.040754] UBSAN: array-index-out-of-bounds in
/tmp/vbox.0/common/log/log.c:1791:41
It may or may not be related to your audio issues, but it can't be good.
Thanks
** Information type changed from Private Security to Public
--
You received this
https://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2023q2/017134.html and original post relates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2026757
Title:
Change abandoned by "Julia Kreger " on branch:
stable/2023.1
Review: https://review.opendev.org/c/openstack/ironic/+/910518
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Indeed, and unfortunately it seems like I've been able to identify the
root cause which is still present in 2.90. What changed, we're no longer
seeing a segfault which was the tell-tale sign we were looking for, but
instead we just see it quietly exit with no trace. This led me to
getting a setup
Public bug reported:
I am attempting to add an I2S DAC for line level output on a Raspberry
Pi 5.
The hardware is a Pimoroni Audio DAC Shim which uses the
dtoverlay=hifiberry-dac
The hardware, when used with Raspberry Pi OS (Bookworm) configured per
instructions works fine, this I2S output DAC
Actually, it seems that most programs ignore the openssl.cnf anyway for
security(?) reasons. Played a bit with MinTlsVersion and it did not
change the request which is being sent. Luckily I could ask the DevOps
for the nginx versions used and they have versions with the openssl 3
fix; that comes
This bug was fixed in the package tzdata - 2024a-0ubuntu0.20.04
---
tzdata (2024a-0ubuntu0.20.04) focal; urgency=medium
* New upstream version (LP: #2052739):
- Kazakhstan unifies on UTC+5 beginning 2024-03-01.
- Palestine springs forward a week later after Ramadan.
-
This bug was fixed in the package tzdata - 2024a-0ubuntu0.22.04
---
tzdata (2024a-0ubuntu0.22.04) jammy; urgency=medium
* New upstream version (LP: #2052739):
- Kazakhstan unifies on UTC+5 beginning 2024-03-01.
- Palestine springs forward a week later after Ramadan.
-
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package tzdata - 2024a-0ubuntu0.23.10
---
tzdata (2024a-0ubuntu0.23.10) mantic; urgency=medium
* New upstream version (LP: #2052739):
- Kazakhstan unifies on UTC+5 beginning 2024-03-01.
- Palestine springs forward a week later after Ramadan.
-
+1 from security. Please remember to also release it to the -security
pocket on all releases in addition to just -updates.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
The 7 day aging period will be hit later today. Releasing it now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2052739
Title:
tzdata 2024a release
Status in tzdata
Thanks for continued investigation.
A reproducer would be valuable as it would allow me to verify
independently the patch is effective, within the limits of the
understanding of the situation of course and that can be especially
time-consuming when not having access to the remote server. :/
A
@security, could you please sign off on this tzdata SRU, according to
the SRU procedure[1] for this package?
1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in
** Description changed:
As part of time_t work, -Werror=implicit-function-declaration is being
- set, but that causes the following FTBFS:
+ set on armhf, but that causes the following FTBFS on any arch with the
+ same -Werror=implicit-function-declaration setting:
Public bug reported:
Installing dnsmasq-base v2.90-0ubuntu0.22.04.1 causes network device
virbr0 to shut down during the boot-up process. Device virbr0 is
installed by the libvirtd daemon. libvirtd gets an unexpected error when
dnsmasq is called and then the address record for virbr0 is
Public bug reported:
As part of time_t work, -Werror=implicit-function-declaration is being
set, but that causes the following FTBFS:
https://launchpadlibrarian.net/716768885/buildlog_ubuntu-noble-
armhf.pam_1.5.3-5ubuntu1_BUILDING.txt.gz
In file included from obscure.c:42:
obscure.c: In
This bug was fixed in the package debootstrap - 1.0.126+nmu1ubuntu0.7
---
debootstrap (1.0.126+nmu1ubuntu0.7) jammy; urgency=medium
* Disable usrmerge code on noble+ as they ship symlinks in base-files,
and the code is incompatible (and no longer needed) (LP: #2054925)
The verification of the Stable Release Update for debootstrap has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
On
root@known-seal:~# apt policy debootstrap
debootstrap:
Installed: 1.0.126+nmu1ubuntu0.7
Candidate: 1.0.126+nmu1ubuntu0.7
Version table:
*** 1.0.126+nmu1ubuntu0.7 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
500
I eventually figured out that the control bar for my external speaker
had been turned off somehow in the process. I turned it on and it has
worked fine since.
On Thursday, February 29, 2024 at 07:46:16 AM EST, Pablo Fontoura
<2043...@bugs.launchpad.net> wrote:
Same thing here. Fresh
The bug is present in 22.04 LTS...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1276796
Title:
Long hostname placeholder for PS1 (\H) fails in Bash
Status in bash package
The regression in debuerreotype is expected due to the included change
from the previous SRU (LP: #1990856), packages are now extracted in a
different order for the test case, hence some time stamps shifted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I have uploaded a change to add the 30d cleanup age.
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
On Thu, Feb 29, 2024 at 10:19:40AM -, Frank Heimes wrote:
> Fix Committed with having:
> pam | 1.5.3-4ubuntu1 | noble-proposed | source
FTR this has been temporarily reverted, but it will be fix-committed again
shortly
--
You received this bug notification because you are a member of
Building an noble image with ubuntu-image, using debootstrap
1.0.126+nmu1ubuntu0.7, worked (on a amd64 Jammy).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2054925
Deferring tracking to the other bugs
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
** Changed in: policykit-1 (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Tags removed: rls-nn-incoming
--
You
** Changed in: systemd (Ubuntu Noble)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I agree with Nick, regular cleaning *and* cleaning at /boot is best
behavior.
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Also affects: systemd (Ubuntu Noble)
Importance: Wishlist
Status: Confirmed
--
You received this bug notification because you are a member
This bug was fixed in the package newt - 0.52.24-2ubuntu1
---
newt (0.52.24-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2054152). Remaining changes:
+ Remove libnewt0.52.preinst altogether, which contains destructive
operations with none of the
Public bug reported:
$ busybox wget https://start.ubuntu.com
Floating point exception (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: busybox (not installed)
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules:
Graham pointed out that the upload was actually to unstable and
therefore autosync'ed already!
I'm going to keep the bug open until it migrates due to the possibility
of some testsuite failures.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Xz-utils 5.6.0 was released last Friday. It features a much faster
decompression code on all platforms but on x86_64 in particular, it is
60% faster in my testing. It also aligns better current practices of
enabling multi-threading by default (always with a default memory
Maybe we could do something like this:
--- a/libstdc++-v3/include/pstl/parallel_backend_tbb.h
+++ b/libstdc++-v3/include/pstl/parallel_backend_tbb.h
@@ -15,6 +15,11 @@
#include "parallel_backend_utils.h"
+#ifndef TBB_SUPPRESS_DEPRECATED_MESSAGES
+# define TBB_SUPPRESS_DEPRECATED_MESSAGES 1
(In reply to Jonathan Wakely from comment #11)
> Yes, it was fixed by r11-4187 but the problem is still present on the gcc-10
> branch.
I think that commit simply makes it possible to use oneTBB, which
doesn't give a warning. But if you use TBB 2020.3 or older, then you
still get a warning.
--
Same thing here. Fresh 23.10 installation and no sound.
My USB headset is working properly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2043524
Title:
audio
** Also affects: heimdal (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: heimdal (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: heimdal (Ubuntu Focal)
Status: New => Fix Released
** Changed in: heimdal (Ubuntu Jammy)
Status:
cloud-init upstream PR adding test coverage for this issue:
https://github.com/canonical/cloud-init/pull/4982
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055397
Title:
Attaching cloud-init logs, which include journal logs.
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055397/+attachment/5750656/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Marking cloud-init as invalid as I think there is no workaround to fix this
issue.
Adding netplan.io for reference and awareness.
After confirmation from systemd-networkd, I wonder if it would be
feasible / reasonable to backport
https://github.com/systemd/systemd/pull/19344 to focal.
--
You
Fix Committed with having:
pam | 1.5.3-4ubuntu1 | noble-proposed | source
** Changed in: pam (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-z-systems
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Cloud-init introduced a feature to configure policy routing on AWS EC2
instances with multiple NICs in
https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb
targeting v24.1.
Cloud-init generates the following netplan config:
```
$ cat
This bug was fixed in the package cron - 3.0pl1-184ubuntu1
---
cron (3.0pl1-184ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055105). Remaining changes:
- debian/control: Move MTA to Suggests field.
- debian/cron.default: change to a deprecated message
This bug was fixed in the package kbd - 2.6.4-2ubuntu1
---
kbd (2.6.4-2ubuntu1) noble; urgency=medium
* Merge with Debian unstable (LP: #2055065). Remaining changes:
- Add setfont, kbd_mode, and loadkeys to initramfs for console-setup.
- Use ckbcomp to get the keyboard
Also focal (20.04.6) does have the bug now, per comment #23.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages
I must have forgotten to actually move this into the correct pulse to
fix it, so it's in the 2 weeks starting the week after next now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
48 matches
Mail list logo
