October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1187214] Leap 15.3: sle_version is not set
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1187214 https://bugzilla.suse.com/show_bug.cgi?id=1187214#c28 --- Comment #28 from Max Lin <mlin(a)suse.com> --- for the record, I did the same change for sle_version to 15.4 and 15.3 Respin. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190387] rpmlint: wrong warning for missing Requires
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190387 http://bugzilla.opensuse.org/show_bug.cgi?id=1190387#c8 --- Comment #8 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1190387) was mentioned in https://build.opensuse.org/request/show/924804 Factory / rpmlint -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184924] [Build 134.3] openQA test fails in kdump_and_crash - forced crash didn't result into expected reboot
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1184924 https://bugzilla.suse.com/show_bug.cgi?id=1184924#c24 --- Comment #24 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Tentative fix[1] send upstream. [1] https://lore.kernel.org/linux-efi/20211012082708.121931-1-iivanov@suse.de/T… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183518] Can not connect to enterprise wifi
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1183518 https://bugzilla.suse.com/show_bug.cgi?id=1183518#c15 --- Comment #15 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Peter Stolz from comment #14) > Created attachment 853054 [details] > wpa_supplicant.log > > wpa_supplicant.log after try to connect to enterprise wifi schueler-rfgs. Hi Clemens There are a few error in wpa_supplicant that makes it never successfully associate with AP. I saw that you're the bug owner of openSUSE:Factory/wpa_supplicant. Can you help take a look at this? > 1633942237.392358: SSL: SSL_connect:error in SSLv3/TLS write client hello > 1633942237.392370: SSL: SSL_connect - want more data > 1633942237.392381: SSL: 190 bytes pending from ssl_out Cheers -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186341] emacs-gtk crashes when hitting Ctrl-<space>
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186341 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.opensuse.or | |g/show_bug.cgi?id=1191517 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187651] BTRFS setup leads to unbootable system
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1187651 https://bugzilla.suse.com/show_bug.cgi?id=1187651#c13 Ihno Krumreich <ihno(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #13 from Ihno Krumreich <ihno(a)suse.com> --- Verified. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191556] New: yast inst_overview race condition?
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191556 Bug ID: 1191556 Summary: yast inst_overview race condition? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1961554/modules/star t_install/steps/3 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com CC: okurz(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-textmode+selinux@uefi fails in [start_install](https://openqa.opensuse.org/tests/1961554/modules/start_inst… In the inst_overview screen the test selects the security module to enable SELinux: https://openqa.opensuse.org/tests/1961554#step/enable_selinux/2 After it hit "OK" to enable selinux the test verifies that it sees the inst_overview screen complete again: https://openqa.opensuse.org/tests/1961554#step/enable_selinux/6 Now suddenly yast seems to notice it needs to redo the proposal: https://openqa.opensuse.org/tests/1961554#step/enable_selinux/7 That of course breaks the workflow as openqa already thought it's at a working inst_overview screen and can press the install button. There are some test in the history that pass so looks like a very quick flash of the screen that openQA sometimes doesn't even recognize. It only happens in text mode. The graphical tests work very reliable. Is there a way to avoid this behavior of the ncurses interface, ie not show a screen that has to be redone just the blink of an eye later? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1074057] qemu can't properly capture some keys in libreoffice under GNOME wayland
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1074057 https://bugzilla.suse.com/show_bug.cgi?id=1074057#c84 --- Comment #84 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: qam-regression-gnome@64bit-virtio-vga https://openqa.suse.de/tests/7378036 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 1174936] [doc] 6 Installation of Virtualization Components - Documentation does not mention differences between using Wicked and NetworkManager
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1174936 https://bugzilla.suse.com/show_bug.cgi?id=1174936#c11 --- Comment #11 from James Fehlig <jfehlig(a)suse.com> --- (In reply to James Fehlig from comment #10) > That's one way, but I _think_ the bridges created by nmcli should be usable > in the same fashion as those created via yast+wicked. If you have a working > setup, check if the "usual" vif config results in a working interface in a > VM. E.g. > > <interface type='bridge'> > <mac address='52:54:00:24:d4:6a'/> > <source bridge='br0'/> > <model type='virtio'/> > </interface> I moved my laptop to a wired connection and indeed this works the same as with yast+wicked managed bridges. IOW, once a bridge is created and "up'ed" with nmcli as you've documented, it can be used by VM's as already documented for wicked-manged bridges. > Also, the bridge should be available in virt-manager, for use by new VMs and > new vifs added to existing VMs. virt-manager allows selecting "Bridge device" from the "Network source" drop down, which then allows typing in the bridge name. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174936] [doc] 6 Installation of Virtualization Components - Documentation does not mention differences between using Wicked and NetworkManager
by bugzilla_noreply＠suse.com 11 Oct '21

11 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1174936 https://bugzilla.suse.com/show_bug.cgi?id=1174936#c10 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jfehlig(a)suse.com) | --- Comment #10 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Tom�� Ba��ant from comment #9) > @JimL How is such bridge used by VMs? As described in 'Optional: How to use > br0 with KVM' at the suggested URL? That's one way, but I _think_ the bridges created by nmcli should be usable in the same fashion as those created via yast+wicked. If you have a working setup, check if the "usual" vif config results in a working interface in a VM. E.g. <interface type='bridge'> <mac address='52:54:00:24:d4:6a'/> <source bridge='br0'/> <model type='virtio'/> </interface> Also, the bridge should be available in virt-manager, for use by new VMs and new vifs added to existing VMs. > > Changes in this area of the doc should also mention libvirt's interface > > driver not working with NM (comment #4). > > @Jim: Could you please put such sentence somewhere along > https://github.com/SUSE/doc-sle/pull/972/files#diff- > b18bc91f539e0e4275edf57ef26ae6457b297c409288f251f7e0566d6b75ddbeR290 ? I already wrote something in #4, but perhaps a bit long. How about this shorter version: libvirt's interface driver can be used to manage host network devices, e.g. ethernet, bridges, bonds, vlans, etc. The interface driver only works with wicked and is disabled if Network Manager is enabled. Use of the libvirt interface driver is discouraged in general, and it may be deprecated in a future libvirt release. -- You are receiving this mail because: You are on the CC list for the bug.

1 0