We can live with 115 a few more, If you want to migrate to 128 remember that could require more recent rust and that require new llvm https://bugs.mageia.org/show_bug.cgi?id=33322

we should move to the new ESR version if possible.
Websites start removing css preprocessors, as css nesting (https://developer.mozilla.org/en-US/docs/Web/CSS/Nesting_selector) is globally available. And due to the regular auto-update-feature developers assume this is available since 1 year.

I guess we have this problem for other packages too (upgrading compilers, ..)

Would it be possible, in these (edge) cases, to build the package with cauldron (maybe statically) and provide the update?

My guess is, we have to reduce the development cycle, or find some workaround to deal with such problems.

CC: (none) => mageia

rootcerts must also be updated to 2024-08-23:
https://hg.mozilla.org/projects/nss/raw-file/default/lib/ckfw/builtins/certdata.txt
https://hg.mozilla.org/projects/nss/raw-file/default/lib/ckfw/builtins/nssckbi.h

Source RPM: nss, firefox, firefox-l10n => rootcerts, nss, firefox, firefox-l10n

To close security issues, I guess it will best and fastest, to make an update to 115.14.

Most users (windows, mac, mobile devices) have the latest browser version due to auto-update features. It is a good thing to have the ESR releases, but in case a new version is available, we should ship it.

I am not familiar buildung firefox, just tell, if you need help

I think neoclust (and daviddavid) are working on this, assigning to them

Assignee: bugsquad => mageia
CC: (none) => geiger.david68210, marja11

Mozilla has released Firefox 128.2 on September 3:
https://www.mozilla.org/en-US/firefox/128.2.0/releasenotes/

Security issues fixed:
https://www.mozilla.org/en-US/security/advisories/mfsa2024-40/

CVE: CVE-2024-7519, CVE-2024-7520, CVE-2024-7521, CVE-2024-7522, CVE-2024-7524, CVE-2024-7525, CVE-2024-7526, CVE-2024-7527, CVE-2024-7528, CVE-2024-7529, CVE-2024-7531 => CVE-2024-7519, CVE-2024-7520, CVE-2024-7521, CVE-2024-7522, CVE-2024-7524, CVE-2024-7525, CVE-2024-7526, CVE-2024-7527, CVE-2024-7528, CVE-2024-7529, CVE-2024-7531, CVE-2024-8385, CVE-2024-8381, CVE-2024-8382, CVE-2024-8383, CVE-2024-8384, CVE-2024-8386, CVE-2024-8387
Summary: Firefox 115.14 or 128.1 => Firefox 128.2

Due to the CVEs: why not release 115.14 (which should be easier to build). And have some more time to see, why 128 makes problems in building on mga9 ?

(In reply to Marc Krämer from comment #8)
> Due to the CVEs: why not release 115.14 (which should be easier to build).
> And have some more time to see, why 128 makes problems in building on mga9 ?

I'm wondering the same thing (which is why I searched for a bug like this). Well, 115.15 is available now [1], so it would make most sense not to make us use an outdated version of Firefox. The Firefox release calendar [2] indicates that there will be Firefox 115.x releases until 115.21 on March 4 2025 (and the 115 branch is to go EOL on April 1 2025); considering that Mageia 9 is scheduled to go EOL on March 31 2025, that doesn't seem like big problem (the 115 branch after October 1 2024 seems to be only for Mac and Windows versions no longer supported in 128, but as long as the source code is available, it should be possible to build for Mageia; I guess we'll see if that's the case if the 115.16 source code is available alongside 128.3 in October).

Additionally, you don't want to break a stable release if you don't have to. I remember when the ESR went from 78 to 91, my userChrome.css customizations I got from MozillaZine stopped working correctly and I had to edit it manually. So, Mageia 9 should probably stick to 115.x as long as possible to prevent whatever breakages come with 128.x.

[1] https://www.mozilla.org/en-US/firefox/115.15.0/releasenotes/
[2] https://whattrainisitnow.com/calendar/

(In reply to Keith Bowes from comment #9)
> (In reply to Marc Krämer from comment #8)
> > Due to the CVEs: why not release 115.14 (which should be easier to build).
> > And have some more time to see, why 128 makes problems in building on mga9 ?
> 
> I'm wondering the same thing (which is why I searched for a bug like this).
> Well, 115.15 is available now [1], so it would make most sense not to make
> us use an outdated version of Firefox. The Firefox release calendar [2]
> indicates that there will be Firefox 115.x releases until 115.21 on March 4
> 2025 (and the 115 branch is to go EOL on April 1 2025); considering that
> Mageia 9 is scheduled to go EOL on March 31 2025, that doesn't seem like big
> problem (the 115 branch after October 1 2024 seems to be only for Mac and
> Windows versions no longer supported in 128, but as long as the source code
> is available, it should be possible to build for Mageia; I guess we'll see
> if that's the case if the 115.16 source code is available alongside 128.3 in
> October).
> 
> Additionally, you don't want to break a stable release if you don't have to.
> I remember when the ESR went from 78 to 91, my userChrome.css customizations
> I got from MozillaZine stopped working correctly and I had to edit it
> manually. So, Mageia 9 should probably stick to 115.x as long as possible to
> prevent whatever breakages come with 128.x.
> 
> [1] https://www.mozilla.org/en-US/firefox/115.15.0/releasenotes/
> [2] https://whattrainisitnow.com/calendar/

https://endoflife.date/firefox says 115 will not last much so soon will have to migrate to 128

Maybe we should test and ship nss and rootcerts now, not wait for Firefox build?

CC: (none) => fri

Created attachment 14670 [details]
Backport of "0001-PEI-Don-t-zero-out-noreg-operands.patch" for llvm 15.0.6

Hi,

My test of building Firefox 128.2 with llvm17-suite failed with the same crash of the compiler as with llvm/clang/... 15.

Maybe the patch "0001-PEI-Don-t-zero-out-noreg-operands.patch" for llvm (present into llvm Cauldron but absent from llvm17-suite) can fix that crash.

The given patch is a backport of "0001-PEI-Don-t-zero-out-noreg-operands.patch" for llvm 15.0.6

Best regards,

Nico.

Nicolas Salguero I try build firefox i686 cauldron with llvm18-suite and I get this fail

I can't build in mageia 9 as I don't know how to include testing repositories in copr

 0:02.56 checking for vcs source checkout... no
 0:02.59 checking for a shell... /usr/bin/sh
 0:02.67 checking for host system type... i686-pc-linux-gnu
 0:02.67 checking for target system type... i686-pc-linux-gnu
 0:03.01 checking whether cross compiling... no
 0:03.13 checking for Python 3... /builddir/.mozbuild/srcdirs/firefox-128.2.0-14416ebecb57/_virtualenvs/build/bin/python (3.12.6)
 0:03.15 checking for wget... not found
 0:03.15 checking for ccache... not found
 0:03.16 checking for the target C compiler... /usr/lib/llvm18/bin/clang
 0:03.57 checking whether the target C compiler can be used... yes
 0:03.57 checking the target C compiler version... 18.1.8
 0:03.73 checking the target C compiler works... yes
 0:03.73 checking for the target C++ compiler... /usr/lib/llvm18/bin/clang++
 0:03.76 checking whether the target C++ compiler can be used... yes
 0:03.76 checking the target C++ compiler version... 18.1.8
 0:03.78 checking the target C++ compiler works... yes
 0:03.79 checking for the host C compiler... /usr/lib/llvm18/bin/clang
 0:03.79 checking whether the host C compiler can be used... yes
 0:03.79 checking the host C compiler version... 18.1.8
 0:03.79 checking the host C compiler works... yes
 0:03.79 checking for the host C++ compiler... /usr/lib/llvm18/bin/clang++
 0:03.79 checking whether the host C++ compiler can be used... yes
 0:03.79 checking the host C++ compiler version... 18.1.8
 0:03.79 checking the host C++ compiler works... yes
 0:04.08 checking for target linker... lld
 0:04.11 checking for host linker... lld
 0:04.14 checking for 64-bit OS... no
 0:04.16 checking for new enough STL headers from libstdc++...
 0:04.16 DEBUG: <truncated - see config.log for full output>
 0:04.16 DEBUG: |                 #if defined(__GLIBCXX__) && !defined(_GLIBCXX_RELEASE)
 0:04.16 DEBUG: | #  error libstdc++ not new enough
 0:04.16 DEBUG: | #endif
 0:04.16 DEBUG: | #if defined(_GLIBCXX_RELEASE)
 0:04.16 DEBUG: | #  if _GLIBCXX_RELEASE < 8
 0:04.16 DEBUG: | #    error libstdc++ not new enough
 0:04.16 DEBUG: | #  else
 0:04.16 DEBUG: |      (void) 0
 0:04.16 DEBUG: | #  endif
 0:04.16 DEBUG: | #endif
 0:04.16 DEBUG: |                   ;
 0:04.16 DEBUG: |                   return 0;
 0:04.16 DEBUG: |                 }
 0:04.16 DEBUG: Executing: `/usr/lib/llvm18/bin/clang++ /tmp/conftest.kslp144r.cpp -c`
 0:04.16 DEBUG: The command returned non-zero exit status 1.
 0:04.16 DEBUG: Its error output was:
 0:04.16 DEBUG: | /tmp/conftest.kslp144r.cpp:1:10: fatal error: 'cstddef' file not found
 0:04.16 DEBUG: |     1 | #include <cstddef>
 0:04.16 DEBUG: |       |          ^~~~~~~~~
 0:04.16 DEBUG: | 1 error generated.
 0:04.16 ERROR: The libstdc++ in use is not new enough.  Please run ./mach bootstrap to update your compiler, or update your system libstdc++ installation.
 0:04.21 W Exception when writing resource usage file: [Errno 2] No such file or directory: '/builddir/build/BUILD/firefox-128.2.0/objdir/.mozbuild/profile_build_resources.json'
 Config object not found by mach.
*** Fix above errors and then restart with "./mach build"

Hi,

Did you try modifying firefox SPEC file like this:

https://svnweb.mageia.org/packages/updates/9/firefox/current/SPECS/firefox.spec?r1=2094646&r2=2099429

Best regards,

Nico.

(In reply to Nicolas Salguero from comment #14)
> Hi,
> 
> Did you try modifying firefox SPEC file like this:
> 
> https://svnweb.mageia.org/packages/updates/9/firefox/current/SPECS/firefox.
> spec?r1=2094646&r2=2099429
> 
> Best regards,
> 
> Nico.

I get the spec from mgarepo I just change the llvm version, I'll give other try when llvm19 finish build

Created attachment 14676 [details]
Log of build in copr

Looks like something override the options for compiler because after the llvm things the configure options shows gcc :S

It fetch llvm19-suite and other requires as expected

I find the issue, perhaps a bug in spec of llvmN-suite, just need to add
BuildRequires:  %{newer_llvm}-suite to firefox's spec, the relevant lines in spec will be this

%if 0%{?system_llvm}
BuildRequires:  llvm
BuildRequires:  llvm-devel
BuildRequires:  clang
BuildRequires:  clang-devel
%else
BuildRequires:  %{newer_llvm}-suite
BuildRequires:  %{newer_llvm}-suite-devel
%endif

I'll inform the result when the build finish

BTW if the build is successful also

%global newer_llvm        

Should be set to 
%global newer_llvm        llvm19

The build finish now we need the new llvm be built for mageia 9

Blocks: 33449 => (none)
Depends on: (none) => 33322

Please

CC: (none) => joselp

Please, we need to upgrade to Firefox 128 urgently. 

Some pages are starting to give me errors. But the most important thing is that I can't access by digital certificate to the electronic office of the public administration in Spain, for example here: 

https://tributos.oapgt.es/450005/DTOLEDO

Perhaps we could take a look at the spec of the repository of our colleagues at MLO where firefox 130 is packaged.

(In reply to Jose Manuel López from comment #22)
> Perhaps we could take a look at the spec of the repository of our colleagues
> at MLO where firefox 130 is packaged.

Hi,

MLO only provides firefox for x86_64.  The problem we have is with the 3 other arches.  We absolutely need llvm19-suite and rust to be able to build firefox for i586, aarch64 and armv7hl.

Best regards,

Nico.

For the security reason, is it possible to for now make an exempt and ship for x86_64 only, until building for the other arches are solved?

Mozilla has released NSS 3.105.

Mozilla has released Firefox 128.3 on October 1:
https://www.mozilla.org/en-US/firefox/128.3.0/releasenotes/

Security issues fixed:
https://www.mozilla.org/fr/security/advisories/mfsa2024-47/

Summary: Firefox 128.2 => Firefox 128.3

mga9-64 OK
Plasma, Intel CPU, AMD GPU

Installed now:
 firefox-128.3.0-1.mga9.x86_64
 firefox-sv_SE-128.3.0-1.mga9.noarch
 nss-3.105.0-1.mga9.x86_64
 lib64nss3-3.105.0-1.mga9.x86_64

Already had installed since a while:
 rootcerts-java-20240823.00-1.mga9.noarch
 rootcerts-20240823.00-1.mga9.noarch

Help -> about say "128.3.0esr (64-bit)", and "mageia - 9.0"

Restored previous tabs, settings kept, localisation OK.
Used banking sites, tax office, shops, video sites, saved file, opened and printed pdf to boomaga.

I launched it from konsole, got some output during use:
Gtk-Message: 00:41:26.642: Failed to load module "appmenu-gtk-module": 'gtk_module_display_init': /usr/lib64/gtk-3.0/modules/libwindow-decorations-gtk-module.so: undefined symbol: gtk_module_display_init
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 307877, Main Thread] WARNING: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.: 'glib warning', file /home/iurt/rpmbuild/BUILD/firefox-128.3.0/toolkit/xre/nsSigHandlers.cpp:187
(firefox:307877): GLib-GIO-WARNING **: 00:41:31.298: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.
ATTENTION: default value of option mesa_glthread overridden by environment.

Assignee: mageia => qa-bugs

If we gonna just process this for x86_64 would be good open a bug for the other architectures

Summary: Firefox 128.3 => Firefox 128.3 fot x86_64
Version: Cauldron => 9
Whiteboard: MGA9TOO => (none)
Hardware: All => x86_64
Depends on: 33322 => (none)

Hi.

Installed from testing repos in Mga9 x86_64 Ryzen 7 4800h Integrated graphics.

Youtube, audio and video ok.
Banks ok.
Addons ok.
Digital certificates ok.
Spanish translation ok.
Settings ok, they have stayed well from Firefox 115.
Account and sync ok.

Launched from terminal:

[jose@localhost ~]$ firefox
[Parent 87255, Main Thread] WARNING: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.: 'glib warning', file /home/iurt/rpmbuild/BUILD/firefox-128.3.0/toolkit/xre/nsSigHandlers.cpp:187

(firefox:87255): GLib-GIO-WARNING **: 06:23:11.207: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.
[jose@localhost ~]$

Installed from testing repos in Mga9 x86_64 8 × 11th Gen Intel® Core™ i5-1155G7 @ 2.50GHz Integrated graphics.

Youtube, audio and video ok.
Banks ok.
Addons ok.
Digital certificates ok.
Spanish translation ok.
Settings ok, they have stayed well from Firefox 115.
Account and sync ok.

Launched from terminal:

[jose@localhost ~]$ firefox
[Parent 98668, Main Thread] WARNING: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.: 'glib warning', file /home/iurt/rpmbuild/BUILD/firefox-128.3.0/toolkit/xre/nsSigHandlers.cpp:187

(firefox:98668): GLib-GIO-WARNING **: 08:14:23.428: /usr/share/applications/kde-mimeapps.list contains a [Added Associations] group, but it is not permitted here.  Only the non-desktop-specific mimeapps.list file may add or remove associations.

Installed from testing repos in Mga9 x86_64
CPU: Intel(R) Atom(TM) N450 (2) @ 1,67 GHz
GPU: Intel evice A011 (VGA compatible) [Integrate]

Youtube, audio and video ok.
Banks ok.
Addons ok.
Digital certificates ok.
Spanish translation ok.
Settings ok, they have stayed well from Firefox 115.
Account and sync ok.

Launched from terminal:

[jose@localhost ~]$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=93.1015) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt

The terminal output is perhaps due to the antiquity and limitations of this concrete hardware.

Greetings and thanks to everyone that do this updato possible!!

As far as I have tested, works good.

Great work!

Could we get a complete file list for qarepo, please? The RPM links of both madb sites show the 128.1 version, and one is missing the rootcerts altogether. Both also include i586 packages, and if I'm reading correctly, they aren't a part of this bug now.

CC: (none) => andrewsfarm

Packages in 9/core/updates_testing

x86_64:
firefox-128.3.0-1.mga9
firefox-af-128.3.0-1.mga9
firefox-an-128.3.0-1.mga9
firefox-ar-128.3.0-1.mga9
firefox-ast-128.3.0-1.mga9
firefox-az-128.3.0-1.mga9
firefox-be-128.3.0-1.mga9
firefox-bg-128.3.0-1.mga9
firefox-bn-128.3.0-1.mga9
firefox-br-128.3.0-1.mga9
firefox-bs-128.3.0-1.mga9
firefox-ca-128.3.0-1.mga9
firefox-cs-128.3.0-1.mga9
firefox-cy-128.3.0-1.mga9
firefox-da-128.3.0-1.mga9
firefox-de-128.3.0-1.mga9
firefox-el-128.3.0-1.mga9
firefox-en_CA-128.3.0-1.mga9
firefox-en_GB-128.3.0-1.mga9
firefox-en_US-128.3.0-1.mga9
firefox-eo-128.3.0-1.mga9
firefox-es_AR-128.3.0-1.mga9
firefox-es_CL-128.3.0-1.mga9
firefox-es_ES-128.3.0-1.mga9
firefox-es_MX-128.3.0-1.mga9
firefox-et-128.3.0-1.mga9
firefox-eu-128.3.0-1.mga9
firefox-fa-128.3.0-1.mga9
firefox-ff-128.3.0-1.mga9
firefox-fi-128.3.0-1.mga9
firefox-fr-128.3.0-1.mga9
firefox-fur-128.3.0-1.mga9
firefox-fy_NL-128.3.0-1.mga9
firefox-ga_IE-128.3.0-1.mga9
firefox-gd-128.3.0-1.mga9
firefox-gl-128.3.0-1.mga9
firefox-gu_IN-128.3.0-1.mga9
firefox-he-128.3.0-1.mga9
firefox-hi_IN-128.3.0-1.mga9
firefox-hr-128.3.0-1.mga9
firefox-hsb-128.3.0-1.mga9
firefox-hu-128.3.0-1.mga9
firefox-hy_AM-128.3.0-1.mga9
firefox-ia-128.3.0-1.mga9
firefox-id-128.3.0-1.mga9
firefox-is-128.3.0-1.mga9
firefox-it-128.3.0-1.mga9
firefox-ja-128.3.0-1.mga9
firefox-ka-128.3.0-1.mga9
firefox-kab-128.3.0-1.mga9
firefox-kk-128.3.0-1.mga9
firefox-km-128.3.0-1.mga9
firefox-kn-128.3.0-1.mga9
firefox-ko-128.3.0-1.mga9
firefox-lij-128.3.0-1.mga9
firefox-lt-128.3.0-1.mga9
firefox-lv-128.3.0-1.mga9
firefox-mk-128.3.0-1.mga9
firefox-mr-128.3.0-1.mga9
firefox-ms-128.3.0-1.mga9
firefox-my-128.3.0-1.mga9
firefox-nb_NO-128.3.0-1.mga9
firefox-nl-128.3.0-1.mga9
firefox-nn_NO-128.3.0-1.mga9
firefox-oc-128.3.0-1.mga9
firefox-pa_IN-128.3.0-1.mga9
firefox-pl-128.3.0-1.mga9
firefox-pt_BR-128.3.0-1.mga9
firefox-pt_PT-128.3.0-1.mga9
firefox-ro-128.3.0-1.mga9
firefox-ru-128.3.0-1.mga9
firefox-sc-128.3.0-1.mga9
firefox-si-128.3.0-1.mga9
firefox-sk-128.3.0-1.mga9
firefox-sl-128.3.0-1.mga9
firefox-sq-128.3.0-1.mga9
firefox-sr-128.3.0-1.mga9
firefox-sv_SE-128.3.0-1.mga9
firefox-szl-128.3.0-1.mga9
firefox-ta-128.3.0-1.mga9
firefox-te-128.3.0-1.mga9
firefox-tg-128.3.0-1.mga9
firefox-th-128.3.0-1.mga9
firefox-tl-128.3.0-1.mga9
firefox-tr-128.3.0-1.mga9
firefox-uk-128.3.0-1.mga9
firefox-ur-128.3.0-1.mga9
firefox-uz-128.3.0-1.mga9
firefox-vi-128.3.0-1.mga9
firefox-xh-128.3.0-1.mga9
firefox-zh_CN-128.3.0-1.mga9
firefox-zh_TW-128.3.0-1.mga9

lib64nss-devel-3.105.0-1.mga9
lib64nss-static-devel-3.105.0-1.mga9
lib64nss3-3.105.0-1.mga9
nss-3.105.0-1.mga9
nss-doc-3.105.0-1.mga9

rootcerts-20240823.00-1.mga9
rootcerts-java-20240823.00-1.mga9

SRPM:
firefox-128.3.0-1.mga9.src.rpm
firefox-l10n-128.3.0-1.mga9.src.rpm
nss-3.105.0-1.mga9.src.rpm
rootcerts-20240823.00-1.mga9.src.rpm

mga9, x64

This version is working fine on my Intel machine.  APOD, Youtube videos, banking queries and interactive word game (quordle).  Local text files and Google maps street view working.  History works OK.  Installed new themes.

CC: (none) => tarazed25

I'm getting this error when I try to install.

Sorry, the following package cannot be selected:

- firefox-128.3.0-1.mga9.x86_64 (due to unsatisfied libicui18n.so.73()(64bit))

Am i missing a required repo?

CC: (none) => brtians1

(In reply to Brian Rockwell from comment #35)
> I'm getting this error when I try to install.
> 
> Sorry, the following package cannot be selected:
> 
> - firefox-128.3.0-1.mga9.x86_64 (due to unsatisfied
> libicui18n.so.73()(64bit))
> 
> Am i missing a required repo?

You are getting a bad shape mirror from mirror list, that file should be already in the repositories https://bugs.mageia.org/show_bug.cgi?id=33553

Ah good - I refreshed all my repo links:

MGA9-64, Xfce, AMD apu

The following 10 packages are going to be installed:

- firefox-128.3.0-1.mga9.x86_64
- firefox-en_CA-128.3.0-1.mga9.noarch
- firefox-en_GB-128.3.0-1.mga9.noarch
- firefox-en_US-128.3.0-1.mga9.noarch
- icu73-data-73.2-1.mga9.noarch
- lib64icu73-73.2-1.mga9.x86_64
- lib64nss-devel-3.105.0-1.mga9.x86_64
- lib64nss-static-devel-3.105.0-1.mga9.x86_64
- lib64nss3-3.105.0-1.mga9.x86_64
- nss-3.105.0-1.mga9.x86_64

27MB of additional disk space will be used.

===rebooted

so far working: 

email
websites

VM x86_64

Updated

youtube OK
mail.com OK
general navigation looks OK

MGA9-64 Plasma on an HP Pavilion, A8-4555, HD 7600G graphics.

No installation issues. Went shopping for a newer color laser printer, Amazon, eBay, HP support, Brother support. Haven't decided which way to go yet, but Firefox is working well. BTW, it stopped raining according to WSYR-TV Doppler radar, confirmed by looking out the window...

MGA9-64, Cinnamon, Nouveau

The following 8 packages are going to be installed:

- firefox-128.3.0-1.mga9.x86_64
- firefox-en_CA-128.3.0-1.mga9.noarch
- firefox-en_GB-128.3.0-1.mga9.noarch
- firefox-en_US-128.3.0-1.mga9.noarch
- lib64nss3-3.105.0-1.mga9.x86_64
- nss-3.105.0-1.mga9.x86_64
- rootcerts-20240823.00-1.mga9.noarch
- rootcerts-java-20240823.00-1.mga9.noarch

-- rebooted


confirmed version

- all usual websites and audio works

Let me know what you think of this text as advisory:

The current version reach EOL and several security vulnerabilities were fixed by mozilla.
We are having some issues that are delaying the build for some architectures, so for the moment we are releasing this update just for x86_64

Keywords: (none) => advisory

IMO that text for advisory in comment 41 is good.

@Thomas please consider validate this or will lose sense split this update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2024-0325.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED