July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199895] PackageKit does not honor zypper package locks
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1199895 https://bugzilla.suse.com/show_bug.cgi?id=1199895#c14 --- Comment #14 from Michael Andres <ma(a)suse.com> --- Are some pk_backend logs available, so we can see what is happening? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196224] User Kerberos Tickets are not refresh or get destroyed after Update to samba 4.15.4
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1196224 https://bugzilla.suse.com/show_bug.cgi?id=1196224#c17 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andreas.hauffe@tu | |-dresden.de) | --- Comment #17 from Samuel Cabrero <scabrero(a)suse.com> --- I finally reproduced it. https://gitlab.com/samba-team/samba/-/merge_requests/2610 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201015] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c3 --- Comment #3 from Frederic Crozat <fcrozat(a)suse.com> --- (In reply to Johannes Segitz from comment #2) > Can you please describe in more detail what you do here (e.g. how you invoke > transactional-update from cloud init)? Thank you. > > snapper_dbus_chat might be the right interface to call, but I want to > recreate this first yes, of course. I was running the following cloud-init config (this is with Tumbleweed repositories) #cloud-config runcmd: - /usr/sbin/transactional-update -n pkg in cifs-utils k3s-install k3s-selinux power_state: delay: now mode: reboot This causes snapper to be blocked when snapshot is created by transactional-update and cloud-init doesn't finish. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200995] bind does not start because package bind-chrootenv is missing
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200995 https://bugzilla.suse.com/show_bug.cgi?id=1200995#c1 Josef M�llers <josef.moellers(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Josef M�llers <josef.moellers(a)suse.com> --- Kudos to the customer who has fixed some issues himself: 1) /usr/lib/tmpfiles.d/bind.conf needs an entry for /var/log/named 2) In /etc/sysconfig/named, NAMED_INITIALIZE_SCRIPTS should be initialized to an empty string 3) some directives were to removed from /etc/named.conf. These are already fixed in SLE15-SP4, so this bug is closed as INVALID. Thanks again for the great work! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201015] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c2 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |jsegitz(a)suse.com --- Comment #2 from Johannes Segitz <jsegitz(a)suse.com> --- Can you please describe in more detail what you do here (e.g. how you invoke transactional-update from cloud init)? Thank you. snapper_dbus_chat might be the right interface to call, but I want to recreate this first -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193250] [META] Fully switch TW to DRM graphics drivers and disable fbdev drivers
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193250 Bug 1193250 depends on bug 1201205, which changed state. Bug 1201205 Summary: Kernel-default 5.18.9 hangs on boot https://bugzilla.suse.com/show_bug.cgi?id=1201205 What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201205] Kernel-default 5.18.9 hangs on boot
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201205 https://bugzilla.suse.com/show_bug.cgi?id=1201205#c23 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #23 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Manfred Hollstein from comment #22) > Just wanted to confirm that kernel-default-5.18.9-3.ga7c5f9c-default no > longer has the problem, thanks for fixing! > > Here's my current setup: > > - TW20220705 > - kernel-default-5.18.9-3.ga7c5f9c-default Thanks for testing. I close this issue as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200937] Command dig terminates unexpectedly
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200937 https://bugzilla.suse.com/show_bug.cgi?id=1200937#c4 Josef M�llers <josef.moellers(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|josef.moellers(a)suse.com |kernel-bugs(a)suse.de --- Comment #4 from Josef M�llers <josef.moellers(a)suse.com> --- Good news and bad news: Good news: I'm able to reproduce the issue on an aarch64 machine (and unable to reproduce on x86_64). Bad news: I still don't have a clue why this is happening. I wrote a small PERL/Expect script to continuously run "dig smtp.gmail.com" until the program has no more "exited normally". That DOES take a few (understatement of the week) iterations: 170, 276, 243 ... When the issue occurs, the stack trace consistantly looks like this: #0 0x0000fffff7b31934 in syscall () from /lib64/libc.so.6 #1 0x0000fffff731f87c in uv.epoll_pwait () from /usr/lib64/libuv.so.1 #2 0x0000fffff731da48 in uv.io_poll () from /usr/lib64/libuv.so.1 #3 0x0000fffff730e8d4 in uv_run () from /usr/lib64/libuv.so.1 #4 0x0000fffff7c82978 in ?? () from /usr/lib64/libisc-9.16.20.so #5 0x0000fffff7c9bd20 in isc.trampoline_run () from /usr/lib64/libisc-9.16.20.so #6 0x0000fffff7c1b748 in start_thread () from /lib64/libpthread.so.0 #7 0x0000fffff7b3571c in thread_start () from /lib64/libc.so.6 What I do see is that it happens inside an "epoll_wait" system call, so I'll assign this to the kernel people and see if they can make sense out of it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200939] New: mokutil hangs with 100% CPU when installing openSUSE-signkey-cert-20220613-lp154.2.3.1.x86_64.rpm
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200939 Bug ID: 1200939 Summary: mokutil hangs with 100% CPU when installing openSUSE-signkey-cert-20220613-lp154.2.3.1.x86_64.rpm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to roll-back to a previous version of openSUSE-signkey-cert the same happens. The executed command by yast is: rpm --root / --dbpath /usr/lib/sysimage/rpm -U --percent --noglob --force --nodeps -- /var/cache/zypp/packages/repo-oss/x86_64/openSUSE-signkey-cert-20210302-lp154.1.2.x86_64.rpm resulting in this child process: cat /proc/28283/cmdline mokutil--import/etc/uefi/certs/1F673297-kmp.crt--root-pw which hangs at 100% cpu. Executing the same command directly in the shell also hangs without an error message. Pressing Abort in Yast is not possible, sending a SIGTERM to mokutil via 'top' does not terminate mokutil, SIGKILL is necessary. After this, zypper up starts installing openSUSE-signkey-cert-20220613-lp154.2.3.1.x86_64.rpm, again. Two SIGKILLs on mokutil are necessary. Mokutil cmdlines are: mokutil--import/etc/uefi/certs/1F673297-kmp.crt--root-pw mokutil--import/etc/uefi/certs/BDD31A9E-kmp.crt--root-pw -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201204] regression: cannot build arm-trusted-firmware on 15.3/15.4 - missing cross-arm-none-gcc7
by bugzilla_noreply＠suse.com 07 Jul '22

07 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201204 https://bugzilla.suse.com/show_bug.cgi?id=1201204#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Actually, they are. u-boot is built in SLE and is broken due to missing ATF Hopefully only for platforms not supported by SLE. -- You are receiving this mail because: You are on the CC list for the bug.

1 0