<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">I opened this bug: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1919538" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1919538</a></div><div class=""><br class=""></div><div class="">I'd love to know if there is a work around until you have time to make a fix.</div><div class=""><br class=""></div><div class="">Barry</div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 16 Jan 2021, at 15:42, Barry Scott <<a href="mailto:barry@barrys-emacs.org" class="">barry@barrys-emacs.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I have a reproducible problem with systemd-ask-password.<br class=""><br class=""># rpm -q systemd<br class="">systemd-246.7-2.fc33.x86_64<br class=""><br class="">1. boot fedora 33<br class="">2. login to KDE<br class="">3. start a terminal and run top<br class="">4. start a terminal and run:<br class=""> systemctl >before<br class=""> systemd-ask-password 'testing: ' </dev/null >p<br class="">5. Observe that top is showing systemd using ~80% CPU<br class="">6. stop systemd-ask-password and CPU returns to idle<br class=""> systemctl >after<br class="">7. Check journal:<br class=""><br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">Jan 16 15:18:19 vmf33.chelsea.private systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped.<br class="">etc...<br class=""><br class=""># journalctl -b | grep Condition | wc -l<br class="">37555<br class=""><br class="">8. run again:<br class=""> systemd-ask-password 'testing: ' </dev/null >p<br class="">9. messgae sent to all terminals:<br class="">Broadcast message from <a href="mailto:root@vmf33.chelsea.private" class="">root@vmf33.chelsea.private</a> (Sat 2021-01-16 15:28:02 GMT):<br class=""><br class="">Password entry required for 'testing:' (PID 1862).<br class="">Please enter password with the systemd-tty-ask-password-agent tool.<br class=""><br class="">-----<br class=""><br class="">Looking at the services before and after running systemd-ask-password once I see this diff:<br class=""><br class=""># diff -u before after | grep '^[-+]'<br class="">--- before 2021-01-16 15:35:51.850438282 +0000<br class="">+++ after 2021-01-16 15:36:08.875736785 +0000<br class="">- systemd-ask-password-plymouth.path loaded active waiting Forward Password Requests to Plymouth Directory Watch <br class="">- systemd-ask-password-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch <br class="">+ systemd-ask-password-wall.path loaded active running Forward Password Requests to Wall Directory Watch <br class="">- fprintd.service loaded active running Fingerprint Authentication Daemon <br class="">+ systemd-ask-password-wall.service loaded active running Forward Password Requests to Wall <br class="">-196 loaded units listed. Pass --all to see loaded but inactive units, too.<br class="">+195 loaded units listed. Pass --all to see loaded but inactive units, too.<br class=""><br class="">I am seeing this behaviour on two systems. A dell laptop and a VMware VM.<br class=""><br class="">Is there anything I can do to help debug this?<br class="">Or just raise a big report?<br class=""><br class="">What work around would you suggest I use until this is fixed?<br class=""><br class="">Barry<br class=""><br class="">_______________________________________________<br class="">systemd-devel mailing list<br class=""><a href="mailto:systemd-devel@lists.freedesktop.org" class="">systemd-devel@lists.freedesktop.org</a><br class="">https://lists.freedesktop.org/mailman/listinfo/systemd-devel<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>