March 2024 - openSUSE Factory Mozilla - openSUSE Mailing Lists

[Bug 1216797] New: SeaMonkey fails to build with rust >= 1.48
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1216797 Bug ID: 1216797 Summary: SeaMonkey fails to build with rust >= 1.48 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- SeaMonkey was failing to build with rust >= 1.48 due to upstream bug <https://bugzilla.mozilla.org/show_bug.cgi?id=1860935>. To fix this issue, I have added a patch to the SeaMonkey 2.53.17.1 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey>. I am requesting that these changes be included in Leap 15.4 and 15.5. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222137] New: SeaMonkey: update to 2.53.18.2
by bugzilla_noreply＠suse.com 05 Sep '24

05 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222137 Bug ID: 1222137 Summary: SeaMonkey: update to 2.53.18.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: factory-mozilla(a)lists.opensuse.org, linux(a)daniel-bauer.com, maintenance(a)opensuse.org, Manfred.Haertel(a)rz-online.de, meissner(a)suse.com, qa-bugs(a)suse.de, security-team(a)suse.de, wolfgang.engel(a)suse.com Depends on: 1218961 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1218961 +++ Please update the SeaMonkey package in 15.5 and 15.6 to the SeaMonkey 2.53.18.2 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey> The latest version of SeaMonkey, 2.53.18.2, released on 28 March 2024, contains new backports of important security fixes from Firefox 115.9 and Thunderbird 115.9 ESR. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 1

[Bug 1220201] New: Firefox on Wayland - download dialog disappearing
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220201 Bug ID: 1220201 Summary: Firefox on Wayland - download dialog disappearing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using Firefox on Wayland the download dialog is disappearing after chosing "save file" and before selecting the download file and directory. One can see the "enter name ..." dialog for a second, then it vanishes. On the same machine this does not happen with Xorg. There is no error or warning in the journal, i.e. for a crash. Operating System: openSUSE Tumbleweed 20240220 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1213574] New: Thunderbird OAUTH2 broken
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213574 Bug ID: 1213574 Summary: Thunderbird OAUTH2 broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Thunderbird updates broke OAUTH2 and this seems to be a common problem with Thunderbird 102. With this update it no longer presents an OAUTH2 dialog for IMAP. My employer uses Microsoft Office365 and OAUTH2 is essential. This used to work. Even with a clean install and nuking the previous configuration it will never prompt for OAUTH2 authentication like it used to. Note that the OAUTH2 dialog DOES work with SMTP, but not IMAP. Searching the Internet reveals that this is a common problem with this release. Please upgrade Thunderbird to a newer release for 15.4. I'm not quite ready to upgrade to 15.5 just yet since I use this machine for heavy development work. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1214980] New: mozilla-nss: FTBFS because expired certificate since 2023-09-04
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214980 Bug ID: 1214980 Summary: mozilla-nss: FTBFS because expired certificate since 2023-09-04 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- mozilla-nss doesn't build because because expired certificate since 2023-09-04 Bernhard M. Wiedemann already made a nice report at upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1813401 A fix in progress: https://phabricator.services.mozilla.com/D185088 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1218961] New: SeaMonkey: update to 2.53.18.1
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218961 Bug ID: 1218961 Summary: SeaMonkey: update to 2.53.18.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: Andreas.Stieger(a)gmx.de, factory-mozilla(a)lists.opensuse.org, linux(a)daniel-bauer.com, maintenance(a)opensuse.org, Manfred.Haertel(a)rz-online.de, meissner(a)suse.com, qa-bugs(a)suse.de, security-team(a)suse.de, wolfgang.engel(a)suse.com Depends on: 1217916 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1217916 +++ Please update the SeaMonkey package in 15.5 and 15.6 to the SeaMonkey 2.53.18.1 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey> The latest version of SeaMonkey, 2.53.18.1, released on 16 January 2024, contains new backports of important security fixes from Firefox 115.7 and Thunderbird 115.7 ESR. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 2

[Bug 1212259] New: MozillaThunderbird: bundled rnp/Botan, and supporting pluggable OpenPGP providers
by bugzilla_noreply＠suse.com 24 Mar '24

24 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1212259 Bug ID: 1212259 Summary: MozillaThunderbird: bundled rnp/Botan, and supporting pluggable OpenPGP providers Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Mozilla Thunderbird bundles a number of libraries for OpenPGP support: * rnp: https://github.com/rnpgp/rnp and openSUSE:Factory/rnp * (bundled in rnp) https://github.com/rnpgp/sexp * Botan (rnp has an experimental OpenSSL backend too) We should look into un-bundling here due to: * general packaging policy - avoiding bundled libs * especially for crypto routines: shared crypto policy, and maybe to use OpenSSL FIPS? * incorrectly attributed bugs, e.g. bug 1212253 (CVE-2023-29479) considered against MozillaThunderbird and missed for rnp. * there are other compatible and pluggable providers of the Thunderbird plugin: https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp Background: RH dropping Botan https://bugzilla.redhat.com/show_bug.cgi?id=1837512 FC splitting plugin: https://src.fedoraproject.org/rpms/thunderbird/c/edf3b30dbedcb43be087001509… FC system rnp: https://src.fedoraproject.org/rpms/thunderbird/c/0a585f45242a8fc024dfc1761a… -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1221531] Extension could not be verified for use in Firefox and has been disabled
by bugzilla_noreply＠suse.com 20 Mar '24

20 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221531 https://bugzilla.suse.com/show_bug.cgi?id=1221531#c47 --- Comment #47 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- (In reply to Frank Krüger from comment #46) > (In reply to Pedro Monreal Gonzalez from comment #31) > > The DEFAULT policy in crypto-policies does not allow SHA-1 signatures but > > the LEGACY one does allow it. Could somebody test if switching to LEGACY > > helps?: > > > > > sudo update-crypto-policies --set LEGACY > > > > Note that, this command is shipped by the crypto-policies-scripts package. > > > > If it help, I would force using the LEGACY policy only in mozilla-nss by > > default for now in crypto-policies and submit in a moment. > > > > TIA > > Since the crypto-policies support has been disabled in the nss packages for > the time being, is there an SR already from your side? Thx. Since crypto-policies support has been disabled in nss, there is no need to submit any changes in CP for now. We may have to allow SHA1 in the nss DEFAULT policy for some time if we want to enforce crypto-policies back for it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221531] Extension could not be verified for use in Firefox and has been disabled
by bugzilla_noreply＠suse.com 19 Mar '24

19 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221531 https://bugzilla.suse.com/show_bug.cgi?id=1221531#c46 --- Comment #46 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Pedro Monreal Gonzalez from comment #31) > The DEFAULT policy in crypto-policies does not allow SHA-1 signatures but > the LEGACY one does allow it. Could somebody test if switching to LEGACY > helps?: > > > sudo update-crypto-policies --set LEGACY > > Note that, this command is shipped by the crypto-policies-scripts package. > > If it help, I would force using the LEGACY policy only in mozilla-nss by > default for now in crypto-policies and submit in a moment. > > TIA Since the crypto-policies support has been disabled in the nss packages for the time being, is there an SR already from your side? Thx. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221531] New: Extension could not be verified for use in Firefox and has been disabled
by bugzilla_noreply＠suse.com 19 Mar '24

19 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1221531 Bug ID: 1221531 Summary: Extension could not be verified for use in Firefox and has been disabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: oleg.b.antonyan(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873591 --> https://bugzilla.suse.com/attachment.cgi?id=873591&action=edit Extensions window with errors All extensions suddenly disabled on 17.03.2024 with error: could not be verified for use in Firefox and has been disabled. Firefox 123 from main repo, 123 from mozilla repo, 123 tarball from mozilla.org - all have the same issue. Creating new profile doesn't help. Nighly from mozilla.org is ok -- You are receiving this mail because: You are the assignee for the bug.

1 16