February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208686] [Build A.441.1] openQA test fails in yast2_nfs_server
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208686 https://bugzilla.suse.com/show_bug.cgi?id=1208686#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |INVALID --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- openQA bug, tracked on progress.o.o. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208589] VUL-0: chromium: multiple security issues fixed in 110.0.5481.177
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208589 http://bugzilla.opensuse.org/show_bug.cgi?id=1208589#c6 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #6 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- done -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201089] [META] GCC 13 package failures
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1201089 https://bugzilla.suse.com/show_bug.cgi?id=1201089#c11 --- Comment #11 from Martin Li��ka <martin.liska(a)suse.com> --- timezone packages waits for the following fix: https://github.com/eggert/tz/commit/9cfe9507fcc22cd4a0c4da486ea1c7f0de6b075f -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201089] [META] GCC 13 package failures
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1201089 Bug 1201089 depends on bug 1207339, which changed state. Bug 1207339 Summary: glibc FTBFS with gcc13 https://bugzilla.suse.com/show_bug.cgi?id=1207339 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207339] New: glibc FTBFS with gcc13
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207339 Bug ID: 1207339 Summary: glibc FTBFS with gcc13 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently we see errors like [ 48s] In file included from <command-line>: [ 48s] ../sysdeps/ieee754/ldbl-96/s_modfl.c:72:29: error: conflicting types for built-in function 'modff64x'; expected '_Float64x(_Float64x, _Float64x *)' [-Werror=builtin-declaration-mismatch] [ 48s] 72 | libm_alias_ldouble (__modf, modf) [ 48s] | ^~~~ which seems to be fixed in master with f66780ba46805760a328f01967836416b06c93ca by passing the appropriate -fno-builtin-XXX flags for the build of those files. That change needs to be picked to our glibc package. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1177260] Switching python-numpy to plain BLAS causes significant performance regression
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1177260 https://bugzilla.suse.com/show_bug.cgi?id=1177260#c51 --- Comment #51 from Egbert Eich <eich(a)suse.com> --- (In reply to Richard Biener from comment #50) > Maybe you can just override LD? OTOH to get libgfortran linked the link > probably uses FC, not CC, or does it explicitely add -lgfortran? To me it > looks like an issue in the openblas makefiles. It uses CC for linking - which points to gcc11 (on Leap/SLE) while FC which points to the stock gfortran is used to build the fortran sources. The latter may not be all that problematic, however, a binary may use other fortran libraries built with the stock gfortran compiler or be built/linked itself using this compiler. And, yes, the final link (done with $CC) adds -lgfortran. The problem is that we need to link C and Fortran objects together and make sure, the right libgfortran is used. I will try what happens if I naively set -lgfortran4. Likely, gcc11 will not find this library. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202690] New: peazip .desktop category is wrong (should be in utilities instead of system tools + peazip 8.8.0 update is out (package should be updated)
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202690 Bug ID: 1202690 Summary: peazip .desktop category is wrong (should be in utilities instead of system tools + peazip 8.8.0 update is out (package should be updated) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: c.j(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (posting 2 issues together as they concern the same package and are both very easy fixes). ISSUE 1 (peazip .desktop category is wrong with 2 different places for archive managers in the Applications menu): File-rooler (Gnome archive manager) is in "Utilities" > Categories=GTK;GNOME;Utility;Archiving;Compression;X-GNOME-Utilities; Peazip is also an archive manager , it is in "System Tools". This doesn't make sense to have both archive managers in different places (and they are both utilities). >Categories=Qt;KDE;Utility;System;Archiving; should be corrected into: >Categories=Qt;KDE;Utility;Archiving; ISSUE 2: peazip 8.7.0 is in the repo but peazip 8.8.0 is out. It's a very simple update that only requires to change the .spec version number to 8.8.0 and changing the source file url to https://github.com/peazip/PeaZip/releases/download/8.8.0/peazip-8.8.0.src.z… (I forked it myself, it builds perfectly) QUESTION: (while I'm here it makes sense to ask this here - I didn't find anything in the docs/wiki/google) Where can we flag packages out of date to inform the maintainers of the updates? -> Archlinux has a FLAG link on the package's information page for this. example: https://archlinux.org/packages/extra/x86_64/libreoffice-fresh/flag/ Do we always have to open a bugzilla report ? (this seems overkill, a flag like arch would make it easier/convenient for everybody imho). Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208684] AUDIT-0: Reconsider pam_kwallet security audit - and if already passed - add as a default.
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

1 0

[Bug 1203650] New: breeze-dark theme not applied to gtk2 apps
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203650 Bug ID: 1203650 Summary: breeze-dark theme not applied to gtk2 apps Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: c.j(a)tuta.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gtk2 apps don^t get the breeze dark them applied (gtk3 are fine). Example app to test / see the problem: "mediainfo-gui". Manually downloading the "breeze-dark-gtk" theme and applying it works, but this theme is a little different than the official one, so it will also change the gtk3 apps and make them not fully consistent with the other kde breeze theming. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1177260] Switching python-numpy to plain BLAS causes significant performance regression
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1177260 https://bugzilla.suse.com/show_bug.cgi?id=1177260#c50 --- Comment #50 from Richard Biener <rguenther(a)suse.com> --- Maybe you can just override LD? OTOH to get libgfortran linked the link probably uses FC, not CC, or does it explicitely add -lgfortran? To me it looks like an issue in the openblas makefiles. -- You are receiving this mail because: You are on the CC list for the bug.

1 0