February 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1195395] hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 https://bugzilla.suse.com/show_bug.cgi?id=1195395#c16 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #16 from Dirk Mueller <dmueller(a)suse.com> --- (In reply to B from comment #15) > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907 > I've switched to wicked service instead of networkmanager and the problem is > gone even with the 2.10 (standard version) wpa_supplicant Good news! > Issue in Networkmanager instead? unlikely, the logs show wpa_supplicant failing to connect though. I think this is confirmed by the finding in the debian BTS. when they reverted the patch that implements the SAE dbus interface that networkmanager is using, the connection worked. I'm not 100% confident that wicked can use WPA3, so wicked working might mean you're actually connecting via WPA2. if you have control over your wpa_supplicant.conf, please try whether adding pmf=2 or pmf=1 at the beginning of the file changes the situation. My current guess is that pmf=2 would make you able to connect again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195412] smb does not start if openSUSE-SLE-15.3-2022-283 is installed and smb.conf has printers set up
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195412 https://bugzilla.suse.com/show_bug.cgi?id=1195412#c1 Andreas Osterburg <andreas.osterburg(a)digide.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andreas.osterburg(a)digide.ne | |t --- Comment #1 from Andreas Osterburg <andreas.osterburg(a)digide.net> --- Same here. It seems that apparmor is the problem. My workaround: Add the following two lines to /etc/apparmor.d/local/usr.sbin.smbd /usr/lib64/samba/samba-bgqd ix, /run/samba/samba-bgqd.pid rw, and reload the appamor profile /sbin/apparmor_parser -r /etc/apparmor.d/usr.sbin.smbd That works for me. Another solution is (if applicable) disabling spoolss in global section of smb.conf: disable spoolss = yes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190041] xterm window is wrongly rendered when auto started on boot
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1190041 https://bugzilla.suse.com/show_bug.cgi?id=1190041#c8 --- Comment #8 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: desktopapps-gnome-x11 https://openqa.opensuse.org/tests/2169898 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183234] Console font shows Ì instead of UTF-8 line glyph U+2500 (0xe2 0x94 0x80) randomly
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1183234 https://bugzilla.suse.com/show_bug.cgi?id=1183234#c46 --- Comment #46 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: upgrade_Leap_15.0_kde https://openqa.opensuse.org/tests/2169767 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194208] [Build 20220101] openQA test fails in ustat01
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1194208 https://bugzilla.suse.com/show_bug.cgi?id=1194208#c7 --- Comment #7 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-ltp-syscalls@uefi_virtio-2G https://openqa.opensuse.org/tests/2169566 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193909] [Build 20211218] dovecot - invalid sample config
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1193909 https://bugzilla.suse.com/show_bug.cgi?id=1193909#c3 --- Comment #3 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_textmode https://openqa.opensuse.org/tests/2169392 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195360] Kernel 5.16.1-1 PAM issue after upgrading from 20220101 to 20220121
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195360 https://bugzilla.suse.com/show_bug.cgi?id=1195360#c8 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #8 from Enzo Matsumiya <ematsumiya(a)suse.com> --- (In reply to Joe S from comment #6) > > Back in 12/2020 I reported the issue with pam-config not having built in > > support for the pam_cifscreds.so module but I reported it here: > > > > https://github.com/SUSE/pam-config/issues/7 > > > > Would it be better to submit a separate bug request to have that support > > added so that I don't have to keep manually fixing the pam config files > > after most TW updates? > > Probably yes. Agreed. I'd suggest opening a new bug with pam maintainer and probably the security team as well. They'll be the ones to decide whether it's safe/ok to include/enable pam_cifscreds in the default install. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195395] hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 https://bugzilla.suse.com/show_bug.cgi?id=1195395#c13 --- Comment #13 from B <reiokorn(a)tutanota.com> --- (In reply to Dirk Mueller from comment #11) > thanks for the traces. so I switched to networkmanager as well, and it still > works here just fine. > > however, I found this which describes the same issue, also with > status_code=0x40 rejection: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907 > > > it looks like a defect on the fritzbox side according to the analysis there, > where WPA2+WPA3 transitional mode is not working as the AP is not indicating > it needs 11W, while it refused to connect without it. I would like to note that the previous version did not cause any problems, even with the WPA2+WPA3 transition mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195360] Kernel 5.16.1-1 PAM issue after upgrading from 20220101 to 20220121
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195360 https://bugzilla.suse.com/show_bug.cgi?id=1195360#c7 --- Comment #7 from Paulo Alcantara <palcantara(a)suse.com> --- (In reply to Joe S from comment #6) > Any idea when the fix will appear in the TW builds ? No idea. I will let you know when it gets applied upstream and backported to TW kernel. Then I'll build a TEST kernel so you can try it out. > I'm using tumbleweed_cli to control which TW build I'm using, which is > currently 20220121. > > Will the fix be included in those build repos too or will I need to update > to a later TW build? Sorry, but I don't know which tool is that. AFAICS, once it's backported, next update should have it. > Back in 12/2020 I reported the issue with pam-config not having built in > support for the pam_cifscreds.so module but I reported it here: > > https://github.com/SUSE/pam-config/issues/7 > > Would it be better to submit a separate bug request to have that support > added so that I don't have to keep manually fixing the pam config files > after most TW updates? Probably yes. Thank you for the detailed report! Really appreciate it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195395] hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10
by bugzilla_noreply＠suse.com 01 Feb '22

01 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.debian.org/1003 | |907 -- You are receiving this mail because: You are on the CC list for the bug.

1 0