** Patch added: "focal_yoga.debdiff"
https://bugs.launchpad.net/neutron/+bug/2017748/+attachment/5759481/+files/focal_yoga.debdiff
** Changed in: cloud-archive/yoga
Assignee: (unassigned) => Hua Zhang (zhhuabj)
** Changed in: cloud-archive/zed
Assignee: (unassigned) => Hua Zhang
** Description changed:
- faketime 0.9.10-2.1ubuntu1 is stuck in -proposed.
+ faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on
+ armhf.
+
+ On armhf, the testsuite confusingly fails with a stack smash error. But
+ this error happens in bash, which isn't even meant to be
I continued exploring this topic myself last week and was able to rely
on a tool developed for this: https://github.com/coreos/cargo-vendor-
filterer/.
This tool is not ideal in the sense that:
- it vendorize the whole content
- then, it filters by replacing entire crates based on some filtering
> One of the requirements is the newer releases (supported & devel) are fixed.
> Can you please provide the debdiffs for them, for us to proceed?
>
> $ for release in noble mantic jammy focal bionic; do git show
> pkg/ubuntu/${release}-devel:debian/control | grep 'X-Python-Version:'; done
> $
In progress upstream:
https://github.com/micheleg/dash-to-dock/pull/2149
Also I have deleted tasks for the now unsupported deb versions of some
extensions.
** No longer affects: gnome-shell-extension-dashtodock (Ubuntu)
** No longer affects: gnome-shell-extension-autohidetopbar (Ubuntu)
** No
Public bug reported:
nginx 1.24.0-2ubuntu6 changes ABI on armhf after a no-change rebuild. As a
result existing binary modules fail to load.
Since nginx 1.24.0 shipped in mantic, this should be handled as a transition,
bumping the ABI in the Provides: field.
** Affects: nginx (Ubuntu)
unblocking current nginx for migration via removal of existing armhf
extensions, but that still means breakage on upgrade if old packages are
not removed.
Removing packages from noble:
libnginx-mod-http-auth-pam 1:1.5.5-2 in noble armhf
libnginx-mod-http-brotli-filter 1.0.0~rc-5
** Changed in: xf86-input-xwiimote (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: xwiimote (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've noticed that two no-change rebuilds (against libcurl4t64 and libssl3t64)
were triggered, which obviously increased the version of the s390-tools. But at
the same time s390-tools-signed version stayed the same, hence the s390-tools
would have become uninstallable without a proper
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056718
Title:
openvswitch gentling
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056364
Title:
Add test script for
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053155
Title:
Add DPLL and syncE
** Package changed: linux (Ubuntu Noble) => linux-oem-6.8 (Ubuntu Noble)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058357
Title:
noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
To manage
** Changed in: network-manager
Status: New => 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/1997553
Title:
network-manager fails to trigger dispatcher scripts with action
After carefully reviewing many patches, I finally backported the
following 3 patches to Yoga.
[PATCH 1/3] 686698284b Update tap ip in metadata agent when metadata port ip
updated
[PATCH 2/3] 6205158831 ovn-metadata: Refactor events
[PATCH 3/3] b992d639b9 Handle creation of Port_Binding with
Ok, there is also this reply to consider from the developers of a2jmidid:
https://github.com/jackaudio/a2jmidid/issues/25#issuecomment-2019233806
Maybe we should hold back?
** Bug watch added: github.com/jackaudio/a2jmidid/issues #25
https://github.com/jackaudio/a2jmidid/issues/25
--
You
Public bug reported:
[Impact]
The **rtla** is a meta-tool that includes a set of commands that aims to
analyze the real-time properties of Linux.
Considering the latest "low-latency" capabilities acquired by the
generic kernel and also considering the recent trend in Ubuntu to focus
on
** Patch added:
"debdiff_s390-tools-signed_noble_from_2.31.0-0ubuntu1_to_2.31.0-0ubuntu4.diff"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2058944/+attachment/5759487/+files/debdiff_s390-tools-signed_noble_from_2.31.0-0ubuntu1_to_2.31.0-0ubuntu4.diff
--
You received this bug
> Many thanks for raising this way before Plasma 6 is released to
Ubuntu, this way we can assure this bug is gone by the time Plasma 6
becomes officially supported in Ubuntu.
This was my intend. :)
I'm using KDE neon, which is an extension of Ubuntu 22.04 providing the
most recent KDE
** Patch added:
"debdiff_s390-tools_noble_from_2.31.0-0ubuntu3_to_2.31.0-0ubuntu4.diff"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2058944/+attachment/5759486/+files/debdiff_s390-tools_noble_from_2.31.0-0ubuntu3_to_2.31.0-0ubuntu4.diff
--
You received this bug notification because you
You have an unsupported DKMS module installed that breaks kernel header
installation. Please remove it:
$ dkms remove amdgpu/6.2.4-1683306.22.04
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Micheal,
Any update on the logs shared. Also, from the jounalctl logs shared
looks like the checksum for linux packages are not matching as shown
below from 'journalctl' logs.
Mar 21 08:58:56 ubuntu-server casper-md5check[2791]: Checking
Building module:
Cleaning build area...(bad exit status: 2)
make -j12 KERNELRELEASE=6.5.0-26-generic TTM_NAME=amdttm SCHED_NAME=amd-sched
-C /lib/modules/6.5.0-26-generic/build
M=/var/lib/dkms/amdgpu/6.2.4-1683306.22.04/build...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File
Public bug reported:
gnome-remote-desktop 46~rc-0ubuntu2 is built in -proposed but not on
armhf. This will not block migration because armhf binaries are being
removed from the release pocket, but unless addressed will regress armhf
availability of this package in 24.04 LTS.
** Affects:
Public bug reported:
rakarrack 0.6.1-8build1 is built in -proposed but not on armhf. This
will not block migration because armhf binaries are being removed from
the release pocket, but unless addressed will regress armhf availability
of this package in 24.04 LTS.
** Affects: rakarrack (Ubuntu)
** 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/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
To manage notifications about this bug go to:
Public bug reported:
krita 1:5.2.2+dfsg-2build5 is built in -proposed but not on armhf. This
will not block migration because armhf binaries are being removed from
the release pocket, but unless addressed will regress armhf availability
of this package in 24.04 LTS.
** Affects: krita (Ubuntu)
All autopkgtests for the newly accepted linux-meta-oracle (5.15.0.1055.51) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.12 (arm64)
Please visit the excuses page listed below and investigate the
Sorry I only just figured out that comment #17 is about mantic, not
jammy.
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/mantic/update_excuses.html#mutter
And the Debian fix I mentioned in comment #18 is actually in 44.8-1
onward *and* 45.2-2 onward. So mantic would get the fix for
Unsurprisingly, there are some symbol differences.
# diff -u <(objdump -T /usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 |
grep '\.text' | cut -b34- | sort -u) <(objdump -T ./src/libfaketime.so.1 | grep
'\.text' | cut -b34- | sort -u)@@ -1,50 +1,51 @@
Base__clock_gettime
+Base
Public bug reported:
The command `automake` gives "Segmentation fault (core dumped)" error.
Even the calls `automake --version` and `automake --help` give this
error.
The system details:
$> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Noble Numbat
Seems like the bug is back.
It pops up occasionally (one error line every ~2 hours) on Linux 6.5.0-14,
6.6.0-14 and 6.8.0-20.
Appears on both Jammy: Xorg (Mate) and Mantic: Xorg/Wayland (Mate/KDE).
Default kernel cmdline.
On Xorg the graphics is fine, but on Wayland it can a bit "flickery" at
Public bug reported:
faketime 0.9.10-2.1ubuntu1 is stuck in -proposed.
** Affects: faketime (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058944
Title:
[UBUNTU 24.04] dbginfo.sh: updates required for /bin/dash shell
To manage notifications about this bug go to:
Fix is from v6.6. Noble is not affected. Question is whether this should
not also be added to Mantic?
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mantic has already included this two commits in #2049202 [1].
c95b65ba744d x86/fpu: Allow caller to constrain xfeatures when copying to
uabi buffer
97cdceb46fb3 KVM: x86: Constrain guest-supported xfeatures only at
KVM_GET_XSAVE{2}
[1] https://bugs.launchpad.net/bugs/2049202
--
You
Public bug reported:
filament 1.9.25+dfsg2-13build1 is stuck in -proposed. It FTBFS on all
arches with:
[ 46%] Building CXX object
libs/filamat/CMakeFiles/filamat.dir/src/sca/GLSLTools.cpp.o
cd /<>/obj-x86_64-linux-gnu/libs/filamat && /usr/bin/clang++
-DFILAMENT_DRIVER_SUPPORTS_VULKAN
The problem is the format string using %ld with the new time_t in armhf,
now it's long long int (%lld)...
query2 = xstrdup_printf("insert into %s (creation_time, "
"mod_time, table_name, definition) "
"values (%ld, %ld, '%s', '%s') "
"on duplicate key update "
For now it would be simplest to just remove the package:
nr@six:~/u/p/t/filament$ reverse-depends -r noble src:filament
nr@six:~/u/p/t/filament$ reverse-depends -r noble src:filament -a source
Reverse-Build-Depends
=
* filament (for libfilament-tools)
**
See bug #2059140 for additional information
** Bug watch added: Debian Bug tracker #1065972
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065972
** Also affects: pngphoon (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065972
Importance: Unknown
Status:
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
$ reverse-depends src:licheerv-rtl8723ds-dkms -a source
No reverse dependencies found
$ reverse-depends src:licheerv-rtl8723ds-dkms
No reverse dependencies found
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue was fixed in the openstack/python-aodhclient wallaby-eom
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974682
Title:
openstack-tox-py3N jobs continously fails
To manage
This issue was fixed in the openstack/python-aodhclient xena-eom
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974682
Title:
openstack-tox-py3N jobs continously fails
To manage
"_TIME_BITS=64 can be defined only when _FILE_OFFSET_BITS=64 is also
defined." [1]
[1] https://www.gnu.org/software/libc/manual/html_node/Feature-Test-
Macros.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nauty.h defines _FILE_OFFSET_BITS to 0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059155
Title:
nauty FTBFS on armhf
To manage notifications about this bug go to:
This is caused by passing -makedefault to swig, which was dropped
upstream: https://github.com/swig/swig/blob/v4.2.1/CHANGES#L579. Simply
dropping use of this old flag fixes the build.
** Changed in: adonthell (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
tests being ignored, this will be promoted to the release pocket, so
marking high for fixing or binary removal
** Changed in: slurm-wlm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
xnee 3.19-9.1 is stuck in -proposed. It FTBFS on armhf:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3
-I../include -g -DUSE_VERBOSE -DNO_BUF_VERBOSE -DHAVE_XOSD
** Changed in: uvloop (Ubuntu)
Assignee: (unassigned) => Graham Inggs (ginggs)
** Changed in: uvloop (Ubuntu)
Status: New => In Progress
** Bug watch added: Debian Bug tracker #1056893
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056893
** Also affects: uvloop (Debian) via
Public bug reported:
Output from BMC SOL console:
Unhandled Exception from EL2
x0 = 0x11f210305619
x1 = 0x
x2 = 0x
x3 = 0x
x4 = 0x5f972493
x5 = 0x
> alfonsosanchezbeato: to be clear, the networkctl reload/reconfigure commands
> seem to work, but after 6-8 minutes the state goes back to the one expressed
> by the old .network files
> alfonsosanchezbeato: you can even force the revert to happen sooner with sudo
> udevadm trigger, with that
** Attachment added: "build log on armhf"
https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+attachment/5759741/+files/buildlog_ubuntu-noble-armhf.slurm-wlm_23.11.4-1.2ubuntu6~ppa1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
There are lots of instances of this issue. After fixing the one above it
breaks in a different place
root@autopkgtest-lxd-bqwqyd:~# slurmdbd -D
slurmdbd: accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL
server version is: 5.5.5-10.11.7-MariaDB-2ubuntu1
slurmdbd: error: Database
** Changed in: uvloop (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/2051150
Title:
uvloop 0.19.0+ds1-2 FTBFS on noble
To manage notifications
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1082.78)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk/unknown (arm64)
wireguard-linux-compat/1.0.20201112-1~20.04.1 (arm64)
Please visit the excuses page
.
Press any key to continue...
ISO used: https://cdimage.ubuntu.com/ubuntu-server/daily-
live/20240326/noble-live-server-ppc64el.iso
I am not able to print "real-base" values as well. I tried setting the
value but faced the same issue even after that.
Memory Keyboard Network S
Hi @kowshik.jois,
the (daily) images still have the same kernel inside (the 6.8 -11):
$ rmadison --arch=ppc64el --suite=noble,noble-proposed linux-generic
linux-generic | 6.8.0-11.11+1 | noble | ppc64el
linux-generic | 6.8.0-20.20+1 | noble-proposed | ppc64el
But there is now a newer
I reviewed trace-cmd 3.2-1 as checked into noble. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
> TRACE-CMD: The front-end application to Ftrace. The back-end
application to KernelShark.
- CVE History
- none
- Build-Depends
- most are for docs
-
I reviewed libtraceevent 1:1.8.2-1 as checked into noble. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
> libtraceevent - Linux kernel trace event library
- CVE History:
- none
- Build-Depends?
- nothing concerning
- most dependencies are for
Public bug reported:
Storing credit cards in firefox fails.
When firefox is started, the following output is given:
$ firefox -ProfileManager
/home/michael/snap/firefox/common/.cache/gio-modules/libgiognomeproxy.so:
cannot open shared object file: No such file or directory
Failed to load
Thanks for reporting the bug. I tried to reproduce the issue on latest 22.04.4
and did not see the issue. On my system I am seeing the application window is
displayed.
Can you please try again on 22.04.4 and see if you can reproduce the issue. And
if its reproducible then please give the steps
Public bug reported:
ca-certificates-java fails can-configure-cross-compilation test[1] due
to mmdebstrap not being able to setup the chroot[2]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043247
[2]
** Changed in: glibc
Importance: Medium => Low
--
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 notifications
** 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/2059123
Title:
Build failure due to t64 on armhf
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee:
Public bug reported:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was
** Changed in: update-manager (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: update-manager (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: update-manager (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in:
This issue was fixed in the openstack/keystonemiddleware wallaby-eom
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987355
Title:
[SRU] Error validating X-Service-Token
To manage
This issue was fixed in the openstack/keystonemiddleware victoria-eom
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987355
Title:
[SRU] Error validating X-Service-Token
To manage
This issue was fixed in the openstack/keystonemiddleware xena-eom
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987355
Title:
[SRU] Error validating X-Service-Token
To manage
Tried kernel parameter i915.enable_dc=0 as suggested by
https://wiki.archlinux.org/title/intel_graphics#Crash.2Ffreeze_on_low_power_Intel_CPUs;
still crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just uploaded nginx 1.24.0-2ubuntu7~ppa2 in ogayot/noble-proposed.
Upgraded from 1.24.0-2ubuntu6 to 1.24.0-2ubuntu7~ppa2 forces removal of
libnginx-mod-* packages so that seems to work as expected.
https://launchpad.net/~ogayot/+archive/ubuntu/noble-
proposed/+build/27962400
Not adding the
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
** Summary changed:
- Drop fips-check script from trees
+ Drop fips-checks script from trees
** Description changed:
[Impact]
When producing a new version of some kernels, we need to check for
changes that might affect FIPS certs and justify why a commit was kept.
- For that, we have a
** Changed in: linbox (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059060
Title:
linbox fails to build with -D_FORTIFY_SOURCE=3
To manage notifications
Upgrading bios firmware resolves failure
$ sudo dmidecode -t 0
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.
Handle 0x0001, DMI type 0, 26 bytes
BIOS Information
** Changed in: fabric-manager-535 (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: fabric-manager-535 (Ubuntu Bionic)
Assignee: (unassigned) => Kuba Pawlak (kuba-t-pawlak)
** Changed in: fabric-manager-535 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in:
Public bug reported:
ycmd 0+20231230+git9e43034+ds-2build2 has failing tests on armhf after
the time_t transition. No failures on other archs so must be a time_t
bug somewhere.
** Affects: ycmd (Ubuntu)
Importance: High
Status: New
** Tags: time-t update-excuse
** Changed in:
Thanks for the update @superm1, I appreciate the help.
> I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
Should this fix the flickering issue? I'm happy to test it out.
> FYI - there are two
https://launchpad.net/~snappy-
dev/+archive/ubuntu/image/+packages?field.name_filter=snapd_filter=published_filter=focal
https://launchpad.net/~snappy-
dev/+archive/ubuntu/image/+packages?field.name_filter=snapd_filter=published_filter=jammy
https://launchpad.net/~snappy-
The postinstall runs fails because luatex now has the 'socket'
functionality disabled by default. [CVE-2023-32668]
The upstream source for mtxrun has --socket added to the luatex command
line to reenable the functionality while running 'mtxrun --make'. See
lines having '--socket' in
Bypassing security-review, as per "This does not need a security
review". So we'd still need the tests fixed before this is ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056099
Title:
[MIR]
1 - 100 of 354 matches
Mail list logo
