Could we have the apport-autoreport.service journal logs as well?
I'm now realizing that the reason I don't get spammed could simply be
that I configured my system to report everything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that I still don't understand why it loops, whereas on my system
whoopsie will happily create the upload/uploaded files (with a NULL ID).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
I found the wild goose!
Your Python crashes are owned by vorlon:vorlon, which is why whoopsie
cannot read them. I'm guessing that /var/crash doesn't have the 3777
permissions that would allow inheriting the whoopsie GID. My own system
has 1777, whereas fresh containers seem to be correctly using
*** This bug is a duplicate of bug 2066995 ***
https://bugs.launchpad.net/bugs/2066995
** This bug has been marked a duplicate of bug 2066995
apport-gtk keeps prompting to report crashes in a loop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
: needrestart (Ubuntu)
Importance: Medium
Assignee: Simon Chopin (schopin)
Status: Triaged
** Affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Affects: needrestart (Ubuntu Oracular)
Importance: Medium
Assignee: Simon Chopin (schopin
** Description changed:
Unstable has openssl 3.2.1 which is need to fix some tests for nodejs
and some features for cryptsetup and is a good step to 3.3 for 24.10.
Merge request:
https://code.launchpad.net/~adrien/ubuntu/+source/openssl/+git/openssl/+merge/466581
+
+ Copied over from
The bug didn't occur after the reboot anyway so I'll keep my extensions.
I do feel like no extension should be able to lock up the shell to the point I
can't even reach the console.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a quick chmod +x, it works on my local machine with a lxd runner.
However, I think it's best to just add the needs-sudo restriction since
you're actually using it.
I've sponsored the upload (with the needs-sudo tag added).
** Changed in: freerdp2 (Ubuntu)
Status: New => Fix
Is this ready for review/sponsoring?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054390
Title:
Refine proc mounts entries traversal
To manage notifications about this bug go to:
Public bug reported:
On Noble, using Gnome (not the Ubuntu desktop) + a few plugins, I had my
desktop completely unresponsive after logging in. The mouse cursor was
still moving, but the hot corner didn't work, nor did the various
keyboard shortcuts. Surprisingly, the Ctrl-Alt-Fn access to
It seems this doesn't have anything to do with glibc? Marking as Invalid
there.
** Changed in: glibc (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/2062522
I'm not entirely sure nautilus is the right package to assign this to,
but I'm definitely certain needrestart has nothing to do with the issue
:)
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: needrestart (Ubuntu)
Status: New => Invalid
--
** Changed in: needrestart (Ubuntu Oracular)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: needrestart (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: Fix Released
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Also, thanks for using the DEP-3 headers on the patch, however Launchpad
bugs should usually go in the Bug-Ubuntu field, leaving Bug: for any
potential upstream bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Having a proper upstream fix is way more involved, because we can't
*know* what the time_t size is on any random system. It's probably a
good idea to open a bug in their tracker to let them figure it out,
though ;).
While the version in your Noble debdiff is technically OK since we
already have a
Marking this as Normal (or maybe Low?) severity on Noble since it's only
relevant for armhf users that upgrade from a previous system *and* still
use utmp/wtmp. We have drop utmp support in pam in Noble, leaving us
with last(1)/lastb(1)/lastlog(1)/faillog(1) as the main consumers of
those files in
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1042562:
Package: libc6
Version: 2.37-6
Tags: upstream
The utmp(5) interface has broken its compatibility in 32-bit programs
built with -D_TIME_BITS=64. In bits/utmpx.h we see this:
,
| /* The fields ut_session and ut_tv
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: needrestart (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: needrestart (Ubuntu Oracular)
Assignee: (unassigned) => Simon Chopin (schopin)
-
** Changed in: needrestart (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063442
Title:
needrestart on Ubuntu 24.04 is restart
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063442
Title:
needrestart on Ubuntu 24.04 is restarting google-guest-agent startup
and shutdown scrips on reinstall
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
(placeholder bug, details to be filled in later by liushuyu, I just
needed the bug number)
** Affects: rustc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Interestingly, I see the same "could not be opened" patter in my recent
logs, all for crashes within Python executables.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk
Steve, do you still have the crash file on your system? If so, could you
give us its mod and owner?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066995
Title:
apport-gtk keeps prompting to report
Well, we're not in the world of needrestart just yet, it's only seeded in
Server.
On Thu, 30 May 2024, 04:20 Seth Arnold, <244...@bugs.launchpad.net>
wrote:
> Adrien, thanks so much for digging into this again.
>
> This is so very complicated, why does openssl need special handling in
> the
Public bug reported:
This is an expansion on bug 2059337. There's likely a fair number of
custom services out there that are similar in nature to cloud-init,
unattended-upgrade and the likes. Rather than forcing every user to
track down and debug this issue, needrestart should instead have some
Hi Sudip,
I've uploaded the Mantic and Jammy packages to the SRU queue. Thanks for
your work :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061637
Title:
[SRU] xx-svn-review crashed with
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065863
Title:
needrestart causes kernel upgrade messages in motd
To manage notifications about this bug go to:
This is a new feature that I implemented based on what I had understood
were your requirements: integrating needrestart with /run/reboot-
required. Apparently, MOTD picks up whatever we write in that file.
Shall I walk that part back and not write to that file in the case of
kernel updates? I
Thanks for testing and catching that regression! I've found and fixed
the issue in an oracular upload. Once it clears -proposed I'll amend the
noble-proposed version.
** Changed in: shadow (Ubuntu Noble)
Status: Fix Committed => In Progress
--
You received this bug notification because
** Description changed:
[ Impact ]
On Ubuntu Core 24 calling the command line
useradd --extrausers --groups somegroup somenewuser
... fails with:
useradd: cannot lock /etc/group; try again later.
It worked on 22.04. /etc is not writable. It also fails if somegroup is
This has been uploaded :)
** Changed in: wget (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/2065883
Title:
Please merge wget 1.24.5-1 into
** Description changed:
+ [ Impact ]
+
On Ubuntu Core 24 calling the command line
useradd --extrausers --groups somegroup somenewuser
... fails with:
useradd: cannot lock /etc/group; try again later.
It worked on 22.04. /etc is not writable. It also fails if somegroup is
** Changed in: shadow (Ubuntu Noble)
Importance: Undecided => High
** Changed in: shadow (Ubuntu Noble)
Status: New => In Progress
** Changed in: shadow (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are
I marked Mantic as Wont Fix since this is a bug that primarily affects
Ubuntu Core, Mantic users are likely unaffected, so I'd rather spare
them an unnecessary update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I opted for the "quickfix" approach, as it has the merits of minimizing
the changes to the "normal" codepaths, thus reducing the risks of
regressions for non-core users. While the extrausers case is not as
correct as it would have been with a full fix, it's consistent with the
behaviour in 22.04
** Also affects: shadow (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: shadow (Ubuntu Oracular)
Importance: Undecided
Assignee: Simon Chopin (schopin)
Status: New
** Also affects: shadow (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: fitsverify (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059185
Title:
fitsverify is uninstallable on Noble
To man
It should, indeed. I though I had gathered all the relevant bugs in the
changelog, seems I missed this one. Sorry :)
** Changed in: needrestart (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dpkg (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dpkg (Ubuntu Oracular)
Importance:
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dpkg (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dpkg (Ubuntu Oracular)
Importance:
The issue was introduced with https://github.com/shadow-
maint/shadow/pull/237
Basically, the previous group validation was done using glibc's getgrid
directly, which was presumably coping well with the RO status of
/etc/group, but that poses consistency problems because you could add a
local
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /etc/group
To manage notifications about this bug go to:
Quick repro steps:
❯ lxc launch ubuntu-daily:noble shadow
Creating shadow
Starting shadow
❯ lxc exec shadow bash
root@shadow:~# mv /etc /etc_write
root@shadow:~# mkdir /etc
root@shadow:~# mount -o bind,ro /etc_write /etc
root@shadow:~# useradd --extrausers --groups somegroup somenewuser
useradd:
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /
Public bug reported:
perf_indicators.c: In function ‘getTicksPerMicrosec’:
perf_indicators.c:37:30: error: implicit declaration of function
‘get_ticks_per_usec’ [-Werror=implicit-function-declaration]
37 | ticks_per_microsec = get_ticks_per_usec();
|
* Define _DISTRO_EVADE_TIME_BITS for the build, not setting _TIME_BITS
+ and _FILE_OFFSET_BITS in the compiler by default.
+ See https://sourceware.org/bugzilla/show_bug.cgi?id=31624.
+ -> build fix, mostly useful for c-t-b(-p)
+
+ [ Simon Chopin ]
+ * debian/patches/git-updates.diff
Public bug reported:
Details to follow.
** Affects: glibc (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/2062228
Title:
[FFe] late glibc
(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
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,
** 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.
+
** 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
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:
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
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.
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
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
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.
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"
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
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
** 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
** 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
** 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)
** 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
** 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
** 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
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
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
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
> Launchpad-Bug-Reporter: S
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
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:
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
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
** 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
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.
**
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
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
** 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
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
@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
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:;
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
** 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
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
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:
** 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
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
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
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,
** 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
**
1 - 100 of 668 matches
Mail list logo