Description of problem: When choosing Release notes or Eratta from Mageia Welcome, they open *Newcomers Start Here* and *Documentation - Mageia Wiki* respectively Version-Release number of selected component (if applicable): Mageia-8-rc-***.iso DATE: Thu 14 Jan 2021 12:40:24 AM CET (Round 2) How reproducible: every time Steps to Reproduce: 1.Boot a Live or install a round2 version of Mageia-8-rc-***.iso 2.connect to internet and choose either of the above links in Mageia Welcome 3.
Keywords: (none) => 8rc2
Not reproduced with FR locale from mageiawelcome-2.07-1.mga8.noarch installed on tuesday 12th january 2021 at 14:13:38 Pretty Mageia 8 from Beta 2 installation and up to date. Leaving for other locale. I can't launch it in English (put LANG=C before launching it produces FR GUI...) CC' papoteur.
CC: (none) => ouaurelien, yves.brungard_mageia
Same with $ LANGUAGE=C mageiawelcome $ LANGUAGE=en_ZA mageiawelcome I can't reproduce this with mageiawelcome-2.07-1.mga8 Which version is in RC iso?
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
ISO Name: Mageia-8-rc-x86_64 DATE.txt: Wed 13 Jan 2021 11:31:41 PM CET md5sum: 3d7615b2b0d374da12d7686fb278e067 All DE install, and ISO Name: Mageia-8-rc-Live-Plasma-x86_64 DATE.txt: Thu 14 Jan 2021 12:40:24 AM CET md5sum: 5e909ec0d9158bb340e71046ecb4d76a
mageiawelcome-2.07-1.mga8
mageiawelcome-2.07-1.mga8 $ echo $LANG cy_GB.UTF-8 Confirm Ben's point: MW-More Information-Documentation-Release Notes -> https://wiki.mageia.org/en/Newcomers_start_here Same path-Errata -> https://wiki.mageia.org/en/Documentation
Summary: Mageia Welcome: Release notes and Errata open incorrect web pages => Mageia Welcome: Release notes and Errata open incorrect web pages for English at leastCC: (none) => lewyssmith
This is a problem in translation catalogs. Bad links are present, I don't know how they come. I will push a new release with correction. Papoteur
Status: UNCONFIRMED => ASSIGNEDAssignee: bugsquad => yves.brungard_mageiaEver confirmed: 0 => 1
Should be OK with mageiawelcome 2.08 in cauldron.
update to2.08 has fixed this. closing
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED