Attached is the diff that was uploaded to Unstable.
** Description changed:
The new sbuild version contains a number of fixes for the unshare
- backend that would be good to have in Noble.
+ backend that would be good to have in Noble. In Debian, we have rebuild
+ all of Debian stable (bookworm
The problem is not with a Raspberry Pi as that works fine:
ubuntu@ubuntu:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu Noble Numbat (development branch)"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.c
(and of course not include the system headers in its include paths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032624
Title:
mumax3 test suite fails against glibc 2.38
To manage notifications a
I'm much more OK with removing the binary than uploading that patch to
glibc.
System headers are just that: headers that reflect the system they're
installed in. The fact that you can sometimes get away with using system
headers when cross-compiling to a different environment is just an
accident,
@enr0n, could you share `snap changes` as well as `snap info lxd`,
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not handled and lxd snap not i
** Also affects: apport-symptoms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Invalid
** Description changed:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
- See attached screenshot for error.
+ /us
Public bug reported:
Should be a simple symlink of some kind, may have to do some Calamares
magic to DTRT based on what the user is called
** Affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a membe
** Changed in: libelfin (Ubuntu)
Status: New => 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/2060786
Title:
libelfin autopkgtests fail against newer clang
To manage notificati
Public bug reported:
The autopkgtests are failing due to clang warnings:
101s autopkgtest [09:01:23]: test test-build-libdwarf++:
[---
101s Output from pkg-config --cflags libdwarf++:
101s -I/usr/include/libelfin
101s success: pkg-config call succeeded
101s success: Compila
th a public SVG somewhere that works
as a replacement, we're falling back to the generic mascot from here:
https://github.com/canonical/ubuntu-desktop-
provision/blob/main/packages/ubuntu_provision/assets/images/mascot.svg
** Affects: ubuntucinnamon-environment (Ubuntu)
Importance: High
I had a look at the Debian tracker for this package, and I'm guessing
it's entangled in a similar transition, so I'd suggest upstreaming the
patch there as well.
I removed the ubuntu-sponsors tag, please add it back when you feel
you've addressed my question :)
--
You received this bug notificat
Why does it have an explicit dependency on the library package? Using
the -dev instead should be enough and would avoid similar problem next
time libtins changes ABI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: calamares (Ubuntu)
Status: New => Confirmed
** Changed in: calamares (Ubuntu)
Importance: Undecided => High
** Changed in: calamares (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a
Public bug reported:
Newly added autopkgests for tree are failing.
431s autopkgtest [13:00:47]: test command1: [---
431s #1 tree debian
431s
431s [FAILED #1, line 7] tree debian
431s @@ -4,6 +4,7
For Noble the conflicting manpages should probably be removed from
src:manpages, because I'd rather not spin a new glibc just for this.
That delta should however be dropped in subsequent releases as we sync
back with Debian where they're seemingly going in the opposite direction
(which is probably
That's not time-t. Some scripts in /usr/libexec/installed-
tests/gtk-4.0/tools used to be executable and now are not:
noble-dev ❯ ls -lh /usr/libexec/installed-tests/gtk-4.0/tools/simplify
.rwxr-xr-x root root 1.0 KB Fri Jan 26 20:26:45 2024
/usr/libexec/installed-tests/gtk-4.0/tools/simplify
** Changed in: nautilus (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/2060154
Title:
Sort by "Modified" uses lexicographic ordering
To manage notifications ab
nautilus --version
GNOME nautilus 45.rc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060154
Title:
Sort by "Modified" uses lexicographic ordering
To manage notifications about this bug go to:
ht
Public bug reported:
I have opened a folder where the subfolder dates go back a few years.
Expect 16 Feb 2024 < 9 Feb 2024
Actual 9 Feb 2024 < 16 Feb 2024
It seems that the folders are sorted lexicographically by their date
string, not chronologically.
** Affects: nautilus (Ubuntu)
Impor
This should be fixed in 24.04.23 (but I forgot to add the bug stanza)
** Changed in: calamares-settings-ubuntu (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I would have submitted the fix in the Gitea instance but it seems
account creations are disabled? Anyway, I'm attaching the patch here.
** Patch added: "0001-Set-GOCACHE-to-stay-within-the-build-directory.patch"
https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060151/+
Public bug reported:
make[2]: Leaving directory '/<>/common/modules/pkgselect/build'
(cd common/snap-seed-glue && go build -gcflags="all=-N -l"
-ldflags="-compressdwarf=false" -o snap-seed-glue main.go)
failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir
/sbuild-nonex
Public bug reported:
there are some fixes that we need
particulary 5.9.12 fixes
> The resolve plugin tries to maintain the order of DNS servers it
installs via resolvconf or resolv.conf
take into account noble (22.04) is at 5.9.13 now
** Affects: strongswan (Ubuntu)
Importance: Undecided
What now remains to be done is to heavily patch faketime to, when on
armhf:
1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of
__clock_gettime)
2/ expose those symbols instead of the legacy 32-bit ones.
--
You received this bug notification because you are a member of Ubunt
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059278
Title:
glibc: apparmor userns mitigation breaks test suite (again)
To manage notifications about this bug go to:
** Changed in: glibc (Ubuntu Noble)
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/2055175
Title:
[UBUNTU 23.10] s390x: clone clobbers r7
To manage notificati
** Changed in: glibc (Ubuntu)
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/2059278
Title:
glibc: apparmor userns mitigation breaks test suite (again)
To
** Changed in: glibc (Ubuntu)
Status: New => 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/2058466
Title:
glibc 2.39 test failure on ppc64el: elf/tst-decorate-maps
To manage no
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052929
Title:
failed autopkgtests for evolver vs glibc 2.39 on amd64
To manage notific
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054343
Title:
arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039
still open)
To manage notifications
Hi,
This is only temporary, see https://lists.ubuntu.com/archives/ubuntu-
devel/2024-March/042954.html for more details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059498
Title:
Fatally broken
I'm assuming you're running Noble?
** Changed in: 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/2059498
Title:
Fatally broken update
To manage notifications ab
Public bug reported:
The test sometimes fail, I don't know why.
I'm xfailing it for now but it'd be good to understand exactly what's
going on.
--
--
FAIL: elf/tst-shstk-legacy-1g
original exit status 1
--
** Affects: glibc (Ubuntu)
Importance: Undecided
St
Thank you both!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053192
Title:
geoipupdate should be moved to universe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is
nterimap; component=main;
> status=New; importance=Unknown; assignee=None;
> Launchpad-Bug-Tags: time-t update-excuse
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: schopin
> Launc
The telepathy-haze package is no longer shipped in the archives. It's
not in Focal which is the oldest supported release. Marking as
incomplete for autoclosing in a few days.
** Changed in: telepathy-haze (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification becau
libgnomeprint is no longer shipped in the archive after Precise, as
such, marking as incomplete (can't mark as won't fix) for autoclose in a
few days.
** Changed in: libgnomeprint (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
Related analysis: https://bugzilla.samba.org/show_bug.cgi?id=14830
It appears to affect Debian too: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1067838
** Bug watch added: Samba Bugzilla #14830
https://bugzilla.samba.org/show_bug.cgi?id=14830
** Bug watch added: Debian Bug tracker #106
Public bug reported:
The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
version the test name was "stress" while the failing one is "testsuite",
so presumably this isn't a regression so much as the new testsuite
failing due to i386 being a partial arch.
Relevant parts of the lo
Public bug reported:
tmux-server crashes with this assertion:
1711556753.777994 event.c:3172: Assertion tv->tv_usec >= 0 failed in
timeout_next
Something somewhere doesn't speak 64bit time_t, it seems.
** Affects: tmux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: ti
Public bug reported:
The latest policy on apparmor vs userns isn't to reject the namespace
creation outright but rather to deny all capabilities within that
namespace.
That breaks the glibc testsuite, again, because our patch only takes the
former policy into account, and so all tests that use te
Public bug reported:
368s src/github.com/google/gopacket/pcap/pcap_unix.go:344:18: cannot use
_Ctype_gopacket_time_secs_t(ci.Timestamp.Unix()) (value of type _Ctype_long) as
_Ctype_longlong value in assignment
368s src/github.com/google/gopacket/pcap/pcap_unix.go:345:19: cannot use
_Ctype_gopa
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el,
+ s390x.
- armhf
This was fixed in 0.4.1-3 (2021).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798967
Title:
bubblewrap has wrong description after setuid bit was removed
To manage notifications about this bug g
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058303
Title:
lxd
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058302
Title:
lxd
Oh, hang on. The bash build has apparently been uploaded just a day
after the t64 gcc, which means gcc was presumably still building when
the bash build started:
gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs)
A bash rebuild should "fix" this somewhat. Well, at least a little bit.
** Al
The failure is because bash, for some reason, still links against
gettimeofday rather than __gettimeofday64, and calls that to seed its
internal random number generator. I still can't figure out why it's
using the old version, though.
ubuntu@noble-armhf:~$ readelf -W -s a.out | grep timeof # a sim
Thanks Andreas for pointing me to the page size.
There's an assumption made in the test that the early allocation code
will need to grow beyond the initial data page, as those extra pages
would be the ones marked "[anon: glibc: loader malloc]". However, if the
page size is large enough, I guess th
** Changed in: interimap (Ubuntu)
Status: New => Fix Committed
** Tags added: time-t
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059120
Title:
interimap time
Public bug reported:
interimap packs a timeval to pass as a socket timeout, but it uses
'l!l!' as a template. That's broken when time_t != long.
** Affects: interimap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubunt
Calamares is ran using sudo -E
If I run `sudo -E env` on my local system, I can see this env var:
SUDO_USER=tsimonq2
Which means a `sudo -u tsimonq2 firefox` would probably do the trick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Paolo thanks for probing this. I finally managed to get my hands on a
suitable power system with recent enough kernel to reproduce this and
file an upstream bug report, and the conversation there led me to
conclude that it's just a faulty assumption in the test (namely that the
initial allocation
Public bug reported:
Please remove src:hkl and src:sardana from noble
hkl is FTBFS and blocks the t64 glib2.0 transition. sardana is its only hard
rdep.
It has been removed from Debian testing:
https://tracker.debian.org/news/1513984/hkl-removed-from-testing/
❯ check-removal sardana
### Source
** Bug watch added: Sourceware.org Bugzilla #31553
https://sourceware.org/bugzilla/show_bug.cgi?id=31553
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=31553
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Public bug reported:
It's FTBFS on armhf: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065993
Binaries:
xwiimote
libxwiimote2
libxwiimote-dev
xserver-xorg-input-xwiimote
❯ SOURCE=xwiimote; reverse-depends -a source src:$SOURCE; echo binaries:;
reverse-depends src:$SOURCE; echo seeded:; s
Uploaded along with a quick fix for https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1067075
Could you please open a bug in Debian/upstream to see if they'd be open
to adopt your patch? It'd be nice to be able to remove the delta
altogether :)
** Bug watch added: Debian Bug tracker #1067075
Public bug reported:
Please remove the armhf binaries for src:libosmo-netif and its reverse-
dependencies:
* libosmo-netif
* libosmo-sccp
* osmo-bsc
* osmo-hlr
* osmo-iuh
* osmo-mgw
* osmo-msc
* osmo-sgsn
libosmo-netif is non-trivially broken on armhf due to the time_t
transition, see https://bu
** Changed in: socat (Ubuntu)
Status: Invalid => 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/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To manage notificatio
FWIW, we've actually seen at least one package seemingly failing to build
because of this issue:
https://launchpadlibrarian.net/720254657/buildlog_ubuntu-noble-armhf.libflorist_2022.0.1~20220616-5_BUILDING.txt.gz
> posix-c.ads:876:07: error: size for "suseconds_t" too small, minimum
allowed is 6
Public bug reported:
This test fails on Noble/ppc64el
3775s FAIL: elf/tst-decorate-maps
3775s original exit status 1
3775s error: tst-decorate-maps.c:152: not true: r.n_loader_malloc_mmap >= 1
3775s error: tst-decorate-maps.c:167: not true: r.n_loader_malloc_mmap >= 1
3775s error: tst-decorate-ma
** Bug watch added: Sourceware.org Bugzilla #31510
https://sourceware.org/bugzilla/show_bug.cgi?id=31510
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=31510
Importance: Unknown
Status: Unknown
** Summary changed:
- understand conform test failures on
Public bug reported:
When the host uses a manually compiled LXD where binaries were not
stripped, the `lxd-agent` can be ~31MiB big. This binary is copied
inside the VM guest when the VM boots up. This copy operation can fail
as the tmpfs in the VM is mounted with `size=25MiB`.
This binary is the
Public bug reported:
This was originally reported at https://github.com/lxc/incus/issues/484
which is recopied here (s/incus/lxd/):
On Red Hat based VMs using SELinux, we seem to be occasionally hitting
lxd-agent startup issues due to systemd not being able to execute the
agent binary.
This is b
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942133
Title:
Nvidia driver packages prevent suspend due to leftover Systemd units
To manag
Using the PPA's libquadmath makes the tests pass, so I sent the patch
upstream:
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647635.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052929
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052930
Title:
liblocale-gettext-perl autopkgtests fail against glibc 2.39
To manage no
This ended up being fixed in the upstream libdfp, I pushed a patched
version in the archive, currently in -proposed.
** Changed in: libdfp (Ubuntu)
Status: New => Fix Committed
** Changed in: glibc (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification becau
As mentioned, I'm fuzzy on the detailed steps that led to this problem,
and have thus far been unable to observe it.
** Changed in: glibc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This will be fixed in Noble in an upcoming bugfix upload of glibc (a
couple of weeks), however we aren't planning on doing a Mantic SRU
unless something critical comes up.
** Changed in: glibc (Ubuntu Mantic)
Status: New => Won't Fix
** Changed in: glibc (Ubuntu Noble)
Status: New =
Hi, thanks for taking the time to report this.
According to the upstream bug, the fix is present from 2.37 onward, and
has been backported to the release branches down to 2.34, while Focal
has 2.31. Given the sheer size of the diff, I'm wary of backporting it
that far. Jammy should be possible, th
** Changed in: glibc (Ubuntu)
Importance: Undecided => Medium
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Also affects: glibc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Cha
To be more precise: I can't reproduce it using gcc or clang, no matter
the fortify level, and the upstream fix
https://sourceware.org/git/?p=glibc.git;a=commit;h=5a5f94af0542f9a35aaa7992c18eb4e2403a29b9
mentions that you can only trigger it on older releases that aren't
available in Jammy.
As a po
Hi, thanks for reporting the issue.
could you provide us with a reproducer for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056751
Title:
Error compiling with glibc2.35 in Ubuntu22.04.3 LTS
This bug is actually in gcc-14, more specifically libquadmath, as they
do a misaligned read from args to a float128, which produces the
segfault.
It was hidden so far because args was allocated using alloca() which I
guess must be naturally aligned, but in 2.39 they removed that in favor
of append
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the s
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification becau
Public bug reported:
## Issue at hand
Yesterday's livefs builds for Lubuntu and other flavors were failing[1]
due to an issue with dependency resolution.
efivar and mokutil both depend on libefivar1. efivar (both the name of
the source and of a binary, referring to the source in this case) was
u
After a bit more reflexion, I'd even argue that this 'built tree'
exception shouldn't exist in the first place as it seems like a nice
footgun, but I'm guessing it's not that simple, so in the mean time I'll
just go and amend my wrapper script to not use `autopkgtest .` but
rather `dpkg-buildpackag
I'll be damned. That's the issue, indeed. I tried to reproduce with a
fresh `hello` but couldn't so I wrongly concluded that it was because it
wasn't on the image.
I'd argue it's still a bug, as in *this should be documented*! I'd never
consider that an unpackage source package would be in a 'buil
Confirmed on salsa, and yes I'm using noble, 5.32ubuntu3, sorry about
that.
One solution I could think of is to go through the list of dependencies
and add a strict version if it's a binary generated by the tested source
package (lib/adt_testbed.py, install_apt)
--
You received this bug notifica
Public bug reported:
While working on needrestart autopkgtests, I've run into issues testing
it using my standard invocation:
autopkgtest . -U -- lxd autopkgtest/ubuntu/noble/amd64
The runner wouldn't install the built package but would just keep
whichever version is in the archive, while still
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
prope
To be clear, this appeared right after you selected the english
keyboard?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054193
Title:
locale-gen crashed with SIGABRT in __GI___wait4()
To manage no
Public bug reported:
As a header to all .conf files in systemd there's a comment saying
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by
Thanks Dan, that prompted me to also call out that's something that
manifests only on distro upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd-agent-setup cannot be started a
** Summary changed:
- lxd-agent-setup cannot be started
+ lxd-agent-setup cannot be started after a distro upgrade to 24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd-agent-se
** Description changed:
+ Fancier description:
+
+ 2024-02-23 - 09:41:38 [1]: ERROR: Error while running: TypeError:
+ chmod: path should be string, bytes, os.PathLike or integer, not
+ TextIOWrapper
+
+ Original description:
+
Testing Lubuntu Noble daily ISO dated 22-02-2024
Install
I have the same issue with an AMD EPYC 9334 32-core processor.
The Problem appears with an upgrade to Ubuntu 22.04.4., already with live
ubuntu from a bootstick. Ubuntu 22.04.3 works fine.
A fresh install (without updates on OS install) of 22.04.3 runs without
problems. After the 1st apt upgrade
Public bug reported:
After the upgrade from Ubuntu 22.04.3 to 22.04.4 I get the message 'CPU32
failed to report alive state' on booting. CPU32 is also reported as offline
under lscpu. The CPU is an AMD EPYC 9334, 32 cores/64 threads.
Problem is also present with 22.04.4 USB livestick. 22.04.3 US
** Summary changed:
- needrestart should integrate with /run/reboot-required
+ needrestart should integrate with /run/reboot-needed
** Description changed:
We have a standard mechanism to notify users that their machine should
- be rebooted through /run/reboot-required, needrestart should use
Public bug reported:
To quote vorlon in bug 2049208
> The debconf frontend is always non interactive when running under
unattended-upgrades; failing to restart affected services when auto
applying security updates is critically BROKEN BY DESIGN
While a bit hyperbolic, the point still stands.
**
Public bug reported:
We have a standard mechanism to notify users that their machine should
be rebooted through /run/reboot-required, needrestart should use that
instead of debconf prompts.
** Affects: needrestart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Hi, thanks for reporting this issue.
Could you please specify which version of Ubuntu you're using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051766
Title:
needrestart should priorize and wait
ecided => Wishlist
** Changed in: ssh-import-id (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745538
Title:
Support for Lau
https://github.com/canonical/cloud-init/pull/4970 contains a proposed
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055219
Title:
`zpool status` called even if not installed in a container
To
Public bug reported:
It seems that cloud-init tries to use `zpool status ` whenever
`/dev/zfs` exists. This can causes some bogus warnings if the zpool
command it not available despite that `/dev/zfs` existing.
Here is how to reproduce:
```
lxc launch ubuntu-daily:22.04 v1 --vm
sleep 30
lxc exec
401 - 500 of 16608 matches
Mail list logo
