August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224773] NVIDIA KMP: initrd not regenerated on transactional systems using systemd-boot like Aeon >= RC2
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c54 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sunscape1@hotmail |needinfo?(vortex(a)z-ray.de) |.com) | --- Comment #54 from Stefan Dirsch <sndirsch(a)suse.com> --- (correcting NEEDINFO) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204318] podman unable to delete infrastructure infra container, TW 20221012
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1204318 https://bugzilla.suse.com/show_bug.cgi?id=1204318#c1 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |alexandre.vicenzi(a)suse.com, | |containers-bugowner(a)suse.de Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com Status|NEW |RESOLVED --- Comment #1 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I was not able to reproduce the same error in Tumbleweed. If you have running or paused containers they cannot be removed without force. In this case, the proper way to remove is to stop the containers first. podman pod stop db podman pod rm db -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227908] auditd obsolete built-in options
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227908 https://bugzilla.suse.com/show_bug.cgi?id=1227908#c8 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | CC| |fvogt(a)suse.com --- Comment #8 from Fabian Vogt <fvogt(a)suse.com> --- FWICT this was introduced by https://github.com/linux-audit/audit-userspace/commit/d1ccd8f642e11ad65cdc8…, which added a log entry with "auid=42". This is something for upstream to figure out how to fix IMO. I see several options: a) Remove the gdm part again b) Use some uid that doesn't exist and hardcode unknown(123456) c) Start auparse in a test mode that ignores the host system and maps 42 to gdm. Downstream this could be hacked around using a patch that does s/gdm/unknown(42)/. That would work in OBS, but if someone builds that locally (sholudn't be that common) it would fail in the case that 42 is assigned to something. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212841] Lots of objtool warnings when building the nvidia driver
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1212841 https://bugzilla.suse.com/show_bug.cgi?id=1212841#c15 --- Comment #15 from Stefan Dirsch <sndirsch(a)suse.com> --- Stil the same with 550.100. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227223] podman stats doesn't show the MEM USAGE in rootless containers
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227223 https://bugzilla.suse.com/show_bug.cgi?id=1227223#c6 --- Comment #6 from Walddys Emmanuel Dorrejo Céspedes <dev.dorrejo(a)gmail.com> --- (In reply to Dan Čermák from comment #5) > (In reply to Walddys Emmanuel Dorrejo Céspedes from comment #4) > > Hello, Have the same issue, and looks like nobody of openSUSE team is > > following this. > > > > `memory.stat: no such file or directory` > > > > in the folder: /sys/fs/cgroup/ appear all cgroups > > > > but in folder: /sys/fs/cgroup/user.slice: it would not be added io and > > memory. > > Which OS are you on and what's the systemd version that you are running? Leap 15.6 - Systemd: 254.15-150600.4.8.1, Up-To-Date OS. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228659] Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c36 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume(a)suse.com --- Comment #36 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Andrei Borzenkov from comment #35) > The problem is dependencies are computed once for the whole transaction. So, > when transaction starts, all dependencies are correct. Now, in the middle of > transaction zypper updates systemd from v255 to v256 and it immediately > invalidates all computed dependencies involving other systemd subpackages. > > Yes, if zypper computed dependencies *now* it probably would have noticed > that existing systemd-boot v255 has missing dependency on systemd v255 and > would first update systemd-boot to version v256. But it is too late. To > implement it, zypper (or libzypp or libsolv) would effectively need to > recompute dependencies after every package. I wonder what zypper maintainers > think about it :) If a lot of other packages rely on systemd functionality but not vice-versa, would it make sense to hardcode that systemd/udev packages get update before all others? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226167] Patch to ansible adds reference to undefined name.
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226167 https://bugzilla.suse.com/show_bug.cgi?id=1226167#c1 Johannes Kastl <opensuse_buildservice(a)ojkastl.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Johannes Kastl <opensuse_buildservice(a)ojkastl.de> --- Sorry, but Ansible 2.9 is EOL for a long time. I hope to have working Ansible packages for 15.6, but it is quite tricky. Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198844] minikube fails to build at k8s.io/minikube/cmd/minikube: go.mod file not found in current directory or any parent directory;
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1198844 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com CC| |containers-bugowner(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198844] minikube fails to build at k8s.io/minikube/cmd/minikube: go.mod file not found in current directory or any parent directory;
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1198844 https://bugzilla.suse.com/show_bug.cgi?id=1198844#c2 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexandre.vicenzi(a)suse.com Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- The package in OBS is gone, Leap 15.4 is EOL. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222534] No wired network after hibernation
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222534 https://bugzilla.suse.com/show_bug.cgi?id=1222534#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Is this a regression? That is, does it work with the older kernel? -- You are receiving this mail because: You are on the CC list for the bug.

1 0