April 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1240650] New: Temporary brightness glitch on startup screen
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1240650 Bug ID: 1240650 Summary: Temporary brightness glitch on startup screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: elydgolden(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Pretty much the title. Affects openSUSE Tumbleweed 20250329. Not sure where the bug is but probably in the kernel or plymouth if I had to guess. Hardware is an Acer Aspire A715-42G -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1241986] New: r8169 breaks after upgrading to 6.14.3-1
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241986 Bug ID: 1241986 Summary: r8169 breaks after upgrading to 6.14.3-1 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: enzooocf(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently im on 6.14.3-1-default where it works fine. after upgrading to kernel-default-6.14.4-1.1 it no longer works. I cant get it up and running again even after several reboots and reloading the module. hw ino: ``` sata@t14:~$ lspci -nnk | grep -iA3 ether pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e) Subsystem: Lenovo Device [17aa:50ee] Kernel driver in use: r8169 Kernel modules: r8169 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1240894] New: rpmlint report python-bytecode-inconsistent-mtime when building python packages locally
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1240894 Bug ID: 1240894 Summary: rpmlint report python-bytecode-inconsistent-mtime when building python packages locally 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: daniel.garcia(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- rpmlint report python-bytecode-inconsistent-mtime when building python packages locally. Looks like the mtime of .pyc files is different from source mtime when running "osc build". This error is not happening in OBS so it might depend on the mount options for the FS you use for local building that the mtime/atime and so on are not maintained as the check expects. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1241946] New: Opening a USB Device Causes It to Reconnect
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241946 Bug ID: 1241946 Summary: Opening a USB Device Causes It to Reconnect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: petershh(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am trying to open a USB device (if that matters, it's Daheng Imaging camera, ID 2ba2:4d55, it doesn't have any kernel) through libusb. When I open it, open(2) syscall after a small delay returns ENODEV and device gets reconnected. Libusb debug log: [ 0.008016] [0000585f] libusb: debug [libusb_open] open 4.9 [ 2.183466] [0000585f] libusb: error [get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/004/009, errno=19 [ 2.183504] [0000585f] libusb: debug [libusb_open] open 4.9 returns -1 Kernel log: Apr 27 23:36:14 eternity kernel: usb 4-1: USB disconnect, device number 9 Apr 27 23:36:17 eternity kernel: usb 4-1: new SuperSpeed USB device number 10 using xhci_hcd Apr 27 23:36:17 eternity kernel: usb 4-1: New USB device found, idVendor=2ba2, idProduct=4d55, bcdDevice= 0.00 Apr 27 23:36:17 eternity kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=10 Apr 27 23:36:17 eternity kernel: usb 4-1: Product: MER2-503-36U3M Apr 27 23:36:17 eternity kernel: usb 4-1: Manufacturer: Daheng Imaging Apr 27 23:36:17 eternity kernel: usb 4-1: SerialNumber: FCK23090082 Kernel version: Linux eternity 6.14.3-1-default #1 SMP PREEMPT_DYNAMIC Mon Apr 21 06:23:20 UTC 2025 (493ad77) x86_64 x86_64 x86_64 GNU/Linux Tubmleweed version: 20250425 This bug does not seem to reproduce on Arch Linux with the same kernel version. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1242092] New: fuseiso: migration to fuse 3 and deprecation of fuse (1)
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1242092 Bug ID: 1242092 Summary: fuseiso: migration to fuse 3 and deprecation of fuse (1) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: dsterba(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: qa-bugs(a)suse.de Blocks: 1242079 Target Milestone: --- Found By: --- Blocker: --- Dear maintainer, please update your package to use fuse 3 instead of fuse. That would be pkgconfig(fuse3) as provided by fuse3-devel, and libfuse3.so.* - instead of pkgconfig(fuse) from fuse-devel, and libfuse.so.2. Do not forget to change "Requires: fuse" to "Requires: fuse3" if specified. As usual please perform any testing you need to be comfortable with this change. As with other such changes, please do one of the following: 1. If upstream already supports it, build your package to fuse 3 2. If needed, bump to an upstream version that supports fuse 3 and use it. 3. Pull a change from upstream git if unreleased, or a WIP pull request 4. Raise an upstream bug to request a change to support fuse 3. 5. copy a patch from another distribution, see links 6. write a downstream patch 7. (not desired) check if the package is still actively maintained, or if there are forks If you submitted to openSUSE:Factory please just comment the request into the bug and resolve it. For general discussion see parent bug. Similar efforts: https://release.debian.org/transitions/html/fuse-to-fuse3.html Many thanks, Andreas From fuseiso.spec: > BuildRequires: fuse-devel > Requires: fuse Debian patch: https://salsa.debian.org/debian/fuseiso/-/blob/debian/unstable/debian/patch… -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1240411] New: [SELinux] cannot login from terminal nor from gui (sddm/plasma wayland)
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1240411 Bug ID: 1240411 Summary: [SELinux] cannot login from terminal nor from gui (sddm/plasma wayland) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mrkcee(a)protonmail.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed (aarch64) SELinux status, mode and policy name: SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 SELinux policy version and repository: 20250324-1.1 repo-oss The software (incl. version) that is affected by the SELinux issue and the error message: I cannot log in whether via terminal or gui. It just goes back to the prompt after trying. SELinux Audit log: 1. When logging in via gui / sddm: Mar 26 22:14:25 xxxxxxx systemd[1538]: selinux: avc: denied { start } for auid=1000 uid=1000 gid=1000 path="/usr/lib/systemd/user/plasma-workspace-wayland.target" cmdline="/usr/bin/startplasma-wayland" function="bus_unit_method_start_generic" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_unit_file_t:s0 tclass=service permissive=0 ---- Mar 26 22:07:51 xxxxxxx systemd[1544]: selinux: avc: denied { start } for auid=1000 uid=1000 gid=1000 path="/usr/lib/systemd/user/plasma-ksplash.service" cmdline="/usr/bin/startplasma-wayland" function="bus_unit_method_start_generic" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:systemd_unit_file_t:s0 tclass=service permissive=0 no avcs in ausearch 2. When logging in terminal (have not tried logging in yet in gui) time->Wed Mar 26 23:15:01 2025 type=USER_AVC msg=audit(1743002101.365:145): pid=947 uid=498 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:system_r:systemd_homed_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-broker" sauid=498 hostname=? addr=? terminal=?' ---- time->Wed Mar 26 23:15:01 2025 type=USER_AVC msg=audit(1743002101.394:147): pid=947 uid=498 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:system_r:systemd_homed_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-broker" sauid=498 hostname=? addr=? terminal=?' ---- time->Wed Mar 26 23:15:01 2025 type=USER_AVC msg=audit(1743002101.413:151): pid=947 uid=498 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:system_r:systemd_homed_t:s0 tclass=dbus permissive=0 exe="/usr/bin/dbus-broker" sauid=498 hostname=? addr=? terminal=?' Any other important details: I am able to log in the terminal AFTER trying to log in via gui. I am running openSUSE Tumbleweed aarch64 on Apple Silicon. I know this is not a standard setup but I don't think it should matter. I am also using systemd-homed. Everything was running fine until I updated to Tumbleweed aarch64 snapshot 20250324. I just don't remember which snapshot I was in before updating. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1228804] New: Regression: qemu-uefi-aarch64 does not work with virtualization=on anymore
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1228804 Bug ID: 1228804 Summary: Regression: qemu-uefi-aarch64 does not work with virtualization=on anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: jlee(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: virt-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- qemu-system-aarch64 -M virt,virtualization=on -cpu max -m 4G -smp 4 -bios /usr/share/qemu/aavmf-aarch64-code.bin -serial stdio used to work with qemu-uefi-aarch64-202208-150500.4.1.noarch (From 15.5) but does not work with newer versions such as qemu-uefi-aarch64-202402-1.1.noarch (from TW), it just data aborts immediately before any output (visible with -d int). The latest build from linaro works fine though: wget https://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upst… qemu-system-aarch64 -M virt,virtualization=on -cpu max -m 4G -smp 4 -bios QEMU_EFI.fd -serial stdio -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1242079] New: TRACKERBUG: migration to fuse 3 and deprecation of fuse (1)
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1242079 Bug ID: 1242079 Summary: TRACKERBUG: migration to fuse 3 and deprecation of fuse (1) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: Andreas.Stieger(a)gmx.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug tracks the work needed to migrate to fuse 3 to allow the deprecation of fuse (1). Rationale: fuse 3 appeared upstream 2016, and in openSUSE 2018. fuse 2.9.9 was released 2019-01-04 and should be considered deprecated. Similar efforts: https://release.debian.org/transitions/html/fuse-to-fuse3.html Starting counts: build requires fuse (transitive) : 136 build requires fuse fuse3 (transitive): 64 requires libfuse.so.2 : 70 requires libfuse3.so.4: 30 requires: "fuse" : 30 requires: "fuse3": 10 Maintainer text follows. --- Dear maintainer, please update your package to use fuse 3 instead of fuse. That would be pkgconfig(fuse3) as provided by fuse3-devel, and libfuse3.so.* - instead of pkgconfig(fuse) from fuse-devel, and libfuse.so.2. Do not forget to change "Requires: fuse" to "Requires: fuse3" if specified. As usual please perform any testing you need to be comfortable with this change. As with other such changes, please do one of the following: 1. If upstream already supports it, build your package to fuse 3 2. If needed, bump to an upstream version that supports fuse 3 and use it. 3. Pull a change from upstream git if unreleased, or a WIP pull request 4. Raise an upstream bug to request a change to support fuse 3. 5. copy a patch from another distribution, see links 6. write a downstream patch 7. (not desired) check if the package is still actively maintained, or if there are forks If you submitted to openSUSE:Factory please just comment the request into the bug and resolve it. For general discussion see parent bug. Similar efforts: https://release.debian.org/transitions/html/fuse-to-fuse3.html Many thanks, Andreas -- You are receiving this mail because: You are on the CC list for the bug.

1 57

[Bug 1241885] New: Kernel BUG in btrfs-transaction when enabling tracepoints
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241885 Bug ID: 1241885 Summary: Kernel BUG in btrfs-transaction when enabling tracepoints Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I did localhost:/sys/kernel/tracing/events # echo 1 > enable and a few seconds later, the kernel breaks due to a NULL deref: [ 60.994942] [ C3] Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and stat_runtime require the kernel parameter schedstats=enable or kernel.sched_schedstats=1 [ 66.337222] [ T599] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 66.337250] [ T599] #PF: supervisor read access in kernel mode [ 66.337263] [ T599] #PF: error_code(0x0000) - not-present page [ 66.337275] [ T599] PGD 0 P4D 0 [ 66.337286] [ T599] Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI [ 66.337300] [ T599] CPU: 3 UID: 0 PID: 599 Comm: btrfs-transacti Not tainted 6.14.2-5-default #1 openSUSE Tumbleweed dc04f669912e0958ce31a6ac4199441a5dc82ed5 [ 66.337322] [ T599] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 [ 66.337337] [ T599] RIP: 0010:trace_event_raw_event_btrfs__prelim_ref+0x73/0x130 [btrfs] [ 66.337398] [ T599] Code: e8 42 48 5a ea 48 85 c0 74 78 4d 85 e4 0f 84 90 00 00 00 49 8b 94 24 c0 06 00 00 48 8b 0a 48 89 48 08 48 8b 52 08 48 89 50 10 <49> 8b 55 18 48 89 50 18 49 8b 55 20 48 89 50 20 41 0f b6 55 28 88 [ 66.337424] [ T599] RSP: 0018:ffffb55a0070f770 EFLAGS: 00010286 [ 66.337437] [ T599] RAX: ffff8ccec3c75d3c RBX: ffff8ccec9105f50 RCX: db432689768cd6ed [ 66.337451] [ T599] RDX: 76eb822809e8cfac RSI: ffff8ccec3c75d38 RDI: ffff8ccec3c75d38 [ 66.337464] [ T599] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000010 [ 66.337478] [ T599] R10: 00000000000027e4 R11: 00000000ffffffff R12: ffff8ccec63cb000 [ 66.337492] [ T599] R13: 0000000000000000 R14: ffffb55a0070f778 R15: 0000000000000000 [ 66.337510] [ T599] FS: 0000000000000000(0000) GS:ffff8ccf3bd80000(0000) knlGS:0000000000000000 [ 66.337546] [ T599] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 66.337572] [ T599] CR2: 0000000000000018 CR3: 0000000102338000 CR4: 0000000000750ef0 [ 66.337593] [ T599] PKRU: 55555554 [ 66.337604] [ T599] Call Trace: [ 66.337618] [ T599] <TASK> [ 66.337636] [ T599] prelim_ref_insert+0x1c1/0x270 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.337711] [ T599] add_prelim_ref+0x9a/0x100 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.337764] [ T599] find_parent_nodes+0x148f/0x1ed0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.337825] [ T599] ? ulist_alloc+0x55/0xa0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.337882] [ T599] ? srso_alias_return_thunk+0x5/0xfbef5 [ 66.337899] [ T599] ? trace_event_raw_event_kmalloc+0x7a/0xc0 [ 66.337919] [ T599] ? __entry_text_end+0x101e45/0x101e49 [ 66.337934] [ T599] ? __kmalloc_cache_noprof+0x26f/0x430 [ 66.337957] [ T599] btrfs_find_all_roots_safe+0x96/0x140 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338013] [ T599] btrfs_qgroup_trace_extent_post+0x8f/0xd0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338074] [ T599] add_delayed_ref+0x41d/0x900 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338137] [ T599] btrfs_free_tree_block+0xc2/0x260 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338200] [ T599] btrfs_force_cow_block+0x31a/0x780 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338260] [ T599] btrfs_cow_block+0xcd/0x230 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338315] [ T599] btrfs_search_slot+0x518/0xe40 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338373] [ T599] ? __btrfs_run_delayed_items+0x30/0x290 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338431] [ T599] btrfs_lookup_inode+0x3c/0xc0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338492] [ T599] __btrfs_update_delayed_inode+0x74/0x2b0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338556] [ T599] __btrfs_run_delayed_items+0x19f/0x290 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338612] [ T599] btrfs_commit_transaction+0x186/0xb90 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338676] [ T599] transaction_kthread+0x159/0x1c0 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.338731] [ T599] ? __pfx_transaction_kthread+0x10/0x10 [btrfs 5694dd95f2817ba592633ea583377520ce418b16] [ 66.339153] [ T599] kthread+0xec/0x220 [ 66.339512] [ T599] ? __pfx_kthread+0x10/0x10 [ 66.339832] [ T599] ret_from_fork+0x31/0x50 [ 66.340130] [ T599] ? __pfx_kthread+0x10/0x10 [ 66.340423] [ T599] ret_from_fork_asm+0x1a/0x30 [ 66.340734] [ T599] </TASK> [ 66.341019] [ T599] Modules linked in: af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct rfkill nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink nls_iso8859_1 nls_cp437 vfat fat intel_rapl_msr intel_rapl_common kvm_amd ccp iTCO_wdt i2c_i801 intel_pmc_bxt iTCO_vendor_support kvm virtio_net i2c_smbus pcspkr i2c_mux lpc_ich net_failover virtio_balloon failover tiny_power_button joydev button loop fuse dm_mod configfs efi_pstore ip_tables x_tables sr_mod cdrom hid_generic usbhid polyval_clmulni ahci polyval_generic ghash_clmulni_intel libahci sha512_ssse3 virtio_scsi libata sha256_ssse3 sd_mod sha1_ssse3 scsi_dh_emc scsi_dh_rdac scsi_dh_alua sg aesni_intel xhci_pci crypto_simd xhci_hcd scsi_mod cryptd virtio_gpu usbcore virtio_blk scsi_common virtio_dma_buf serio_raw btrfs blake2b_generic xor raid6_pq efivarfs dmi_sysfs qemu_fw_cfg virtio_rng [ 66.342979] [ T599] CR2: 0000000000000018 [ 66.343296] [ T599] ---[ end trace 0000000000000000 ]--- [ 66.343642] [ T599] RIP: 0010:trace_event_raw_event_btrfs__prelim_ref+0x73/0x130 [btrfs] [ 66.343996] [ T599] Code: e8 42 48 5a ea 48 85 c0 74 78 4d 85 e4 0f 84 90 00 00 00 49 8b 94 24 c0 06 00 00 48 8b 0a 48 89 48 08 48 8b 52 08 48 89 50 10 <49> 8b 55 18 48 89 50 18 49 8b 55 20 48 89 50 20 41 0f b6 55 28 88 [ 66.344659] [ T599] RSP: 0018:ffffb55a0070f770 EFLAGS: 00010286 [ 66.345007] [ T599] RAX: ffff8ccec3c75d3c RBX: ffff8ccec9105f50 RCX: db432689768cd6ed [ 66.345339] [ T599] RDX: 76eb822809e8cfac RSI: ffff8ccec3c75d38 RDI: ffff8ccec3c75d38 [ 66.345677] [ T599] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000010 [ 66.346009] [ T599] R10: 00000000000027e4 R11: 00000000ffffffff R12: ffff8ccec63cb000 [ 66.346340] [ T599] R13: 0000000000000000 R14: ffffb55a0070f778 R15: 0000000000000000 [ 66.346683] [ T599] FS: 0000000000000000(0000) GS:ffff8ccf3bd80000(0000) knlGS:0000000000000000 [ 66.347013] [ T599] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 66.347341] [ T599] CR2: 0000000000000018 CR3: 0000000102338000 CR4: 0000000000750ef0 [ 66.347688] [ T599] PKRU: 55555554 [ 66.348050] [ T599] note: btrfs-transacti[599] exited with irqs disabled [ 66.348449] [ T599] note: btrfs-transacti[599] exited with preempt_count 2 Linux localhost.localdomain 6.14.2-5-default #1 SMP PREEMPT_DYNAMIC Mon Apr 14 06:14:46 UTC 2025 (5512154) x86_64 x86_64 x86_64 GNU/Linux The system is unusable afterwards as the filesystem is no longer responding. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1241890] New: texlive-scheme-full requires unavailable texlive-kpathsea-bin >= 2025
by bugzilla_noreply＠suse.com 13 May '25

13 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241890 Bug ID: 1241890 Summary: texlive-scheme-full requires unavailable texlive-kpathsea-bin >= 2025 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: hierher(a)ymail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 882149 --> https://bugzilla.suse.com/attachment.cgi?id=882149&action=edit Dockerfile including the command that fails and all I've done before Hi all! I am running in a bug when I try to install TeXLive in the latest version. On a fresh install of Leap 15.6, when I try to run zypper install texlive-scheme-full with the repo from https://download.opensuse.org/repositories/Publishing:TeXLive/15.6/Publishi…, I get this error: Problem: 1: nothing provides 'texlive-kpathsea-bin >= 2025' needed by the to be installed texlive-xdvi-2025.218.svn62387-lp156.215.2.noarch Solution 1: do not install texlive-scheme-full-2025.220.svn54074-lp156.247.1.noarch Solution 2: break texlive-xdvi-2025.218.svn62387-lp156.215.2.noarch by ignoring some of its dependencies I think there's an issue with the dependencies. For reference, I attach my Dockerfile I am trying to build, and the lines above occur in L 13. Would be great if someone could fix the respective dependency. Cheers! PBiel -- You are receiving this mail because: You are on the CC list for the bug.

1 1