[Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
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: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 wise we have: # Before fixes real1m11.731s us sy id wa st 71 20 9 0 0 59.16% landscape-sysin 14.23% swapper 6.16% sshd 5.78% lsb_release 3.35% apt-config 0.86% dbus-daemon 0.80% systemd 0.59% gdbus 0.56% dpkg 0.48% systemd-logind # After fixes real0m21.257s us sy id wa st 32 34 34 0 0 42.00% swapper 22.45% sshd 2.94% dbus-daemon 2.79% systemd 2.08% gdbus 2.07% grep 1.88% run-parts 1.58% systemd-logind 1.46% find 1.23% bash 1.22% update-motd-fsc 1.18% systemd-journal 1.13% cat That is good. Ready to open MRs for this. At a very high summary: - delay cut down by 2/3 of the initial duration - consumption reduced by 71% (duration) and by 26% (consumption while running). This is multiplicative so for the example we have an saving of ~81.27% of cpu cycles -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
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 - https://github.com/stefanberger/libtpms/releases/tag/v0.9.1 - https://github.com/stefanberger/libtpms/releases/tag/v0.9.2 - https://github.com/stefanberger/libtpms/releases/tag/v0.9.3 - plus the patch you've found - a ppc64 build fix from debian / upstream #297 I'll try to prepare this so that someone else review and ack (or disagree). None of this needs a FFe IMHO all just fixes - we'll want to hold back the actual upload until beta-freeze is over, but that does not prevent to prepare the fixes. In addition to reduce delta one day I filed: - https://github.com/stefanberger/libtpms/pull/305 I have prepared that in: PPA: https://launchpad.net/~paelzer/+archive/ubuntu/libtpms-jammy-0.9.3 MR: https://code.launchpad.net/~paelzer/ubuntu/+source/libtpms/+git/libtpms/+merge/417854 P.S. this will also resolve the fact that it is - so far - missing on ppc64 Please anyone review and/or consume it from that PPA and let me know if you are +1 on an upload of that. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
With the three combined I get down to: real0m20.900s us sy id wa st 32 33 35 0 0 43.88% swapper 21.48% sshd 3.07% dbus-daemon 2.78% systemd 2.10% gdbus 1.96% grep 1.80% run-parts 1.68% systemd-logind 1.38% find 1.24% systemd-journal 1.23% bash 1.12% update-motd-fsc 1.10% cat 0.95% awk 0.85% 50-motd-news 0.76% uname 0.70% 00-header 0.69% 91-release-upgr 0.67% 97-overlayroot 0.67% 50-landscape-sy 0.62% date 0.61% 90-updates-avai 0.56% 95-hwe-eol 0.54% cut None of the remaining big contributions to consumption is from the MOTD efforts (all <2%). That is reasonable, nice time gain as well as reduced cpu consumption. ** Changed in: landscape-client (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => In Progress ** Changed in: update-notifier (Ubuntu) Status: New => In Progress ** Changed in: update-notifier (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 (paelzer) ** Changed in: landscape-client (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High ** Changed in: update-notifier (Ubuntu) Importance: Undecided => High ** Changed in: update-motd (Ubuntu) Importance: High => Medium ** Changed in: pam (Ubuntu) Importance: High => Medium ** Changed in: update-motd (Ubuntu) Status: Confirmed => Invalid -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
#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 output I've added checks to
replace this more often and not replace a good output with a bad one.
--- orig/50-landscape-sysinfo 2022-03-30 07:53:04.320551811 +
+++ /etc/update-motd.d/50-landscape-sysinfo 2022-03-30 10:04:00.536053398
+
@@ -1,17 +1,39 @@
#!/bin/sh
-# pam_motd does not carry the environment
-[ -f /etc/default/locale ] && . /etc/default/locale
-export LANG
-cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
-[ "$cores" -eq "0" ] && cores=1
-threshold="${cores:-1}.0"
-if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ]; then
-echo
-echo -n " System information as of "
-/bin/date
-echo
-/usr/bin/landscape-sysinfo
-else
-echo
-echo " System information disabled due to load higher than $threshold"
+
+# do try refresh this more than once per minute
+# Due to cpu consumption and login delays (LP: #1893716)
+stamp="/var/lib/landscape/landscape-sysinfo.cache"
+NEED_UPDATE="FALSE"
+find $stamp -newermt 'now-1 minutes' 2> /dev/null | grep -q -m 1 '.' ||
NEED_UPDATE="TRUE"
+# If the last report in cache wasn't useful (load was too high) still wait at
least 5 seconds
+if grep -q "System information disabled" $stamp 2> /dev/null; then
+find $stamp -newermt 'now-5 seconds' 2> /dev/null | grep -q -m 1 '.' ||
NEED_UPDATE="TRUE"
fi
+
+if [ "$NEED_UPDATE" = "TRUE" ]; then
+# pam_motd does not carry the environment
+[ -f /etc/default/locale ] && . /etc/default/locale
+export LANG
+cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
+[ "$cores" -eq "0" ] && cores=1
+threshold="${cores:-1}.0"
+if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ];
then
+ (
+echo
+echo -n " System information as of "
+/bin/date
+echo
+/usr/bin/landscape-sysinfo
+) > $stamp
+else
+ # do not replace a formerly good result due to load
+ if ! grep -q "System information as of" $stamp 2> /dev/null; then
+ (
+ echo
+ echo " System information disabled due to load higher than
$threshold"
+ ) > $stamp
+ fi
+fi
+fi
+
+[ ! -r "$stamp" ] || cat "$stamp"
# Info:
It might be worth to note, the optimizations to 95-hwe-eol and
91-release-upgrade save CPU cycles (which is good and worth on its own), but do
not improve the delay much.
The optimization to
P.S. I'll need some minor updates for style and avoiding errors (e.g.
the && exit 0 was working but could be bad)
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
#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 checking new sources.lists there is no need to update this more often than once every few minutes or hours. Could be even slower without loosing most of its value, but we already achieve most of what we need with a delay of ~1h. We started with: 5.37% apt-config Now: -- no more present --- orig/95-hwe-eol 2022-03-30 07:53:18.396529018 + +++ /etc/update-motd.d/95-hwe-eol 2022-03-30 09:13:16.160985148 + @@ -1,5 +1,11 @@ #!/bin/sh +# this stamp is created and updated by /usr/lib/update-notifier/update-motd-hwe-eol +stamp="/var/lib/update-notifier/hwe-eol" + +# do not try to refresh this more than once per hour +find $stamp -newermt 'now-1 hours' 2> /dev/null | grep -m 1 '.' && exit 0 + if [ -x /usr/lib/update-notifier/update-motd-hwe-eol ]; then exec /usr/lib/update-notifier/update-motd-hwe-eol fi No big need left to reduce the apt-config usage in update-motd-hwe-eol after this change. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 +1,12 @@ #!/bin/sh # if the current release is under development there won't be a new one -if [ "$(lsb_release -sd | cut -d' ' -f4)" = "(development" ]; then +[ -r /etc/lsb-release ] && . /etc/lsb-release +if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then +DISTRIB_DESCRIPTION=$(lsb_release -s -d) +fi + +if [ "$(echo "$DISTRIB_DESCRIPTION" | cut -d' ' -f4)" = "(development" ]; then exit 0 fi -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967048] Re: Please remove node-puppeteer source and binaries from jammy
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 | jammy-proposed/universe | source, all And as you see it is also outdated compared to what is in debian as it is stuck since being synced and no more synced since then. The new version has only updated versions in the dependencies - not a fix to the problem. Source and binary have the same name, no other binaries or rdeps. Ack and done $ ./remove-package -m "unsatisfiable chrome dependency (LP: #1967048)" --suite jammy-proposed node-puppeteer Removing packages from jammy-proposed: node-puppeteer 13.1.0+dfsg-4 in jammy node-puppeteer 13.1.0+dfsg-4 in jammy amd64 node-puppeteer 13.1.0+dfsg-4 in jammy arm64 node-puppeteer 13.1.0+dfsg-4 in jammy armhf node-puppeteer 13.1.0+dfsg-4 in jammy i386 node-puppeteer 13.1.0+dfsg-4 in jammy ppc64el node-puppeteer 13.1.0+dfsg-4 in jammy riscv64 node-puppeteer 13.1.0+dfsg-4 in jammy s390x Comment: unsatisfiable chrome dependency (LP: #1967048) Remove [y|N]? y 1 package successfully removed. ** Changed in: node-puppeteer (Ubuntu) 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/1967048 Title: Please remove node-puppeteer source and binaries from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-puppeteer/+bug/1967048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967048] Re: Please remove node-puppeteer source and binaries from jammy
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), firefox-esr (<< 56) Enhances: chromium, chromium-browser, firefox Instead I'd ask you to make a trivial proposal to Debian to either generally reduce this dependency (totally fine if it could also control remote chromiums) or one of the "if ubuntu then suggest". If there is hard refusal, well then yes the use case is rather special and it might be blocked. But I'd not give up immediately :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967048 Title: Please remove node-puppeteer source and binaries from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-puppeteer/+bug/1967048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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. Use the same check others use The rest already uses caching AND/OR is small, fast and simple. The follow on of making pam_motd truly not do anything on non- interactive can then be a follow on case and would no more be that important. For these fixes three packages need to be touched: Source: ubuntu-release-upgrader Source: update-notifier Source: landscape-client ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 Jammy real0m19.616s us sy id wa st 33 30 37 0 0 This is pretty close to "no-motd" and has no single spike left. The next ones I found in the list are now low and already use caching. The improvement for those would be a (slower and more complex) modification to pam_motd to detect and skip on non-interactive sessions. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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) but clearly those are the two worst contributors. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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. Some difference in the cycles consumed though, but not too bad. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 buffcache si sobibo in cs us sy 17 0 0 2022-03-29 13:13:15 0 00 22103628312 15698000 0 2124 4319 1330 67 19 14 0 0 2022-03-29 13:13:20 1 00 19677228320 15852400 011 4290 1274 68 19 13 0 0 2022-03-29 13:13:25 ... Focal real0m44.742s user0m2.489s sys 0m0.477s procs ---memory-- ---swap-- -io -system-- cpu -timestamp- r b swpd free buffcache si sobibo in cs us sy id wa st UTC 1 004278418448 26704800 011 4554 3561 67 24 8 0 0 2022-03-29 13:14:13 1 003773218456 26910000 012 4577 3851 65 25 10 0 0 2022-03-29 13:14:18 1 001840018464 27081200 011 4554 3547 67 24 9 0 0 2022-03-29 13:14:23 Jammy real1m8.010s user0m2.436s sys 0m0.484s --procs-- ---memory-- ---swap-- -io -system-- cpu -timestamp- rb swpd free buffcache si sobi bo in cs us sy id wa st UTC 0005826417760 25854400 0 9 4374 1953 68 20 11 0 0 2022-03-29 13:15:20 1003284417772 26033200 0 16 4352 1851 68 20 11 0 0 2022-03-29 13:15:25 1004942817784 26226800 0 17 4387 1985 67 22 12 0 0 2022-03-29 13:15:30 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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. how much time a bunch of low effort logins take (we measure only the overhead) 2. how much cpu is utilized while doing that 3. how that work is spread across programs (disable them one by one and look at data) The two I see most are: - /usr/lib/update-notifier/update-motd-hwe-eol apt-config shell SourceList Dir::Etc::sourcelist - /etc/update-motd.d/50-landscape-sysinfo /usr/bin/python3 /usr/bin/landscape-sysinfo Very non-pro data gathering: $ cat tracestart.sh #!/bin/bash sudo rm perf.data perf.log log.vmstat nohup vmstat -wt 5 &> log.vmstat & nohup perf record --event cpu-clock --all-cpus &> perf.log & sleep 5 $ cat traceend.sh #!/bin/bash killall perf killall vmstat cat perf.log cat log.vmstat #perf report --sort comm --stdio Most simple load involving those helpers. for sys in login-bionic login-focal login-jammy; do ssh $sys "sudo ~/tracestart.sh"; time for i in $(seq 1 100); do ssh $sys "/bin/true"; done; ssh $sys "sudo ~/traceend.sh"; done I'll get those numbers for Bionic/Focal/Jammy and enabling/disabling it all and/or individual elements. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
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 the an HWE kernel back then and running the same tests that now stumbled over this. I usually run with: linux-image-generic-hwe-20.04-edge 5.13.0.27.29~20.04.13 => the one that initially failed And now I cross tested: linux-generic 5.4.0.105.109 => working fine Would it be helpful to you to also get (it is somewhat suspicious that egde is behind non-edge): linux-image-generic-hwe-20.04 5.13.0.39.44~20.04.24 Would there be any other build that I should try helping you to pinpoint this? -- 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 20.04.4 5.13.0-27-generic crashing disabling CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
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 ] [ 537.566946] WARNING: CPU: 7 PID: 2421 at block/blk-mq.c:3087 blk_mq_release+0x45/0xe0 [ 537.566958] Modules linked in: nbd(+) xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 rpcrdma sunrpc rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl intel_cstate efi_pstore ioatdma hpilo acpi_ipmi ipmi_si acpi_tad mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs [ 537.567073] blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect aesni_intel sysimgblt mlx5_core fb_sys_fops pci_hyperv_intf crypto_simd ixgbe cec psample cryptd xfrm_algo nvme i2c_i801 rc_core mlxfw hpsa xhci_pci dca drm lpc_ich i2c_smbus tg3 xhci_pci_renesas nvme_core tls mdio scsi_transport_sas wmi [ 537.567146] CPU: 7 PID: 2421 Comm: modprobe Tainted: P O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 537.567151] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 537.567154] RIP: 0010:blk_mq_release+0x45/0xe0 [ 537.567159] Code: 48 31 d2 eb 07 83 c2 01 39 f2 74 27 48 63 c2 48 8b 04 c7 48 85 c0 74 ed 48 8b 88 30 02 00 00 48 05 30 02 00 00 48 39 c1 75 db <0f> 0b 83 c2 01 39 f2 75 d9 49 8b 84 24 90 05 00 00 49 8d 9c 24 90 [ 537.567163] RSP: 0018:c287c17f3a58 EFLAGS: 00010246 [ 537.567167] RAX: 9f2611f50230 RBX: 9f2609bfefa0 RCX: 9f2611f50230 [ 537.567170] RDX: RSI: 0001 RDI: 9f261e60ef38 [ 537.567173] RBP: c287c17f3a70 R08: 0004 R09: 002c [ 537.567175] R10: 9f2601c07800 R11: 01b6 R12: 9f2609bfef20 [ 537.567178] R13: 9f2609bfef20 R14: 9f2609bfefa0 R15: [ 537.567181] FS: 7f1728b36680() GS:9f2d5fbc() knlGS: [ 537.567185] CS: 0010 DS: ES: CR0: 80050033 [ 537.567188] CR2: 7f814132242d CR3: 000119bf4003 CR4: 001706e0 [ 537.567191] Call Trace: [ 537.567197] blk_release_queue+0xbc/0x140 [ 537.567203] kobject_release+0x4b/0x160 [ 537.567211] kobject_put+0x49/0x60 [ 537.567215] blk_put_queue+0x12/0x20 [ 537.567224] disk_release+0x68/0x90 [ 537.567231] device_release+0x3b/0xa0 [ 537.567239] kobject_release+0x4b/0x160 [ 537.567243] kobject_put+0x49/0x60 [ 537.567247] put_device+0x13/0x20 [ 537.567252] put_disk+0x1b/0x20 [ 537.567258] nbd_dev_add+0x259/0x2b0 [nbd] [ 537.567275] nbd_init+0x11a/0x1000 [nbd] [ 537.567284] ? 0xc0ffd000 [ 537.567287] do_one_initcall+0x48/0x1d0 [ 537.567298] ? __cond_resched+0x19/0x30 [ 537.567308] ? kmem_cache_alloc_trace+0x37c/0x440 [ 537.567319] do_init_module+0x62/0x260 [ 537.567325] load_module+0x125d/0x1440 [ 537.567332] __do_sys_finit_module+0xc2/0x120 [ 537.567337] ? __do_sys_finit_module+0xc2/0x120 [ 537.567343] __x64_sys_finit_module+0x1a/0x20 [ 537.567347] do_syscall_64+0x61/0xb0 [ 537.567354] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 537.567362] ? syscall_exit_to_user_mode+0x27/0x50 [ 537.567367] ? __x64_sys_newfstat+0x16/0x20 [ 537.567373] ? do_syscall_64+0x6e/0xb0 [ 537.567379] ? asm_exc_page_fault+0x8/0x30 [ 537.567385] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 537.567390] RIP: 0033:0x7f1728c7876d [ 537.567394] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 36 0d 00 f7 d8 64 89 01 48 [ 537.567398] RSP: 002b:7ffcfaa186a8 EFLAGS: 0246 ORIG_RAX: 0139 [ 537.567402] RAX: ffda RBX: 559308b38000 RCX: 7f1728c7876d [ 537.567405] RDX: RSI: 559307d34358 RDI: 0003 [ 537.567407] RBP: 0006 R08: R09: [
[Bug 1966870] Re: Focal 20.04.4 crashing when using openvswitch and disabling CPUs
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. ubuntu@node-horsea:~$ sudo chcpu -d 5-11 Killed [ +3.357665] IRQ 56: no longer affine to CPU5 [ +0.21] IRQ 72: no longer affine to CPU5 [ +0.09] IRQ 82: no longer affine to CPU5 [ +0.11] IRQ 96: no longer affine to CPU5 [ +0.19] IRQ 121: no longer affine to CPU5 [ +0.12] IRQ 136: no longer affine to CPU5 [ +0.002380] smpboot: CPU 5 is now offline [ +0.000468] BUG: kernel NULL pointer dereference, address: 0008 [ +0.031357] #PF: supervisor write access in kernel mode [ +0.023816] #PF: error_code(0x0002) - not-present page [ +0.023147] PGD 0 P4D 0 [ +0.011391] Oops: 0002 [#1] SMP PTI [ +0.015688] CPU: 11 PID: 5967 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ +0.043614] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ +0.037462] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ +0.023926] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ +0.084916] RSP: 0018:acf3ccddbbb0 EFLAGS: 00010286 [ +0.023534] RAX: ccf3bfb7a580 RBX: RCX: acf3ccddbbb0 [ +0.033000] RDX: ccf3bfb7a588 RSI: RDI: [ +0.032118] RBP: acf3ccddbbe8 R08: R09: acf3ccddbaa8 [ +0.032456] R10: 0001 R11: 0001 R12: 8da022a5 [ +0.032331] R13: ccf3bfb7a580 R14: acf3ccddbbb0 R15: 0005 [ +0.032137] FS: 7f1a4aff9580() GS:8da29fcc() knlGS: [ +0.036480] CS: 0010 DS: ES: CR0: 80050033 [ +0.025981] CR2: 0008 CR3: 0005b29d6006 CR4: 001706e0 [ +0.032158] Call Trace: [ +0.010991] ? blk_mq_exit_hctx+0x160/0x160 [ +0.018782] cpuhp_invoke_callback+0x179/0x430 [ +0.020112] cpuhp_invoke_callback_range+0x44/0x80 [ +0.021557] _cpu_down+0x109/0x310 [ +0.015284] cpu_down+0x36/0x60 [ +0.014475] cpu_device_down+0x16/0x20 [ +0.016905] cpu_subsys_offline+0xe/0x10 [ +0.017652] device_offline+0x8e/0xc0 [ +0.016520] online_store+0x4c/0x90 [ +0.015662] dev_attr_store+0x17/0x30 [ +0.016581] sysfs_kf_write+0x3e/0x50 [ +0.016546] kernfs_fop_write_iter+0x138/0x1c0 [ +0.020381] new_sync_write+0x117/0x1b0 [ +0.017389] vfs_write+0x185/0x250 [ +0.015407] ksys_write+0x67/0xe0 [ +0.014961] __x64_sys_write+0x1a/0x20 [ +0.016879] do_syscall_64+0x61/0xb0 [ +0.016095] ? syscall_exit_to_user_mode+0x27/0x50 [ +0.021544] ? __x64_sys_faccessat+0x1c/0x20 [ +0.019347] ? do_syscall_64+0x6e/0xb0 [ +0.016881] entry_SYSCALL_64_after_hwframe+0x44/0xae [ +0.022785] RIP: 0033:0x7f1a4af140a7 [ +0.016084] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ +0.086348] RSP: 002b:7ffd8b2963d8 EFLAGS: 0246 ORIG_RAX: 0001 [ +0.034055] RAX: ffda RBX: 0040 RCX: 7f1a4af140a7 [ +0.032183] RDX: 0001 RSI: 55feb3b47869 RDI: 0004 [ +0.032139] RBP: 7f1a4aff9500 R08: R09: 7ffd8b296380 [ +0.032232] R10: R11: 0246 R12: 0004 [ +0.032338] R13: 7ffd8b2963e0 R14: 55feb3b47869 R15: 0001 [ +0.032799] Modules linked in: ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel rpcrdma kvm sunrpc rdma_ucm rapl intel_cstate ib_iser libiscsi scsi_transport_iscsi efi_pstore rdma_cm ib_umad ib_ipoib iw_cm ib_cm hpilo ioatdma acpi_ipmi ipmi_si acpi_power_meter acpi_tad mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs [ +0.48] blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200
[Bug 1966870] Re: Focal 20.04.4 crashing when using openvswitch/hugepages
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: 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] #PF: error_code(0x0002) - not-present page - [ 1444.478052] PGD 0 P4D 0 + [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul
[Bug 1966870] acpidump.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] WifiSyslog.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] ProcModules.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] UdevDb.txt
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: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] ProcInterrupts.txt
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. https://bugs.launchpad.net/bugs/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] ProcEnviron.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Lsusb-v.txt
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: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] ProcCpuinfo.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Lspci-vt.txt
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 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Lsusb-t.txt
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: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] CurrentDmesg.txt
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. https://bugs.launchpad.net/bugs/1966870 Title: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Lsusb.txt
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: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] Lspci.txt
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: Focal 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966870] [NEW] Focal 20.04.4 crashing when using openvswitch/hugepages
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] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr [ 1445.636951] ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ses enclosure mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops aesni_intel mlx5_core cec ixgbe pci_hyperv_intf crypto_simd xfrm_algo psample nvme cryptd rc_core hpsa mlxfw i2c_i801 dca xhci_pci drm i2c_smbus lpc_ich tg3 tls xhci_pci_renesas nvme_core mdio scsi_transport_sas wmi [ 1446.267521] CR2: 0008 [ 1446.282506] ---[ end trace 99f81ab62ed1f929 ]--- [ 1446.308857] RIP:
[Bug 1966870] CRDA.txt
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 20.04.4 crashing when using openvswitch/hugepages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
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. https://bugs.launchpad.net/bugs/1966237 Title: ldnsutils emits wrong sha256 hashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953363] Re: [MIR] python-xmlschema, elementpath, importlib-resources
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 | stable | source python-xmlschema | 1.10.0-1 | testing| source python-xmlschema | 1.10.0-1 | unstable | source python-xmlschema | 1.4.2-1 | impish/universe | source python-xmlschema | 1.4.2-1 | jammy/universe | source uscan:=> Newer package available from https://github.com/sissaschool/xmlschema/archive/refs/tags/v1.10.0.tar.gz Publishing history indicates there was no major update since January 2021 / Hirsute, so this request is still up. https://launchpad.net/ubuntu/+source/python-xmlschema/+publishinghistory Marking incomplete until updated ** Changed in: python-xmlschema (Ubuntu) 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/1953363 Title: [MIR] python-xmlschema, elementpath, importlib-resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elementpath/+bug/1953363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 pam_vprompt This gets the conversation function via retval = pam_get_item (pamh, PAM_CONV, ); and on that it then emits the message retval = conv->conv (1, , _resp, conv->appdata_ptr); Either via this PAM_CONV and then attributes of that channel (as it is what we'd print on) OR via something like pam_get_item(pamh, PAM_TTY, ); we might get access from pam_motd to something that we can work out if it is interactive. I'm busy with other things now (for the rest of today), but I want ton continue tomorrow. I want this at least to get into a clear state that is sure if: a) this is as important as I think b) the steps needed from here are clear ** Also affects: pam (Ubuntu) Importance: Undecided Status: New ** Changed in: pam (Ubuntu) Status: New => Confirmed ** Changed in: update-motd (Ubuntu) Status: Triaged => Confirmed ** Changed in: pam (Ubuntu) Importance: Undecided => High -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 399071. And updated since a long while to do the very same. Due to this overall situation upstream has no interest/need to fix something, this is IMHO on Ubuntu. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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. 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
The net is full of suggestions e.g. https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch With that: [[ $- == *i* ]] && echo 'Interactive' || echo 'Not interactive' >> /tmp/update-motd-test shopt -q login_shell && echo 'Login shell' || echo 'Not login shell' >> /tmp/update-motd-test In a test like: ssh testuser1@10.253.194.246 "ls ~/" It will detect: Not interactive Not login shell If not in libpam we could clearly use this in the script snippets to fast-pass most of them. Sadly above checks seem trivial I've found that they always report non-interactive/non-login even when being such. It seems the way this is executed prevents proper detection. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
I found this bug while searching for cases forgotten for too long - sorry to all of you. And after reading into the case I feel even worse that it was forgotten so long :-/ I know it is just a config file and one could just remove some of the /etc/update-motd.d files to adapt. Also pam config can be changed. All that will stay true, but I think this is worth improving the default experience a bit. The following is mostly a log of thoughts on the case that I had while re-triaging this: -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
I must re-state that agree one might expect (I did) that on non-interactive shells these motd content would not execute at all. ... but it does ... why? Nowadays this is all from libpam which has pam_mount (man page) and is enabled by default here: root@j:~# grep -Hrn motd /etc/pam* /etc/pam.d/login:31:# This includes a dynamically generated part from /run/motd.dynamic /etc/pam.d/login:32:# and a static (admin-editable) part from /etc/motd. /etc/pam.d/login:33:sessionoptional pam_motd.so motd=/run/motd.dynamic /etc/pam.d/login:34:sessionoptional pam_motd.so noupdate /etc/pam.d/sshd:31:# This includes a dynamically generated part from /run/motd.dynamic /etc/pam.d/sshd:32:# and a static (admin-editable) part from /etc/motd. /etc/pam.d/sshd:33:sessionoptional pam_motd.so motd=/run/motd.dynamic /etc/pam.d/sshd:34:sessionoptional pam_motd.so noupdate Ok on a login shell (/etc/pam.d/login) it makes sense, but on ssh I'd expect (just like the reporter) to be only shown if interactive. At least that is a great place to disable this manually if needed, but sadly disabling this in only /etc/pam.d/sshd also removes it for an ssh-based login shells. So an ssh based login shell will not be configured by /etc/pam.d/login :-/ Pam is trying to outsmart us ... :-/ After all [1] says "... which is displayed by the pam_motd(8) module on interactive shell logins." which should, but isn't true. One can debate if it is good or not in the first place to log in for every command as there will be a lot more every time (e.g. audit entries, syslog entries, the env being spawned, ...), overall this is only one of the things that makes this conceptually wrong. But still I find it embarrassing to see this trivial test to be so bad: $ time for i in $(seq 1 100); do ssh -i /tmp/id-rsa-test testuser1@10.253.194.246 "ls ~"; done - With pam_motd.so enabled in /etc/pam.d/sshd => 0m59,709s - With pam_motd.so disabled in /etc/pam.d/sshd => 16,159s On any cloud or hipervisor that scales a lot not only the expired time but also the cycles will add up to quite a lot. So either way it comes to slowdown as well as unnecessary price or power consumption I'm tempted to suggest a discussion to disable it in /etc/pam.d/sshd unless we find a way to make it only happen on interactive logins. P.S. I have the feeling we had this discussion, maybe others will remember better - I need to talk to a few people ... [1]: http://manpages.ubuntu.com/manpages/bionic/man5/update-motd.5.html ** Tags added: server-todo ** Changed in: update-motd (Ubuntu) Importance: Wishlist => High -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
Slow operations are recommended in motd to use caching and here I think this should be done as well. Just like other operations using slow calls or network they should cache it and only run every few seconds. That will already cut down any mistaken "run on non-interactive" by an order of magnitude and generally it doesn't matter too much for this output if it is current or 5 seconds old as long as it isn't from yesteryear. So even if all else fails this should - as a fallback - help a bit right? -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964285] Re: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build
Hi, the new issue you found is known and being worked on here: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1964923 For what is left here about the off profile-rc.d it seems you no more can reproduce it. If you happen to see/reproduce it again continue to help us solving the open questions (see above). Without those resolved (or a reproducer) I think there is nothing that can be done at the moment. I'll mark this bug incomplete representing that right now we can't continue (and also hope it is fixed as you said 24/mar/2022 works), but please do not hesitate to update and/or re-open if you find more about this. ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964285 Title: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1964285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
FYI - This also seems to affect all Ubuntu Desktop installs on VMware where we got a few reports. I'll redirect people here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965958] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
*** This bug is a duplicate of bug 1964923 *** https://bugs.launchpad.net/bugs/1964923 This is already discussed in bug 1964923 and seems to be worked on by foundations there. Marking this one as a duplicate. ** This bug has been marked a duplicate of bug 1964923 list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965958 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1965958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
nchors.xml which also refers to
"E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D" so
I'm pretty sure our new build of ldns is the bad one here.
[1]:
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jammy-jammy.html#ubuntu-server-team
[2]:
https://launchpadlibrarian.net/591984954/buildlog_ubuntu-jammy-amd64.dns-root-data_2021011101_BUILDING.txt.gz
** Changed in: ldns (Ubuntu Impish)
Status: Confirmed => In Progress
** Changed in: ldns (Ubuntu Impish)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Description changed:
[Impact]
- * When ldns is compiled with gcc11 without a fix for
-strict-aliasing it will silently emit wrong sha256 hashes
+ * When ldns is compiled with gcc11 without a fix for
+ strict-aliasing it will silently emit wrong sha256 hashes
- * This affected Jammy where it was build with GCC11 already
-and a fix was uploaded there.
+ * This affected Jammy where it was build with GCC11 already
+ and a fix was uploaded there.
- * If rebuilt as-is today in Impish it would expose that bad
-behavior. But the build of today is still from hirsute with GCC10.
-Therefore we want to avoid this from ever becoming a problem,
-but at the same time have no reason to push an update all
-the way through.
-The intention is to get this into impish-proposed and stay there
-in case any later fix/security-update comes by it will not
-trigger this problem.
+ * If rebuilt as-is today in Impish it would expose that bad
+ behavior. But the build of today is still from hirsute with GCC10.
+ Therefore we want to avoid this from ever becoming a problem,
+ but at the same time have no reason to push an update all
+ the way through.
+ The intention is to get this into impish-proposed and stay there
+ in case any later fix/security-update comes by it will not
+ trigger this problem.
[Test Plan]
-
$ cat > root.key << EOF
. 86400 IN DNSKEY 257 3 8
AwEAAaz/tAm8yTn4Mfeh5eyI96WSVexTBAvkMgJzkKTOiW1vkIbzxeF3+/4RgWOq7HrxRixHlFlExOLAJr5emLvN7SWXgnLh4+B5xQlNVz8Og8kvArMtNROxVQuCaSnIDdD5LKyWbRd2n9WGe2R8PzgCmr3EgVLrjyBxWezF0jLHwVN8efS3rCj/EWgvIWgb9tarpVUDK/b58Da+sqqls3eNbuv7pr+eoZG+SrDK6nWeL3c6H5Apxz7LjVc1uTIdsIXxuOLYA4/ilBmSVIzuDWfdRUfhHdY6+cn8HFRm+2hM8AnXGXws9555KrUB5qihylGa8subX2Nn6UwNR1AkUTV74bU=
;{id = 20326 (ksk), size = 2048b} ;;state=2 [ VALID ]
EOF
$ ldns-key2ds -n -2 root.key
- . 86400 IN DS 20326 8 2
+ . 86400 IN DS 20326 8 2
wrong result:
0ae721f59a19244008217c3d2a646183acef2f17cf4c30929a3f29d09311c05e
correct result:
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
+ Note: To avoid confusion - once more to be clear - the ldns in impish as
+ of today is ok as it was built with older GCC, to see the bad-behavior
+ you'd need to rebuild it as-is.
[Where problems could occur]
- * If there is another - not yet discovered - issue with GCC11 it would
-pick this one up; But it would do so as well without this fix and
-with it we prevent at least one issue.
+ * If there is another - not yet discovered - issue with GCC11 it would
+ pick this one up; But it would do so as well without this fix and
+ with it we prevent at least one issue.
- * If there was someone building ldns from package source relying on
-strict-aliasing for anything this will now be disabled - but
-intentionally, so IMHO ok.
+ * If there was someone building ldns from package source relying on
+ strict-aliasing for anything this will now be disabled - but
+ intentionally, so IMHO ok.
[Other Info]
-
- * As I mentioned above, this is not meant to migrate to -release,
-we want it in -proposed to avoid a latter issue.
+ * As I mentioned above, this is not meant to migrate to -release,
+ we want it in -proposed to avoid a latter issue.
original bug report
-
Hi,
originally this started by a finding of an FTFBS issue of dns-root-data [1]
as reported in the most recent archive rebuild [2]
But comparing those I've found that it is actually ldns that is broken,
as it seems most likely by openssl3.0 changes.
Separating this from dns-root-data, you can:
$ cat > root.key << EOF
. 86400 IN DNSKEY 257 3 8
AwEAAaz/tAm8yTn4Mfeh5eyI96WSVexTBAvkMgJzkKTOiW1vkIbzxeF3+/4RgWOq7HrxRixHlFlExOLAJr5emLvN7SWXgnLh4+B5xQlNVz8Og8kvArMtNROxVQuCaSnIDdD5LKyWbRd2n9WGe2R8PzgCmr3EgVLrjyBxWezF0jLHwVN8efS3rCj/EWgvIWgb9tarpVUDK/b58Da+sqqls3eNbuv7pr+eoZG+SrDK6nWeL3c6H5Apxz7LjVc1uTIdsIXxuOLYA4/ilBmSVIzuDWfdRUfhHdY6+cn8HFRm+2hM8AnXGXws9555KrUB5qihylGa8subX2Nn6UwNR1AkUTV74bU=
;{id = 20326 (ksk), size = 2048b} ;;state=2 [ VALID ]
EOF
$ ldns-key2ds -n -2 root.key
. 86400 IN DS 20326 8 2
0ae721f59a19244008217c3d2a646183acef2f17cf4c30929a3f29d09311c05e
The problem here is
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
Uploaded to Jammy, once in we can re-check dns-root-data and if all is fine we can consider if/how/when to SRU this. -- 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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
And @SSL3-patches, I beg your pardon - it was GCC11 after all :-) ** Tags removed: transition-openssl3-jj ** Also affects: ldns (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ldns (Ubuntu Jammy) Importance: High Status: New ** Changed in: ldns (Ubuntu Jammy) Status: New => Confirmed ** Changed in: ldns (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: ldns (Ubuntu Impish) Status: New => Confirmed ** Changed in: ldns (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: ldns (Ubuntu Jammy) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- 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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
Build instructions: git clean -xdf git checkout . git submodule update --init libtoolize -ci autoreconf -fi ./configure --disable-rpath --with-examples --with-drill --enable-ed25519 --disable-ldns-config --build=x86_64-linux-gnu --prefix=/usr --includedir=/usr/include --mandir=/usr/share/man --infodir=/usr/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=/usr//lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking make ./examples/ldns-key2ds -n -2 ~/root.key Various builds later (git = from git as above; pkg = re-build the pkg as-is): git 1.7.1@i - bad result git 1.7.1@j - ftbfs openssl pkg 1.7.1@i - bad result pkg 1.7.1@j - bad result git 1.8.1@j - good result Insight: - 1.7.1 in Impish (e.g. on rebuild) is affected by the same issue - old in-archive builld is from hirsute 19 Nov 2020 - Something in 1.8.1 makes this right in jammy - openssl3 breakage blocks most free bisecting git 1.8.1@i - good result git 1.8.0@j - good result Insight: - whatever is in 1.8.x fixes impish as well - 1.8.0 is already good - we might be able to bisect on Impish (no openssl3 block there) Bisect new tag:1.8.0 <-> old tag:release-1.7.1 Identified: - https://github.com/NLnetLabs/ldns/issues/131 - https://github.com/NLnetLabs/ldns/commit/4d2057f0b5220487882be1b19c302833b84cffe3 git 1.7.1@i + cherry pick - good result git 1.8.1@j - revert fix - bad result Insight: - it is actually a gcc-11 issue of ldns - fix can be backported and fixes the issue - fixed in 1.8.0 and later ** Bug watch added: github.com/NLnetLabs/ldns/issues #131 https://github.com/NLnetLabs/ldns/issues/131 -- 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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966319] Re: FTBFS with llvm-14
That llvm v14 is rather recent - we were lucky that llvm-13 worked fine. Officially the most recent postgresql-release just added llvm-12 support [1]. In jammy we have: llvm-13 | 1:13.0.1-2ubuntu2 | jammy/universe | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x llvm-14 | 1:14.0.0-1ubuntu1 | jammy-proposed/universe | amd64, arm64, armhf, i386, ppc64el, s390x I can't see us transitioning completely to llvm-14 in time for jammy, so llvm-13 might stay as well? (ask Foundations please to be sure). If it does stay, this might be as easy as putting a versioned build dep onto `llvm-dev` in d/control of postgresql-14. On the other hand, maybe those are all just deprecation warnings and related follow on issues. Having a test build with [2] might be worth a try. Actually the REL_14_STABLE branch has a combined backport of this and other llvm-14 changes. Those will be released with postgresql-14.3 some day, to fix it right now most likely the best shot would be [3]. And once 14.3 comes by we can drop our delta again. [1]: https://www.postgresql.org/docs/14/release-14.html [2]: https://github.com/postgres/postgres/commit/a56e7b66010f330782243de9e25ac2a6596be0e1 [3]: https://github.com/postgres/postgres/commit/d9f7ad54e552262ee0090e88d5abd3e04fcdeac8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966319 Title: FTBFS with llvm-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1966319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802005] Re: socket is inaccessible for libvirt-dbus
Thanks a lot Martin! For the sake of helping your look into this, the old fix in Ubuntu was [1] part of [2]. The two things one might assume to fail are a) the conditional checks we didn't have before b) the switch from usermod to adduser Let me know what you find and if you need help. [1]: https://git.launchpad.net/~paelzer/ubuntu/+source/libvirt-dbus/commit/?h=lp-1802005-allow-libvirtdbus-to-access-libvirt-GROOVY=afd692dfcdc2ab94b1dd5b7f4854cbda496df57f [2]: https://git.launchpad.net/~paelzer/ubuntu/+source/libvirt-dbus/log/?h=lp-1802005-allow-libvirtdbus-to-access-libvirt-GROOVY ** Tags removed: server-next ** 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/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1802005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
Most likely change: "2020-08-24 Use EVP_sha256 instead of HMAC_Update (for openssl-3.0.0)" From https://github.com/NLnetLabs/ldns/commit/12ab6f7a408cd99e9b43b7db86724c2ee66bc36e That is the latest ssl3 toleration they have upstream (merged in 1.8.0, no updates in 1.8.1), but it seems something in there is wrong. I'll try from git 1.8.1 and our version tomorrow and start looking for a fix from there. -- 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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] Re: ldnsutils emits wrong sha256 hashes
Subscribed Simon who added the openssl3 delta, he might have more context from having worked on so many of these changes. -- 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: https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966237] [NEW] ldnsutils emits wrong sha256 hashes
Public bug reported:
Hi,
originally this started by a finding of an FTFBS issue of dns-root-data [1] as
reported in the most recent archive rebuild [2]
But comparing those I've found that it is actually ldns that is broken,
as it seems most likely by openssl3.0 changes.
Separating this from dns-root-data, you can:
$ cat > root.key << EOF
. 86400 IN DNSKEY 257 3 8
AwEAAaz/tAm8yTn4Mfeh5eyI96WSVexTBAvkMgJzkKTOiW1vkIbzxeF3+/4RgWOq7HrxRixHlFlExOLAJr5emLvN7SWXgnLh4+B5xQlNVz8Og8kvArMtNROxVQuCaSnIDdD5LKyWbRd2n9WGe2R8PzgCmr3EgVLrjyBxWezF0jLHwVN8efS3rCj/EWgvIWgb9tarpVUDK/b58Da+sqqls3eNbuv7pr+eoZG+SrDK6nWeL3c6H5Apxz7LjVc1uTIdsIXxuOLYA4/ilBmSVIzuDWfdRUfhHdY6+cn8HFRm+2hM8AnXGXws9555KrUB5qihylGa8subX2Nn6UwNR1AkUTV74bU=
;{id = 20326 (ksk), size = 2048b} ;;state=2 [ VALID ]
EOF
$ ldns-key2ds -n -2 root.key
. 86400 IN DS 20326 8 2
0ae721f59a19244008217c3d2a646183acef2f17cf4c30929a3f29d09311c05e
The problem here is that this is the wrong hash.
The very same file used to emit:
. 86400 IN DS 20326 8 2
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
And on Impish it still does:
ldnsutils | 1.7.1-2build1 | impish/universe | amd64, arm64,
armhf, ppc64el, riscv64, s390x
ldnsutils | 1.7.1-2ubuntu3| jammy/universe | amd64, arm64,
armhf, ppc64el, riscv64, s390x
The difference between the two builds related to this seem to be the
openssl3.0 changes.
I say it is sha256 explicitly as that is what "-2" selects.
If I run with any of the other hashes jammy/impish still agree which tells me
that the rest of the process is still good.
-1 Use SHA1 as the hash function.
-2 Use SHA256 as the hash function
-4 Use SHA384 as the hash function
root@j:~# /usr/bin/ldns-key2ds -n -1 root.key
. 86400 IN DS 20326 8 1
ae1ea5b974d4c858b740bd03e3ced7ebfcbd1724
root@j:~# /usr/bin/ldns-key2ds -n -4 root.key
. 86400 IN DS 20326 8 4
538f47ba9bb88908e1dc335d6dfd51ca66b4d824192e6e6e210ae8cc18ece46a0f62b9f0d2f88dfc87d4bb8b8aed21cb
root@i:~# /usr/bin/ldns-key2ds -n -1 root.key
. 86400 IN DS 20326 8 1
ae1ea5b974d4c858b740bd03e3ced7ebfcbd1724
root@i:~# /usr/bin/ldns-key2ds -n -4 root.key
. 86400 IN DS 20326 8 4
538f47ba9bb88908e1dc335d6dfd51ca66b4d824192e6e6e210ae8cc18ece46a0f62b9f0d2f88dfc87d4bb8b8aed21cb
The build compares this to a root-anchors.xml from
http://data.iana.org/root-anchors/root-anchors.xml which also refers to
"E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D" so
I'm pretty sure our new build of ldns is the bad one here.
[1]:
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jammy-jammy.html#ubuntu-server-team
[2]:
https://launchpadlibrarian.net/591984954/buildlog_ubuntu-jammy-amd64.dns-root-data_2021011101_BUILDING.txt.gz
** Affects: ldns (Ubuntu)
Importance: High
Status: New
** Tags: server-todo transition-openssl3-jj
** Tags added: server-todo
** Changed in: ldns (Ubuntu)
Importance: Undecided => High
--
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:
https://bugs.launchpad.net/ubuntu/+source/ldns/+bug/1966237/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] Re: systemd ignores RootDirectory option in .service units
This is still present in jammy as debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch If we want to keep this as long as there could be an 18.04 that is like 2028 at least. So AFAIU this bug is actually asking LXD to consider a backport (if possible) to then drop the revert from systemd (all releases). ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Impish) Importance: Undecided Status: New ** No longer affects: lxd (Ubuntu Focal) ** No longer affects: lxd (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966201] Re: ruby3.0 probably needs a provides ruby-rexml
Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966201 Title: ruby3.0 probably needs a provides ruby-rexml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/1966201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966201] [NEW] ruby3.0 probably needs a provides ruby-rexml
Public bug reported: Hi, the archive rebuild [1] identified a bunch of ruby dependency issues. The majority seems to be about ruby-rexml. For example: https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+build/23342118 "Missing build dependencies: ruby-rexml" This particular source package was removed back in the day as libruby provides that now [2]. The old libruby2.7 had root@i:~# apt-cache show libruby3.0 | grep rexml Provides: ... ruby-rexml (= 3.2.3.1) And the code is still in libruby3.0 root@j:~# dpkg -L libruby3.0 | grep rexml /usr/lib/ruby/gems/3.0.0/gems/rexml-3.2.5 And also libruby 3.0 actually has root@j:~# apt-cache show libruby3.0 | grep rexml Provides: ... ruby-rexml (= 3.2.5) But only a provides might not be enough: root@j:~# apt install ruby-rexml Reading package lists... Done Building dependency tree... Done Reading state information... Done Package ruby-rexml is a virtual package provided by: libruby2.7 2.7.4-1ubuntu4 (= 3.2.3.1) libruby3.0 3.0.2-7ubuntu2 (= 3.2.5) You should explicitly select one to install. E: Package 'ruby-rexml' has no installation candidate I'm not entirely sure, do we just also need a replaces ruby-rexml for this - anything else? In any case please have a look to reduce the FTFBS in Jammy before release. [1]: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jammy-jammy.html [2]: https://launchpad.net/ubuntu/+source/ruby-rexml/+publishinghistory ** Affects: ruby3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: server-todo ** 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/1966201 Title: ruby3.0 probably needs a provides ruby-rexml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby3.0/+bug/1966201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887187] Re: [MIR] nftables
Ok, summarizing the change Required: #1 embedded source => Done: security said that is ok for them #2 symbols tracking => Done: resolved and improved via bug 1965464 Recommended: #3 some vague security concerns => Done: did not come up in the security review #4 does not have a test suite that runs at build time, please try to enable some tests at build time. We're good for now, though, as we have automated autopkgtests => Open: but not blocking #5 The distutils package is deprecated => Thanks seth for the pointer, that is ok then as it will be resolved and should be ok a future merge. Overall, we are good to go now. There is nothing in seeds or dependency yet, that would be up to you (?Steve B.?) to update. Once done it would show up in component mismatches and we can promote it. Assigning it back to you to be clear. P.S. are there any follow on actions in packages using iptables to switch over, if so could they be filed as bugs? ** Changed in: nftables (Ubuntu) Status: Incomplete => In Progress ** Changed in: nftables (Ubuntu) Assignee: (unassigned) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887187 Title: [MIR] nftables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1887187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
https://launchpad.net/ubuntu/+source/nftables/1.0.2-1ubuntu2 migrated to Jammy-release And in additon the Debian PR was merged. LGTM, let us focus on what is left in the MIR bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965676] Re: virt-manager looses connection to virtualization hosts at moderate loads
Hi Thomas, on one hand let me ask a few questions (below) as the report as-is can't really be acted on. on the other hand - even then - this is a topic that does not sound like an Ubuntu specific problem or fix and therefore more likely will be successful if deiscussed upstream (https://github.com/virt-manager/virt-manager/issues). If you happen to file a case there please let us know so that we can track it from here. If there is a fix coming out of it this will help to fix/backport it to Ubuntu afterwards. Ok, after that being said let me start with the obvious questions. 1. You use v3.2 right now, have you seen the same with former (e.g. 2.2.1 in Focal) or later (4.0 in Jammy) versions as well? 2. What exactly is "moderate load" in your case? 3. could you come up with a step by step reproduction based on clean systems? For example take two Ubuntu VMs version X, sized with that many CPU/Mem connected to the same virtual network via Y. Then run a KVM guest on one like Z, connect to it from the other system. Then run the net-workload X on the host to simulate the load. 4. what error messages do you get exactly? Are they always the same? ** Changed in: virt-manager (Ubuntu) Status: New => Incomplete ** Tags added: need-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965676 Title: virt-manager looses connection to virtualization hosts at moderate loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1965676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966085] Re: cloud-init status --wait never returns if datasource not found
Backports to Ubuntu releases started for Jammy at https://github.com/canonical/cloud-init/pull/1350 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966085 Title: cloud-init status --wait never returns if datasource not found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1966085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966004] Re: Logo refresh
** Tags added: server-todo ** Changed in: apache2 (Ubuntu) Status: New => In Progress ** Changed in: apache2 (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966004 Title: Logo refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1966004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
FYI the requested security fixes (see above), the apparmor hardening (bug 1950631) and the update to 0.6.3 to stabilize all just migrated to jammy-release (=> https://launchpad.net/ubuntu/+source/swtpm/0.6.3-0ubuntu1). We should be back to "just" waiting for the security review and hopefully no major findings. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
FYI: new version started to build in Jammy https://launchpad.net/ubuntu/+source/nftables/1.0.2-1ubuntu2 Updated the Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007888 Provided a matching salsa PR for Debian https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
Thanks for the feedback, uploaded to Jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964686] Re: Command "host non-existent-host-name" hangs forever in Ubuntu jammy
** Changed in: bind9 (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964686 Title: Command "host non-existent-host-name" hangs forever in Ubuntu jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1964686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965521] Re: named.service starts too early: Unable to fetch DNSKEY set '.': failure
** Tags removed: server-triage-discuss ** Tags added: network-online-ordering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965521 Title: named.service starts too early: Unable to fetch DNSKEY set '.': failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1965521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966085] Re: cloud-init status --wait never returns if datasource not found
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu) 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/1966085 Title: cloud-init status --wait never returns if datasource not found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1966085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
@Steve After Seth asked me to have a look (see above comments) I tried to help as much as possible, therefore there now is: - a MR https://code.launchpad.net/~paelzer/ubuntu/+source/nftables/+git/nftables/+merge/417523 - PPA https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4811/+packages for you. I hope this helps you to quickly and easily resolve this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
Applying both changes seems to work fine for me and does not break due to LTO. I'll polish this for you to consider a follow-on upload ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965973] Re: Remove mini-buildd from jammy temporarily to allow Django transiton
Reminder: Please do continue trying to get mini-buildd fixed in a way to work in Jammy and get it uploaded before release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965973 Title: Remove mini-buildd from jammy temporarily to allow Django transiton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965973] Re: Remove mini-buildd from jammy temporarily to allow Django transiton
I think this request is reasonable and added a few more details to the description. After checking with Doko to be sure I agree and will remove this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965973 Title: Remove mini-buildd from jammy temporarily to allow Django transiton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965973] Re: Remove mini-buildd from jammy temporarily to allow Django transiton
Removing packages from jammy: mini-buildd 1.1.19 in jammy mini-buildd 1.1.19 in jammy amd64 mini-buildd 1.1.19 in jammy arm64 mini-buildd 1.1.19 in jammy armhf mini-buildd 1.1.19 in jammy i386 mini-buildd 1.1.19 in jammy ppc64el mini-buildd 1.1.19 in jammy riscv64 mini-buildd 1.1.19 in jammy s390x mini-buildd-doc 1.1.19 in jammy amd64 mini-buildd-doc 1.1.19 in jammy arm64 mini-buildd-doc 1.1.19 in jammy armhf mini-buildd-doc 1.1.19 in jammy i386 mini-buildd-doc 1.1.19 in jammy ppc64el mini-buildd-doc 1.1.19 in jammy riscv64 mini-buildd-doc 1.1.19 in jammy s390x mini-buildd-utils 1.1.19 in jammy amd64 mini-buildd-utils 1.1.19 in jammy arm64 mini-buildd-utils 1.1.19 in jammy armhf mini-buildd-utils 1.1.19 in jammy i386 mini-buildd-utils 1.1.19 in jammy ppc64el mini-buildd-utils 1.1.19 in jammy riscv64 mini-buildd-utils 1.1.19 in jammy s390x python3-mini-buildd 1.1.19 in jammy amd64 python3-mini-buildd 1.1.19 in jammy arm64 python3-mini-buildd 1.1.19 in jammy armhf python3-mini-buildd 1.1.19 in jammy i386 python3-mini-buildd 1.1.19 in jammy ppc64el python3-mini-buildd 1.1.19 in jammy riscv64 python3-mini-buildd 1.1.19 in jammy s390x Comment: Python2 dependency (1.0.x) or broken (>=1.1.x) and blocking python-django (LP: #1965973) Remove [y|N]? y 1 package successfully removed. ** Changed in: mini-buildd (Ubuntu) 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/1965973 Title: Remove mini-buildd from jammy temporarily to allow Django transiton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965973] Re: Remove mini-buildd from jammy temporarily to allow Django transiton
** Description changed: The Django 3.2 transition is currently being blocked in proposed by mini-buildd because it is severely outdated. mini-buildd's current version in Jammy is 1.1.19, which is an old experimental version. The two options to fix this would either be to move it back to stable (1.0.49) - which would need a full python3 transition, or move it up to the newest experimental version in Debian (1.9.98) - which has some runtime errors. Unfortunately both options are non-trivial and will take time to fix, so it may be best to remove the package for now and re-add it once it is updated and working. The original bug report for this is located here: https://pad.lv/1965724 There are no reverse dependencies of mini-buildd + $ reverse-depends --release jammy src:mini-buildd + No reverse dependencies found + Related similar struggles in Debian - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933751 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965973 Title: Remove mini-buildd from jammy temporarily to allow Django transiton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965973] Re: Remove mini-buildd from jammy temporarily to allow Django transiton
** Description changed: The Django 3.2 transition is currently being blocked in proposed by mini-buildd because it is severely outdated. mini-buildd's current version in Jammy is 1.1.19, which is an old experimental version. The two options to fix this would either be to move it back to stable (1.0.49) - which would need a full python3 transition, or move it up to the newest experimental version in Debian (1.9.98) - which has some runtime errors. Unfortunately both options are non-trivial and will take time to fix, so it may be best to remove the package for now and re-add it once it is updated and working. The original bug report for this is located here: https://pad.lv/1965724 There are no reverse dependencies of mini-buildd + + Related similar struggles in Debian + - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933751 + - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965973 Title: Remove mini-buildd from jammy temporarily to allow Django transiton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mini-buildd/+bug/1965973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
At the moment you are kind of getting around the "wrong symbols" by not using the map (missing 1d507ce7f1d) and thereby not using the wrong symbols (nft_set_optimize/nft_get_optimize). But that explains (as you already know and said above) why it is all @base. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965464] Re: add debian symbols tracking for libnftables1 package
@Steve - don't you also need http://git.netfilter.org/nftables/commit/?id=e98a9b83cd52c7c75bedb3dad46539b197ed17ba ? And then an updated symbols file for it? As well as http://git.netfilter.org/nftables/commit/?id=1d507ce7f1d3c12481ee24bd1dcac2fc1984ee9f actually. You said you tried, but what exactly is the LTO issue and other than trying to resolve it you can (until resolved) always consider disabling LTO per package. AFAICS that is also what holds back the Debian contribution of the same change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965464 Title: add debian symbols tracking for libnftables1 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1965464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950631] Re: [FFe] wrap swtpm in an apparmor profile
FYI - Fixup uploaded as part of 0.6.3-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950631 Title: [FFe] wrap swtpm in an apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1950631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
FYI - I got positive feedback for my MR and in general from Foundations, I'll upload this to Jammy now. This will address bug 1950631, the security request by sarnold and a general stabilization update. => 0.6.3-0ubuntu1 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965090] Re: [FFe] updated needrestart (form git) for Jammy
Got a Team ack on MM, uploading this now ... Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading needrestart_3.5-5ubuntu2.dsc: done. Uploading needrestart_3.5-5ubuntu2.debian.tar.xz: done. Uploading needrestart_3.5-5ubuntu2_source.buildinfo: done. Uploading needrestart_3.5-5ubuntu2_source.changes: done. Successfully uploaded packages. ** Changed in: needrestart (Ubuntu) Status: Confirmed => 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/1965090 Title: [FFe] updated needrestart (form git) for Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1965090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964600] Re: [MIR] gnome-bluetooth3
** Changed in: gnome-bluetooth3 (Ubuntu) Assignee: Ioanna Alifieraki (joalif) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964600 Title: [MIR] gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964285] Re: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build
Thanks for outlining your steps in detail. In my former tests I did use "minimal" instead of "normal" and did not yet purge+install open-vm-tools. Let me try exactly yours to be closer to your case... 1. I get the ISO from https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-amd64.iso 1.1 as I said before, policy-rc.d isn't on the image 2. Create VM in ESXi 2.1 for me vmware player 3. Install guest OS with this image jammy-desktop-amd64.iso in "normal" mode. 3.1 do you keep the "download updates while installing" option enabled? 4. reboot after finished installation 4.1 /usr/sbin/policy-rc.d wasn't present in my case 5. login system, type "apt-get update" in terminal 5.1 /usr/sbin/policy-rc.d wasn't present in my case yet 6. input "apt-get purge open-vm-tools" in terminal 6.1 /usr/sbin/policy-rc.d wasn't present in my case yet 6.2 BTW since ubuntu-desktop meta package depends on it that is removed as well which is generally bad 7. input "apt-get install open-vm-tools" in terminal 7.1 /usr/sbin/policy-rc.d wasn't present in my case yet - all worked fine 7.2 FYI, that does not re-install ubuntu-desktop nor open-vm-tools-desktop, but that isn't the problem here So in neither of these steps I see policy-rc.d present on the system, it needs to come from somewhere for you. Could you please check the following to allow us to get closer to where this comes from in your case? a) You could check just after reboot at #4 - if in your case policy-rc.d is there already we can ignore any latter stages for now. b) maybe it is ESXi or a configuration in your particular current ESXi? I do not have an ESXi available at the moment to compare, could you on your side try the same on an VMWare player and if possible on a new unmodified ESXi? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964285 Title: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1964285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940029] Re: Default of fcf-protection should only be enabled where it can work
Re-ping again, this is breaking all (well there aren't too many) 486 compiles. -- 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: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1940029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950321] Re: [MIR] glusterfs
Just to state it also here and not just in meetings and calls, this is urgent and important for Jammy, so as much asap as you can manage to complete this is appreciated :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950321 Title: [MIR] glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950631] Re: [FFe] wrap swtpm in an apparmor profile
It is all ready for review and tested in https://code.launchpad.net/~paelzer/ubuntu/+source/swtpm/+git/swtpm/+merge/417221 already. No need to act other than reviewing this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950631 Title: [FFe] wrap swtpm in an apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1950631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
I have prepared the changes requested by Seth, stable fixes and an apparmor/test fix. Can be reviewed here: => https://code.launchpad.net/~paelzer/ubuntu/+source/swtpm/+git/swtpm/+merge/417221 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950631] Re: [FFe] wrap swtpm in an apparmor profile
Now things pass locally, running the same on infra over lunch to see if it is good there as well. Testsuite summary for swtpm 0.6.3 # TOTAL: 58 # PASS: 50 # SKIP: 8 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 make[3]: Leaving directory '/tmp/autopkgtest.GhwPFN/build.2Yo/src/tests' make[2]: Leaving directory '/tmp/autopkgtest.GhwPFN/build.2Yo/src/tests' make[1]: Leaving directory '/tmp/autopkgtest.GhwPFN/build.2Yo/src/tests' make[1]: Entering directory '/tmp/autopkgtest.GhwPFN/build.2Yo/src' make[1]: Leaving directory '/tmp/autopkgtest.GhwPFN/build.2Yo/src' autopkgtest [12:52:59]: test run-tests: ---] autopkgtest [12:53:00]: test run-tests: - - - - - - - - - - results - - - - - - - - - - run-testsPASS autopkgtest [12:53:00]: - - - - - - - - - - running shell - - - - - - - - - - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950631 Title: [FFe] wrap swtpm in an apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1950631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression
Same error with kernel 5.13.0-37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960018 Title: Boot Failure - linux-image-5.13.0-28-generic | regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950631] Re: [FFe] wrap swtpm in an apparmor profile
Test stuck here:
4 0 356 1 20 0 2888 1716 - Ss hvc1 0:00 /bin/sh
1 03081 356 20 0 2888 140 - S+ hvc1 0:00 \_
/bin/sh
4 030823081 20 0 10192 4268 - S+ hvc1 0:00
\_ su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile
>/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.y9SOlW/build.P79/src"; mkdir -
4 100030913082 20 0 7892 3844 do_wai Ss ? 0:00
\_ bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.y9SOlW/build.P79/src"; mkdir -p -m 1777 -- "
0 100030993091 20 0 2888 1000 do_wai S? 0:00
\_ /bin/sh /tmp/autopkgtest.y9SOlW/build.P79/src/debian/tests/run-tests
1 100031003099 20 0 7892 1756 do_wai S? 0:00
\_ bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null
2>&1 || true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.y9SOlW/build.P79/src"; mkdir -p -m 1
0 100031043100 20 0 6192 1024 pipe_r S? 0:00
| \_ tee -a /tmp/autopkgtest.y9SOlW/run-tests-stderr
1 100031013099 20 0 7892 1672 do_wai S? 0:00
\_ bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null
2>&1 || true; . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.y9SOlW/build.P79/src"; mkdir -p -m 1
0 100031033101 20 0 6192 1016 pipe_r S? 0:00
| \_ tee -a /tmp/autopkgtest.y9SOlW/run-tests-stdout
0 100060383099 20 0 6676 2484 do_wai S? 0:00
\_ make -j4 check VERBOSE=1
0 100060396038 20 0 7760 3388 do_wai S? 0:00
\_ /bin/bash -c fail=; \ if (target_option=k; case
${target_option-} in ?) ;; *) echo "am__make_running_with_option: internal
error: invalid" "target option '${target_option-}' spe
1 100070816039 20 0 7760 1988 do_wai S? 0:00
\_ /bin/bash -c fail=; \ if (target_option=k; case
${target_option-} in ?) ;; *) echo "am__make_running_with_option: internal
error: invalid" "target option '${target_option-}'
0 100070827081 20 0 6684 2676 do_wai S? 0:00
\_ make check
0 100070867082 20 0 6684 2696 do_wai S? 0:00
\_ make check-TESTS
0 100070947086 20 0 7760 3344 do_wai S? 0:00
\_ /bin/bash -c set +e;
bases='test_vtpm_proxy.log test_tpm2_vtpm_proxy.log test_ctrlchannel2.log
test_ctrlchannel4.log test_tpm2_ctrlchannel2.log test_commandline.
0 100071037094 20 0 6908 2892 do_wai S? 0:00
\_ make test-suite.log
TEST_LOGS=test_vtpm_proxy.log test_tpm2_vtpm_proxy.log test_ctrlchannel2.log
test_ctrlchannel4.log test_tpm2_ctrlchannel2.log test_comman
0 100071417103 20 0 7764 3264 do_wai S? 0:00
\_ /bin/bash ../test-driver --test-name
test_commandline --log-file test_commandline.log --trs-file
test_commandline.trs --color-tests no --enable-hard-erro
0 100071637141 20 0 8160 4012 pipe_r S? 0:00
| \_ bash ./test_commandline
0 100076137163 20 0 17092 9184 skb_wa S? 0:00
| \_ python3
/tmp/autopkgtest.y9SOlW/build.P79/src/tests/test_clientfds.py
0 100076267613 20 0 8532 2348 do_pol S? 0:00
| \_ /usr/bin/swtpm socket
--fd=3 --ctrl type=unixio,clientfd=5 --pid file=/tmp/tmp.jkBt3n3qVc/swtpm.pid
--tpmstate dir=/tmp/tmp.jkBt3n3qVc --secc
0 100074067103 20 0 7764 3268 do_wai S? 0:00
\_ /bin/bash ../test-driver --test-name
test_ctrlchannel3 --log-file test_ctrlchannel3.log --trs-file
test_ctrlchannel3.trs --color-tests no --enable-hard-e
0 100074257406 20 0 8168 3940 pipe_r S? 0:00
\_ bash ./test_ctrlchannel3
0 100074447425 20 0 9220 6640 do_pol S? 0:00
\_ /usr/bin/swtpm socket --flags
not-need-init --ctrl type=unixio,path=/tmp/tmp.6u48xQf27g/sock --tpmstate
dir=/tmp/tmp.6u48xQf27g -t --pid file=/tm
0 100074867425 20 0 17092 9252 skb_wa S? 0:00
\_ python3
[Bug 1950631] Re: [FFe] wrap swtpm in an apparmor profile
FYI this is blocked in proposed failing its autopkgtests. This is reproducible in Ubuntu infra as well as locally in VM. I'll try to extend the rules as needed and will let you know what i found eventually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950631 Title: [FFe] wrap swtpm in an apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1950631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965523] Re: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them
Thanks for the confirmation, sorry for it to happen in the first place. Would I have been aware of the backport of the broken debhelper it could have been prevented. I'll drop the delta on next major merge after rechecking if debhelper is fixed then. Until then I'm marking this fix released. ** Changed in: libvirt (Ubuntu) Status: New => Fix Released ** 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/1965523 Title: Server Team Backports PPA: latest upgrades to libvirt shuts down domains without restarting them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1965523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948748] Re: [MIR] swtpm
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4809 The former test-hang that affects current proposed migration is still present. I'll debug that -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autogen/+bug/1948748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964285] Re: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build
** Attachment added: "showing vmware player install without the reported issue" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1964285/+attachment/5571721/+files/vm-jammy-no-policyrc.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964285 Title: hit message "invoke-rc.d: policy-rc.d denied execution of stop" when uninstall open-vm-tools in ubuntu desktop 22.04 daily build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1964285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
