October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1232226] New: selinux-autorelabel tries to relabel btrfs partition containing ro snapshots, fails and leaves system in an unbootable state
by bugzilla_noreply＠suse.com 25 Apr '25

25 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1232226 Bug ID: 1232226 Summary: selinux-autorelabel tries to relabel btrfs partition containing ro snapshots, fails and leaves system in an unbootable state Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: registrations(a)wuthoehle.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I run MicroOS on my home server and have a btrfs partition mounted at /var/lib/data. The filesystem exclusively contains btrfs subvolumes which are mounted by various podman containers. These volumes are backed up regulary by btrbk (which is more-or-less a very convenient frontend to btrfs subvolume snapshot/btrfs send/btrfs receive). Accrodingly, there are always a few read-only snapshots inside /var/lib/data/snapshot. In the last few weeks, I experienced that the server wouldn't come up after an automatic reboot multiple times. It turns out that somehow something created a /etc/selinux/.autorelabel file (I guess that this was a byproduct of an update?), which leads to the system trying to relabel everything on the next boot. Unfortunately, when trying to relabel my /var/lib/data partition, restorecon fails when it arrives at the snapshots folder and quits with a "Read only file system" error. Even worse, this leads to a fail of the generated -relabel.service, local-fs.target and thus of the whole boot process. I had a quick look on the generator and it seems to have hardcoded a few paths which aren't supposed to be relabelled but unfortunately this doesn't seem to be configurable. Apparently volumes which have "noauto" set are ignored, too, but this doesn't help either as I want to have my services autostarted at boot time. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222044] New: zypper %posttrans fails with "Failed to start jobs"
by bugzilla_noreply＠suse.com 24 Apr '25

24 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1222044 Bug ID: 1222044 Summary: zypper %posttrans fails with "Failed to start jobs" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873853 --> https://bugzilla.suse.com/attachment.cgi?id=873853&action=edit zypper.log Upgrading from TW Snapshot 20240321 to 20240325 with zypper -v dup had the following output at the end: Ausgabe des Skripts %posttrans(zypper-1.14.70-1.1.x86_64): Failed to start jobs: Failed to enqueue some jobs, see logs for details: No such file or directory Nach-Transaktions-Skripte werden ausgeführt ..............................................................................................................................................................................................[fertig] CommitResult (total 432, done 432, error 0, skipped 0, updateMessages 0) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1231231] New: Rootless podman inside distrobox not working
by bugzilla_noreply＠suse.com 24 Apr '25

24 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1231231 Bug ID: 1231231 Summary: Rootless podman inside distrobox not working 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: martin.sirringhaus(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following the upstream guide on how to use podman inside distrobox (https://distrobox.it/useful_tips/#using-podman-inside-a-distrobox) I can't get rootless podman to work, even though the upstream guide is actually using Tumbleweed. I only seem to be able to get `sudo podman` to work (albeit with a warning): ❯ sudo podman run --rm -ti alpine WARN[0000] Failed to add conmon to cgroupfs sandbox cgroup: creating cgroup path /libpod_parent/conmon: write /sys/fs/cgroup/libpod_parent/cgroup.subtree_control: operation not supported / # Rootless podman however fails: ❯ podman run --rm -ti alpine ERRO[0000] invalid internal status, try resetting the pause process with "podman system migrate": could not find any running process: no such process ❯ And if I try to run `podman system migrate`, podman segfaults: ❯ podman system migrate stopped 8acf10be6dbf4336260113fd2b54b45bcdf803970cd84b21d4933a5b5eccd2ad panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x55e5f4a8f49b] goroutine 1 [running]: github.com/containers/podman/v5/libpod.(*storageService).UnmountContainerIm…, {0xc00054be80?, 0x0?}, 0x0) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/storage.go:235 +0x3b github.com/containers/podman/v5/libpod.(*Container).unmount(0xc000880fa0, 0x80?) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_internal.go:2467 +0x3a github.com/containers/podman/v5/libpod.(*Container).cleanupStorage(0xc00088… /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_internal.go:2007 +0x505 github.com/containers/podman/v5/libpod.(*Container).cleanup(0xc000880fa0, {0x55e5f55fcc50, 0x55e5f6399840}) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_internal.go:2097 +0x5bb github.com/containers/podman/v5/libpod.(*Container).waitForConmonToExitAndS… /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_internal.go:1512 +0x4c5 github.com/containers/podman/v5/libpod.(*Container).stop(0xc000880fa0, 0xa) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_internal.go:1454 +0x5d2 github.com/containers/podman/v5/libpod.(*Container).StopWithTimeout(0xc0008…, 0xa?) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_api.go:282 +0xd7 github.com/containers/podman/v5/libpod.(*Container).Stop(...) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/container_api.go:252 github.com/containers/podman/v5/libpod.(*Runtime).Migrate(0xc0005848c0, {0x0, 0x0}) /home/abuild/rpmbuild/BUILD/podman-5.2.3/libpod/runtime_migrate_linux.go:76 +0x2e5 github.com/containers/podman/v5/pkg/domain/infra/abi.(*ContainerEngine).Mig…, {0x0?, 0x0?}, {{0x0?, 0x8453589700000000?}}) /home/abuild/rpmbuild/BUILD/podman-5.2.3/pkg/domain/infra/abi/system.go:298 +0x25 github.com/containers/podman/v5/cmd/podman/system.migrate(0x55e5f62a12e0?, {0x55e5f6399840?, 0x0?, 0x0?}) /home/abuild/rpmbuild/BUILD/podman-5.2.3/cmd/podman/system/migrate.go:56 +0x63 github.com/spf13/cobra.(*Command).execute(0x55e5f62a12e0, {0xc000040470, 0x0, 0x0}) /home/abuild/rpmbuild/BUILD/podman-5.2.3/vendor/github.com/spf13/cobra/command.go:989 +0xa91 github.com/spf13/cobra.(*Command).ExecuteC(0x55e5f628b420) /home/abuild/rpmbuild/BUILD/podman-5.2.3/vendor/github.com/spf13/cobra/command.go:1117 +0x3ff github.com/spf13/cobra.(*Command).Execute(...) /home/abuild/rpmbuild/BUILD/podman-5.2.3/vendor/github.com/spf13/cobra/command.go:1041 github.com/spf13/cobra.(*Command).ExecuteContext(...) /home/abuild/rpmbuild/BUILD/podman-5.2.3/vendor/github.com/spf13/cobra/command.go:1034 main.Execute() /home/abuild/rpmbuild/BUILD/podman-5.2.3/cmd/podman/root.go:116 +0xb4 main.main() /home/abuild/rpmbuild/BUILD/podman-5.2.3/cmd/podman/main.go:61 +0x4b2 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1215657] New: VUL-0: CVE-2023-42811: rage-encryption: aes-gcm: chosen ciphertext attack via `decrypt_in_place*` APIs
by bugzilla_noreply＠suse.com 24 Apr '25

24 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1215657 Bug ID: 1215657 Summary: VUL-0: CVE-2023-42811: rage-encryption: aes-gcm: chosen ciphertext attack via `decrypt_in_place*` APIs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/379692/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: william.brown(a)suse.com Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: cunix(a)mail.de, security-team(a)suse.de Depends on: 1215654 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1215654 +++ CVE-2023-42811 aes-gcm is a pure Rust implementation of the AES-GCM. Starting in version 0.10.0 and prior to version 0.10.3, in the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification fails. If a program using the `aes-gcm` crate's `decrypt_in_place*` APIs accesses the buffer after decryption failure, it will contain a decryption of an unauthenticated input. Depending on the specific nature of the program this may enable Chosen Ciphertext Attacks (CCAs) which can cause a catastrophic breakage of the cipher including full plaintext recovery. Version 0.10.3 contains a fix for this issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42811 https://www.cve.org/CVERecord?id=CVE-2023-42811 https://docs.rs/aes-gcm/latest/src/aes_gcm/lib.rs.html#309 https://github.com/RustCrypto/AEADs/security/advisories/GHSA-423w-p2w9-r7vq -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230688] New: VUL-0: CVE-2024-45405: obs-service-cargo: gix-path: gix-path improperly resolves configuration path reported by Git
by bugzilla_noreply＠suse.com 24 Apr '25

24 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1230688 Bug ID: 1230688 Summary: VUL-0: CVE-2024-45405: obs-service-cargo: gix-path: gix-path improperly resolves configuration path reported by Git Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/419949/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-45405:6.4:(AV:L/AC:H/PR:H/UI:N/ S:U/C:H/I:H/A:H) CVSSv4.0:SUSE:CVE-2024-45405:7.0:(AV:L/AC:H/AT:P/PR:H/ UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H) Severity: Normal Priority: P5 - None Component: Security Assignee: xiaoguang.wang(a)suse.com Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1230682 Target Milestone: --- Found By: --- Blocker: --- `gix-path` is a crate of the `gitoxide` project (an implementation of `git` written in Rust) dealing paths and their conversions. Prior to version 0.10.11, `gix-path` runs `git` to find the path of a configuration file associated with the `git` installation, but improperly resolves paths containing unusual or non-ASCII characters, in rare cases enabling a local attacker to inject configuration leading to code execution. Version 0.10.11 contains a patch for the issue. In `gix_path::env`, the underlying implementation of the `installation_config` and `installation_config_prefix` functions calls `git config -l --show-origin` to find the path of a file to treat as belonging to the `git` installation. Affected versions of `gix-path` do not pass `-z`/`--null` to cause `git` to report literal paths. Instead, to cover the occasional case that `git` outputs a quoted path, they attempt to parse the path by stripping the quotation marks. The problem is that, when a path is quoted, it may change in substantial ways beyond the concatenation of quotation marks. If not reversed, these changes can result in another valid path that is not equivalent to the original. On a single-user system, it is not possible to exploit this, unless `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` have been set to unusual values or Git has been installed in an unusual way. Such a scenario is not expected. Exploitation is unlikely even on a multi-user system, though it is plausible in some uncommon configurations or use cases. In general, exploitation is more likely to succeed if users are expected to install `git` themselves, and are likely to do so in predictable locations; locations where `git` is installed, whether due to usernames in their paths or otherwise, contain characters that `git` quotes by default in paths, such as non-English letters and accented letters; a custom `system`-scope configuration file is specified with the `GIT_CONFIG_SYSTEM` environment variable, and its path is in an unusual location or has strangely named components; or a `system`-scope configuration file is absent, empty, or suppressed by means other than `GIT_CONFIG_NOSYSTEM`. Currently, `gix-path` can treat a `global`-scope configuration file as belonging to the installation if no higher scope configuration file is available. This increases the likelihood of exploitation even on a system where `git` is installed system-wide in an ordinary way. However, exploitation is expected to be very difficult even under any combination of those factors. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45405 https://bugzilla.redhat.com/show_bug.cgi?id=2310412 https://www.cve.org/CVERecord?id=CVE-2024-45405 https://github.com/Byron/gitoxide/blob/1cfe577d461293879e91538dbc4bbfe01722… https://github.com/Byron/gitoxide/commit/650a1b5cf25e086197cc55a68525a411e1… https://github.com/Byron/gitoxide/security/advisories/GHSA-m8rp-vv92-46c7 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227605] New: ollama stopt working with the newest update. msg: illegal instrucktion (core dumped)
by bugzilla_noreply＠suse.com 22 Apr '25

22 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1227605 Bug ID: 1227605 Summary: ollama stopt working with the newest update. msg: illegal instrucktion (core dumped) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kl-tech(a)posteo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- don't now if just on opensuse pakaging of ollama. Log messages: dev@localhost:~> ollama start 2024/07/10 08:57:05 routes.go:1064: INFO server config env="map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_HOST:http://127.0.0.1:11434 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE: OLLAMA_LLM_LIBRARY: OLLAMA_MAX_LOADED_MODELS:1 OLLAMA_MAX_QUEUE:512 OLLAMA_MAX_VRAM:0 OLLAMA_MODELS:/home/dev/.ollama/models OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:1 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://*] OLLAMA_RUNNERS_DIR: OLLAMA_SCHED_SPREAD:false OLLAMA_TMPDIR: ROCR_VISIBLE_DEVICES:]" time=2024-07-10T08:57:05.590+02:00 level=INFO source=images.go:730 msg="total blobs: 16" time=2024-07-10T08:57:05.592+02:00 level=INFO source=images.go:737 msg="total unused blobs removed: 0" [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached. [GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production. - using env: export GIN_MODE=release - using code: gin.SetMode(gin.ReleaseMode) [GIN-debug] POST /api/pull --> github.com/ollama/ollama/server.(*Server).PullModelHandler-fm (5 handlers) [GIN-debug] POST /api/generate --> github.com/ollama/ollama/server.(*Server).GenerateHandler-fm (5 handlers) [GIN-debug] POST /api/chat --> github.com/ollama/ollama/server.(*Server).ChatHandler-fm (5 handlers) [GIN-debug] POST /api/embeddings --> github.com/ollama/ollama/server.(*Server).EmbeddingsHandler-fm (5 handlers) [GIN-debug] POST /api/create --> github.com/ollama/ollama/server.(*Server).CreateModelHandler-fm (5 handlers) [GIN-debug] POST /api/push --> github.com/ollama/ollama/server.(*Server).PushModelHandler-fm (5 handlers) [GIN-debug] POST /api/copy --> github.com/ollama/ollama/server.(*Server).CopyModelHandler-fm (5 handlers) [GIN-debug] DELETE /api/delete --> github.com/ollama/ollama/server.(*Server).DeleteModelHandler-fm (5 handlers) [GIN-debug] POST /api/show --> github.com/ollama/ollama/server.(*Server).ShowModelHandler-fm (5 handlers) [GIN-debug] POST /api/blobs/:digest --> github.com/ollama/ollama/server.(*Server).CreateBlobHandler-fm (5 handlers) [GIN-debug] HEAD /api/blobs/:digest --> github.com/ollama/ollama/server.(*Server).HeadBlobHandler-fm (5 handlers) [GIN-debug] GET /api/ps --> github.com/ollama/ollama/server.(*Server).ProcessHandler-fm (5 handlers) [GIN-debug] POST /v1/chat/completions --> github.com/ollama/ollama/server.(*Server).ChatHandler-fm (6 handlers) [GIN-debug] GET / --> github.com/ollama/ollama/server.(*Server).GenerateRoutes.func1 (5 handlers) [GIN-debug] GET /api/tags --> github.com/ollama/ollama/server.(*Server).ListModelsHandler-fm (5 handlers) [GIN-debug] GET /api/version --> github.com/ollama/ollama/server.(*Server).GenerateRoutes.func2 (5 handlers) [GIN-debug] HEAD / --> github.com/ollama/ollama/server.(*Server).GenerateRoutes.func1 (5 handlers) [GIN-debug] HEAD /api/tags --> github.com/ollama/ollama/server.(*Server).ListModelsHandler-fm (5 handlers) [GIN-debug] HEAD /api/version --> github.com/ollama/ollama/server.(*Server).GenerateRoutes.func2 (5 handlers) time=2024-07-10T08:57:05.592+02:00 level=INFO source=routes.go:1111 msg="Listening on 127.0.0.1:11434 (version 0.0.0)" time=2024-07-10T08:57:05.593+02:00 level=INFO source=payload.go:30 msg="extracting embedded files" dir=/tmp/ollama2475486328/runners time=2024-07-10T08:57:05.629+02:00 level=INFO source=payload.go:44 msg="Dynamic LLM libraries [cpu cpu_avx cpu_avx2]" time=2024-07-10T08:57:05.644+02:00 level=INFO source=types.go:98 msg="inference compute" id=0 library=cpu compute="" driver=0.0 name="" total="19.4 GiB" available="17.6 GiB" [GIN] 2024/07/10 - 08:57:15 | 200 | 52.753µs | 127.0.0.1 | HEAD "/" [GIN] 2024/07/10 - 08:57:15 | 200 | 1.841915ms | 127.0.0.1 | GET "/api/tags" [GIN] 2024/07/10 - 08:57:34 | 200 | 28.313µs | 127.0.0.1 | HEAD "/" [GIN] 2024/07/10 - 08:57:34 | 200 | 21.780392ms | 127.0.0.1 | POST "/api/show" time=2024-07-10T08:57:34.518+02:00 level=INFO source=memory.go:309 msg="offload to cpu" layers.requested=-1 layers.model=28 layers.offload=0 layers.split="" memory.available="[17.7 GiB]" memory.required.full="9.0 GiB" memory.required.partial="0 B" memory.required.kv="540.0 MiB" memory.required.allocations="[9.0 GiB]" memory.weights.total="8.5 GiB" memory.weights.repeating="8.4 GiB" memory.weights.nonrepeating="164.1 MiB" memory.graph.full="212.0 MiB" memory.graph.partial="376.1 MiB" time=2024-07-10T08:57:34.519+02:00 level=INFO source=server.go:368 msg="starting llama server" cmd="/tmp/ollama2475486328/runners/cpu_avx/ollama_llama_server --model /home/dev/.ollama/models/blobs/sha256-5ff0abeeac1d2dbdd5455c0b49ba3b29a9ce3c1fb181b2eef2e948689d55d046 --ctx-size 2048 --batch-size 512 --embedding --log-disable --parallel 1 --port 42197" time=2024-07-10T08:57:34.519+02:00 level=INFO source=sched.go:382 msg="loaded runners" count=1 time=2024-07-10T08:57:34.520+02:00 level=INFO source=server.go:556 msg="waiting for llama runner to start responding" time=2024-07-10T08:57:34.520+02:00 level=INFO source=server.go:594 msg="waiting for server to become available" status="llm server error" time=2024-07-10T08:57:34.771+02:00 level=ERROR source=sched.go:388 msg="error loading llama server" error="llama runner process has terminated: signal: illegal instruction (core dumped) " [GIN] 2024/07/10 - 08:57:34 | 500 | 277.570917ms | 127.0.0.1 | POST "/api/chat" ----------------------------------------------------------------------------- Command message: dev@localhost:~> ollama run deepseek-coder-v2:latest Error: llama runner process has terminated: signal: illegal instruction (core dumped) dev@localhost:~> -------------------------------------------------------------------- The same result with llama3 and gemma(2). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228659] New: Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 21 Apr '25

21 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1228659 Bug ID: 1228659 Summary: Snapshot 20240730 - unbootable after transactional-update dup Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Transactional Update Assignee: aplanas(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All Aeon installations (and I suspect all MicroOS systemd-boot installations) are failing to boot after a transactional-update dup to the latest snapshot I suspect the cause is the misbehaviour of the sdbootutil plugin reported during the transactional-update Example logs below: (25/41) Installing: kernel-default-6.10.2-1.1.x86_64 [... Error: No ESP detected. Legacy system? ................................................................................................... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.10.2-1-default 6.10.2-1-default dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: No KEYMAP configured. dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut-install: ERROR: installing 'grub2-editenv' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.kGpiZ2/initramfs -a date btrfs awk grub2-editenv dracut[I]: *** Including module: pcr-signature *** dracut[I]: *** Including module: transactional-update *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[E]: Failed to detect udev version! dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Generating early-microcode cpio image *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=btrfs dracut[I]: rd.driver.pre=overlay dracut[I]: root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=403,subvol=/@/.snapshots/98/snapshot,subvol=@/.snapshots/98/snapshot dracut[I]: *** Stripping files *** dracut[I]: *** Stripping files done *** dracut[I]: *** Creating image file '/boot/initrd-6.10.2-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.10.2-1-default' done *** /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory CA enrolled. Skip /etc/uefi/certs/1F673297.crt Error: No ESP detected. Legacy system? ... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory done] -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1229396] New: Old kernel file and initrd not deleted when removing kernels with systemd boot
by bugzilla_noreply＠suse.com 19 Apr '25

19 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1229396 Bug ID: 1229396 Summary: Old kernel file and initrd not deleted when removing kernels with systemd boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: rosuna(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Problem as explained in description. I reported it as a zypper problem, so this issue will probably be closed as invalid: https://github.com/openSUSE/zypper/issues/564 OS: openSUSE Tumbleweed Bootloader: systemd boot Other info: encrypted filesystem Does this always happened? At least I can confirm it for the last two kernel updates. Which files are the ones I'm reporting as not having been deleted as expected? They're under /boot/efi/bad01a2647cb4fef8827293b9d389245 (obviously the last directory has some random string related to systemd boot). There's a kernel directory for each installed version there, containing the kernel itself and at least one initrd (more if dracut has been called several times). Why am I reporting this? The default size for /boot/efi defaults to half a GB, which seems to be enough... Well, I'm definitely going to double that in my next installation, but even with the default 2 kernels, this is easy to fill if calling dracut for whatever reasons (and sometimes, scripts are the ones calling it). If one of the kernels to be purged is not actually purged there, the partition gets filled very easily. I'm attaching some output to illustrate it. Let me know if you need anything else. Please also let me know if this is not zypper purge-kernels's fault (and if possible, point me to where to report this). mordor:~ # rpm -qa | grep -i kernel-default kernel-default-6.10.3-1.1.x86_64 kernel-default-6.10.4-1.1.x86_64 mordor:~ # uname -a Linux mordor.arkayate.org 6.10.4-1-default #1 SMP PREEMPT_DYNAMIC Mon Aug 12 05:49:20 UTC 2024 (0363a35) x86_64 x86_64 x86_64 GNU/Linux mordor:~ # ls -l /boot/efi/bad01a2647cb4fef8827293b9d389245/ total 12 drwxr-x--- 2 root root 4096 Aug 16 22:55 6.10.2-1-default drwxr-x--- 2 root root 4096 Aug 16 22:55 6.10.3-1-default drwxr-x--- 2 root root 4096 Aug 16 22:55 6.10.4-1-default mordor:~ # du -sh /boot/efi/bad01a2647cb4fef8827293b9d389245/* 175M /boot/efi/bad01a2647cb4fef8827293b9d389245/6.10.2-1-default 95M /boot/efi/bad01a2647cb4fef8827293b9d389245/6.10.3-1-default 175M /boot/efi/bad01a2647cb4fef8827293b9d389245/6.10.4-1-default mordor:~ # df -h /boot/efi/ Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p1 511M 449M 63M 88% /boot/efi mordor:~ # zypper purge-kernels -D Reading installed packages... Preparing to purge obsolete kernels... Configuration: latest,latest-1,running Running kernel release: 6.10.4-1-default Running kernel arch: x86_64 Resolving package dependencies... Nothing to do. In the output above, the directory /boot/efi/bad01a2647cb4fef8827293b9d389245/6.10.2-1-default should get deleted (I believe that by zypper purge-kernels, but not 100% sure). P.S.: Completely unrelated, but I'm happy to have seen that my FDE encryption with TPM chip as decryption key now survives kernel updates, this was also broken and got fixed recently, even before I could report this. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1224103] New: Hybrid sleep wakes up on bluetooth device (normal sleep does not)
by bugzilla_noreply＠suse.com 18 Apr '25

18 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1224103 Bug ID: 1224103 Summary: Hybrid sleep wakes up on bluetooth device (normal sleep does not) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: katonag(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I send my laptop to hybrid sleep it wakes up when I power on my bluetooth headset. Using simple sleep works as expected. This is only happening since a few weeks. I have also added a rule to udev: ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="8087", ATTR{power/wakeup}="disabled" because my bluetooth adapter shows up in lsusb, but there is no change. The system is Tumbleweed 20240503 with KDE6. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223674] New: tensorflow-lite fails to build with GCC 13, keeps gcc12 from being removed
by bugzilla_noreply＠suse.com 18 Apr '25

18 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1223674 Bug ID: 1223674 Summary: tensorflow-lite fails to build with GCC 13, keeps gcc12 from being removed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When building tensorflow-lite with GCC 13 (the default compiler), there's a spurious -Wstringop-overflow diagnostic promoted to an error becuause we build the package with -Werror. Adding -Wno-error=stringop-overflow causes other issues to appear: [ 51s] In file included from /home/abuild/rpmbuild/BUILD/tensorflow-2.10.0/tflite-build/build/abseil-cpp/absl/strings/internal/str_format/extension.cc:16: [ 51s] /home/abuild/rpmbuild/BUILD/tensorflow-2.10.0/tflite-build/build/abseil-cpp/absl/strings/internal/str_format/extension.h:34:6: warning: elaborated-type-specifier for a scoped enum must not use the ‘class’ keyword [ 51s] 34 | enum class FormatConversionChar : uint8_t; [ 51s] | ~~~~ ^~~~~ [ 51s] | ----- [ 51s] /home/abuild/rpmbuild/BUILD/tensorflow-2.10.0/tflite-build/build/abseil-cpp/absl/strings/internal/str_format/extension.h:34:33: error: found ‘:’ in nested-name-specifier, expected ‘::’ [ 51s] 34 | enum class FormatConversionChar : uint8_t; [ 51s] | ^ [ 51s] | :: ... [ 51s] /home/abuild/rpmbuild/BUILD/tensorflow-2.10.0/tflite-build/build/abseil-cpp/absl/strings/internal/str_format/extension.h:173:8: warning: elaborated-type-specifier for a scoped enum must not use the ‘class’ keyword [ 51s] 173 | enum class Enum : uint8_t { [ 51s] | ~~~~ ^~~~~ [ 51s] | ----- and more Likely fixed in newer upstream versions of tensorflow. -- You are receiving this mail because: You are on the CC list for the bug.

1 5