Description of problem: attempting to invoke Yabinero, the application exits silently. attempting: $ /usr/games/yabinero returns: $ /usr/games/yabinero thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }', src/gui/user_data.rs:201:79 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [work@localhost Documents]$ yabinero thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }', src/gui/user_data.rs:201:79 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace Version-Release number of selected component (if applicable): yabinero-1.63.0-3.mga9 How reproducible: always Steps to Reproduce: 1. create a new install, LXDE only, with sufficient root partition space to install task-games (+20GB) and update to latest. 2.install task-games. 3.attempt to invoke Yabinero from application launcher or commandline.
Created attachment 14289 [details] lspcidrake output
Source RPM: task-games-9-1.mga9 => yabinero-1.63.0-3.mga9.src.rpm
CC: (none) => nicolas.salgueroAssignee: bugsquad => nicolas.salguero
Suggested advisory: ======================== The updated package fixes a a crash when the game is launched for the first time. References: https://github.com/nsalguero/yabinero/releases/tag/v1.68.0 ======================== Updated package in core/updates_testing: ======================== yabinero-1.68.0-1.mga9 from SRPM: yabinero-1.68.0-1.mga9.src.rpm
Assignee: nicolas.salguero => qa-bugsStatus: NEW => ASSIGNED
Advisory from comment 2 added to SVN. Please remove the "advisory" keyword if it needs to be changed. It also helps when obsolete advisories are tagged as "obsolete"
CC: (none) => marja11Keywords: (none) => advisory
Tested in real hardware Mageia 9 x86_64 lxqt Install current yabinero Run and reproduce the crash Update to testing package without issue Run yabinero without issues
Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarm
Thomas, did you think we can validate this?
Normally I'd say yes, but this time the advisory states that the issue appears the first time the game is launched. Your test confirmed update over the previous version, which is an important test, but running the original version to confirm the crash could have created a config file that could mean that running the updated version was now the second time it was launched. (Being picky, I know.) I downloaded the update with qarepo, and installed it on a system where it hadn't been installed before. Then I ran it, and there was no crash. That confirms the OK. Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0042.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED