Description of problem: Notifications with timeout generated by python3-pystray will never close. For example, dnfdragora-updater is affected (notifications must be closed manually). This issue has been fixed in version 0.17.3 (https://pypi.org/project/pystray/) Related issues: - https://github.com/manatools/dnfdragora/issues/178 - https://github.com/moses-palmer/pystray/issues/84 Version-Release number of selected component (if applicable): 0.17.1-1 How reproducible: Always Steps to Reproduce: 1. 2. 3.
CC: (none) => hector
Assigning to the registered maintainer
Assignee: bugsquad => ngompa13CC: (none) => marja11
Submitted python3-pystray-0.17.3-1.mga8.noarch.rpm python3-pystray-doc-0.17.3-1.mga8.noarch.rpm Source: python-pystray-0.17.3-1.mga8.src.rpm
CC: (none) => yvesbrungardAssignee: ngompa13 => qa-bugs
MGA8-64 Plasma on HP Pavilion 15 urpmq shows only dnfdragora-updater as requiring python3-pystray, so it was time for me to try it out. Installed the QT dnfdragora and dnfdragora-updater and dependencies, including python3-pystray. Ran dnfdragora as root, and let it set itself up. It took a while, but eventually I was rewarded with a drakrpm-like gui populated with packages to install. Closed dnfdragora and ran dnfdragora-updater, which put an icon in the systray. Clicked on that, and selected "Check for uopdates." It took a while again, but eventually there was a popup telling me there were none waiting. I waited a while, but the popup didn't close itself, confirming the issue. I used qarepo and drakrpm-update to update the packages, not trusting myself to use dnf for that just yet. No installation issues. I tried dnfdragora-updater once more, once again eventually getting a popup - but this time it went back down after a short time. So it looks like this issue is fixed. Giving it an OK, and validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugsWhiteboard: (none) => MGA8-64-OK
Advisory based on comment 2 and description added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0103.html
Status: NEW => RESOLVEDResolution: (none) => FIXED