February 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180761] Virtualbox shared volume mounting as root
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1180761 https://bugzilla.suse.com/show_bug.cgi?id=1180761#c19 --- Comment #19 from Rihards Olups <richlv(a)nakts.net> --- Created https://www.virtualbox.org/ticket/20168 . Just to check, the changes, mentioned in #c8, couldn't have negatively impacted this, right? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180761] Virtualbox shared volume mounting as root
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1180761 https://bugzilla.suse.com/show_bug.cgi?id=1180761#c18 --- Comment #18 from Rihards Olups <richlv(a)nakts.net> --- Thanks, will do. It worked a few versions ago, hopefully they will be able to spot where the regression is. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181657] VUL-1: sudo: Ineffective NO_ROOT_MAILER and Baron Samedit
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181657 https://bugzilla.suse.com/show_bug.cgi?id=1181657#c2 Alexandros Toptsoglou <atoptsoglou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suseino(a)riseup.net --- Comment #2 from Alexandros Toptsoglou <atoptsoglou(a)suse.com> --- *** Bug 1181712 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180761] Virtualbox shared volume mounting as root
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1180761 https://bugzilla.suse.com/show_bug.cgi?id=1180761#c17 --- Comment #17 from Larry Finger <Larry.Finger(a)gmail.com> --- It appears that the mac host version behaves differently than the x86 variety. All I can suggest is that you file a defect with Oracle/VirtualBox (https://www.virtualbox.org/wiki/Bugtracker) on this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181680] New: Wrong LIBEXECDIR path in cmake
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181680 Bug ID: 1181680 Summary: Wrong LIBEXECDIR path in cmake Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The upstream GNUInstallDirs.cmake module has a hardcoded "libexec" path for CMAKE_INSTALL_LIBEXECDIR, whilst the %{_libexecdir} macro points at /usr/lib. Can this be rectified? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1181377] [Enhancement] Support GCC 11's x86-64 Microarchitecture Feature Levels for more performance
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181377 https://bugzilla.suse.com/show_bug.cgi?id=1181377#c7 --- Comment #7 from Ryan Bach <romulasry(a)protonmail.com> --- https://build.opensuse.org/package/show/Base:System/glibc 2.33 is now in Base:System -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181242] lvm[630]: Udev database has incomplete information about device /dev/sda.
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181242 https://bugzilla.suse.com/show_bug.cgi?id=1181242#c8 --- Comment #8 from Suse User <suseino(a)riseup.net> --- > did you change external_device_info_source = "udev" to external_device_info_source = "none" No, I did not. Also I am not sure if I understand. Should I do it? (i.e. are you suggesting it as a workaround or just asking?) > We need the boot log if you want us to help. If you can't provide everything, remove those pieces that you consider sensitive. Here is a much larger chunk including all lines between the first and last mention of 'lvm' (case insensitive) + extra lines: https://susepaste.org/17c4c0fb > I've been in this business for 20 years, and never encountered anyone claiming that his boot log contained private information. Learn something new every day. By 'private' I mean stuff that should not be shared publicly on a site which everyone can access and where it will stay for many years. This includes open ports, serial numbers or other sensitive info. This is not a testing system. I am sure that you are quite well aware that logs are not something public. Let me know if you need anything else from me. I highly value your work and I hope the bugs I report will help to improve the quality of the product for the whole community. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174365] VM does not shutdown on host reboot
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1174365 https://bugzilla.suse.com/show_bug.cgi?id=1174365#c12 --- Comment #12 from Klaus Mueller <andihartmann(a)freenet.de> --- A completely other example: Given is a standard KDE session (normal user is logged in). In the KDE konsole, a VM is started with "virsh start VM". The VM itself doesn't have any graphical window (-> no SDL configured). The only way to reach this VM is via net or vnc. If you end this KDE session (logout), the VM continuous - isn't stopped. That's expected and ok. The VM completely runs outside of a systemd service definition. If you now restart the host via systemctl reboot or maybe do a shutdown via systemctl, the VM is suspended, too. Iow: there must be a way, how libvirtd is informed about the shutdown / reboot - of the host independently of a systemd service definition. This way seems to be used always - even if there is service definition, which cares about running VMs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181339] RTL8723BS Bluetooth not working , but wifi works !
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181339 https://bugzilla.suse.com/show_bug.cgi?id=1181339#c27 --- Comment #27 from Takashi Iwai <tiwai(a)suse.com> --- Could you tell BT works on which Ubuntu kernel -- as new as possible? If it's close to 5.10 / 5.11, we can get the config and try to build a similar kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181339] RTL8723BS Bluetooth not working , but wifi works !
by bugzilla_noreply＠suse.com 02 Feb '21

02 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181339 https://bugzilla.suse.com/show_bug.cgi?id=1181339#c26 --- Comment #26 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. The lsinitrd output indicated that no bluetooth-related modules are involved, so my previous guess was wrong, it happens after the initrd. Hmm. -- You are receiving this mail because: You are on the CC list for the bug.

1 0