Description of problem: Hello, Flightgear version 2020.3.19 has just been released. https://www.flightgear.org/ Can you put it in the Mageia 9 testing repositories before putting it in the release repositories if the tests are ok? THANKS --------------------------------------------------------------------- Hello, Flightgear en version 2020.3.19 vient d'etre publiée. https://www.flightgear.org/ Pouvez vous la mettre dans les dépots testing de Mageia 9 avant de la mettre dans les dépots release si les tests sont ok ? Merci ---------------------------------- Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
It'll need to land in cauldron, first. Since it is a bugfix release, it can then be pushed to updates_testing, for QA to test it before it gets pushed as regular update. Please keep an eye on this report and help QA team to test the updated package. https://wiki.mageia.org/en/QA_process_for_validating_updates
Version: 9 => CauldronAssignee: bugsquad => eatdirtCC: (none) => marja11Whiteboard: (none) => MGA9TOO
Hi there, there is no need to, the last version I pushed 2020.3.18.1.1.mga9 already included the patches that have been officially incorporated into 2019.3.19. So we're good till 2020.3.20. Cheers, chris.
I would have tested this 2020.3.19 because currently, there are texture bugs with the 2020.3.18 provided in mageia 9 (which was not available in mageia 8, I had tested it) ---------------------------------------------------------- J'aurais bien testé cette 2020.3.19 car actuellement, il y des bugs de textures avec la 2020.3.18 fournie dans mageia 9 (qu'il n'y avait pas dans mageia 8, je l'avais testée)
The version 2020.3.18.1.1.mga9 is exactly the same as the publicly released 2020.3.19. In our last bug fixing, I've backported all the patches that went in into 2020.3.19 afterwards. For the texturing problem, it won't help then. But, please, open a bug report for the texturing issues. This possibly come from the compositor I have enabled for mga9. Please test with this option added to "fgfs", it you're not doing that already: fgfs --compositor=Compositor/als
Translated with google: Good morning, here is the test report. 1) with the version provided 2020.3.18 now by mageia 9, the ground is well displayed, the main bug has been corrected 2) there are still some texture issues (a few rare missing textures and red-orange road pieces) 3) by trying with ALS, or without, via the flightgear menu, or by adding the text "--compositor=Compositor/als" in the start / Setting menu, it's almost the same thing. Without ALS I have some extra textures OK, but with or without, there are always red bits of road. so nothing convincing. A user with the appimage version indicates that he does not have red road pieces. That's why I was curious to test 2020.3.19 to see. (But if you say it's exactly the same as the 2020.3.18 provided by mageia...) ----------------------------------------------------------------------- bonjour, voici le compte rendu des tests. 1) avec la version fournie 2020.3.18 à présent par mageia 9, le sol est bien affiché, le bug principal a bien été corrigé 2) il demeure quelques problèmes de textures (quelques rares textures manquantes et des morceaux de route rouges-orangées) 3) en essayant avec ALS, ou sans, via le menu de flightgear, ou en ajoutant le texte "--compositor=Compositeur/als" dans le menu de démarrage / Setting, c'est quasiment la même chose. Sans ALS, j'ai quelques textures supplémentaires OK, mais avec ou sans, il y a toujours des morceaux de route rouges. donc rien de probant. Un utilisateur avec la version appimage indique qu'il n'a pas morceaux de route rouges. C'est pourquoi j'étais curieux de tester la 2020.3.19 pour voir. (Mais si vous dites que c'est exactement la même que la 2020.3.18 fournie par mageia...)
Ok, I've manage to confirm using a computer with an old nvidia card. The compositor is not robust to different hardware, so I am going to push an update disabling it for mga9. On Cauldron, I'll push the latest snapshot 2020.4.0, which is working quite well Thanks for the bug report, and sorry for the delays.
simgear-2020.3.19-1.mga9 flightgear-2020.3.19-1.mga9 flightgear-data-2020.3.19-1.mga9 landing in core/updates_testing, built with compositor OFF. The rendering issues should be gone. Let me know how it works.
Assignee: eatdirt => qa-bugs
(In reply to Chris Denice from comment #6) > Ok, I've manage to confirm using a computer with an old nvidia card. The > compositor is not robust to different hardware, so I am going to push an > update disabling it for mga9. > > On Cauldron, I'll push the latest snapshot 2020.4.0, which is working quite > well > Thanks for the bug report, and sorry for the delays. I take it from this that this is no longer a Cauldron bug. Switching it to Mageia 9...
CC: (none) => andrewsfarmWhiteboard: MGA9TOO => (none)Version: Cauldron => 9
MGA9-64 Plasma, i5-7500, Nvidia Quadro K620 graphics, using nvidia-current. Installed Flightgear and dependencies, then updated with no issues. I ran it, and played around. Autostarted the Cessna, but it must have still been tied down because it wouldn't move. So, I found a setting that would put it in the air, flying at settings I only guessed about. I flew it for a while, threatening to lose control at any moment. I think I ran out of fuel, because eventually it just stopped. Seems to be OK, as far as I can tell. Validating.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_updateWhiteboard: (none) => MGA9-64-OK
Source RPM: (none) => flightgear-2020.3.18-1.1.mga9,flightgear-data-2020.3.18-1.3.mga9,simgear-2020.3.18-1.1.mga9Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0082.html
Status: NEW => RESOLVEDResolution: (none) => FIXED