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#c22 --- Comment #22 from B <reiokorn(a)tutanota.com> --- Just to make sure, I modified and added that parameter in /etc/wpa_supplicant.conf That's the right one, yes? I noticed that there is also a conf file with the same name in another place in the system in /etc/dbus-1/system.d -- 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 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 https://bugzilla.suse.com/show_bug.cgi?id=1195395#c21 --- Comment #21 from B <reiokorn(a)tutanota.com> --- (In reply to Dirk Mueller from comment #16) > (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. Tried both with your modified version - no change. No connection possible. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195013] No audio output/input found - Dell Vostro 7510
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195013 https://bugzilla.suse.com/show_bug.cgi?id=1195013#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Hm, it just takes time until the new kernel gets propagated into TW snapshot, unfortunately. You can try the latest stable 5.16.x kernel in OBS Kernel:stable repo, instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c4 --- Comment #4 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Michal Suchanek from comment #2) > But we don't need to reinstall bootloader on KMP removal, do we? No, and we don't. That only happens in the main kernel scriptlets. > LILO needed reinstall because it referenced specific blocks in the > filesystem rather than the filename. > > Do we have some scheme that copies the initrd (such as to the EFI partition) > that would require reinstall of bootloader when initrd changes? No idea. It might be a leftover from ancient past. (In reply to Michal Suchanek from comment #3) > we probably don't track if the ramdisk was built or rebuilt but that should > be feasible Not sure where you're heading here. When we remove kernel-default-extra, we must remove the initrd, *unless* we already know we'll remove kernel-default, too. I know it's true in >90% of cases, but that doesn't solve the problem that we don't know for sure. posttrans is really the only way. in posttrans we'll see that the kernel is gone, and we can't build an initrd for it. I have patches here that do this but they haven't had enought testing, and we won't merge them before 15.4 release. Sorry about that. -- 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 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195395 https://bugzilla.suse.com/show_bug.cgi?id=1195395#c20 --- Comment #20 from Marcus Meissner <meissner(a)suse.com> --- i switched my Friotzbox wlan to WPA2(CCMP) (so no WPA3) ... and the laptop now connects over wifi with dirks last wpa_supplicant. So there is some WPA3 fishyness. The Fritz!box 7430 has a a PMF setting "Unterst�tzung f�r gesch�tzte Anmeldungen von WLAN-Ger�ten (PMF) aktivieren" which is default enable for WPA3, but can be selectively enabkled for WPA2 only. -- 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#c8 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scabrero(a)suse.com --- Comment #8 from Samuel Cabrero <scabrero(a)suse.com> --- (In reply to Mathias Homann from comment #5) > > That worked, but the updated samba server does *not* offer any printers. Hi Mathias, in samba 4.13 the printer list was loaded in smbd startup and refreshed at regular intervals configured by the "printcap cache time" parameter. In samba 4.15 the list is no longer loaded in the startup and you have to wait until the cache times out for the printers to show up. Could you please confirm the printers show up after the configured printcap cache time? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195423] New: Setting the keyboard to German (with "dead" keys) without permanent effect
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195423 Bug ID: 1195423 Summary: Setting the keyboard to German (with "dead" keys) without permanent effect Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: 64bit OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: klaus.thoennissen(a)web.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- During the initial installation and later via YaST, the keyboard was set to German (with "dead" keys). Problem: After a reboot or after logging out and logging in, entering ' and e causes the character string 'e instead of ��. A workaround is possible with Compose ' and e, causes ��. The effect occurs in all applications and also in the console. Fixing the error in a running session: Call YaST - Hardware - System Keyboard Layout : In the configuration of the system keyboard is shown as active: German (with "dead" keys) now selection of German in the selection list and then again German (with "dead" keys). Exit with Apply From then on, entering ' and e correctly leads to �� But after logging out and logging in, the input is again without effect of the dead keys. The effect is reproducible on my three different computers with Leap 15.3 systems. Information on one of the systems: Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-150300.59.43.1 OS Type: 64-bit Processors: 6 �� Intel�� Core�� i5-9400 CPU @ 2.90GHz Memory: 7.5 GiB gfxcard: Intel UHD Graphics 630 (Desktop 9 Series) graphic-system: X11 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1195013] No audio output/input found - Dell Vostro 7510
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195013 https://bugzilla.suse.com/show_bug.cgi?id=1195013#c14 --- Comment #14 from Richard Costa <richard.costa(a)suse.com> --- (In reply to Takashi Iwai from comment #13) > Also the latest TW kernel (5.16.3 or later) should have the same fix. > Please verify with the latest kernel. It's already working on 5.16.2-1-default (TW), but probably due to the sof-firmware 2.0 package installation. Should I remove the sof-firmware package before upgrading the kernel? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c3 --- Comment #3 from Michal Suchanek <msuchanek(a)suse.com> --- we probably don't track if the ramdisk was built or rebuilt but that should be feasible -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195291] initrd is being rebuilt when kernel is being removed after kernel update
by bugzilla_noreply＠suse.com 02 Feb '22

02 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1195291 https://bugzilla.suse.com/show_bug.cgi?id=1195291#c2 --- Comment #2 from Michal Suchanek <msuchanek(a)suse.com> --- But we don't need to reinstall bootloader on KMP removal, do we? LILO needed reinstall because it referenced specific blocks in the filesystem rather than the filename. Do we have some scheme that copies the initrd (such as to the EFI partition) that would require reinstall of bootloader when initrd changes? -- You are receiving this mail because: You are on the CC list for the bug.

1 0