April 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1197192] [Build 20220315] openQA test fails in installation
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197192 https://bugzilla.suse.com/show_bug.cgi?id=1197192#c19 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #19 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Thomas Blume from comment #18) > Still, we should point out that this can fail with autoyast profiles > providing an resume parameter. > It would only work if the resume parameter on the machine, where the profile > is created, is identical to the local resume device. Oh, I misunderstood the problem then, I thought the only issue with these autoyast profiles was during the initrd generation. If the resume argument changes after that and points to a wrong device, dracut can't do anything... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197192] [Build 20220315] openQA test fails in installation
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197192 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(thomas.blume@suse | |.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197192] [Build 20220315] openQA test fails in installation
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197192 https://bugzilla.suse.com/show_bug.cgi?id=1197192#c18 --- Comment #18 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Antonio Feijoo from comment #17) > Created attachment 857649 [details] > Resume sanity check patch > > Let's try to unlock this situation. After checking that this cannot be > solved via systemd, I think we have two options to fix this via dracut: > > 1. Create a custom SUSE patch (see attachment), so dracut will not add the > resume module if there is an incorrect resume command line parameter. We > have to assume that this would not be accepted upstream with a 99% > probability. Test package: > https://build.opensuse.org/package/show/home:afeijoo:branches:openSUSE: > Factory:bsc1197192/dracut > > 2. Revert https://github.com/openSUSE/dracut/commit/fe239c23 and reopen bug > 1192506 forever, assuming that any possible solution would break existing > autoyast profiles with wrong resume parameters. Provide > https://www.suse.com/en-en/support/kb/doc/?id=000020287 every time someone > complains about hibernation not working after a fresh installation. > > Any thoughts on this? The sanity check looks ok. Still, we should point out that this can fail with autoyast profiles providing an resume parameter. It would only work if the resume parameter on the machine, where the profile is created, is identical to the local resume device. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195689] New: libsolv segfault when using python API
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1195689 Bug ID: 1195689 Summary: libsolv segfault when using python API Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: mathias.reitinger(a)loop0.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm using libsolv via the python bindings and am hitting a segfault when performing problem resolution. This is using a custom build of rpm (4.17.0) and libsolv (0.7.20) to verify the issue persists with the latest version but I can reproduce this with rpm/libsolv as shipped by Leap 15.2 as well. This happens when calling element.Job() on the list of solution elements. relevant pysolv part: https://github.com/openSUSE/libsolv/blob/master/examples/pysolv#L796 Backtrace from gdb: (gdb) t a a bt full Thread 1 (Thread 0x7ffff7fd7540 (LWP 25152) "python3"): #0 0x00007ffff2c1e69a in solver_solutionelement_extrajobflags (solv=0x55555589f880, problem=<optimized out>, solution=<optimized out>) at /usr/src/debug/atikon-bb-libsolv-0.7.20-lp152.35.1.x86_64/src/problems.c:974 solidx = <optimized out> #1 0x00007ffff235e9c5 in Solutionelement_Job (self=0x555555ac88c0) at /usr/src/debug/atikon-bb-libsolv-0.7.20-lp152.35.1.x86_64/bindings/python3/solv_python.c:5673 extraflags = <optimized out> extraflags = <optimized out> #2 _wrap_Solutionelement_Job (self=<optimized out>, args=<optimized out>) at /usr/src/debug/atikon-bb-libsolv-0.7.20-lp152.35.1.x86_64/bindings/python3/solv_python.c:18344 resultobj = 0x0 arg1 = 0x555555ac88c0 argp1 = 0x555555ac88c0 res1 = <optimized out> obj0 = <Solutionelement(this=<SwigPyObject at remote 0x7ffff231f330>) at remote 0x7ffff2334828> result = 0x0 fail = <optimized out> #3 0x00007ffff79b0bfd in _PyCFunction_FastCallDict (func_obj=<built-in method Solutionelement_Job of module object at remote 0x7ffff260ddb8>, args=0x7ffff22d26e0, nargs=<optimized out>, kwargs=<optimized out>) at Objects/methodobject.c:234 tuple = (<Solutionelement(this=<SwigPyObject at remote 0x7ffff231f330>) at remote 0x7ffff2334828>,) func = 0x7ffff25d8360 meth = 0x7ffff235e960 <_wrap_Solutionelement_Job> self = <module at remote 0x7ffff260ddb8> result = <optimized out> flags = <optimized out> #4 0x00007ffff7a22582 in call_function (pp_stack=pp_stack@entry=0x7fffffffd778, oparg=<optimized out>, kwnames=kwnames@entry=0x0) at Python/ceval.c:4851 tstate = 0x555555609450 pfunc = 0x7ffff22d26d8 func = <built-in method Solutionelement_Job of module object at remote 0x7ffff260ddb8> x = <optimized out> w = <optimized out> nkwargs = <optimized out> nargs = <optimized out> stack = <optimized out> -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1197680] VUL-0: chromium: multiple security issues fixed in 100.0.4896.60
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

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

1 0

[Bug 1197913] New: Curl package is missing
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197913 Bug ID: 1197913 Summary: Curl package is missing Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Curl package is missing in the Leap15.4 build which should be part of the build by-default. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1197192] [Build 20220315] openQA test fails in installation
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197192 https://bugzilla.suse.com/show_bug.cgi?id=1197192#c17 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. |needinfo?(thomas.blume@suse |org) |.com) --- Comment #17 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Created attachment 857649 --> https://bugzilla.suse.com/attachment.cgi?id=857649&action=edit Resume sanity check patch Let's try to unlock this situation. After checking that this cannot be solved via systemd, I think we have two options to fix this via dracut: 1. Create a custom SUSE patch (see attachment), so dracut will not add the resume module if there is an incorrect resume command line parameter. We have to assume that this would not be accepted upstream with a 99% probability. Test package: https://build.opensuse.org/package/show/home:afeijoo:branches:openSUSE:Fact… 2. Revert https://github.com/openSUSE/dracut/commit/fe239c23 and reopen bug 1192506 forever, assuming that any possible solution would break existing autoyast profiles with wrong resume parameters. Provide https://www.suse.com/en-en/support/kb/doc/?id=000020287 every time someone complains about hibernation not working after a fresh installation. Any thoughts on this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197746] [Staging] Kernel 5.17 fails to boot with SELinux enabled setup
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197746 https://bugzilla.suse.com/show_bug.cgi?id=1197746#c9 --- Comment #9 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Micha�� Rostecki from comment #7) > What is setting the security=selinux parameter? Is it YaST? I will try to > check, but I would appreciate some hints from someone who knows the answer. YaST and prebuilt images at least, it's also part of the documentation. It's also used in some scripts like transactional-update. > If so, I think the good solution would be setting lsm=[...],bpf (with > ensuring that BPF is the last one) exactly at the same place. IMO breaking the security= option is not acceptable, especially with this rather misleading error and using lsm=...,bpf instead is a workaround at best. It would have to be implemented in YaST, changed in prebuilt images and also handled on kernel update installation (editing grub config in %post...). Is there any reason bpf signals that it implements the getprocattr hook? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197746] [Staging] Kernel 5.17 fails to boot with SELinux enabled setup
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197746 https://bugzilla.suse.com/show_bug.cgi?id=1197746#c8 --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Micha�� Rostecki from comment #7) > What is setting the security=selinux parameter? Is it YaST? I will try to > check, but I would appreciate some hints from someone who knows the answer. I am no expert, I found this yesterday by coincidence: # rpm -q selinux-targeted-setup --scripts |grep -A 4 if.*\$GRUB_CFG if [[ -f $GRUB_CFG ]]; then if [[ ! $(grep "^GRUB_CMDLINE_LINUX_DEFAULT=" $GRUB_CFG | grep security=selinux) ]]; then sed -i -e 's|$^GRUB_CMDLINE_LINUX_DEFAULT=.*$"|\1 security=selinux selinux=1"|g' $GRUB_CFG fi fi -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197746] [Staging] Kernel 5.17 fails to boot with SELinux enabled setup
by bugzilla_noreply＠suse.com 01 Apr '22

01 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197746 https://bugzilla.suse.com/show_bug.cgi?id=1197746#c7 --- Comment #7 from Micha�� Rostecki <mrostecki(a)suse.com> --- What is setting the security=selinux parameter? Is it YaST? I will try to check, but I would appreciate some hints from someone who knows the answer. If so, I think the good solution would be setting lsm=[...],bpf (with ensuring that BPF is the last one) exactly at the same place. -- You are receiving this mail because: You are on the CC list for the bug.

1 0