Based on the recent ISO, QA Tracker and installation tests around the 24.04
release,
this issues got solved and it did not happened anymore with recent images,
hence I'm closing this LP bug.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Changed in: subiquity
** 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/2009495
Title:
[Ubuntu 22.04] smc_run does not work, libsmc-preload.so
Hi @seth-arnold,
I am not in-depth familiar with security related updates (since they happen
rarely for me, and if private-security are handled by the security team anyway).
"
My assumption is that these package updates should be published first to
-updates for autopkgtest testing, and once
With that I'm closing this LP bug by updating it to Won't Fix.
(This does not mean that fixes will never be possible or done at all,
'Won't Fix' in this case indicates that the workaround / alternative fix was
not desired, hence was not chosen; and it was taken in lieu of a better status.)
**
** 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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job
Hello @Jamie, thanks for your answer and feedback. Your decision is
understood.
@Robie Based on this, there is no need to follow the alternative
approach anymore, and I think this SRU request can be recalled and I
would like to ask you to reject socat from the focal unapproved queue.
--
You
I just had a look at noble's master-next tree:
$ git remote get-url origin
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
$ git branch
* master-next
and found that commit 19c1ceeca8ed is already applied:
$ git log --oneline | grep -n "block: Fix page refcounts for
** Also affects: ubuntu-power-systems
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/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released
** 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/2050019
Title:
[24.04 FEAT] [SEC2353] zcrypt: extend error recovery to deal
** 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/2051835
Title:
[24.04 FEAT] Memory hotplug vmem pages (s390x)
To manage
I've noticed that Vasily's commit has meanwhile landed in linux-next,
so I took it from there and applied it to noble master-next,
but it failed due to changed context.
Hence I did a bit of backporting work and got now it in.
I triggered appropriate kernel test builds here:
Is it know if 'Test: trace pid events filter' also ended up in a
segfault on earlier versions, e.g. 1.7.0-1 / mantic? (Probably not,
looks like the test suite is only triggered during build starting with
1.8.0-1ubuntu1 / noble...)
--
You received this bug notification because you are a member of
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
** Tags added: reverse-proxy-bugzilla
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
SRU Justification:
[ Impact ]
* Symptom:
* There is an issue with the Secure Execution (SE) tooling,
especially the new IBM host-key subject locality,
that leads to the fact that on April 24 (z15) / March 29 (z16)
users will notice
** Also affects: ipp-crypto (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ipp-crypto (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Cool, thanks a lot Steffen!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059303
Title:
[UBUNTU 20.04] SE-tooling: New IBM host-key subject locality
(s390-tools)
To manage notifications about
I gave ~ppa5 a try on my s390x system.
If I set all interfaces to "optional: true" (incl. encc000), but except
encc000.2653, I don't face the timeout anymore. But if I UNset
"optional: true" for encc000 on top, I tap into the timeout again.
In the past it was okay to NOT have "optional: true"
Marc and me, we had a side discussion and finally found the missing commits and
have a proper build for focal.
The build is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp205930
and the debdiff(s) attached.
** Attachment added: "debdiff_focal.tgz"
Hi Marc,
I've added f5744b95db9, but I unfortunately still get the build errors:
https://launchpadlibrarian.net/724893134/buildlog_ubuntu-focal-s390x.s390-tools_2.12.0-0ubuntu3.9_BUILDING.txt.gz
(search for "error:")
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
SRU Justification:
[ Impact ]
- * Symptom:
+ * Symptom:
-* There is an issue with the Secure Execution (SE) tooling,
- especially the new IBM host-key subject locality,
- that leads to the fact that on April 24 (z15) / March 29 (z16)
-
For focal the commit d14e7593cc6
(https://github.com/ibm-s390-linux/s390-tools/commit/d14e7593cc6380911ca42b09e11c53477ae13d5c)
does not properly build and the logs show a few errors:
https://launchpadlibrarian.net/723098720/buildlog_ubuntu-focal-s390x.s390-tools_2.12.0-0ubuntu3.8_BUILDING.txt.gz
s390-tools and s390-tools-signed debdiffs for 22.04/jammy
** Attachment added: "debdiff_jammy.tgz"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5765796/+files/debdiff_jammy.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Steffen,
many thanks for the tests, that's highly appreciated!
I'm glad to see that we are fine with noble, mantic and jammy.
It was btw. good to pick the version from the noble archive, since it's in
beta).
(And btw. we usually do not alter DISTRELEASE in common.mak.)
I'm uploading first of
s390-tools and s390-tools-signed debdiffs for 23.10/mantic
** Attachment added: "debdiff_mantic.tgz"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2059303/+attachment/5765782/+files/debdiff_mantic.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok, this came out of the discussions.
With that I'm closing this bug ...
** Changed in: virtinst (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ubuntu-power-systems
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Well, to me it looks like socat is like a Swiss army knife, where some
features are popular and are used often, but others are very rarely
used.
Also please consider potential reactions of users that run into this (or
similar cases):
1) (trivial) Users notice this problem (or not) and don't do
*** This bug is a duplicate of bug 2056485 ***
https://bugs.launchpad.net/bugs/2056485
** This bug has been marked a duplicate of bug 2056485
Behaviour of socat in Ubuntu 20.04 unexpected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 2055175 ***
https://bugs.launchpad.net/bugs/2055175
I strongly believe that this is a duplicate of LP#2055175, which is
meanwhile Fix Released and should be included in the latest noble/24.04
daily images.
glibc in noble (release) is currently (Apr 10th)
** Changed in: ubuntu-z-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/2059303
Title:
[UBUNTU 20.04] SE-tooling: New IBM host-key subject locality
** 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/2058944
Title:
[UBUNTU 24.04] dbginfo.sh: updates required for /bin/dash
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Tags added: s390x
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => bugproxy (bugproxy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Steffen,
thanks for checking the updated packages.
Indeed, I had to restart the build of the s390-tools-signed packages for
mantic/23.10, /jammy/22.04 and focal/20.04.
These build will be complete in an hour or so (so well before Monday).
Since the updates need to be done starting with the
** Changed in: socat (Ubuntu Focal)
Status: Incomplete => 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/2056485
Title:
Behaviour of socat in Ubuntu 20.04 unexpected
To manage
Fantastic, thanks for re-testing and confirming!
Closing this ticket as Fix Released.
** Changed in: ubuntu-power-systems
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
I see (deep in my mind I remember that such a discussion happened or at
least started somewhere).
Just notice that one interface is still _not_ optional, here in my case:
encc000
And the behavior changed recently, with the above config I didn not hit
the timeout in the past (even with earlier
** 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/2046439
Title:
Wrong code execution of s390x code with qemu TCG
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/2055175
Title:
[UBUNTU 23.10] s390x: clone clobbers r7
To manage
Builds finally completed:
noble: https://launchpad.net/~fheimes/+archive/ubuntu/lp2059303
mantic, jammy, focal: https://launchpad.net/~fheimes/+archive/ubuntu/test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for having a look at this SRU.
The general compile of the socat code works after just having commit
5ebf36038f39 "Under certain circumstances, options of the first address
were applied to the second address" applied.
However, the build also triggers a huge amount of tests, and one, test
** Description changed:
+ SRU Justification:
+
+ [ Impact ]
+
+ * Symptom:
+
+* There is an issue with the Secure Execution (SE) tooling,
+ especially the new IBM host-key subject locality,
+ that leads to the fact that on April 24 (z15) / March 29 (z16)
+ users will notice
** Changed in: python-greenlet (Ubuntu)
Assignee: (unassigned) => bugproxy (bugproxy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060108
Title:
greenlet 3.0.3 fails to build on ppc64el (and
Public bug reported:
greenlet 3.0.3 fails to build on riscv64 and ppc64el:
complete build logs at
https://launchpad.net/ubuntu/+source/python-greenlet/3.0.3-0ubuntu2
riscv64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security
ource/s390-tools/+bug/2059303/+attachment/5761332/+files/debdiffs.tgz
** Changed in: s390-tools (Ubuntu Noble)
Assignee: (unassigned) => Frank Heimes (fheimes)
** Changed in: s390-tools-signed (Ubuntu Noble)
Assignee: (unassigned) => Frank Heimes (fheimes)
** Changed in: s390-too
Oh sorry, I just noticed that the ppc64el ISO was NOT updated and is
still from March 28th, means it still has the -11 kernel inside.
We need to investigate why it wasn't updated - and why there is no daily
from April 1st and 2nd ...
--
You received this bug notification because you are a
Unsubscribed ubuntu-sponsors, since meanwhile a new LP bug came in (LP:
#2059303), and I'm going to upload a new debdiff that covers both - LP:
#2059303 and this, LP: #058944.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not incl. in Ubuntu-6.8.0-20.20, but will be included in the
next updated kernel.
--
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)
Hello Kowshik, thanks for bringing this up.
2GB RAM is not a lot, but according to 22.04 it should be sufficient (for
Ubuntu Server, Ubuntu Desktop already wants 4GB) - so I am not sure if the min.
req. for RAM may have or will change with 24.04 - I'll check.
Meanwhile, would you please re-try
Well, I already had a hard time to get the requested commits applied to
noble (which is on 2.31.0).
I figured out that:
1) commit f6c6f0cc712433221fb0588c754e0d09884453dd ("rust/pv/test: Code +
Certificate refactoring") is needed on top as pre-requisite, otherwise the
other patches do not
** Also affects: s390-tools (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: s390-tools-signed (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: s390-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects:
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
** Also affects: s390-tools-signed (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper
** Changed in: ubuntu-z-systems
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 notifications
Thanks for testing the '-20' kernel @kowshik.jois and thanks for the
updates @arighi and @hariharan.ts.
With that I'm closing this ticket (as Fix Released in 6.8.0-20).
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-power-systems
Status:
Great, thx for the update Dan!
** 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/2016860
Title:
Error/crash while trying to
Included in pam | 1.5.3-5ubuntu3.
** Changed in: pam (Ubuntu)
Status: Fix Committed => Fix Released
** 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.
** 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/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: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you
** 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/2055702
Title:
installer crashes after importing my launchpad SSH key
** Changed in: ubuntu-power-systems
Status: Triaged => 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/2055003
Title:
Qemu cmdline core dumped with more(8193 or more) cpus
To
Hi Kowshik,
sorry, just noticed the machine data line in the log:
"IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013)
hv:phyp"
Well, there is no proposed "ISO" - "-proposed" is just a special (pre-release)
area in the archive for packages, incl. kernel.
So I just
Applied for 6.8.0-12.12, so included in -20 (that is atm still in
-proposed).
--
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
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059237
Title:
[Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
every reboot
To manage notifications about
And another quick question:
on which systems does that happen?
P9 (bare-metal or PowerVM) or P10 (PowerVM) or KVM on Power?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059237
Title:
Hello Kowshik Jois, thanks for raising our attention on this.
I apologize, but once a Launchpad ticket got closed (for example as Fix
Released), like with LP#2055126, it is no longer actively monitored anymore (by
our team), hence we missed your additional comments.
(I just found your comments,
*** This bug is a duplicate of bug 2059237 ***
https://bugs.launchpad.net/bugs/2059237
** This bug has been marked a duplicate of bug 2059237
[Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every
reboot
--
You received this bug notification because you are a member of
** 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
1 - 100 of 5654 matches
Mail list logo
