June 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1200081] SysV fail synchronizing state /sbin/insserv: No such file or directory
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200081 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel(a)suse.com Assignee|screening-team-bugs(a)suse.de |systemd-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199051] [Build 20220430] dracut - post trans failure
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199051 https://bugzilla.suse.com/show_bug.cgi?id=1199051#c10 --- Comment #10 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Finally the patch has been merged upstream: https://github.com/OSInside/kiwi/pull/2154 When will the OBS version be updated with this fix, so we can create dracut service requests without having to implement a temporary workaround for this issue? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137373] Systemd mount and unmount partition during boot
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

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

1 0

[Bug 1200179] contents of the file named.conf.include dissapears upgrading from 15.3 to 15.4
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200179 https://bugzilla.suse.com/show_bug.cgi?id=1200179#c1 Josef M�llers <josef.moellers(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Josef M�llers <josef.moellers(a)suse.com> --- Can you explain what bug ID 1199033 describes? I seem to not have the required authorization to access that bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200328] New: Online upgrade 15.3 -> 15.4 ends in black screen
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200328 Bug ID: 1200328 Summary: Online upgrade 15.3 -> 15.4 ends in black screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 859481 --> http://bugzilla.opensuse.org/attachment.cgi?id=859481&action=edit extract from journalctl Desktop system upgraded to Leap 15.4 GA ends up in black screen after boot. Just mouse cursor is visible. Xorg.0.log does not show any issues, but journalctl gives a coredump (attached) for sddm.greeter. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1200335] xrdp-0.9.19 breaks hyper-v "enhanced" connectivity ; reverting to xrdp-0.9.15 fixes
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200335 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |yfjiang(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200290] kerberized nfs mounts on a client-only config do not work due to rpc.gssd not being started
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200290 https://bugzilla.suse.com/show_bug.cgi?id=1200290#c1 --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- This is a very specialized expert scenario. I don't think this is supported by YaST. This is when the expert needs to use expert tools, i.e. start configuring things manually. YaST does many things, but not everything; it is not meant to cover every possible scenario. IMHO this is a WONTFIX. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200259] New: Kernel Panic after Update to 5.3.18-150300.59.68.1
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200259 Bug ID: 1200259 Summary: Kernel Panic after Update to 5.3.18-150300.59.68.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fgruener(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859446 --> http://bugzilla.opensuse.org/attachment.cgi?id=859446&action=edit dmesg from crash>log After upgrading the default kernel ("kernel-default") provided via regular update from the official OpenSuse Leap 15.3 (Upstream SLES) repository from 5.3.18-150300.59.63.1-default to the newest Leap Standard Kernel 5.3.18-150300.59.68.1-default, I encountered already several Kernel Panics. This could happened within an one day period 2 to 3 times, but also last time it took 2 to 3 days, until it reoccurs. An possibility to reproduce the issue step by step, I have not yet found, only be using my PC. crash>log unveiled a null pointer execption. Please see dmesg attachted. Enabling KDUMP unveiled the following backtrace: crash> bt PID: 23800 TASK: ffff8d1b32ae8000 CPU: 0 COMMAND: "fstrim" #0 [ffffb2134512f790] machine_kexec at ffffffffa7e6fe01 #1 [ffffb2134512f7e8] __crash_kexec at ffffffffa7f595fd #2 [ffffb2134512f8b0] crash_kexec at ffffffffa7f5a4bd #3 [ffffb2134512f8c8] oops_end at ffffffffa7e36d3f #4 [ffffb2134512f8e8] no_context at ffffffffa7e82bbf #5 [ffffb2134512f950] do_page_fault at ffffffffa7e83e40 #6 [ffffb2134512f980] page_fault at ffffffffa880130e [exception RIP: bfq_bio_bfqg+37] RIP: ffffffffa8277b55 RSP: ffffb2134512fa30 RFLAGS: 00010002 RAX: 000000000000001f RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff8d1b8f614e00 RSI: ffff8d1b7fd47200 RDI: ffff8d1b7fd47200 RBP: ffff8d1887ff0800 R8: ffff8d199aeb54b8 R9: ffff8d199aeb5488 R10: 0000000000000000 R11: ffff8d1ab7742e00 R12: ffff8d17c7744640 R13: ffff8d1887ff0800 R14: ffff8d1b7fd47200 R15: ffff8d1b8d91a894 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb2134512fa40] bfq_bic_update_cgroup at ffffffffa8277e78 #8 [ffffb2134512fa78] bfq_bio_merge at ffffffffa826ee9f #9 [ffffb2134512fad0] blk_mq_submit_bio at ffffffffa8248769 #10 [ffffb2134512fb58] submit_bio_noacct at ffffffffa823c343 #11 [ffffb2134512fbe8] submit_bio at ffffffffa823c3db #12 [ffffb2134512fc38] submit_bio_wait at ffffffffa8234cc4 #13 [ffffb2134512fc78] blkdev_issue_discard at ffffffffa8243d20 #14 [ffffb2134512fd08] ext4_trim_fs at ffffffffc079a7ea [ext4] #15 [ffffb2134512fe10] ext4_ioctl at ffffffffc0790ef6 [ext4] #16 [ffffb2134512fef8] ksys_ioctl at ffffffffa80fadc2 #17 [ffffb2134512ff30] __x64_sys_ioctl at ffffffffa80fadf6 #18 [ffffb2134512ff38] do_syscall_64 at ffffffffa7e0538b #19 [ffffb2134512ff50] entry_SYSCALL_64_after_hwframe at ffffffffa880008c RIP: 00007f73ecd54c47 RSP: 00007ffc4e041c08 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: 000055764b87c310 RCX: 00007f73ecd54c47 RDX: 00007ffc4e041c20 RSI: 00000000c0185879 RDI: 0000000000000003 RBP: 000055764b8788c0 R8: 000055764b87c310 R9: 0000000000000002 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc4e041d00 R13: 000055764b8788c0 R14: 0000000000000003 R15: 000055764b87a890 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b According to the logfiles of the changed items of the last patch, there was a patch added to address: - bfq: Update cgroup information before merging bio (bsc#1197926). Searching in the internet "bfq_bic_update_cgroup+0x28/0x1b0 core dump opensuse" I also found: https://lkml.kernel.org/linux-block/20220330124255.24581-2-jack@suse.cz/T/ There at least in the same stack changes have been done in the same area. @@ -2457,10 +2457,17 @@ static bool bfq_bio_merge(struct request_queue *q, struct bio *bio, + bfq_bic_update_cgroup(bic, bio); Maybe bio is not fully initialized? Maybe my refernece is wrong, but it is remarkable, that at least the kernel post contains a change in the same stack. As this is my first post, I am not quite sure what other information might be helpfull here. Please ask, if you will need further information. Thanks already for taking this issue into account. And for your openSuse. Best regards cyp -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1200237] kernel-preempt / kernel-rt not installable on Leap 15.4
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200237 https://bugzilla.suse.com/show_bug.cgi?id=1200237#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Ah OK, there was a conflict. It can be ignored. But yeah, it's still not ready for easy use, so uninstalling kernel-rt would be a safer choice. Alternatively, you can try the kernel in OBS Kernel:SLE15-SP4-RT repo until the official kernel-rt package appears. It's an unofficial build from the latest git branch. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200366] New: Starting registry.opensuse.org/opensuse/tumbleweed shows a non-relevant message about SUSEConnect
by bugzilla_noreply＠suse.com 09 Jun '22

09 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200366 Bug ID: 1200366 Summary: Starting registry.opensuse.org/opensuse/tumbleweed shows a non-relevant message about SUSEConnect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation The command ``` podman run --rm -it registry.opensuse.org/opensuse/tumbleweed ``` shows irrelevant warnings: ``` WARN[0000] Path "/etc/SUSEConnect" from "/etc/containers/mounts.conf" doesn't exist, skipping WARN[0000] Path "/etc/zypp/credentials.d/SCCcredentials" from "/etc/containers/mounts.conf" doesn't exist, skipping ``` ## Expected result Those warnings should be avoided. As a Tumbleweed user I don't care about SUSEConnect or SCC. -- You are receiving this mail because: You are on the CC list for the bug.

1 0