December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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 1233423] New: No wifi adapter with kernel-default-5.14.21-150500.2.1.gc4d3cf0.x86_64
by bugzilla_noreply＠suse.com 21 Apr '25

21 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1233423 Bug ID: 1233423 Summary: No wifi adapter with kernel-default-5.14.21-150500.2.1.gc4d3cf0.x86_64 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Networking Assignee: kernel-bugs(a)suse.de Reporter: chcao(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug report comes from bsc#1233134: https://bugzilla.suse.com/show_bug.cgi?id=1233134#c18: After having kernel-default-5.14.21-150500.2.1.gc4d3cf0.x86_64.rpm installed on my laptop Leap15.5, AMD Ryzen 7 PRO 5850U, the system can not connect with wifi, there's no WIFI adapter. Steps: - download the kernel-default-5.14.21-150500.2.1.gc4d3cf0.x86_64.rpm from patch: https://download.opensuse.org/repositories/home:/tiwai:/bsc1233134/pool/ - rpm -Uvh kernel-default-5.14.21-150500.2.1.gc4d3cf0.x86_64.rpm --force --nodeps - reboot - Turn the secure boot off from BIOS, and boot continue After boot to OS, my laotop can not connect to wifi, there's no wifi adapter. If any more info needed here, please feel free to contact me, thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[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

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 18 Apr '25

18 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed:<br/><br/>[...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 1233542] New: patterns-base forces chrony which prevents use of other ntpd applications.
by bugzilla_noreply＠suse.com 17 Apr '25

17 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1233542 Bug ID: 1233542 Summary: patterns-base forces chrony which prevents use of other ntpd applications. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am using ntpd-rs which correctly conflicts on other ntp-daemons: https://build.opensuse.org/projects/network:time/packages/ntpd-rs/files/ntp… This causes leap upgrades to break, since patterns-base-base-20200505-59 now *requires* chrony. Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Problem: 1: the to be installed patterns-base-base-20200505-59.1.x86_64 requires 'chrony', but this requirement cannot be provided not installable providers: chrony-4.6-165.5.i586[network_time] chrony-4.6-165.5.x86_64[network_time] chrony-4.6-1.2.x86_64[openSUSE-20240830-0] chrony-4.6-1.2.x86_64[repo-oss] Solution 1: deinstallation of ntpd-rs-1.3.0-13.4.x86_64 Solution 2: deinstallation of patterns-base-base-20200505-57.1.x86_64 Solution 3: keep obsolete patterns-base-base-20200505-57.1.x86_64 Solution 4: break patterns-base-base-20200505-59.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): patterns-base-base should *not force* chrony on systems which prevents upgrades. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1234765] New: systemd-network recommends development package
by bugzilla_noreply＠suse.com 16 Apr '25

16 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1234765 Bug ID: 1234765 Summary: systemd-network recommends development package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Normally no run-time package should depend on a development package. tw:/run/systemd/network # zypper in systemd-network Loading repository data... Reading installed packages... Resolving package dependencies... The following recommended package was automatically selected: libidn2-devel The following 2 NEW packages are going to be installed: libidn2-devel systemd-network -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224386] New: Please package systemd-resolved seperate from systemd-network
by bugzilla_noreply＠suse.com 16 Apr '25

16 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1224386 Bug ID: 1224386 Summary: Please package systemd-resolved seperate from systemd-network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I get why resolved is packaged with networkd but there's also use cases where resolved would be very , very useful, even with NetworkManager eg. I want it for openSUSE Aeon, with GNOME, with NetworkManager, but using resovled for more intelligent DNS resolution as people hop networks/VPNs. Could we please package -resolved as it's own seperate thing and have it required by -networkd, as I really wouldn't like to have -networkd installed if I can avoid it. -- You are receiving this mail because: You are on the CC list for the bug.

1 1