** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage
This LP bug was entirely s390x specific, hence not affecting any other platform.
So setting verification again to done, to potentially unblock any further
processes.
** Tags removed: verification-needed-jammy-linux-nvidia-6.5
** Tags added: verification-done
This LP bug was entirely s390x specific, hence not affecting any other platform.
So setting verification again to done, to potentially unblock any further
processes.
** Tags removed: verification-needed-jammy-linux-nvidia-6.5
** Tags added: verification-done
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
)
Importance: Undecided
Status: New
** Changed in: s390-tools-signed (Ubuntu)
Status: New => In Progress
** Changed in: s390-tools-signed (Ubuntu)
Assignee: (unassigned) => Frank Heimes (fheimes)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** 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
** 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
Kicked-off a PPA build of patched s390-tools version 2.31.0-0ubuntu4 here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2058944
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: s390-tools (Ubuntu)
Status: New => In Progress
--
You received this bug
signee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes
(fheimes)
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I've submitted the PR to the kernel teams mailing list:
https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149742
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Information type
I did more tests, on LPAR, z/VM, with FCP/SCSI, DASD/ECKD and have not
faced this issue a single time (or any udev related issues).
So I would consider the installer "edge/lp-2016860" as fixed and working.
(I used the noble daily from today March 15th as base.)
--
You received this bug
Hi Dan, things look very promising, since I installed using
edge/lp-2016860 on this ECKD FBA guest, where the situation was worst,
and the install succeeded !
(Trying now on more and different systems and disk types ...)
--
You received this bug notification because you are a member of Ubuntu
Got marked as APPLIED by kernel team (Paolo).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051835
Title:
[24.04 FEAT] Memory hotplug vmem pages (s390x)
To manage notifications about this bug go
> High
** Changed in: socat (Ubuntu Focal)
Assignee: (unassigned) => Frank Heimes (fheimes)
** Changed in: socat (Ubuntu)
Assignee: Frank Heimes (fheimes) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Patches that are needed for noble/24.04 submitted to the kernel teams mailing
list:
https://lists.ubuntu.com/archives/kernel-team/2024-March/149667.html
https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149667
** Changed in: linux (Ubuntu)
Importance: Undecided => High
**
** Summary changed:
- [24.04 FEAT] Memory hotplug vmem pages
+ [24.04 FEAT] Memory hotplug vmem pages (s390x)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051835
Title:
[24.04 FEAT] Memory
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016860
Title:
Error/crash while trying to wipe disk during 23.04+ install
To
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051835
Title:
[24.04 FEAT] Memory hotplug vmem pages
To manage notifications about this bug go to:
Hello Talha, had a look and re-uploaded (just made the GPL-3 section a separate
one).
It's now in NEW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048462
Title:
[needs-packaging] dfx-mgr from
** Tags removed: installer
** Tags added: installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934887
Title:
Enhance the initial, basic network configuration
To manage notifications about
** Tags removed: installer
** Tags added: installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2016860
Title:
Error/crash while trying to wipe disk during 23.04+ install
To manage
** Tags removed: installer
** Tags added: installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024901
Title:
[UBUNTU 20.04] Unsupported setup: Directory '/boot' is located on a
While testing with the today's ISO image (March 15th) I noticed that
things have improved, especially on DASD/ECKD and FCP/SCSI systems.
Where I'm seeing that now mainly is on DASD/FBA systems, that are a bit
special, anyway attaching the crash file and entire /var/log - just in
case...
**
** Changed in: ubuntu-power-systems
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/2056373
Title:
Problems with HVCS and hotplugging
To manage
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023243
Title:
Multiple issues found on Ubuntu 20.04 against drmgr
To
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056491
Title:
not able to install noble on PowerVM LPARs `Kernel panic - not
** Description changed:
- Using the ISO image 11032024 on an LPAR hosted on a LinuxONE III system
- with an NVMe drive attched, it looks like the installation fails because
- fdasd is called with the NVMe drive as argument.
+ Since the original message that jumped to my eyes when the crash
** Changed in: ubuntu-z-systems
Status: New => Incomplete
** Changed in: subiquity (Ubuntu)
Importance: Critical => High
** Changed in: ubuntu-z-systems
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Had a closer look at the crash file(s), and I'm not sure if the message
that was presented to me during the installation, after the crash is due
to the kind of optimistic approach and probing that is done during
installation ?!
But it actually never makes sense to do:
"
Running command ['fdasd',
Public bug reported:
Using the ISO image 11032024 on an LPAR hosted on a LinuxONE III system
with an NVMe drive attched, it looks like the installation fails because
fdasd is called with the NVMe drive as argument.
"
get_blockdev_sector_size: (log=512, phys=512)
Running command ['fdasd',
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
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 notifications about
New build (with changes squashed into one) are successfully build here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056485-2
Especially test #384 was successful:
"
test 384 SOCAT_OPT_HINT: check if merging single character options is
rejected... OK
"
The overall test results are like
tu0.1.diff
** Changed in: ubuntu-power-systems
Status: Triaged => In Progress
** Changed in: socat (Ubuntu)
Status: Triaged => In Progress
** Changed in: socat (Ubuntu)
Assignee: (unassigned) => Frank Heimes (fheimes)
--
You received this bug notification because you are a me
The second build with the additional patch succeeded:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056485
"
test 385 TERMIOS_PH_ALL: are termios options applied to the correct address...
OK
"
(actually all test were not successfully completed)
I'm now merging both into one package change
I kicked-off some initial test builds in PPA, but one test fails now:
"
test 385 TERMIOS_PH_ALL: are termios options applied to the correct address...
FAILED
./socat -t 0.1 -T 1 STDIO,echo=0 EXEC:cat
"
and I see that is related, and got added to test.sh by the requested patch:
"
+# test for a
** Summary changed:
- Multiple issues found on Ubuntu 20.04 against socat
+ Behaviour of socat in Ubuntu 20.04 unexpected
--
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
SRU request submitted to the Ubuntu kernel team mailing list for mantic, lunar
and jammy.
https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149437
Changing status to 'In Progress' for jammy and focal.
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Canonical
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: socat (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * HVCS (Hypervisor Virtual Console Server) is broken because the
+virtual terminal mkvterm fails, caused by pvmutil failing.
+
+ * When mkvterm is ran, it ultimately fails because it calls pvmutil
+
Currently test kernels are being build for focal/20.04 and jammy/22.04 in this
PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056373
** Changed in: linux (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => In Progress
**
** Summary changed:
- Multiple issues found on Ubuntu 20.04 against HVCS
+ Problems with HVCS and hotplugging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056373
Title:
Problems with HVCS and
Hello and many thanks for raising these HVCS issue.
I first of all analyzed the commits upstream and in the specific Ubuntu
kernel trees and found that focal and to some extend jammy are affected.
Mantic and noble are not affected:
commit 57409d4fb12c got upstream accepted with v5.5(-rc1)
commit
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
** Tags added: noble ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: linux (Ubuntu) => libvirt (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: libvirt (Ubuntu)
Assignee: Skipper
Just a side note,
we should have the right package versions in 24.04 as of today:
$ rmadison --suite=noble,noble-proposed openssl-pkcs11-sign-provider
opencryptoki
openssl-pkcs11-sign-provider | 1.0.1-0ubuntu1 | noble/universe
| source, amd64, arm64, armhf, ppc64el, s390x
Many thanks for your testing and feedback on focal @jldolan.
With that I'm updating the tags to verification done.
(The two additional bugs about kernel and socat will then be addressed
in their own LP bug, I already noticed one of them.)
** Tags removed: removal-candidate verification-needed
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage
Hi Andreas, thanks for your patched Apache 2.4 build, great!
(I'm curious about the autopkgtest results.)
Regarding the provider, there are different implementations out there.
This one - available in noble - is supposed to work with this Apache2
modification:
Well, I think you initially had an ISO with 6.8.0-4-generic.
Then 6.8.0-11-generic became available and part of a newer ISO by default.
And even if one does an install with an (let's say oudated) ISO (that
has a kernel, like 6.8.0-4-generic, that got meanwhile replaced), the
installer looks for
Well, in case the KVM host you are currently using is Ubuntu 'noble' /
24.04 that could be the case - yes.
(I guess that 'noble' got hundreds of package updates in the last few days.)
That would not explain what you described with Fedora,
which makes me think that it might have been caused by
Okay, I see.
Now we can be sure that it got fixed with an updated ISO.
Right after feature freeze it takes a while until things get settled,
and I would assume that 20240305 is the one that brought stability,
since this is also the one that is recommended to use during the
'Ubuntu testing week'
Hello @bskjois, this is good news - thx for sharing.
The virt-install cmd-line is actually the same than the one you've used
before.
Did you used an updated ISO image?
I'm just curious, because we are still in heavy development with the 'noble'
release, (esp. around feature freeze, that we had
Closing in favor of a solution based on dynamic keys.
** Changed in: ubuntu-power-systems
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing in favor of a solution based on dynamic keys.
** Changed in: ubuntu-power-systems
Status: Incomplete => Invalid
** Changed in: grub2 (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This subiquity bug here seems to be unrelated to the initial bug that
was reported here, hence it was split into a separate bug: LP#2055702
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055126
Hello Narayana Murty, okay, so we are on the same page.
Since we build the libvirt package in a different way that does not require
this patch (and we don't see other/further failures while building the Ubuntu
libvirt DEB packages),
and since any update of the libvirt package would come with a
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055702
Title:
installer crashes after importing my launchpad SSH key
To manage
** Changed in: ubuntu-z-systems
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/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
To manage
*** This bug is a duplicate of bug 2038583 ***
https://bugs.launchpad.net/bugs/2038583
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are
Hi Olivier, thanks for the investigations.
Well, we recently had the 22.04.4 release where we did quite some
testing upfront - using the same systems with the same accounts, but
haven't hit this kind of issue (and btw. same for mantic).
You're writing that the fix is already in noble? Was it
Updating status to Fix Released, since a kernel 6.8 version has landed in
noble-release:
linux-generic | 6.8.0-11.11+1 | noble | amd64, arm64, armhf, ppc64el, s390x
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
To manage
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042853
Title:
[UBUNTU 23.04] Kernel config option missing for s390x PCI
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not
Thanks for the update Hector.
The change itself is small and looks reasonable (more a build time
issue).
I had to adjust the changelog entry (since we are still in noble devel)
to:
--8<--
qatlib (24.02.0-0ubuntu2) noble; urgency=medium
* d/not-installed: Do not install
** Changed in: ubuntu-power-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055126
Title:
Unable to bring up a guest using 24.04(Noble Numbat) ISO
To manage
This bug affects s390x only, hence I'm updating all further verification
requests to done, to unblock potential ongoing processes.
** Tags removed: verification-needed-focal-linux-aws-5.15
verification-needed-jammy verification-needed-jammy-linux-mtk
** Tags added:
This bug affects s390x only, hence I'm updating all further verification
requests to done, to unblock potential ongoing processes.
** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-done-jammy-linux-mtk
--
You received this bug notification because you are a member
This bug only affected s390x, updating all other verification requests
to done (to unblock potential processes).
** Tags removed: verification-needed-jammy verification-needed-jammy-linux-mtk
** Tags added: verification-done-jammy verification-done-jammy-linux-mtk
--
You received this bug
his bug only affected s390x, updating all other verification requests to
done (to unblock potential processes).
** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-done-jammy-linux-mtk
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[ Impact ]
* When UBSAN is enabled in an s390x kernel configuration, kpatch-build
can fail to find matching symbols in the vmlinux symbol table (see
attached example_livepatch.patch). This was discovered in both Jammy
5.15 and Kinetic 5.19 kernels, where
This bug only affected s390x, updating all other verification requests
to done (to unblock potential processes).
** Tags removed: verification-needed-focal-linux-aws-5.15
verification-needed-jammy verification-needed-jammy-linux-mtk
** Tags added: verification-done-focal-linux-aws-5.15
This bug only affected s390x, updating all other verification requests
to done (to unblock potential processes).
** Tags removed: verification-needed-focal
verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-mtk
verification-needed-kinetic
** Tags added:
This bug could be related LP#2055294 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055126
Title:
Unable to bring up a guest using 24.04(Noble Numbat) ISO
To manage notifications about this
Potential regressions were resolved, now blocked by freeze.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046439
Title:
Wrong code execution of s390x code with qemu TCG
To manage notifications
** Changed in: s390-tools (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
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/2039567
Title:
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
Bugs, which
*** This bug is a duplicate of bug 2038583 ***
https://bugs.launchpad.net/bugs/2038583
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 2038583
Turning COMPAT_32BIT_TIME off on s390x
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 2050028 ***
https://bugs.launchpad.net/bugs/2050028
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049887
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
To manage notifications
** Description changed:
Feature Freeze Exception (FFe):
---
- Since this may take a little longer now and noble's FF is coming up soon,
- I'm pro-actively transferring this request into a feature freeze exception
(FFe).
+ Since the work on this request may take
@ahasenack Yes, that is the main driver for this.
Let me pick this and put it also into the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050017
Title:
[FFe] [24.04 FEAT]
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003672
Title:
[24.04 FEAT] Secure Execution - Secure guest tool to bind
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049612
Title:
[24.04 FEAT] Upgrade s390-tools to latest version (2.31)
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
** Changed in: s390-tools (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: s390-tools-signed (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Committed
** Changed in: s390-tools (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: rls-mm-incoming 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/2055175
Title:
[UBUNTU 23.10] s390x: clone clobbers r7
To manage notifications about this bug go to:
Since the current glibc situation in Ubuntu is like this:
libc6 | 2.35-0ubuntu3| jammy | amd64, arm64, armhf, i386,
ppc64el, riscv64, s390x
libc6 | 2.35-0ubuntu3.6 | jammy-security | amd64, arm64, armhf, i386,
ppc64el, riscv64, s390x
libc6 | 2.35-0ubuntu3.6 | jammy-updates
** Package changed: linux (Ubuntu) => glibc (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: glibc (Ubuntu)
Assignee: Skipper Bug
Hello and thanks for raising this - a few questions / thoughts:
- It would be good to have the full virt-install command that was used,
that allows to reproduce.
- Esp. which argument was used (and how) for virt-install used - using "
--cdrom" or "--location"? Since virt-install behaves
** Tags added: ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055126
Title:
Unable to bring up a guest using 24.04(Noble Numbat) ISO
To manage notifications about this bug go to:
** Package changed: ubuntu => virtinst (Ubuntu)
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
--
You received this bug
Uploaded (to NEW queue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048462
Title:
[needs-packaging] dfx-mgr from Xilinx
To manage notifications about this bug go to:
Since the libdfx got uploaded a few days ago,
I now started to review dfx-mgr, in preparation for it's upload:
- changelog:
- version is okay(ish, unfortunately upstream does not follow semantic
versioning yet: https://semver.org/ - hope we could convince them to do that in
future)
-
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054632
Title:
ninja command failing for upstream libvirt compilation
To manage
** Tags added: noble
** Also affects: qemu (Ubuntu Noble)
Importance: High
Status: New
** Changed in: ubuntu-power-systems
Status: New => Triaged
** Changed in: qemu (Ubuntu Noble)
Status: New => Triaged
--
You received this bug notification because you are a member of
quilt patch for commit c4f91d7b7be
** Patch added: "ppc-spapr-initialize-max_cpus-limit.patch"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2055003/+attachment/5749515/+files/ppc-spapr-initialize-max_cpus-limit.patch
--
You received this bug notification because you are a member of
** Changed in: ubuntu-z-systems
Status: In Progress => 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/2050014
Title:
[24.04 FEAT] [SEC2207] openCryptoki: ep11 token support for
** Changed in: ubuntu-z-systems
Status: In Progress => 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/2050015
Title:
[24.04 FEAT] [SEC2327] openssl-pkcs11-sign-provider: fork
Package opencryptoki_3.23.0+dfsg-0ubuntu1 uploaded ...
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050014
Title:
[24.04 FEAT] [SEC2207]
101 - 200 of 5690 matches
Mail list logo
