Description of problem: dnfdragora-updater does not respond when any of the menu items is selected, including "Exit". Version-Release number of selected component (if applicable): dnfdragora-updater-2.1.5-7.fc41.noarch dnfdragora-2.1.5-7.fc41.noarch Tested with F41 Xfce in a VM. How reproducible: Always. Steps to Reproduce: 1. Enable dnfdragora-updater autostart in Xfce settings. 2. Logout and login. 3. Select a dnfdragora-updater menu item, such as "Exit". Actual results: No response. Expected results: dnfdragora-updater exits. Additional info:
Proposed as an F41BetaFreezeException, because dnfdragora-updater appears in the Xfce menu bar, where users will expect it to actually do something.
We signed off the Beta for release today, so nothing can be an FE any more. Is this a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2310097 ?
(In reply to Adam Williamson from comment #2) > We signed off the Beta for release today, so nothing can be an FE any more. > > Is this a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2310097 ? Not a dupe. I was testing the update that fixes Bug 2310097: dnfdragora-2.1.5-7.fc41 https://bodhi.fedoraproject.org/updates/FEDORA-2024-de10fa25cc NB: There are *two* progs: dnfdragora: Bug 2310097 is for the startup failure, and it is fixed. dnfdragora-updater: This appears in the Xfce menu bar, and this bug is for non-responsive menu items.
(In reply to Steve from comment #3) > dnfdragora-updater: This appears in the Xfce menu bar, and this bug is for non-responsive menu items. For F41 Beta there will need to be a common bugs note for that. The workaround is to start dnfdragora-updater from the Xfce Applications:System menu. That has the side-effect of displaying a *second* dnfdragora-updater icon in the menu bar. The menu under that second instance is functional. Tested with F41 Xfce in a VM.
I tried again, and now the dnfdragora-updater menu is working consistently. The controlling factor appears to be whether or not this file exists when dnfdragora-updater starts: ~/.config/dnfdragora.yaml No dnfdragora.yaml: Non-responsive menu. dnfdragora.yaml exists: Menu works as expected. Running the fixed version of dnfdragora once from the Xfce Applications:System menu is sufficient to create dnfdragora.yaml. Debugging tip: Run this command between test runs if the dnfdragora-updater menu is non-responsive: $ pkill dnfdragora-upda # The name is required to be no longer than 15 characters, hence the truncation. That saves the time for logging out and logging in. Ian: Thanks for pointing out the significance of dnfdragora.yaml in Bug 2310097, Comment 0. I never would have thought to look for it otherwise.
That means the updater won't work after a fresh install which is a bit of a shame. On upgrades, in the past, old versions of the file have been known to upset newer versions dnfdragora and cause it to crash, so as a matter of course I delete the ~/.config/dnfdragora.yaml file and get dnfdragora to recreate it. As I typically get rid of the updater and have only dnfdragora on the system I would not have noticed this issue before, it may not be a new issue.
Fedora-Xfce-Live-x86_64-41_Beta-1.2.iso is available for testing here: https://kojipkgs.fedoraproject.org/compose/41/latest-Fedora-41/compose/Spins/x86_64/iso/ For a smoke test, this works: $ qemu-kvm -m 12G -cdrom Fedora-Xfce-Live-x86_64-41_Beta-1.2.iso Xfce can run with much less memory, but if updates are installed while running the Live image, that can consume a lot of memory. I don't use dnfdragora-updater either, so I am not sure what the expected behavior is. However, dnfdragora-updater doesn't appear in the menu bar at first boot. Perhaps it only appears when there are updates.
(In reply to Steve from comment #7) > However, dnfdragora-updater doesn't appear in the menu bar at first boot. Perhaps it only appears when there are updates. In the Live session, dnfdragora-updater doesn't appear in the menu bar at first boot. In an installed session, dnfdragora-updater does appear in the menu bar. And whether or not it starts after logging in is configurable under: Applications:Settings:Session and Startup:Application Autostart. See, also, dnfdragora:Options:User preferences for an option to hide dnfdragora-update if there are no updates.
We take some steps to intentionally hide update-related things in live environments, because we don't typically want people to try and do a full system update on a live image. Unless you have a lot of memory it'll probably exhaust it and lock the system up.
(In reply to Adam Williamson from comment #9) Thanks for the clarification.
Duplicated by #bug2334881 To fix it, I had to delete/rename ~/.config/dnfdragora.yaml, and start dnfdragora (not dnfdragora-updater) once.