February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207944] intel_iommu=on Is not work on Alderlake
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207944 https://bugzilla.suse.com/show_bug.cgi?id=1207944#c3 Dario Faggioli <dfaggioli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfaggioli(a)suse.com, | |kokeko(a)mac.com Flags| |needinfo?(kokeko(a)mac.com) --- Comment #3 from Dario Faggioli <dfaggioli(a)suse.com> --- (In reply to Michiya Hagimoto from comment #0) > HI I update my leap 15.4 transactional-server from Skylake(6th core)to > Alderlake(12th core) nuc. > > nuc12wshi5 > Intel Core i5-1240P > 32GB DDR4 memory > > I add "intel_iommu=on" on grub.cfg command line, but cannot pathtrough pcie > device. > Tell us more about this "cannot". E.g., can you give us (a lot of, possibly!) more details about how you're trying to do this pcie device passthrough? Do you have any (as specific as possible) error message that you are getting and you can share? Can we know more about the system hardware and software? > On Alderlake platform cannot use PCI pathtrough? > Can we have full logs (e.g., dmesg) of both the old and working Skylake system, and of the new and not working one? (I suppose not, as the Skylake system may be gone... But I tried) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208056] New: AUDIT-FIND: colord: LPE from colord to root (with fs.protected_hardlinks=0)
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208056 Bug ID: 1208056 Summary: AUDIT-FIND: colord: LPE from colord to root (with fs.protected_hardlinks=0) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There's a sub-optimal construct in the %post section of colord.spec: 192 # Fix ownership of /var/lib/colord from first packages (in 12.1) 193 test ! -d %{_localstatedir}/lib/colord || chown -R colord:colord %{_localstatedir}/lib/colord On systems with fs.protected_hardlinks=0, this allows the user `colord` to escalate to root: # id uid=466(colord) gid=466(colord) groups=466(colord) # cat /proc/sys/fs/protected_hardlinks 0 # ls -l /test/shadow -rw------- 1 root root 0 Feb 8 13:00 /test/shadow # ln /test/shadow /var/lib/colord/ ... then, after the colord package is updated ... # ls -l /test/shadow -rw------- 2 colord colord 0 Feb 8 13:00 /test/shadow This is not a security vulnerability per se because all our distributions have protected_hardlinks=1 by default, and we advice our customers not to disable it [1]. Nevertheless it would be preferable to avoid such constructs. In this case we simply delete the entire line, because the distros that require it have long reached their end of life. [1] https://www.suse.com/support/kb/doc/?id=000019565 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207943] btrfs i/o error on Alderlake
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207943 https://bugzilla.suse.com/show_bug.cgi?id=1207943#c5 --- Comment #5 from Michiya Hagimoto <kokeko(a)mac.com> --- Today, I try to no-hostonly setup on drauct. 1. make configfile vim /etc/dracut.conf.d/99-no-hostonly.conf hostonly=no 2. regenerate initrd sudo transactional-update initrd grub.cfg 3. reboot & no error on 1hour after. I confirm initrd size is incruease. before ls -lh /boot/ total 91M -rw-r--r-- 1 root root 1.7K Jun 1 2022 boot.readme -rw-r--r-- 1 root root 246K Jan 16 10:10 config-5.14.21-150400.24.41-default drwxr-xr-x 3 root root 16K Jan 1 1970 efi drwxr-xr-x 1 root root 98 Feb 7 15:41 grub2 lrwxrwxrwx 1 root root 35 Jan 27 11:22 initrd -> initrd-5.14.21-150400.24.41-default -rw------- 1 root root 58M Feb 7 15:41 initrd-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 446K Jan 16 10:44 symvers-5.14.21-150400.24.41-default.gz -rw-r--r-- 1 root root 484 Jan 16 10:44 sysctl.conf-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 4.9M Jan 16 10:37 System.map-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 17M Jan 16 10:49 vmlinux-5.14.21-150400.24.41-default.gz lrwxrwxrwx 1 root root 36 Jan 27 11:22 vmlinuz -> vmlinuz-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 11M Jan 16 12:48 vmlinuz-5.14.21-150400.24.41-default after ls -lh /boot/ total 175M -rw-r--r-- 1 root root 1.7K Jun 1 2022 boot.readme -rw-r--r-- 1 root root 246K Jan 16 10:10 config-5.14.21-150400.24.41-default drwxr-xr-x 3 root root 16K Jan 1 1970 efi drwxr-xr-x 1 root root 98 Feb 8 13:37 grub2 lrwxrwxrwx 1 root root 35 Jan 27 11:22 initrd -> initrd-5.14.21-150400.24.41-default -rw------- 1 root root 142M Feb 8 13:37 initrd-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 446K Jan 16 10:44 symvers-5.14.21-150400.24.41-default.gz -rw-r--r-- 1 root root 484 Jan 16 10:44 sysctl.conf-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 4.9M Jan 16 10:37 System.map-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 17M Jan 16 10:49 vmlinux-5.14.21-150400.24.41-default.gz lrwxrwxrwx 1 root root 36 Jan 27 11:22 vmlinuz -> vmlinuz-5.14.21-150400.24.41-default -rw-r--r-- 1 root root 11M Jan 16 12:48 vmlinuz-5.14.21-150400.24.41-default it is low cost for safety. I will set no-hostonly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207484] New: openssl-3: regression regarding certificate path availability
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207484 Bug ID: 1207484 Summary: openssl-3: regression regarding certificate path availability Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pmonrealgonzalez(a)suse.com Reporter: amajer(a)suse.com QA Contact: security-team(a)suse.de CC: jsikes(a)suse.com, meissner(a)suse.com Found By: --- Blocker: --- While testing why nodejs18 unit tests were failing in openssl-1_1 vs. openssl-3, I found that the errors are a result of unavailable directory /var/lib/ca-certificates/openssl If this directory does not exist, many unit tests are failing with errors similar to 'Error: error:16000069:STORE routines::unregistered scheme' ~/rpmbuild/BUILD/node-v18.13.0> ./node18 test/sequential/test-tls-connect.js node:assert:750 throw err; ^ AssertionError [ERR_ASSERTION]: The input did not match the regular expression /no cipher match/i. Input: 'Error: error:16000069:STORE routines::unregistered scheme' at Object.<anonymous> (/home/abuild/rpmbuild/BUILD/node-v18.13.0/test/sequential/test-tls-connect.js:53:10) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) at Module._load (node:internal/modules/cjs/loader:922:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:23:47 { generatedMessage: true, code: 'ERR_ASSERTION', actual: Error: error:16000069:STORE routines::unregistered scheme at configSecureContext (node:internal/tls/secure-context:230:11) at Object.createSecureContext (node:_tls_common:117:3) at Object.connect (node:_tls_wrap:1636:48) at /home/abuild/rpmbuild/BUILD/node-v18.13.0/test/sequential/test-tls-connect.js:54:9 at getActual (node:assert:757:5) at Function.throws (node:assert:903:24) at Object.<anonymous> (/home/abuild/rpmbuild/BUILD/node-v18.13.0/test/sequential/test-tls-connect.js:53:10) at Module._compile (node:internal/modules/cjs/loader:1218:14) at Module._extensions..js (node:internal/modules/cjs/loader:1272:10) at Module.load (node:internal/modules/cjs/loader:1081:32) { opensslErrorStack: [ 'error:0A0000B9:SSL routines::no cipher match', 'error:80000002:system library::No such file or directory' ], library: 'STORE routines', reason: 'unregistered scheme', code: 'ERR_OSSL_OSSL_STORE_UNREGISTERED_SCHEME' }, expected: /no cipher match/i, operator: 'throws' } Node.js v18.13.0 If I simply create this directory, the unit tests pass as openssl-3 doesn't generate errors. One possible solution is to ship empty directory in the main library package. Alternative is to track down why OpenSSL is throwing these weird errors when this path is simply missing. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1207940] [Build 20230205] openssl-3: tpm unable to enable public key encoding
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207940 https://bugzilla.suse.com/show_bug.cgi?id=1207940#c2 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|pmonrealgonzalez(a)suse.com |otto.hollmann(a)suse.com --- Comment #2 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- Assigning back to the OpenSSL maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c11 --- Comment #11 from roke beedell <rokejulianlockhart+1674683091(a)outlook.com> --- Regarding https://bugzilla.suse.com/show_bug.cgi?id=1208003#c7, any idea of whether there's an issue in this tracker to rebase with upstream? I ask because it is noticeably older than Mozilla and Fedora's instances. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c10 --- Comment #10 from Steffen Winterfeldt <snwint(a)suse.com> --- FWIW: https://github.com/openSUSE/installation-images/pull/623 This makes the install media boot; it does not add support in our installer, though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206674] New: No network (wicked) after 23-12-2022 updates
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206674 Bug ID: 1206674 Summary: No network (wicked) after 23-12-2022 updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: alessandro.sturniolo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863670 --> http://bugzilla.opensuse.org/attachment.cgi?id=863670&action=edit Network related log files and configurations. Today (23-12-2022) I have updated my system, and after reboot (there was a new kernel version), network no longer worked. After a while I realized that the interfaces remained down, so if I manually bring them up (ip link set devName up), network came back to works. Currently, after every system restart, I have to bring up manually my network interfaces, to get the network to works. Obviously before today updates, my network it always worked without problems for years. My network setup is based on wicked (no NetworkManager), has two network interfaces (enp3s0 and enp4s0) configured as slaves of a bonding device (bond0). I followed these instructions https://en.opensuse.org/index.php?title=openSUSE:Bugreport_wicked and I've collected some files that I attach to this report. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1207928] Rust 1.67 breaks rusticl build in Mesa:drivers (rust upstream fix available in git)
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207928 https://bugzilla.suse.com/show_bug.cgi?id=1207928#c10 --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- IIRC --> IIUC -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207928] Rust 1.67 breaks rusticl build in Mesa:drivers (rust upstream fix available in git)
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207928 https://bugzilla.suse.com/show_bug.cgi?id=1207928#c9 --- Comment #9 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to William Brown from comment #8) > Okay, I guess we just have to wait on a .1 release then ... I guess so, if this is what they mean with a 'point release'. If we need to update urgently please let me know. I think it's possible to temporarily buildrequire rust 1.66 by Mesa (IIRC; untested though). But we then need to track this, so I won't forget to go back to buildrequire rust without version number. -- You are receiving this mail because: You are on the CC list for the bug.

1 0