January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1211124] Path "/etc/SUSEConnect" from "/etc/containers/mounts.conf" (and others) doesn't exist on every container startup
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211124 https://bugzilla.suse.com/show_bug.cgi?id=1211124#c6 --- Comment #6 from Jason Record <jason.record(a)suse.com> --- (In reply to Jason Record from comment #5) > I found this error as well in SLE Micro 5.5 new install running a container > as a non-root user. > > cat /etc/containers/mounts.conf > # This configuration file specifies the default mounts for each container of > the > # tools adhering to this file (e.g., CRI-O, Podman, Buildah). The format of > the > # config is /SRC:/DST, one mount per line. > /etc/SUSEConnect:/etc/SUSEConnect > /etc/zypp/credentials.d/SCCcredentials:/etc/zypp/credentials.d/SCCcredentials > > My container starts, but I get the warning: > > podman run -dt -v scavol:/var/scatool:z -e MONITORING=1 -e > MONITORING_ID=ce4ebd84-bb19-4d42-a077-870ca0ad024d --name scamonitor > scatool:latest > > WARN[0000] Failed to mount subscriptions, skipping entry in > /etc/containers/mounts.conf: open /etc/zypp/credentials.d/SCCcredentials: > permission denied > > b5a3b675ffa6a41f4135648707bbec539342f716463b47546336bc63903a47ad > > However, since I do not need any access to the mounts, I did the following > to remove the errors. > > touch ${HOME}/.config/containers/mounts.conf I have also worked around it by running setfacl and giving my user rights to /etc/zypp/credentials.d/* -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211124] Path "/etc/SUSEConnect" from "/etc/containers/mounts.conf" (and others) doesn't exist on every container startup
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211124 https://bugzilla.suse.com/show_bug.cgi?id=1211124#c5 Jason Record <jason.record(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason.record(a)suse.com --- Comment #5 from Jason Record <jason.record(a)suse.com> --- I found this error as well in SLE Micro 5.5 new install running a container as a non-root user. cat /etc/containers/mounts.conf # This configuration file specifies the default mounts for each container of the # tools adhering to this file (e.g., CRI-O, Podman, Buildah). The format of the # config is /SRC:/DST, one mount per line. /etc/SUSEConnect:/etc/SUSEConnect /etc/zypp/credentials.d/SCCcredentials:/etc/zypp/credentials.d/SCCcredentials My container starts, but I get the warning: podman run -dt -v scavol:/var/scatool:z -e MONITORING=1 -e MONITORING_ID=ce4ebd84-bb19-4d42-a077-870ca0ad024d --name scamonitor scatool:latest WARN[0000] Failed to mount subscriptions, skipping entry in /etc/containers/mounts.conf: open /etc/zypp/credentials.d/SCCcredentials: permission denied b5a3b675ffa6a41f4135648707bbec539342f716463b47546336bc63903a47ad However, since I do not need any access to the mounts, I did the following to remove the errors. touch ${HOME}/.config/containers/mounts.conf -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219191] VUL-0: gpg2: Smartcard generation keeps an unprotected backup key on disk
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219191 https://bugzilla.suse.com/show_bug.cgi?id=1219191#c1 --- Comment #1 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- I don't see a CVE assigned to this. Factory submission: sr#1141569 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219195] /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min increased from 6.6. to 6.7 way too much
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219195 https://bugzilla.suse.com/show_bug.cgi?id=1219195#c1 Vasilis Liaskovitis <vliaskovitis(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vliaskovitis(a)suse.com --- Comment #1 from Vasilis Liaskovitis <vliaskovitis(a)suse.com> --- The change was possibly introduced in: commit 1958946858a62b6b5392ed075aa219d199bcae39 Author: Ma Jun <Jun.Ma2(a)amd.com> Date: Thu Oct 12 09:33:45 2023 +0800 drm/amd/pm: Support for getting power1_cap_min value Support for getting power1_cap_min value on smu13 and smu11. For other Asics, we still use 0 as the default value. Signed-off-by: Ma Jun <Jun.Ma2(a)amd.com> Reviewed-by: Kenneth Feng <kenneth.feng(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> The above commit may also be an indirect fix for this upstream issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2992 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217613] Leap 15.6 not reviving from suspend on '12 MacPro w/nvidia card
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217613 https://bugzilla.suse.com/show_bug.cgi?id=1217613#c21 --- Comment #21 from Fritz Hudnut <non.space.1(a)gmail.com> --- Today, my Manjaro 23.1.3 system running their 5.15.146-1-MANJARO kernel failed to revive from suspend . . . using grub "advanced options" that rolled the kernel back to 5.4.266-1-MANJARO . . . and the problem went away, system revives the display as per request. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211571] nmap non-OSI approved "Nmap Public Source License" NPSL
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211571 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219193] New: 5G Wifi Stopped Working after Kernel 6.7.1 Upgrade
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219193 Bug ID: 1219193 Summary: 5G Wifi Stopped Working after Kernel 6.7.1 Upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ismettogay+linux(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 Build Identifier: Today, I have upgraded Tumbleweed release to 20240124 and 5G Wifi stopped working after the upgrade. Yet, 2G Wifi connection still works. My WLAN controller: Intel Dual Band Wireless-AC 7265 My Wifi Modem Router: ASUS DSL-AC51 Reproducible: Always Steps to Reproduce: 1. Connect to a 5G network 2. Wait 5-10 seconds Actual Results: You get the "Connection [SSID-5G] deactivated. The Wifi network could not be found" error. Expected Results: It should connect to the 5G network. A similar post on reddit for Arch Linux: https://www.reddit.com/r/archlinux/comments/19e103k/anyone_else_having_prob… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219192] New: On the intel AX200 WiFi there is an issue with 5 GHz (2.4 GHz is fine)
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219192 Bug ID: 1219192 Summary: On the intel AX200 WiFi there is an issue with 5 GHz (2.4 GHz is fine) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: R_Nik_C(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is no way to connect to WiFi at 5 GHz (2.4 GHz is fine), there is a "configuration interface" and that's it. When I boot older - 6.6.11 kernel, everything seems fine.. issues are on newer - 6.7.1 kernel. > lspci | grep Network 04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) > zypper se -is iwlwifi kernel-default NetworkManager S | Name | Type | Version | Arch | Repository ---+----------------------------------+---------+--------------+--------+------------------ i+ | kernel-default | package | 6.6.11-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.6.10-1.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-default-devel | package | 6.6.11-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.6.10-1.1 | x86_64 | (System Packages) i | kernel-default-devel | package | 6.7.1-1.1 | x86_64 | repo-oss i | kernel-firmware-iwlwifi | package | 20240115-1.1 | noarch | repo-oss i | libKF5NetworkManagerQt6 | package | 5.114.0-1.1 | x86_64 | repo-oss i+ | NetworkManager | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-bluetooth | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-branding-openSUSE | package | 42.1-6.1 | noarch | repo-oss i | NetworkManager-dns-dnsmasq | package | 1.0-1.2 | noarch | repo-oss i | NetworkManager-openconnect | package | 1.2.10-2.1 | x86_64 | repo-oss i | NetworkManager-openvpn | package | 1.10.2-3.1 | x86_64 | repo-oss i | NetworkManager-pptp | package | 1.2.12-2.2 | x86_64 | repo-oss i | NetworkManager-tui | package | 1.44.2-4.2 | x86_64 | repo-oss i | NetworkManager-wwan | package | 1.44.2-4.2 | x86_64 | repo-oss >> 2.4GHz connected, then I tried switch to 5GHz. >> When it couldn't do that, it connected to 2.4 again. >> here dmesg about that. [ 2116.959020] wlp4s0: AP is in CSA process, reject auth [ 2132.615435] wlp4s0: AP is in CSA process, reject auth [ 2143.199413] wlp4s0: AP is in CSA process, reject auth [ 2159.041293] wlp4s0: 80 MHz not supported, disabling VHT [ 2159.061350] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 2159.062684] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 2159.094116] wlp4s0: authenticated [ 2159.098723] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 2159.108670] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 2159.176913] wlp4s0: associated [ 4993.544199] wlp4s0: deauthenticating from b0:4e:26:80:7f:03 by local choice (Reason: 3=DEAUTH_LEAVING) [ 4994.135435] wlp4s0: AP is in CSA process, reject auth [ 4997.149938] wlp4s0: AP is in CSA process, reject auth [ 4998.975834] wlp4s0: AP is in CSA process, reject auth [ 5000.552059] wlp4s0: AP is in CSA process, reject auth [ 5010.486930] wlp4s0: AP is in CSA process, reject auth [ 5020.067885] wlp4s0: AP is in CSA process, reject auth [ 5032.642366] wlp4s0: AP is in CSA process, reject auth [ 5045.645518] wlp4s0: AP is in CSA process, reject auth [ 5056.675184] wlp4s0: AP is in CSA process, reject auth [ 5073.646655] wlp4s0: AP is in CSA process, reject auth [ 5084.415274] wlp4s0: AP is in CSA process, reject auth [ 5099.885612] wlp4s0: 80 MHz not supported, disabling VHT [ 5099.908004] wlp4s0: authenticate with b0:4e:26:80:7f:03 (local address=b0:7d:64:63:f2:59) [ 5099.909377] wlp4s0: send auth to b0:4e:26:80:7f:03 (try 1/3) [ 5099.941025] wlp4s0: authenticated [ 5099.946520] wlp4s0: associate with b0:4e:26:80:7f:03 (try 1/3) [ 5099.965937] wlp4s0: RX AssocResp from b0:4e:26:80:7f:03 (capab=0x411 status=0 aid=2) [ 5100.034375] wlp4s0: associated > dmesg | grep iwlwifi [ 7.297412] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002) [ 7.311782] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000 [ 7.311820] iwlwifi 0000:04:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100 [ 7.346507] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 7.346525] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 7.346760] iwlwifi 0000:04:00.0: loaded firmware version 77.ad46c98b.0 cc-a0-77.ucode op_mode iwlmvm [ 7.528107] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 7.693344] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100 [ 7.769562] iwlwifi 0000:04:00.0: base HW address: b0:7d:64:63:f2:59 [ 7.790114] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0 [ 9.613899] iwlwifi 0000:04:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1219191] VUL-0: gpg2: Smartcard generation keeps an unprotected backup key on disk
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219191 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219191] New: VUL-0: gpg2: Smartcard generation keeps an unprotected backup key on disk
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219191 Bug ID: 1219191 Summary: VUL-0: gpg2: Smartcard generation keeps an unprotected backup key on disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pmonrealgonzalez(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It was discovered that GnuPG before 2.4.4 kept an additional unprotected copy of the encryption subkey on disk. 2.4.2, 2.4.3, 2.2.42 affected if the card generation was done with the command gpg --card-edit. If the smartcard was created without a backup of the encryption key the problem does not show up either. Having a password protected backup key is expected behavior. References: https://gnupg.org/blog/20240125-smartcard-backup-key.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0