Description of problem: Launching from terminal, I get lot of: /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1530 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1532 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1534 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) ... but finally: /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1573 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1575 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) Unexpected error: <class 'KeyError'> <_M_> [ui] YUILoader.cc:163 deleteUI(): Shutting down UI <_M_> [ew] YExternalWidgets.cc:116 ~YExternalWidgetsTerminator(): Shutting down mga External Widgets <_M_> [ew] YMGAWidgetExtensionFactory.cc:49 ~YMGAWidgetFactory(): Factory removed [paul@localhost ~]$ Version-Release number of selected component (if applicable): [paul@localhost ~]$ dnf repoquery --installed|grep dnfdragora dnfdragora-0:2.0.0-2.fc32.noarch dnfdragora-updater-0:2.0.0-2.fc32.noarch [paul@localhost ~]$ How reproducible: Tried 2 times in a row
Might want to know the update available when it was happening: [paul@localhost log]$ sudo dnf check-update [sudo] Mot de passe de paul : Dernière vérification de l’expiration des métadonnées effectuée il y a 0:03:01 le dim 12 avr 2020 09:10:22. cmake.x86_64 3.17.1-1.fc32 updates-testing cmake-data.noarch 3.17.1-1.fc32 updates-testing cmake-filesystem.x86_64 3.17.1-1.fc32 updates-testing cmake-rpm-macros.noarch 3.17.1-1.fc32 updates-testing container-selinux.noarch 2:2.131.0-1.fc32 updates-testing containers-common.x86_64 1:0.2.0-1.fc32 updates-testing f32-backgrounds-base.noarch 32.1.0-1.fc32 updates-testing fedora-gpg-keys.noarch 32-1 updates-testing fedora-release.noarch 32-1 updates-testing fedora-release-common.noarch 32-1 updates-testing fedora-repos.noarch 32-1 updates-testing ffmpeg-libs.x86_64 4.2.2-5.fc32 rpmfusion-free-updates-testing firefox.x86_64 75.0-1.fc32 fedora firefox-wayland.x86_64 75.0-1.fc32 fedora gbrainy.i686 1:2.4.2-1.fc32 updates-testing glib2.x86_64 2.64.2-1.fc32 updates-testing glib2-devel.x86_64 2.64.2-1.fc32 updates-testing gnome-weather.noarch 3.36.1-1.fc32 updates-testing gtk-update-icon-cache.x86_64 3.24.18-1.fc32 updates-testing gtk3.x86_64 3.24.18-1.fc32 updates-testing intel-mediasdk.x86_64 20.1.0-1.fc32 updates-testing libfido2.x86_64 1.3.1-2.fc32 updates-testing libinput.x86_64 1.15.5-1.fc32 updates-testing librsvg2.x86_64 2.48.3-1.fc32 updates-testing libssh.x86_64 0.9.4-1.fc32 updates-testing libssh-config.noarch 0.9.4-1.fc32 updates-testing net-snmp-libs.x86_64 1:5.8-19.fc32 updates-testing nss.x86_64 3.51.0-1.fc32 fedora nss-softokn.x86_64 3.51.0-1.fc32 fedora nss-softokn-freebl.x86_64 3.51.0-1.fc32 fedora nss-sysinit.x86_64 3.51.0-1.fc32 fedora nss-tools.x86_64 3.51.0-1.fc32 fedora nss-util.x86_64 3.51.0-1.fc32 fedora selinux-policy.noarch 3.14.5-36.fc32 updates-testing selinux-policy-targeted.noarch 3.14.5-36.fc32 updates-testing slirp4netns.x86_64 1.0.0-1.fc32 updates-testing vlc.x86_64 1:3.0.9.2-1.fc32 rpmfusion-free-updates-testing vlc-core.x86_64 1:3.0.9.2-1.fc32 rpmfusion-free-updates-testing webkit2gtk3.x86_64 2.28.0-9.fc32 updates-testing webkit2gtk3-jsc.x86_64 2.28.0-9.fc32 updates-testing why3.x86_64 1.3.1-3.fc32 updates-testing xerces-c.x86_64 3.2.3-1.fc32 updates-testing xfce4-taskmanager.x86_64 1.2.3-1.fc32 updates-testing xorg-x11-drv-intel.x86_64 2.99.917-45.20200205.fc32 updates-testing [paul@localhost log]$
If you have a ~/.config/dnfdragora.yaml file, could you try deleting it and running dnfdragora again?
Renaming have indeed fix this issue for me. [paul@localhost ~]$ cat .config/old_dnfdragora.yaml view: filter: to_update show: all [paul@localhost ~]$ Now that I have: [paul@localhost ~]$ LANG=C cat .config/dnfdragora.yaml cat: .config/dnfdragora.yaml: No such file or directory [paul@localhost ~]$ It works.
I encountered the same on two recently upgraded machines. The contents of ~/.config/dnfdragora.yaml before and after Neal Gompa's recommended "fix" were the same as those shown by Paul Dufresne.
I should note that a new dnfdragora.yaml file was created upon running the utility. The contents were significantly different: settings: always_yes: false do not show groups at startup: false interval for checking updates: 300 metadata: last_update: 2020-05-06 12:13 update_interval: 48 search: match_all: false newest_only: false show updates at startup: true view: filter: to_update show: all
I tried your dnfdragora.yaml configuration as discribed in comment5. It did not and dnfdragora did not start, instead giving a popup noting that an attribute was missing. I deleted the dnfdragora.yaml and dnfdragora started successfully and recreated the dnfdragora.yaml. After closing dnfdragora application the dnfdragora.yaml showed: $ cat .config/dnfdragora.yaml settings: metadata: last_update: 2020-05-17 15:02 update_interval: 48 search: match_all: false newest_only: false view: filter: to_update show: all I now get the same message as on the commandline when I try to update the kernel: $ sudo dnf update -y [sudo] Passwort für xxxxxx: Letzte Prüfung auf abgelaufene Metadaten: vor 0:08:13 am So 17 Mai 2020 15:06:19 CEST. Fehler: Problem 1: package kernel-modules-extra-5.6.7-300.fc32.x86_64 requires kernel-uname-r = 5.6.7-300.fc32.x86_64, but none of the providers can be installed - conflicting requests Problem 2: package kernel-5.6.7-300.fc32.x86_64 requires kernel-core-uname-r = 5.6.7-300.fc32.x86_64, but none of the providers can be installed - conflicting requests (try to add '--skip-broken' to skip uninstallable packages) I am running kernel "5.6.8-300.fc32.x86_64" and the available kernel 5.6.12-300.fc32.x86_64, but this seems to be a different problem. For me dnfdragora is working again.
Hi, I upgraded to Fedora 32 today and I am getting the same error messages when I run dnfdragora: /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 1536 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) When dnfdragora finally dies, I see the same "YUILoader.cc:163 deleteUI(): Shutting down UI" series of messages that the original poster wrote about. Here is the result of several system queries that may be helpful: $ uname -a Linux strathypypes 5.6.13-300.fc32.x86_64 #1 SMP Thu May 14 22:51:37 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ dnf check-update Last metadata expiration check: 0:48:01 ago on Sun 24 May 2020 01:35:35 PM EDT. I have deleted the dnfdragora.yaml file in the user's home directory and also renamed the file in /etc/dnfdragora/dnfdragora.yaml. This is a very repeatable issue on my computer. Everytime I run dnfdragora, the application is still stuck in a loop until it times out and then the application dies. I have also tried reinstalling python and dnfdragora from the command line. All that goes well, but dnfdragora is still not working correctly. Dnf works from the command line as expected, so I don't think the issue is with dnf. I think the issue has to do with either dnfdragora or something it depends upon. Thanks in advance for your help, Ben
on comment #7 it isn't clear to me if deleting local dnfdragora.yaml fixes the problem or not for you. Otherwhise it is another issue. this warning Warning: Source ID 1536 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) is not a problem caused by dnfdragora, iirc just for libyui-gtk warnings issues....
Angelo, You asked whether deleting the dnfdragora.yaml fixed the problem. That did not fix the problem. I removed it in both places and that did not fix the problem. Is there something else I should try? Thanks in advance, Ben
Well it seems different then, anyway you can try what suggested here: https://github.com/manatools/dnfdragora/issues/149#issuecomment-630439296 or adding your own config file copying the one written in comment #6 You could also enable debug logging there settings: metadata: last_update: 2020-05-17 15:02 update_interval: 48 search: match_all: false newest_only: false log: directory: /tmp enabled: true level_debug: true view: filter: to_update show: all You can add directory entry as you wish but writable of course. There you will find dnfdragora.log or dnfdragora-update.log
Created attachment 1692515 [details] dnfdragora.log -- the logfile created per instructions in this forum at comment #10 Angelo, You suggested in comment #10 that I start a logfile. I am attaching that logfile here in hopes that it may help. After following all instructions, including those in the other ticket you referred me to, dnfdragora still does not work properly. The terminal window is full of errors such as these: /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 2833 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) <_M_> [ui] YUILoader.cc:163 deleteUI(): Shutting down UI <_M_> [ew] YExternalWidgets.cc:116 ~YExternalWidgetsTerminator(): Shutting down mga External Widgets <_M_> [ew] YMGAWidgetExtensionFactory.cc:49 ~YMGAWidgetFactory(): Factory removed $ dnf itself still works properly from the command line, it is just that dnfdragora still does not work right. I remain open to any other suggestions. Thanks in advance for your help, Ben
Could you please tell me in what exactly dnfdragora does not work? Log file seems to be ok, the "package caching phase" seems to be passed ok and the problema exited normally. I suppose you pushed quit button, no exceptions or errors are present into log. Application output on stderror is not a dnfdragora issue but a libyui one. It seems there is no API to disable that. Concerning: /usr/lib64/python3.8/site-packages/yui.py:1472: Warning: Source ID 2833 was not found when attempting to remove it return _yui.YDialog_waitForEvent(self, timeout_millisec) I think it is a libyui-gtk issue (try dnfdragora for instance, --qt but you have to install libyui-qt and libyui-mga-qt too), most of those errors have been fixed by besser82 (https://github.com/libyui/libyui-gtk/pull/58) but they are still there :(
sorry they are warnings not errors (libyui-gyk)
Hi Angelo, Yesterday, dnfdragora would start, but no entries would show up in the panels and searching was just nothing. Most items were greyed out. So as far as checking for updates or looking for software to install, dnfdragora would not work. Today, dnfdragora works correctly. I don't know what fixed it, as it did not work correctly last night. I am happy to report that it is working well today and I was able to install some software updates just now. Feel free to close this one out for my issue. Thanks for your help! Cheers, Ben
dnfdragora is grayed when is updating from repositories, building metadata and/or cache. I tried to make most of its actions asynchronously. Time for actions depends on network and also on PC characteristics. Glad to here it works :) I have no power to close issues, but i think it cannot be closed until someone upgrades dnfdragora to last version... so that we can see new issues maybe :p
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.