I upgraded to F41 yesterday, and everything seemed to go smoothly. However a subsequent run of "dnf upgrade" updated firefox, but didn't tell me to restart it. Since I didn't notice this I kept using the (now outdated) Firefox that was already running, until FF suddenly told me it wanted to restart. This has never happened before.
AFAIK the tracer plugin is installed:
python3-dnf-plugin-tracer-4.1.2-3.fc41.noarch
Could this be a problem with dnf5?
poc
On 31 Oct 2024, at 12:07, Patrick O'Callaghan pocallaghan@gmail.com 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.
The dnf5 docs say there are some plugins https://dnf5.readthedocs.io/en/latest/dnf5_plugins/index.html implemented.
Barry
On Fri, 2024-11-01 at 09:25 +0000, Barry wrote:
On 31 Oct 2024, at 12:07, Patrick O'Callaghan pocallaghan@gmail.com 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.
poc
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@gmail.com 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
On Fri, 2024-11-01 at 23:22 +0000, Patrick O'Callaghan wrote:
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@gmail.com 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.
[...]
A fix for tracer is available. Feel free to text and comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f48f5d71c7
poc
On 13/11/24 22:24, Patrick O'Callaghan wrote:
On Fri, 2024-11-01 at 23:22 +0000, Patrick O'Callaghan wrote:
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'Callaghanpocallaghan@gmail.com 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 pluginshttps://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.
[...]
A fix for tracer is available. Feel free to text and comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f48f5d71c7
The command listed here failed for me because of name resolution errors on all the mirrors configured for dnf. It might be because I'm playing around with Cosmic Desktop, but I wouldn't have thought so. I'll try again under KDE.
regards, Steve
poc
On Thu, 2024-11-14 at 08:22 +1100, Stephen Morris wrote:
On 13/11/24 22:24, Patrick O'Callaghan wrote:
On Fri, 2024-11-01 at 23:22 +0000, Patrick O'Callaghan wrote:
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'Callaghanpocallaghan@gmail.com 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 pluginshttps://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.
[...]
A fix for tracer is available. Feel free to text and comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f48f5d71c7
The command listed here failed for me because of name resolution errors on all the mirrors configured for dnf. It might be because I'm playing around with Cosmic Desktop, but I wouldn't have thought so. I'll try again under KDE.
Try this:
sudo dnf --enablerepo=updates-testing update tracer
poc
On 14/11/24 09:30, Patrick O'Callaghan wrote:
Try this:
sudo dnf --enablerepo=updates-testing update tracer
I ran that command and it updated python3-tracer and tracer-common to 1.2 (the command in the link you provided did nothing for me) and it also updated python3-libdnf5
After the update I ran tracer -vv and it gave me messages about needing a restart with a list of processes, then a list of processes that needed manual restarting, then a message about there being 6 processes that needed a session restart and 1 process that required a reboot, and then gave me a traceback because of permission issues because I didn't run the command under sudo (it got a permission failure on /run/reboot-required).
regards, Steve
On Fri, 2024-11-15 at 09:17 +1100, Stephen Morris wrote:
On 14/11/24 09:30, Patrick O'Callaghan wrote:
Try this:
sudo dnf --enablerepo=updates-testing update tracer
I ran that command and it updated python3-tracer and tracer-common to 1.2 (the command in the link you provided did nothing for me) and it also updated python3-libdnf5 After the update I ran tracer -vv and it gave me messages about needing a restart with a list of processes, then a list of processes that needed manual restarting, then a message about there being 6 processes that needed a session restart and 1 process that required a reboot, and then gave me a traceback because of permission issues because I didn't run the command under sudo (it got a permission failure on /run/reboot-required).
That all seems correct. I normally run it as 'sudo tracer -a'.
poc
On 15/11/24 21:28, Patrick O'Callaghan wrote:
That all seems correct. I normally run it as 'sudo tracer -a'.
I was not surprised that I got the traceback when not running it under sudo. When I did that it said there were two processes that required a reboot, so my query on that (which possibly can't be resolved) is what was the process that didn't require sudo for it to determine it needed a reboot, and that did not require running /run/reboot-required to make the determination.
regards, Steve
On 13/11/24 22:24, Patrick O'Callaghan wrote:
On Fri, 2024-11-01 at 23:22 +0000, Patrick O'Callaghan wrote:
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'Callaghanpocallaghan@gmail.com 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 pluginshttps://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.
[...]
A fix for tracer is available. Feel free to text and comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f48f5d71c7
Having tried this under Cosmic Desktop and that getting name failures on all the mirrors, with DNF not exiting after the failures and having to use ctrl-c to exit dnf, I logged out to SDDM and then logged into KDE. I reran the command and after refreshing the repositories DNF did not proceed any further, it just sat there thrashing my hard disks and locked my system out. I had to use the hardware reset to get out of that state. After rebooting the machine I logged into KDE and ran the command again and this time after refreshing the repositories it sat there for a while then said there was nothing to do. How do I know if the updated version is actually installed?
regards, Steve
poc
-
Barry -
Patrick O'Callaghan -
Stephen Morris