April 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1198002] New: VUL-1: CVE-2022-1201: mruby: NULL Pointer Dereference in mrb_vm_exec is capable of making the mruby interpreter crash
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198002 Bug ID: 1198002 Summary: VUL-1: CVE-2022-1201: mruby: NULL Pointer Dereference in mrb_vm_exec is capable of making the mruby interpreter crash Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/327960/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Ruby Assignee: rpm(a)fthiessen.de Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-1201 NULL Pointer Dereference in mrb_vm_exec with super in GitHub repository mruby/mruby prior to 3.2. This vulnerability is capable of making the mruby interpreter crash, thus affecting the availability of the system. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1201 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1201 https://github.com/mruby/mruby/commit/00acae117da1b45b318dc36531a7b0021b809… http://www.cvedetails.com/cve/CVE-2022-1201/ https://huntr.dev/bounties/6f930add-c9d8-4870-ae56-d4bd8354703b -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1188238] [RPi 3 B+] bluetooth command tx timeout and reset failure
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1188238 https://bugzilla.suse.com/show_bug.cgi?id=1188238#c29 --- Comment #29 from Dominik Heidler <dheidler(a)suse.com> --- can we apply it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197969] No repository is present on the system after installing the Default .tar.xz image
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197969 https://bugzilla.suse.com/show_bug.cgi?id=1197969#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- you could do it via: 000release-packages / Leap-Micro-release.spec that could ship /etc/zypp/repos.d/ files. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197969] No repository is present on the system after installing the Default .tar.xz image
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197969 https://bugzilla.suse.com/show_bug.cgi?id=1197969#c3 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- why is there no install process? what kind of image is this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197969] No repository is present on the system after installing the Default .tar.xz image
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197969 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197980] Compose key does not work as expected on Swiss Keyboard (same as bug 1142273 for OS 15.1)
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197980 https://bugzilla.suse.com/show_bug.cgi?id=1197980#c13 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #13 from Steffen Winterfeldt <snwint(a)suse.com> --- So this looks finally fixed. For Leap, I would go with changing the setting manually as Stefan suggested. 'localectl set-keymap ch' should in theory do the trick (including a reboot). You can check /etc/vconsole.conf to make sure the setting has been changed correctly. Note that editing vconsole.conf with an editor manually is not that a good idea. Always use localectl as it syncronizes the changes across the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197980] Compose key does not work as expected on Swiss Keyboard (same as bug 1142273 for OS 15.1)
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197980 https://bugzilla.suse.com/show_bug.cgi?id=1197980#c12 --- Comment #12 from Steffen Winterfeldt <snwint(a)suse.com> --- And this on Tumbleweed: # cat /etc/vconsole.conf KEYMAP=ch FONT=eurlatgr.psfu FONT_MAP= FONT_UNIMAP= # localectl System Locale: LANG=de_DE.UTF-8 VC Keymap: ch X11 Layout: ch X11 Model: microsoftpro X11 Options: terminate:ctrl_alt_bksp # setxkbmap -print xkb_keymap { xkb_keycodes { include "evdev+aliases(qwertz)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+ch+inet(evdev)+terminate(ctrl_alt_bksp)" }; xkb_geometry { include "pc(pc104)" }; }; -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197980] Compose key does not work as expected on Swiss Keyboard (same as bug 1142273 for OS 15.1)
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197980 https://bugzilla.suse.com/show_bug.cgi?id=1197980#c11 --- Comment #11 from Steffen Winterfeldt <snwint(a)suse.com> --- The patch got probably caught in the middle the keyboard refactoring. :-( Anyway, I did some test installs and got this on Leap 15.3: # cat /etc/vconsole.conf KEYMAP=sg-latin1 FONT=eurlatgr.psfu FONT_MAP= FONT_UNIMAP= # localectl System Locale: LANG=de_DE.UTF-8 VC Keymap: sg-latin1 X11 Layout: ch X11 Model: pc105 X11 Variant: de_nodeadkeys X11 Options: terminate:ctrl_alt_bksp # setxkbmap -print xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+ch(de_nodeadkeys)+inet(evdev)+terminate(ctrl_alt_bksp)+terminate(ctrl_alt_bksp)" }; xkb_geometry { include "pc(pc105)" }; }; -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192577] Amavis can't obtain tainted string
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1192577 https://bugzilla.suse.com/show_bug.cgi?id=1192577#c3 --- Comment #3 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Peter Varkoly from comment #2) > It a situation "an expected error has occurred" :-) Perl is only perl :-( Not sure, what you want to tell us, but there are several methods to circumvent the occurrence of warnings like this one in perl. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197981] New: virt-manager fails to start after fresh installation
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197981 Bug ID: 1197981 Summary: virt-manager fails to start after fresh installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: 64bit OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: mv.jordan(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The error message after installation (of virt-manager) is the following: "Unable to connect to libvirt qemu://system. Verify that 'libvirtd' daemon is running." The steps to work around this problem is first install libvirt. Then start the daemon with systemctl. [Side note: in the current release of Leap, adding the root user to the group libvirt is no longer neccessary as it was until Leap 15.2 . It is still neccessary if I want to start virt-manager as non-root.] These steps should be part of the installation. Please fix the package dependencies and postinst scripts. -- You are receiving this mail because: You are on the CC list for the bug.

1 2