August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1195508] New: [RPi 4] Error during boot regarding systemd-vconsole-setup.service
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1195508 Bug ID: 1195508 Summary: [RPi 4] Error during boot regarding systemd-vconsole-setup.service Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: --- Blocker: --- Created attachment 855846 --> https://bugzilla.suse.com/attachment.cgi?id=855846&action=edit boot error # systemctl status systemd-vconsole-setup.service �� systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) Active: failed (Result: exit-code) since Thu 2022-01-06 12:00:00 UTC; 4 weeks 0 days ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Main PID: 154 (code=exited, status=1/FAILURE) Jan 06 12:00:01 localhost systemd-vconsole-setup[156]: cannot open file us.map.gz Notice: journal has been rotated since unit was started, output may be incomplete. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1195047] dracut-install: ERROR: installing '/etc/bluetooth/main.conf'
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1195047 https://bugzilla.suse.com/show_bug.cgi?id=1195047#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:2625-1: An update that has 12 recommended fixes can now be installed. Category: recommended (important) Bug References: 1177461,1184970,1187654,1195047,1195508,1195604,1196267,1197635,1197967,1200236,1200251,1200360 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): dracut-055+suse.279.g3b3c36b2-150400.3.5.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): dracut-055+suse.279.g3b3c36b2-150400.3.5.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187654] MicroOS IMA enabled system, dracut-pre-privot error
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1187654 https://bugzilla.suse.com/show_bug.cgi?id=1187654#c28 --- Comment #28 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:2625-1: An update that has 12 recommended fixes can now be installed. Category: recommended (important) Bug References: 1177461,1184970,1187654,1195047,1195508,1195604,1196267,1197635,1197967,1200236,1200251,1200360 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): dracut-055+suse.279.g3b3c36b2-150400.3.5.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): dracut-055+suse.279.g3b3c36b2-150400.3.5.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201730] Upgrade to LEAP 15.4 breaks installing official Vagrant package with vagrant-libvirt
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201730 https://bugzilla.suse.com/show_bug.cgi?id=1201730#c3 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Dan ��erm��k <dcermak(a)suse.com> --- (In reply to Markus Zimmermann from comment #2) > (just saw that we have GCC in the package list, so i guess ruby-* vagrant-* > is using GCC otherwise we wouldn't add it. For everything else we are using > LLVM which hence is not an issue for this bug report) > > In any case, let me know what i should try. I have two machines where i can > reproduce this problem. The goal would be to install the official Vagrant > package with LEAP 15.4. If we need additional repositories, that is fine for > me. However, since this worked out of the box with 15.3, i see the whole > report as a regression. Especially since the only way of getting this to > work (at least so far) is to install the vagrant package of a specialized > repository in a very specific combination. Would be great if the next users > that want to try vagrant-libvirt do not run into this problem. Sorry for taking so long to reply, but I cannot really support official vagrant package, because I have literally no way to contribute to it. The only thing that I can offer is trying to get a recent vagrant-libvirt to build in Virtualization:vagrant. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202058] New: Prepare libyui package for the upcoming libzypp update
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202058 Bug ID: 1202058 Summary: Prepare libyui package for the upcoming libzypp update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Libzypp is doing some cleanup and as the result the global _1 boot placeholders will not be used. But some libyui code relies on this behavior. https://github.com/libyui/libyui/issues/78 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202027] New: libgccjit.so and cc1obj text sections differs in size
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202027 Bug ID: 1202027 Summary: libgccjit.so and cc1obj text sections differs in size Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gcc12 seems to be not reproducible and one of the difference is visible in the libgccjit package which, for libgccjit.so itself is visible in different sized .text and .rodata: [16] .text PROGBITS 00000000002b97a0 002b97a0 - 0000000001105e42 0000000000000000 AX 0 0 16 - [17] .fini PROGBITS 00000000013bf5e4 013bf5e4 + 0000000001105c82 0000000000000000 AX 0 0 16 + [17] .fini PROGBITS 00000000013bf424 013bf424 000000000000000d 0000000000000000 AX 0 0 4 [18] .rodata PROGBITS 00000000013c0000 013c0000 - 000000000042d950 0000000000000000 A 0 0 32 - [19] .stapsdt.base PROGBITS 00000000017ed950 017ed950 + 000000000042d8f0 0000000000000000 A 0 0 32 disassembly starts with a huge blob of Disassembly of section .text: 00000000002b97a0 <gcc_jit_compatible_types@@LIBGCCJIT_ABI_20-0x1098dc0>: ... 0000000001352560 <gcc_jit_compatible_types@@LIBGCCJIT_ABI_20>: 1352560: f3 0f 1e fa endbr64 which isn't very useful unfortunately. Similar can be observed with cc1obj: [17] .text PROGBITS 0000000000624690 00224690 - 00000000012796dc 0000000000000000 AX 0 0 16 - [18] .fini PROGBITS 000000000189dd6c 0149dd6c + 00000000012796cc 0000000000000000 AX 0 0 16 the disassembly isn't too usable either, it starts within a blob with local functions as well. Since this is all -fprofile-use (but with -fprofile-reproducible=parallel-runs) and with -flto debugging this is hard. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1202054] starting KVM guest crashes kernel 5.14.21-150400.24.11-default
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202054 https://bugzilla.suse.com/show_bug.cgi?id=1202054#c1 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife(a)novell.slipkontur.de Flags| |needinfo?(seife(a)novell.slip | |kontur.de) --- Comment #1 from Borislav Petkov <bpetkov(a)suse.com> --- Does it go away with the latest KOTD: https://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201822] VUL-0: CVE-2022-34037: caddy: oob read allows for DoS
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201822 http://bugzilla.opensuse.org/show_bug.cgi?id=1201822#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1201822) was mentioned in https://build.opensuse.org/request/show/992225 Backports:SLE-15-SP4 / caddy -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201602] /usr/sbin/named-checkconf do not consider chrooted bind
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201602 https://bugzilla.suse.com/show_bug.cgi?id=1201602#c1 Jorik Cronenberg <jorik.cronenberg(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Jorik Cronenberg <jorik.cronenberg(a)suse.com> --- As stated in bind.changes: ------------------------------------------------------------------- Tue Oct 19 14:00:56 UTC 2021 - Josef M�llers <josef.moellers(a)suse.com> ... *** MAJOR CHANGE *** Changed protection of/against "named" from chroot jail to systemd protection. This obsoletes subpackage named-chrootenv. We don't support the chroot environment in Leap 15.4 anymore, since systemd now handles the protections of the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199027] New: autofs: inconsistent naming OPTIONS vs AUTOFS_OPTIONS
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1199027 Bug ID: 1199027 Summary: autofs: inconsistent naming OPTIONS vs AUTOFS_OPTIONS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The environment variable for automount options is called AUTOFS_OPTIONS in the sysconfig file but OPTIONS in the service file. This problem was introduced with the update to 5.1.5: * Fri Jan 11 2019 rgoldwyn(a)suse.com - Upgrade to 5.1.5 ... - Updated spec file to use native autofs service files # grep OPTIONS /usr/share/fillup-templates/sysconfig.autofs AUTOFS_OPTIONS="" # grep OPTIONS /usr/lib/systemd/system/autofs.service ExecStart=/usr/sbin/automount $OPTIONS --systemd-service --dont-check-daemon -- You are receiving this mail because: You are on the CC list for the bug.

1 5