February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208704] New: /etc/sysctl.conf handling
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208704 Bug ID: 1208704 Summary: /etc/sysctl.conf handling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: lnussel(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fbui(a)suse.com Blocks: 1208319 Found By: --- Blocker: --- systemd-sysctl does not load /etc/sysctl.conf(https://github.com/systemd/systemd/commit/04bf3c1a60d82791e0320381e9268f727708f776). So far systemd packaged a static link in /usr/lib/sysctl.d/99-sysctl.conf but that fails in brp check if no package provides /etc/sysctl.conf. Therefore as an interim solution aaa_base can create a symlink in /etc/sysctl.d instead. TODO: get upstream to read /etc/sysctl.conf agin or if that fails move it with some migration script. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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#c52 --- Comment #52 from Richard Biener <rguenther(a)suse.com> --- (In reply to Egbert Eich from comment #51) > (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. Of course not - it doesn't work this way. You can link with the stock gfortran compiler instead. Note you possibly get ABI mismatches when building with the stock gfortran but then link against the wrong library. When you mix compilers you really should know what you are doing ;) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207827] New: Can not install opensuse tumbleweed in second nvme - issue after kernel 5.15 LTS
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207827 Bug ID: 1207827 Summary: Can not install opensuse tumbleweed in second nvme - issue after kernel 5.15 LTS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: freitasmgustavo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi there, I have open a thread on forum first, releated with my issue that i am not able to install opensuse on my second nvme: https://forums.opensuse.org/t/can-not-install-opensuse-tumbleweed-in-second… the problem is that ADATA is repeating in all nvme same EUI64, and the kernel bugged, only see one nvme. my nvme is ADATA SX6000PNP. I do not know the process to open a patch for linux kernel, however i found where we can do a fix on linux source code: https://github.com/torvalds/linux/blob/master/drivers/nvme/host/pci.c#L3422 I have 2 nvme identically, as following output command. both 1TB. [gustavo@home ~]$ /sbin/lspci -nnk | grep Non-Volatile 06:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5763] (rev 01) 07:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5763] (rev 01) [gustavo@ ~]$ sudo nvme id-ctrl /dev/nvme1 NVME Identify Controller: vid : 0x10ec ssvid : 0x10ec sn : 2J4120007707 mn : ADATA SX6000PNP fr : V9002s94 [gustavo@ ~]$ sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x10ec ssvid : 0x10ec sn : 2K2129Q696LA mn : ADATA SX6000PNP fr : V9002s94 -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[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

https://bugzilla.suse.com/show_bug.cgi?id=1208684 https://bugzilla.suse.com/show_bug.cgi?id=1208684#c3 --- Comment #3 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- (In reply to fabian(a)ritter-vogt.de from comment #2) > The module is in the distro (it was even long before bug 993806), but not installed by default. Quoting you from that bug report: > > > Enabling it by default is a no-go at the moment from security perspective. > > If this changed meanwhile, we can include it in the Plasma pattern selection. Ah I missed that point. Well then I will take another tour of the current codebase and judge from that whether this restriction can be lifted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199685] New: [doc] 3 Änderungen beim Paketieren
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199685 Bug ID: 1199685 Summary: [doc] 3 �nderungen beim Paketieren Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: lukas.kucharczyk(a)suse.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: lubos.kocman(a)suse.com Found By: --- Blocker: --- 3 �nderungen beim Paketieren: https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.4/#sec.packa… Broken Link: https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1208215] New: [doc] broken links to openSUSE startup guide in release notes
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208215 Bug ID: 1208215 Summary: [doc] broken links to openSUSE startup guide in release notes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: lukas.kucharczyk(a)suse.com Reporter: adaugherity(a)tamu.edu QA Contact: lubos.kocman(a)suse.com Found By: --- Blocker: --- In Section 2 - System Upgrade <https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.4/#upgrade> There is a link which returns 404: https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… I assume this is intended to link to this? https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-u… Note the "book.opensuse.startup" vs. "book-startup" component. There's another bad link in Section 1 -- https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… which presumably should be: https://doc.opensuse.org/documentation/leap/startup/html/book-startup/part-… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1208659] New: Dist-upgrade made taskbar/init menu disappear
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208659 Bug ID: 1208659 Summary: Dist-upgrade made taskbar/init menu disappear 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: rosuna(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Customer Blocker: --- I was running the snapshot from Feb 10th. When applying the snapshot from Feb 13th (or 14th, unsure), I had problems with nvidia drivers (see bug #1208645 ), as there might be a regression. In addition, the "init bar", "menu bar", "task bar", or whatever it should be called, has disappeared from my user. I've worked around the problem with nvidia by manually installing the previous version, and now all my screens are working fine, however the problem with that bar in the bottom having disappear is still there. I've created a new test user and logged it with it, the bar exists. I've tried to kill the plasmasession and run it again, but that did not change anything (other than I think it is crashing, because the background image did not come back). I have too many configurations to create a new .config directory and would like to avoid this. Rolling back to my btrfs snapshot I created previously fixes everything. Please let me know which logs would be useful to debug this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1208659] Dist-upgrade made taskbar/init menu disappear
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208659 https://bugzilla.suse.com/show_bug.cgi?id=1208659#c9 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rosuna(a)suse.com) --- Comment #9 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Ra�l Osuna from comment #6) > debuginfo (in case it's needed) uploaded here: > https://ziu.nue.suse.com/Bug1208659/ That's what the system downloaded as debuginfo, it's just what the -debuginfo RPMs contain. > Is it something to worry about? Because every time I rolled back to the previous snapshot before the "zypper dup", the bar was there and every time I patched it disappeared. Anyway the solution was easy. Can you attach the old config? There's something in there which the old plasma accepted but the new one doesn't. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208689] AUDIT-0: kde-inotify-survey: review of D-Bus service AND Polkit actions
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208689 https://bugzilla.suse.com/show_bug.cgi?id=1208689#c2 --- Comment #2 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Note that this package emits a dbus-communication-not-allowed rpmlint warning: https://github.com/rpm-software-management/rpmlint/issues/1008 It looks like no one is allowed to talk to this D-Bus service, which can make sense in some special scenarios, but should be looked into. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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

https://bugzilla.suse.com/show_bug.cgi?id=1208684 https://bugzilla.suse.com/show_bug.cgi?id=1208684#c1 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian(a)ritter-vogt.de, | |matthias.gerstner(a)suse.com --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- The major audit of the module was done in bug 993806 and the PAM module was not in good shape back then. But can you please explain what you mean by "make it default"? As security team we only decide whether a PAM module is allowed into the distribution at all, not really how and when it is installed and configured. So maybe you need to involve the package's maintainer rather than us. The package does not seem to have a dedicated maintainer any more though. Adding Fabian as main contributer and KDE project maintainer instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 0