Hmm,
ok I expected libvirt to call this e.g. from src/qemu/qemu_tpm.c and I wondered
already why it is the guests profile.
But since it runs under the guests profile it must be more like "libvirt ->
qemu -> ??? -> swtpm_setup" - do you have an example of the call path that you
see?
Only once
Apparmor follow up filed as:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1968187
Uploaded the tested fix for swtpm:
Uploading swtpm_0.6.3-0ubuntu2.dsc
Uploading swtpm_0.6.3-0ubuntu2.debian.tar.xz
Uploading swtpm_0.6.3-0ubuntu2_source.buildinfo
Uploading
Install fine:
ubuntu@swtpm-jammy:/var/lib/swtpm$ sudo apt update; sudo apt upgrade
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://security.ubuntu.com/ubuntu jammy-security
Public bug reported:
Guest using:
Triggers:
apparmor="DENIED" operation="open"
profile="libvirt-202a34a9-2ee2-4826-b206-c249f535be90"
name="/etc/ssl/openssl.cnf" pid=15149 comm="swtpm" requested_mask="r"
denied_mask="r" fsuid=113 ouid=0
Find from the swtpm side, but we need to open
The fix needed some polishing, but was a great hint.
Test PPA started to build at:
https://launchpad.net/~paelzer/+archive/ubuntu/lp-1968131-swtpm-rndfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes Simon,
that is much better than me trying to fetch home and insert it into the string
:-)
Thanks for the reference.
It feels a bit odd seeing myself coming by between meetings all day and
make debug progress to then see such a simple solution. Please tell me
that my debug helped to make that
A new interim summary
Problem:
- debian/patches/openssl-not-certtool.patch adds "RANDFILE =
$ENV::HOME/.rnd\n"
- this is not picked up correctly at the time this file is evaluated
- Due to that swtpm-localca tries to access $CWD/.rnd and fails in most cases
- The upstreaming of this
In a set of cross checks I ran it as
#1 root, but this time in /home/ubuntu instead of in /root.
I got:
lrwxrwxrwx 1 root root 0 Apr 7 13:40 /proc/11805/cwd -> /home/ubuntu/
And afterwards
-rw--- 1 root root 1024 Apr 7 13:40 /home/ubuntu/.rnd
So it fully ignores $HOME
So root cause
Ok, it has
HOME=/var/lib/swtpm
So due to the config being
"RANDFILE = $ENV::HOME/.rnd\n"
one might expect `/var/lib/swtpm/.rnd`
But that isn't what it will resolve to, instead we see in strace that it uses:
"./.rnd"
And surprise :-P, it does not set CWD, I checked a running
The swtpm user is created as:
swtpm:x:113:121:virtual TPM software stack,,,:/var/lib/swtpm:/bin/false
But
$ ls -laF /var/lib/swtpm
ls: cannot access '/var/lib/swtpm': No such file or directory
I guess we need to give him a better home dir?
For example drop `--no-create-home` from the postinst
I think I got it, it is around that .rnd file as mentioned in the log.
Indeed after running this as root I have:
$ sudo ls -laF /root/.rnd
-rw--- 1 root root 1024 Apr 7 08:16 /root/.rnd
But running as swtpm I get this with strace:
This is the initial failure:
[pid 3049] 13:10:20 (+
# clean
$ sudo apt remove --purge swtpm swtpm-tools
$ sudo rm -rf /var/lib/libvirt/swtpm /var/lib/swtpm-localca /var/log/swtpm
# re-create a clean env by re-installing swtpm
$ sudo apt install swtpm swtpm-tools
# Status after install
$ sudo ls -laF /var/lib/libvirt/swtpm
Summary of initial triage:
- It is reproducible for me as reported => confirmed
- Other than hoped it is not "just" an apparmor denial (it is in the setup
stage,
not the later swtpm that talks with the guest) :-/
- running the failing command as root locally works
- seems to be associated to
I found it in ps
4 1131814 758 20 0 13772 5784 - S? 0:00 \_
/usr/bin/swtpm_setup --tpm2 --tpm-state
/var/lib/libvirt/swtpm/202a34a9-2ee2-4826-b206-c249f535be90/tpm2 --vmid
testguest:202a34a9-2ee2-4826-b206-c249f535be90 --logfile
I wanted to check if this is more virt-manager or libvirt to call it
badly (or call it in a bad environment).
I spawned a default libvirt based guest with uvtool.
In there I then added the most common pattern of
This is showing kind of the same behavior.
So while most tests before were
As invoked by the virt-stack we see:
Starting vTPM manufacturing as swtpm:swtpm @ Thu 07 Apr 2022 08:14:26 AM UTC
Successfully created RSA 2048 EK with handle 0x81010001.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type ek --ek
I agree that worst-case dropping the recommends is an option.
But only to mitigate - it is meant to be available and working.
It worked for me in the (far) past, but it might have been one of the
extra updates/features landing in the meantime. Although I have not used
it with virt-install yet
Since we couldn't get a hold how to fix/debug this I'm glad to hear
that!
** Changed in: open-vm-tools (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As with the other case - Since we couldn't get a hold how to fix/debug
this I'm glad to hear that!
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You are right for a general stance of SRU minimality
But this case felt like fixing 7/8 of a single whole.
And while indeed your case didn't need this one more fix someone else would and
we touch this code anyway. Vice versa all tests since this is upstream is done
with it applied - so the
Upgraded and tested from impish proposed
root@i:~# dpkg -l ldnsutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Request to add the test to the upstream build time test filed here:
https://github.com/NLnetLabs/ldns/issues/169
** Bug watch added: github.com/NLnetLabs/ldns/issues #169
https://github.com/NLnetLabs/ldns/issues/169
--
You received this bug notification because you are a member of Ubuntu
Understanding what happens is critical, then - once we know what it is -
it might be tuned down in priority.
Also tagged/subscribed for foundations (fow swtpm) and server (for the
virt bits) attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Martin,
IIRC the new virt-manager tries to provide swtpm if present and due tot he
dependency change it now it present. Since we do not yet know where the
root-cause or fix will land I've added a few more affected packages for now.
But I must admit I'm super busy and this makes me feel
** Changed in: freeradius (Ubuntu Focal)
Assignee: Lena Voytek (lvoytek) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873923
Title:
freeradius with
Planning to have a look as part of next cycles merge.
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581864
Title:
nginx.service: Failed to read PID from file
Planning to have a look as part of next cycles merge.
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948699
Title:
Please enable luajit for arm64
To manage
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893716
Title:
scripts in /etc/update-motd.d/ run even on login via non-interactive
scp and sftp sessions
To manage
There actually is an autopkgtest exercising this already, as part of
dns-root-data - this is how it was found. The problem is that this test
isn't fired when ldns itself is updated :-/
I'd not want to block the SRU on this Robie.
But I'd be ok to file a request upstream to please add it to their
Prepared
PPA:
https://launchpad.net/~paelzer/+archive/ubuntu/lp-1967814-scsi-error-handling/+packages
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/418636
Let us see if one builds and tests fine and the other gets positive
review feedback.
--
You received this
I'm done reading and while a complex subsystem and a bunch of changes
they individually all seem sane to me (although a108557b could have side
effects that are hard to spot).
For SRU considerations I think this includes potential change of
behavior of formerly silently ignored errors now becoming
I can confirm that just on the patch-level only two need backporting,
the rest applies as is and I have regenerated them to match the
packaging requirements. The backport-adaptations themselves are minimal.
From the content I guess it is complex enough that nobody can be fully sure.
I'm still
For easier debugging this can be reproduced on any affected system
(Tried KVM and EC2) by just running:
$ sudo systemctl start hv-kvp-daemon.service
^^ This will stall while one would assume it should quick-exit due to
the ConditionVirtualization not being met.
A full cycle (90 second stall)
On a fresh AWS instance I already see it stalling on package install, I
do not even need to reboot :-/
ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages
Public bug reported:
I see a boot stall on a normal qemu/libvirt based KVM guest using an almost
fresh cloud image a stall on boot:
While live on the console I see:
[ OK ] Reached target System Time Set.
[ OK ] Finished Load AppArmor pro…s managed internally by snapd.
[* ] A start job is
** Package changed: kvm (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967894
Title:
KVM IPI Virtualization support for SPR
To manage notifications about this bug go to:
FYI: Filed upstream at https://github.com/linux-pam/linux-pam/issues/452
** Bug watch added: github.com/linux-pam/linux-pam/issues #452
https://github.com/linux-pam/linux-pam/issues/452
** Also affects: pam via
https://github.com/linux-pam/linux-pam/issues/452
Importance: Unknown
Overall the majority of this is now fixed and mitigated with the combination of:
ubuntu-release-upgrader | 1:22.04.8 | jammy | source
landscape-client | 19.12-0ubuntu13| jammy | source, amd64,
arm64, armhf, ppc64el, riscv64, s390x
update-notifier | 3.192.54 |
This shows in component mismatches (seed change landed)
nftables: libnftables-dev libnftables1 nftables
MIR: #1887187 (Fix Committed)
[Reverse-Depends: Rescued from nftables (Uploader: paelzer) (Uploader:
paelzer), Ubuntu.Jammy standard seed, nftables (Uploader: paelzer)]
It is only in jammy
** Changed in: nftables (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: nftables (Ubuntu)
Assignee: Steve Beattie (sbeattie) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
List of original commits and the version they were in:
v5.2.0
commit 3b12a7fd39307017c8968b8d05986a63b33752b5
Author: Paolo Bonzini
Date: Thu Nov 12 10:52:04 2020 +0100
scsi-disk: convert more errno values back to SCSI statuses
v6.0.0
commit f95f61c2c9618fae7d8ea4c1d63e7416884bad52
This is back in Jammy and working:
mini-buildd | 1.9.99 | jammy/universe | source, all
It didn't resolve the issue of >1.0 being generally unstable, but what we had
works again.
Thanks
** Changed in: mini-buildd (Ubuntu)
Status: In Progress => Fix Released
--
You received this
This is now showing in component mismatches:
libtpms: libtpms-dev libtpms0
MIR: #1948748 (New)
[Reverse-Depends: Rescued from libtpms (Uploader: paelzer), swtpm (Uploader:
paelzer)]
swtpm: swtpm swtpm-tools
MIR: #1948748 (In Progress)
[Reverse-Depends: swtpm-tools]
[Reverse-Recommends:
This is actually fixed already in 5.13.0.39.44 as shown above, but the
root cause that I'm facing is that edge-Kernel is behind non -egde:
$ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal
linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security |
Added a libvirt task to bring in the dependency.
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
libtpms [1] and even the auto unblocked ppc build of swtpm [2] migrated
to jammy-release in universe.
For both we have the MIR ack, Security ack and all required todos implemented.
Time to seed or depend on this accordingly.
The one I know that was planned was a recommends from libvirt which can
[1] as well as automatically already [2] built.
Let us see over the weekend if all test and migrate fine and then we can
consider seeding/depending on them to promote it.
[1]: https://launchpad.net/ubuntu/+source/libtpms/0.9.3-0ubuntu1
[2]:
Rebuilds, Sanity tests and autopkgtests with the new version worked well.
Uploading libtpms to get this ready for promotion to main next week.
Note: After it is in jammy we can also hit rebuild on [1] to complete
architecture parity of swtpm.
[1]:
Thank you Seth, so this seems all ready once the fixed version of
libtpms landed in jammy.
As mentioned before I have already prepared this in
https://code.launchpad.net/~paelzer/ubuntu/+source/libtpms/+git/libtpms/+merge/417854
It has acks there for the changes so far and should be good.
I'll
Thank you Matthias!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940029
Title:
Default of fcf-protection should only be enabled where it can work
To manage notifications about this bug go to:
Thanks for making us aware Christoph that this was falling through the cracks.
Athos is trying to have a look today and summarize the current state here.
I'll then try to have a look at continuing that tomorrow and hopefully
Simon (Mr. OpenSSL3) can help as well then.
TL;DR:
yes you could say
With the ipmi* support in some of the HA components it might be time to
re-evaluate it.
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576812
Title:
[MIR] ipmitool
To
After some extra checks (The -doc package will be auto-included, but has
only deps to main and thereby is no problem) and confirming with Lukasz
(thanks) that there is no beta-freeze-problem making this harder this is
ready.
None of this is left in -proposed, so only changing in -universe.
It even migrated
python-xmlschema | 1.10.0-1 | jammy/universe | source
This was the last missing bit (thanks Corey!).
Furthmore AFAICS it is already in
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html
Blocking the transition of
python3-pysaml2 | 6.1.0-0ubuntu2
Pengpeng/Yuhua - I have internally asked (at the same time I added the tag a
few days ago) for someone to look after it.
Nothing happened yet, so I pinged again.
In preparation of this - since most of Ubuntu developers won't have a
vsphere around to reproduce this. Is there any other way to
> Hopefully this can be added in a new version to
> be released soon, otherwise mini-buildd may have to be re-added with a
> temporary delta.
Thank you Lena, but due to time - unless they release super-fast - let
us prepare and add this with delta right away once the beta freeze is
lifted
FYI for a different test I upgraded the system to Impish and on the
5.13.0-39-generic there neither of the two kernel bugs happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
I re-installed the former package content, rebooted the system and gave
it some more memory to get rid of any concerns in that regard (from the
perf data).
The diff of the actual content before/after was all reasonable (new
times, different package counts, but otherwise the same)
Consumption
Thanks Seth,
these tpm things are rather new so exposure to testing is low in general.
You are right, but I think we do not only need what you spotted.
In fact while reading this I found that upstream (Thanks Stefan) maintains
great stable branches.
I think we should consider taking in
-
fier (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt
#3 50-landscape-sysinfo
The landscape part already has a statement about "when it is from" as it
is not re-executed on high load. This is handy as it will also ensure
there is no confusion "from when" this info is if we skip for too
frequent invocations.
Since it has an alternate less useful
#2 95-hwe-eol / update-motd-hwe-eol
Sadly this already does some caching in update-motd-hwe-eol by checking
if the last of these checks is older than an update to the source lists.
But to do so it has already executed the - relatively - rather expensive
apt-config calls.
Since it comes down to
Collecting snippets:
This one worked, proven by eliminating lsb_release on the consumption
charts.
#1 Caching for 91-release-upgrade:
--- orig/91-release-upgrade 2022-03-30 07:53:26.560515795 +
+++ /etc/update-motd.d/91-release-upgrade 2022-03-30 07:59:05.819971148
+
@@ -1,7
Uploaded the impish variant for SRU consideration
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966237
Title:
ldnsutils emits wrong sha256 hashes
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libtpms/+git/libtpms/+merge/417854
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948748
Title:
[MIR] swtpm
To
The rest is as reported, it makes sense to be removed and really is only
present in jammy-proposed.
$ rma node-puppeteer
Debian
node-puppeteer | 13.4.1+dfsg-1 | testing| source, all
node-puppeteer | 13.4.1+dfsg-1 | unstable | source, all
Ubuntu:
node-puppeteer | 13.1.0+dfsg-4 |
I agree it doesn't make sense as-is and should be removed from jammy.
I do not (yet) agree on a sync blocker.
Other packages that modify/enhance/need chrome* are doing it differently:
Example:
Package: chrome-gnome-shell
...
Suggests: chromium | chromium-browser, firefox
Breaks: firefox (<< 56),
Summarizing the low hanging fruits here:
- Add caching to 50-landscape-sysinfo
- Add caching to 95-hwe-eol
- /usr/lib/update-notifier/update-motd-hwe-eol calls apt-config multiple times.
consider reducing those calls
- 91-release-upgrade unconditionally calls lsb_release which is expensive.
Analysis has spotted 91-release-upgrade as the most likely expensive remainder.
pam_motd enabled, but disabled:
- 50-landscape-sysinfo
- 91-release-upgrade
- 95-hwe-eol disabled
Bionic
real0m18.669s
us sy id wa st
22 23 55 0 0
Focal
real0m23.821s
us sy id wa st
40 39 21 0 0
pam_motd enabled, but 50-landscape-sysinfo and 95-hwe-eol disabled
Bionic
real0m25.952s
us sy id wa st
41 22 37 0 0
Focal
real0m30.592s
us sy id wa st
49 33 19 0 0
Jammy
real0m25.395s
us sy id wa st
44 28 29 0 0
That is still quite some overhead (~+60% to no motd)
pam_motd completely disabled in /etc/pam.d/sshd
Bionic
real0m15.540s
us sy id wa st
18 14 68 0 0
Focal
real0m16.937s
us sy id wa st
43 40 17 0 0
Jammy
real0m16.260s
us sy id wa st
36 19 45 0 0
The remaining difference of those is in the noise-range.
Time and CPU consumption (results are rather consistent BTW):
Bionic
real1m11.714s
user0m2.577s
sys 0m0.410s
procs ---memory-- ---swap-- -io
-system-- cpu -timestamp-
r b swpd free buff
I wanted to get a better feeling about this before jumping to action.
Therefore I have created three 1G/1vcpu KVM guests Bionic/Focal/Jammy to test
and compare this on.
I do not need hot-loop analysis or anything down to instructions, so no debug
symbols needed.
For now I only want to know:
1.
I tried things once more, this time OVS wasn't active at all (in the
former try it was active after boot and then disabled) - still failing.
Next I tried to use a different kernel(5.4.0-105-generic)
I don't know when in >5.4 this started to fail, it surely worked a few
months ago already using
As the last stage in the crash is in
? blk_mq_exit_hctx+0x160/0x160
I was looking if there was anything else with block devices going on.
I found another crash right at boot/init time (this one is also in the attached
currentDmesg.txt).
[ 537.566942] [ cut here ]
[
I have tried the same again, this time with openvswitch unconfigured (but still
running).
ubuntu@node-horsea:~$ sudo ovs-vsctl del-br ovsbr0
ubuntu@node-horsea:~$ sudo ovs-vsctl show
8dfc2067-7b9b-48d7-a50a-df17bbd3cb6c
ovs_version: "2.13.5"
chcpu disabling/enabling still crashes.
Ok, I have manually retried this - we do not need the KVM guest, it is the
chcpu that kills it.
Simplifying description ...
** Summary changed:
- Focal 20.04.4 crashing when using openvswitch/hugepages
+ Focal 20.04.4 crashing when using openvswitch and disabling CPUs
** Description changed:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574145/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574144/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574142/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574143/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574141/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574140/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574139/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574137/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574138/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574134/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574136/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574132/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574135/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574133/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
Public bug reported:
Hi I'm facing the following crash now two times in a row while runnign the same
test - so somewhat reproducible it seems:
[ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008
[ 1444.431172] #PF: supervisor write access in kernel mode
[ 1444.454715]
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1966870/+attachment/5574131/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966870
Title:
Focal
We do only want to hold it back in impish, jammy we want to complete.
Updating the tag.
** Tags removed: block-proposed
** Tags added: block-proposed-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, summary.
- MIR ack present
- Security Ack present
=> What is still left open is the required TODO from the MIR review as
identified by James "Update to latest upstream release."
That would currently be 1.10 which also is in Debian testing/unstable
python-xmlschema | 1.4.2-1 |
The only current interactivity detection code in pam is part of a
pam.conf -> pam.d conversion tool that won't be useful here.
The pam_motd code emits content via things like try_to_display_fd.
A message is created and then printed via pam_info.
Which is actually pam_prompt which wraps
The upstream feature is static:
https://github.com/allisonkarlitskaya/linux-pam/commit/acd50bf7b6dd78e3185a57368f8568fb7be11d39
While "only static" it can't be disabled either.
Yet without anything to display it to it renders as mostly a no-op.
The dynamic parts are Ubuntu delta due to bug
There are tasks for /etc/pam.d/common-session-noninteractive but those have no
detection logic.
They are just included from several non-intactive pam types: samba, sudo,
polkit, cron.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
BTW I also wanted to confirm that this runs (as reported) on any sftp
connect and therefore (imagine serving a bunch of small files fetched
every now and then) adding overhead there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
301 - 400 of 23066 matches
Mail list logo
