Tracer is broken - was: Is the dnf tracer plugin working?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2024-11-01 at 11:26 +0000, Patrick O'Callaghan wrote:
> On Fri, 2024-11-01 at 09:25 +0000, Barry wrote:
> > 
> > > On 31 Oct 2024, at 12:07, Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote:
> > > 
> > > AFAIK the tracer plugin is installed:
> > > 
> > > python3-dnf-plugin-tracer-4.1.2-3.fc41.noarch
> > 
> > The python plugins don’t work in the C++ dnf5.
> > 
> > 
> 
> It's a pity there was no warning of this when the system was updated.
> 
> > The dnf5 docs say there are some plugins https://dnf5.readthedocs.io/en/latest/dnf5_plugins/index.html implemented.
> 
> That only works for reboot. It doesn't work for updates to the DE. In
> fact even 'sudo tracer -a' doesn't work.
> 
> This is a significant regression in my view.

After a recent run of 'dnf upgrade':

$ sudo tracer -a
$

*BUT*

$ dnf5 needs-restarting -s
Updating and loading repositories:
 Fedora 41 - x86_64 - Updates                                         
100% |  12.3 MiB/s |  13.4 MiB |  00m01s
Repositories loaded.
ModemManager.service
NetworkManager-wait-online.service
abrtd.service
abrt-journal-core.service
abrt-oops.service
abrt-xorg.service
accounts-daemon.service
alsa-state.service
atd.service
avahi-daemon.service
bluetooth.service
chronyd.service
colord.service
cups.service
dracut-shutdown.service
fail2ban.service
firewalld.service
gssproxy.service
irqbalance.service
lactd.service
lm_sensors.service
lvm2-monitor.service
rpc-statd-notify.service
nordvpnd.service
pcscd.service
php-fpm.service
plymouth-quit.service
polkit.service
rsyslog.service
rtkit-daemon.service
sddm.service
smartd.service
switcheroo-control.service
sysstat.service
systemd-machined.service
systemd-resolved.service
kmod-static-nodes.service
tuned.service
tuned-ppd.service
udisks2.service
upower.service
uresourced.service
wpa_supplicant.service
$

poc

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux