May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223373] New: VUL-0: CVE-2024-32879: python-social-auth: Improper Handling of Case Sensitivity in social-auth-app-django
by bugzilla_noreply＠suse.com 10 Jun '24

10 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223373 Bug ID: 1223373 Summary: VUL-0: CVE-2024-32879: python-social-auth: Improper Handling of Case Sensitivity in social-auth-app-django Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/403106/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Python Social Auth is a social authentication/registration mechanism. Prior to version 5.4.1, due to default case-insensitive collation in MySQL or MariaDB databases, third-party authentication user IDs are not case-sensitive and could cause different IDs to match. This issue has been addressed by a fix released in version 5.4.1. An immediate workaround would be to change collation of the affected field. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-32879 https://www.cve.org/CVERecord?id=CVE-2024-32879 https://github.com/python-social-auth/social-app-django/commit/31c3e0c7edb1… https://github.com/python-social-auth/social-app-django/pull/566 https://github.com/python-social-auth/social-app-django/security/advisories… https://bugzilla.redhat.com/show_bug.cgi?id=2277035 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224805] New: Failed to start kdump on update
by bugzilla_noreply＠suse.com 10 Jun '24

10 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224805 Bug ID: 1224805 Summary: Failed to start kdump on update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Looks like this was caused due to being short on memory, but as the machine has SWAP available, could you please confirm that this is not a product bug? # free -m total used free shared buff/cache available Mem: 892 510 44 16 389 382 Swap: 2050 583 1467 2024-05-17T03:32:24.281360+02:00 unreal6 sh[18901]: (537/566) Installing: kdump-2.0.3+git10.gfdb71b2-150600.1.2.x86_64 [... 2024-05-17T03:32:24.281604+02:00 unreal6 sh[18901]: Updating /etc/sysconfig/kdump ... 2024-05-17T03:32:24.334296+02:00 unreal6 systemd[1]: Reloading requested from client PID 18611 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:24.334360+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:24.924343+02:00 unreal6 systemd[1]: Reloading finished in 589 ms. 2024-05-17T03:32:24.961835+02:00 unreal6 systemd[1]: Reloading requested from client PID 18656 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:24.961918+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:25.630446+02:00 unreal6 systemd[1]: Reloading finished in 667 ms. 2024-05-17T03:32:25.666952+02:00 unreal6 systemd[1]: Reloading requested from client PID 18704 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:25.667019+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:26.369634+02:00 unreal6 systemd[1]: Reloading finished in 702 ms. 2024-05-17T03:32:26.439702+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump.service". 2024-05-17T03:32:26.439788+02:00 unreal6 systemd[1]: Reloading requested from client PID 18754 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:26.439877+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:27.110180+02:00 unreal6 systemd[1]: Reloading finished in 669 ms. 2024-05-17T03:32:27.144729+02:00 unreal6 [RPM][18604]: install kdump-2.0.3+git10.gfdb71b2-150600.1.2.x86_64: success 2024-05-17T03:32:27.149403+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump-early.service". 2024-05-17T03:32:27.149452+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump-notify.service". 2024-05-17T03:32:27.149507+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump.service -> /usr/lib/systemd/system/kdump.service. 2024-05-17T03:32:27.149542+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump-early.service -> /usr/lib/systemd/system/kdump-early.service. 2024-05-17T03:32:27.149574+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump-notify.service -> /usr/lib/systemd/system/kdump-notify.service. 2024-05-17T03:32:27.149596+02:00 unreal6 sh[18901]: Stopping kdump ... 2024-05-17T03:32:27.169840+02:00 unreal6 systemd[1]: Reloading requested from client PID 18804 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:27.169906+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:27.792978+02:00 unreal6 systemd[1]: Reloading finished in 622 ms. 2024-05-17T03:32:27.854093+02:00 unreal6 systemd[1]: Stopping Load kdump kernel and initrd... 2024-05-17T03:32:27.872108+02:00 unreal6 unload.sh[18863]: config option KDUMP_COPY_KERNEL is deprecated, ignoring 2024-05-17T03:32:27.896361+02:00 unreal6 systemd[1]: kdump.service: Deactivated successfully. 2024-05-17T03:32:27.930224+02:00 unreal6 systemd[1]: Stopped Load kdump kernel and initrd. 2024-05-17T03:32:27.978698+02:00 unreal6 systemd[1]: Starting Load kdump kernel and initrd... 2024-05-17T03:32:27.994187+02:00 unreal6 load.sh[18867]: config option KDUMP_COPY_KERNEL is deprecated, ignoring 2024-05-17T03:32:30.191833+02:00 unreal6 auditd[826]: Audit daemon rotating log files 2024-05-17T03:32:49.966979+02:00 unreal6 load.sh[22533]: console=com3 in Xen commandline not handled 2024-05-17T03:32:49.980421+02:00 unreal6 load.sh[18867]: Starting kdump kernel load; kexec cmdline: /sbin/kexec -p /var/lib/kdump/kernel --append=" console=ttyS2,115200n8 sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/var/lib/kdump/initrd -a 2024-05-17T03:32:50.552928+02:00 unreal6 kernel: [300981.080213][T22543] kexec: page allocation failure: order:4, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 2024-05-17T03:32:50.552957+02:00 unreal6 kernel: [300981.093661][T22543] CPU: 5 PID: 22543 Comm: kexec Tainted: G n 6.4.0-150600.17-default #1 SLE15-SP6 8d7122a8d4d10b24a1d15f496e70a80423123bfb 2024-05-17T03:32:50.686496+02:00 unreal6 kernel: [300981.107928][T22543] Hardware name: Supermicro X10SLD-F/HF/X10SLD, BIOS 3.2 05/10/2018 2024-05-17T03:32:50.686507+02:00 unreal6 kernel: [300981.107930][T22543] Call Trace: 2024-05-17T03:32:50.686508+02:00 unreal6 kernel: [300981.107932][T22543] <TASK> 2024-05-17T03:32:50.686509+02:00 unreal6 kernel: [300981.107936][T22543] dump_stack_lvl+0x44/0x60 2024-05-17T03:32:50.686509+02:00 unreal6 kernel: [300981.107942][T22543] warn_alloc+0x116/0x190 2024-05-17T03:32:50.686521+02:00 unreal6 kernel: [300981.107946][T22543] __alloc_pages_slowpath.constprop.76+0xd21/0xda0 2024-05-17T03:32:50.686522+02:00 unreal6 kernel: [300981.107949][T22543] ? mas_alloc_nodes+0x58/0x200 2024-05-17T03:32:50.686523+02:00 unreal6 kernel: [300981.142000][T22543] __alloc_pages+0x306/0x350 2024-05-17T03:32:50.686523+02:00 unreal6 kernel: [300981.142018][T22543] ? privcmd_buf_mmap+0x40/0x140 [xen_privcmd 934db45836cbae60a50a9c21606f8d0a484d9c16] 2024-05-17T03:32:50.686524+02:00 unreal6 kernel: [300981.142021][T22543] __kmalloc_large_node+0x7a/0x140 2024-05-17T03:32:50.686525+02:00 unreal6 kernel: [300981.142023][T22543] __kmalloc+0xbe/0x130 2024-05-17T03:32:50.686532+02:00 unreal6 kernel: [300981.142025][T22543] privcmd_buf_mmap+0x40/0x140 [xen_privcmd 934db45836cbae60a50a9c21606f8d0a484d9c16] 2024-05-17T03:32:50.686535+02:00 unreal6 kernel: [300981.142027][T22543] mmap_region+0x26c/0xa70 2024-05-17T03:32:50.686535+02:00 unreal6 kernel: [300981.179256][T22543] do_mmap+0x3c4/0x550 2024-05-17T03:32:50.686536+02:00 unreal6 kernel: [300981.179262][T22543] vm_mmap_pgoff+0xe1/0x1a0 2024-05-17T03:32:50.686537+02:00 unreal6 kernel: [300981.179266][T22543] ksys_mmap_pgoff+0x1a1/0x1e0 2024-05-17T03:32:50.686537+02:00 unreal6 kernel: [300981.179268][T22543] do_syscall_64+0x5b/0x80 2024-05-17T03:32:50.686538+02:00 unreal6 kernel: [300981.179271][T22543] ? syscall_exit_to_user_mode+0x1e/0x40 2024-05-17T03:32:50.686547+02:00 unreal6 kernel: [300981.179273][T22543] ? do_syscall_64+0x67/0x80 2024-05-17T03:32:50.686549+02:00 unreal6 kernel: [300981.179274][T22543] ? irq_exit_rcu+0x40/0xc0 2024-05-17T03:32:50.686550+02:00 unreal6 kernel: [300981.211457][T22543] ? xen_pv_evtchn_do_upcall+0x8f/0xa0 2024-05-17T03:32:50.686550+02:00 unreal6 kernel: [300981.211471][T22543] entry_SYSCALL_64_after_hwframe+0x77/0xe1 2024-05-17T03:32:50.686551+02:00 unreal6 kernel: [300981.211474][T22543] RIP: 0033:0x7ff96012a5f2 2024-05-17T03:32:50.686552+02:00 unreal6 kernel: [300981.227143][T22543] Code: 90 90 90 90 90 90 90 90 41 f7 c1 ff 0f 00 00 75 27 55 89 cd 53 48 89 fb 48 85 ff 74 3b 41 89 ea 48 89 df b8 09 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 76 5b 5d c3 0f 1f 00 48 8b 05 f9 47 0d 00 64 2024-05-17T03:32:50.686558+02:00 unreal6 kernel: [300981.227145][T22543] RSP: 002b:00007fffe14c8538 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 2024-05-17T03:32:50.686559+02:00 unreal6 kernel: [300981.227157][T22543] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff96012a5f2 2024-05-17T03:32:50.686559+02:00 unreal6 kernel: [300981.227158][T22543] RDX: 0000000000000003 RSI: 00000000012ea000 RDI: 0000000000000000 2024-05-17T03:32:50.686560+02:00 unreal6 kernel: [300981.227159][T22543] RBP: 0000000000000001 R08: 0000000000000004 R09: 0000000000000000 2024-05-17T03:32:50.686561+02:00 unreal6 kernel: [300981.227159][T22543] R10: 0000000000000001 R11: 0000000000000246 R12: 00000000000012ea 2024-05-17T03:32:50.686561+02:00 unreal6 kernel: [300981.227160][T22543] R13: 000055d5af63eb20 R14: 000055d5af63f480 R15: 000055d5af63fa80 2024-05-17T03:32:50.686566+02:00 unreal6 kernel: [300981.227163][T22543] </TASK> 2024-05-17T03:32:50.686576+02:00 unreal6 kernel: [300981.227246][T22543] Mem-Info: 2024-05-17T03:32:50.806334+02:00 unreal6 kernel: [300981.301023][T22543] active_anon:27322 inactive_anon:41870 isolated_anon:0 2024-05-17T03:32:50.806343+02:00 unreal6 kernel: [300981.301023][T22543] active_file:26410 inactive_file:35814 isolated_file:0 2024-05-17T03:32:50.806344+02:00 unreal6 kernel: [300981.301023][T22543] unevictable:16761 dirty:196 writeback:0 2024-05-17T03:32:50.806345+02:00 unreal6 kernel: [300981.301023][T22543] slab_reclaimable:22564 slab_unreclaimable:25083 2024-05-17T03:32:50.806365+02:00 unreal6 kernel: [300981.301023][T22543] mapped:15869 shmem:1831 pagetables:5681 2024-05-17T03:32:50.806368+02:00 unreal6 kernel: [300981.301023][T22543] sec_pagetables:0 bounce:0 2024-05-17T03:32:50.806368+02:00 unreal6 kernel: [300981.301023][T22543] kernel_misc_reclaimable:0 2024-05-17T03:32:50.806369+02:00 unreal6 kernel: [300981.301023][T22543] free:11073 free_pcp:149 free_cma:0 2024-05-17T03:32:50.806370+02:00 unreal6 kernel: [300981.301027][T22543] Node 0 active_anon:109288kB inactive_anon:167480kB active_file:105640kB inactive_file:143256kB unevictable:67044kB isolated(anon):0kB isolated(file):0kB mapped:63476kB dirty:784kB writeback:0kB shmem:7324kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:10260kB pagetables:22724kB sec_pagetables:0kB all_unreclaimable? no 2024-05-17T03:32:50.806370+02:00 unreal6 kernel: [300981.301030][T22543] Node 0 DMA free:3464kB boost:0kB min:64kB low:80kB high:96kB reserved_highatomic:0KB active_anon:1056kB inactive_anon:1960kB active_file:1272kB inactive_file:1300kB unevictable:12kB writepending:0kB present:15968kB managed:15908kB mlocked:12kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 2024-05-17T03:32:50.806377+02:00 unreal6 kernel: [300981.301034][T22543] lowmem_reserve[]: 0 849 849 849 849 2024-05-17T03:32:50.806378+02:00 unreal6 kernel: [300981.301036][T22543] Node 0 DMA32 free:40828kB boost:0kB min:3696kB low:4620kB high:5544kB reserved_highatomic:2048KB active_anon:108348kB inactive_anon:165472kB active_file:104448kB inactive_file:141932kB unevictable:67032kB writepending:720kB present:1032604kB managed:898080kB mlocked:63960kB bounce:0kB free_pcp:600kB local_pcp:0kB free_cma:0kB 2024-05-17T03:32:50.806379+02:00 unreal6 kernel: [300981.301040][T22543] lowmem_reserve[]: 0 0 0 0 0 2024-05-17T03:32:50.908415+02:00 unreal6 load.sh[22543]: xencall: error: alloc_pages: mmap (,4842*4096,...) [bufdev] failed: Cannot allocate memory 2024-05-17T03:32:50.908545+02:00 unreal6 load.sh[22543]: kexec_load failed: Cannot allocate memory 2024-05-17T03:32:50.908589+02:00 unreal6 load.sh[22543]: entry = 0x41a49f740 flags = 0x3e0001 2024-05-17T03:32:50.908627+02:00 unreal6 load.sh[22543]: nr_segments = 7 2024-05-17T03:32:50.908663+02:00 unreal6 load.sh[22543]: segment[0].buf = 0x55d5af5902a0 2024-05-17T03:32:50.908695+02:00 unreal6 load.sh[22543]: segment[0].bufsz = 0x30 2024-05-17T03:32:50.908729+02:00 unreal6 load.sh[22543]: segment[0].mem = 0x40d346000 2024-05-17T03:32:50.908762+02:00 unreal6 load.sh[22543]: segment[0].memsz = 0x1000 2024-05-17T03:32:50.908796+02:00 unreal6 load.sh[22543]: segment[1].buf = 0x7ff95df8d010 2024-05-17T03:32:50.908831+02:00 unreal6 load.sh[22543]: segment[1].bufsz = 0x12e94dc 2024-05-17T03:32:50.908863+02:00 unreal6 load.sh[22543]: segment[1].mem = 0x415716000 2024-05-17T03:32:50.908908+02:00 unreal6 load.sh[22543]: segment[1].memsz = 0x12ea000 2024-05-17T03:32:50.908944+02:00 unreal6 load.sh[22543]: segment[2].buf = 0x7ff95f27b010 2024-05-17T03:32:50.908978+02:00 unreal6 load.sh[22543]: segment[2].bufsz = 0xd841e0 2024-05-17T03:32:50.909013+02:00 unreal6 load.sh[22543]: segment[2].mem = 0x416a00000 2024-05-17T03:32:50.909048+02:00 unreal6 load.sh[22543]: segment[2].memsz = 0x39d8000 2024-05-17T03:32:50.909086+02:00 unreal6 load.sh[22543]: segment[3].buf = 0x55d5af63a7c0 2024-05-17T03:32:50.909119+02:00 unreal6 load.sh[22543]: segment[3].bufsz = 0x4121 2024-05-17T03:32:50.909148+02:00 unreal6 load.sh[22543]: segment[3].mem = 0x41a49a000 2024-05-17T03:32:50.909179+02:00 unreal6 load.sh[22543]: segment[3].memsz = 0x5000 2024-05-17T03:32:50.909210+02:00 unreal6 load.sh[22543]: segment[4].buf = 0x55d5af6334b0 2024-05-17T03:32:50.909241+02:00 unreal6 load.sh[22543]: segment[4].bufsz = 0x70e0 2024-05-17T03:32:50.909272+02:00 unreal6 load.sh[22543]: segment[4].mem = 0x41a49f000 2024-05-17T03:32:50.909346+02:00 unreal6 kernel: [300981.301042][T22543] Node 0 DMA: 40*4kB (UME) 29*8kB (UME) 36*16kB (UE) 14*32kB (UME) 4*64kB (UME) 4*128kB (UE) 3*256kB (U) 1*512kB (U) 0*1024kB 0*2048kB 0*4096kB = 3464kB 2024-05-17T03:32:50.909351+02:00 unreal6 kernel: [300981.448605][T22543] Node 0 DMA32: 7108*4kB (UMEH) 1421*8kB (UMEH) 50*16kB (UMH) 3*32kB (H) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 40696kB 2024-05-17T03:32:50.909364+02:00 unreal6 kernel: [300981.448612][T22543] 72778 total pagecache pages 2024-05-17T03:32:50.909367+02:00 unreal6 kernel: [300981.448613][T22543] 4164 pages in swap cache 2024-05-17T03:32:50.909368+02:00 unreal6 kernel: [300981.448614][T22543] Free swap = 1067936kB 2024-05-17T03:32:50.909369+02:00 unreal6 kernel: [300981.448614][T22543] Total swap = 2099648kB 2024-05-17T03:32:50.909375+02:00 unreal6 kernel: [300981.448615][T22543] 262143 pages RAM 2024-05-17T03:32:50.909376+02:00 unreal6 kernel: [300981.448616][T22543] 0 pages HighMem/MovableOnly 2024-05-17T03:32:50.909382+02:00 unreal6 kernel: [300981.448616][T22543] 33646 pages reserved 2024-05-17T03:32:50.909383+02:00 unreal6 kernel: [300981.448617][T22543] 0 pages cma reserved 2024-05-17T03:32:50.909384+02:00 unreal6 kernel: [300981.448617][T22543] 0 pages hwpoisoned 2024-05-17T03:32:50.909328+02:00 unreal6 load.sh[22543]: segment[4].memsz = 0x9000 2024-05-17T03:32:50.909407+02:00 unreal6 load.sh[22543]: segment[5].buf = 0x55d5af6315e0 2024-05-17T03:32:50.909444+02:00 unreal6 load.sh[22543]: segment[5].bufsz = 0x800 2024-05-17T03:32:50.909475+02:00 unreal6 load.sh[22543]: segment[5].mem = 0x41a4a8000 2024-05-17T03:32:50.909505+02:00 unreal6 load.sh[22543]: segment[5].memsz = 0x4000 2024-05-17T03:32:50.909537+02:00 unreal6 load.sh[22543]: segment[6].buf = 0x55d5af5979d0 2024-05-17T03:32:50.909568+02:00 unreal6 load.sh[22543]: segment[6].bufsz = 0x99c00 2024-05-17T03:32:50.909596+02:00 unreal6 load.sh[22543]: segment[6].mem = 0x41a4ac000 2024-05-17T03:32:50.909625+02:00 unreal6 load.sh[22543]: segment[6].memsz = 0x9a000 2024-05-17T03:32:50.912398+02:00 unreal6 load.sh[18867]: kexec failed. 2024-05-17T03:32:50.916526+02:00 unreal6 systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION 2024-05-17T03:32:50.916594+02:00 unreal6 systemd[1]: kdump.service: Failed with result 'exit-code'. 2024-05-17T03:32:50.941787+02:00 unreal6 systemd[1]: Failed to start Load kdump kernel and initrd. 2024-05-17T03:32:50.942145+02:00 unreal6 systemd[1]: kdump.service: Consumed 20.770s CPU time. 2024-05-17T03:32:50.978629+02:00 unreal6 sh[18901]: .. 2024-05-17T03:32:50.978699+02:00 unreal6 sh[18901]: Job for kdump.service failed because the control process exited with error code. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1224292] New: SUMA has a problem with an old key next to a new one in 15.6
by bugzilla_noreply＠suse.com 10 Jun '24

10 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224292 Bug ID: 1224292 Summary: SUMA has a problem with an old key next to a new one in 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- From Michael Calmer there is a problem with the 15.6 repo metadata: repomd.xml is signed, but not with the "repomd.xml.key" $> gpg --keyid-format=long --show-keys --with-fingerprint repomd.xml.key pub rsa2048/B88B2FD43DBDC284 2008-11-07 [SC] [expired: 2024-05-02] Key fingerprint = 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 uid openSUSE Project Signing Key <opensuse(a)opensuse.org> $> gpg --verify repomd.xml.asc gpg: assuming signed data in 'repomd.xml' gpg: Signature made Sat 11 May 2024 02:01:32 AM CEST gpg: using RSA key 35A2F86E29B700A4 I think we switched the key, but we still put the old key next to it? Who can fix this? It break testing SUSE Manager and Uyuni -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1222614] New: osc No module named 'osc.connection'
by bugzilla_noreply＠suse.com 10 Jun '24

10 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222614 Bug ID: 1222614 Summary: osc No module named 'osc.connection' 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: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- lkocman@localhost:~/Workspace/obs/home:lkocman:branches:openSUSE:Leap:15.6/branding-openSUSE> sudo zypper in osc-plugin-staging Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Warning: Repository 'update-non-oss (15.6)' metadata expired since 2023-09-21 14:47:58 CEST. Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manually refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: osc-plugin-staging 1 new package to install. Overall download size: 268.6 KiB. Already cached: 0 B. After the operation, additional 25.3 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: osc-plugin-staging-20230928.864b176-bp156.1.1.noarch (repo-oss (15.6)) (1/1), 268.6 KiB Retrieving: osc-plugin-staging-20230928.864b176-bp156.1.1.noarch.rpm ......................................................................................................................................[done (1.3 MiB/s)] Checking for file conflicts: ..........................................................................................................................................................................................[done] (1/1) Installing: osc-plugin-staging-20230928.864b176-bp156.1.1.noarch ................................................................................................................................................[done] lkocman@localhost:~/Workspace/obs/home:lkocman:branches:openSUSE:Leap:15.6/branding-openSUSE> ls branding-leap-15.6.zip branding-openSUSE.changes branding-openSUSE.spec lkocman@localhost:~/Workspace/obs/home:lkocman:branches:openSUSE:Leap:15.6/branding-openSUSE> sudo su - lkocman-factory lkocman-factory@localhost:~> osc staging -p openSUSE:Leap:15.6 adi Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 9583, in _load_plugins mod = imp.load_source(modname, os.path.join(plugin_dir, extfile)) File "/usr/lib64/python3.6/imp.py", line 172, in load_source module = _load(spec) File "<frozen importlib._bootstrap>", line 684, in _load File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 678, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib/osc-plugins/osc-staging.py", line 17, in <module> from osclib.accept_command import AcceptCommand File "/usr/lib/osc-plugins/osclib/accept_command.py", line 11, in <module> from osclib.core import attribute_value_save, attribute_value_load File "/usr/lib/osc-plugins/osclib/core.py", line 20, in <module> from osc.connection import http_DELETE ModuleNotFoundError: No module named 'osc.connection' /usr/lib/osc-plugins/osc-staging.py: No module named 'osc.connection' Try 'env OSC_PLUGIN_FAIL_IGNORE=1 osc ...' -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222534] New: No wired network after hibernation
by bugzilla_noreply＠suse.com 09 Jun '24

09 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222534 Bug ID: 1222534 Summary: No wired network after hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: jonzn4suse(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240405 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.4-rc1-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC System Version: SBKPF I can turn on WiFi and it works, but to fix the wired issue, I have to reboot. The below logs keeps repeating until a reboot. LOGS: Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4741] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <warn> [1712657390.4744] device (enp1s0): Activation: failed for connection 'Wired Connection' Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4744] device (enp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): canceled DHCP transaction Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): state changed no lease Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5760] policy: auto-activating connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5763] device (enp1s0): Activation: starting connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5764] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5766] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5937] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5939] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. I will also test sleep to see if it has the same issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222761] New: wxWidgets needs to be compiled with spellcheck
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222761 Bug ID: 1222761 Summary: wxWidgets needs to be compiled with spellcheck Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am trying to build an updated kiCad 8.0 and it requires wxWidgets and wxPython with Python > 3.6. Kicad requires wxWidgets >= 3.0.5 so I am trying to build with wxWidgets 3.2. Unfortunately, the wxWidgets supplied with OpenSUSE is not built with spellcheck enabled which is required for wxPython. Can wxWidgets be built with --enable-spellcheck in the configure phase? -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1213370] New: tesseract-ocr should not be built with experimantal opencl support
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213370 Bug ID: 1213370 Summary: tesseract-ocr should not be built with experimantal opencl support 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: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- opencl in tesseract-ocr is considered experimental, according to this thread (https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it is considered just an entry point for possible developers. Their own doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html) states: "Important note: OpenCL support in Tesseract is still considered experimental. There are some major bugs associated with it (see issue 837). Building Tesseract with OpenCL support is not recommended (for any version of Tesseract), unless you are a developer and want to improve the OpenCL code" Please remove the flag "--enable-opencl" from https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr… This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=1207570 PS: I indeed encounter problems with the opencl code path -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224165] New: AUDIT-0: openSUSE Leap 15.6 Gold Master security audit
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224165 Bug ID: 1224165 Summary: AUDIT-0: openSUSE Leap 15.6 Gold Master security audit Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello team this is a request to audit openSUSE:Leap:15.6 GoldMaster code deadline is same as for SLES 15 SP6 GM (May 16th). Our roadmap says: Wed, May 16, 2022 Gold Master code submission deadline built should be within a week from there. However it's all driven by GMC acceptance for SUSE Linux Enterprise 15 SP6 The poo tracker: https://progress.opensuse.org/issues/131864 Leap 15.6 Schedule https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224781] New: VUL-0: CVE-2024-35192: trivy: credential leak via malicious registry
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224781 Bug ID: 1224781 Summary: VUL-0: CVE-2024-35192: trivy: credential leak via malicious registry Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/406773/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Trivy is a security scanner. Prior to 0.51.2, if a malicious actor is able to trigger Trivy to scan container images from a crafted malicious registry, it could result in the leakage of credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR). These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. Systems are not affected if the default credential provider chain is unable to obtain valid credentials. This vulnerability only applies when scanning container images directly from a registry. This vulnerability is fixed in 0.51.2. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35192 https://www.cve.org/CVERecord?id=CVE-2024-35192 https://github.com/aquasecurity/trivy/commit/e7f14f729de259551203f313e57d2d… https://github.com/aquasecurity/trivy/security/advisories/GHSA-xcq4-m2r3-cm… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212909] New: unstripped-binary-or-object for binary libraries in Python directories
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1212909 Bug ID: 1212909 Summary: unstripped-binary-or-object for binary libraries in Python directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is a zillion packages which end up with the warning like python311-scipy.x86_64: W: unstripped-binary-or-object /usr/lib64/python3.11/site-packages/scipy/spatial/_qhull.cpython-311-x86_64-linux-gnu.so (this is from https://build.opensuse.org/package/live_build_log/home:gladiac:mailman/pyth…) Interestingly the same package in the devel project doesn’t seem to present the same problem (https://build.opensuse.org/build/devel:languages:python:numeric/openSUSE_Tu…). Could we find out why these happen and do something about it? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225298] New: systemd-boot fails to boot 6.9.1
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225298 Bug ID: 1225298 Summary: systemd-boot fails to boot 6.9.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875116 --> https://bugzilla.suse.com/attachment.cgi?id=875116&action=edit screen photo Installed TW with systemd-boot about a month ago, updated today to 20240523, rebooted, everything seemed to work but noticed it was still on 6.8.8. Rebooted, selected 6.9.1 from the systemd-boot menu and it gets stuck while booting. Reaches target Initrd File System Times out waiting for device /dev/gpt-auto-root Attached a photo of the screen with boot messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225299] New: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225299 Bug ID: 1225299 Summary: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875117 --> https://bugzilla.suse.com/attachment.cgi?id=875117&action=edit no prompt Installed TW with systemd-boot on my laptop about a month ago. It has 1 drive (nvme), it has one partition for /boot/efi, one for root and an encrypted partition for /home, no LVM. When booting the kernel messages just stop and there's no indicator asking to enter the passphrase for /home partition unless I press a key, then the prompt "Please enter passphrase for disk..." appears. Or if I press escape then it displays this gray semi-graphical screen with the same message. The kernel command line contains 'splash=silent quiet' and Plymouth is installed, I didn't do any configuration there but it's not displayed, just plain kernel messages when booting. It would be nice to have a better passphrase prompt especially on a 14" 2880x1800 screen where the kernel messages are tiny. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224407] New: parcellite dumps core when clicking on one entry of the history list
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224407 Bug ID: 1224407 Summary: parcellite dumps core when clicking on one entry of the history list 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: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- parcellite-1.2.4.0-1.1.x86_64 crashes when one entry of the history list is left clicked. This is on XFCE as the desktop manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223624] New: [Build 20240501] podman bats user integration fails test suites
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223624 Bug ID: 1223624 Summary: [Build 20240501] podman bats user integration fails test suites Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4145118/modules/bats -user-local_tap/steps/47 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Since the latest changes, the tests look better, but not yet completely fixed. Theese are the current failures: bats-user-local: not ok 47 [012] manifest list --add --artifact # (from function `run_podman' in file test/system/helpers.bash, line 416, # from function `manifestListAddArtifactOnce' in file test/system/012-manifest.bats, line 167, # in test file test/system/012-manifest.bats, line 262) # `manifestListAddArtifactOnce' failed not ok 367 [200] podman pod cleans cgroup and keeps limits # (in test file test/system/200-pod.bats, line 750) # `assert "$(< $memory_limit_file)" = "268435456" "Contents of $memory_limit_file"' failed not ok 378 [252] quadlet - basic # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/252-quadlet.bats, line 174) # `assert "$output" == "STARTED CONTAINER" "exact/full match when using the 'passthrough' driver"' failed not ok 427 [280] podman update - test all options # tags: distro-integration # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/280-update.bats, line 109) # `run_podman update "${opts[@]}" $cid' failed not ok 499 [505] No IPv4 # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/505-networking-pasta.bats, line 271) # `run_podman run --net=pasta:-6 $IMAGE ip -j -4 address show' failed not ok 506 [505] IPv6 default route # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/505-networking-pasta.bats, line 363) # `assert "${container_route}" = "${host_route}" \' failed openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_podman_testsuite@64bit fails in [bats-user-local_tap](https://openqa.opensuse.org/tests/4145118/modules/bats… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20240308](https://openqa.opensuse.org/tests/3999689) ## Expected result Last good: [20240307](https://openqa.opensuse.org/tests/3997809) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224120] New: [SELinux] AVC denial systemd-fstab-g on MicroOS
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224120 Bug ID: 1224120 Summary: [SELinux] AVC denial systemd-fstab-g on MicroOS 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: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: arvidjaar(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- mitmanek:~ # ausearch -m AVC -ts boot ---- time->Fri May 10 00:24:35 2024 type=AVC msg=audit(1715293475.979:21): avc: denied { map_read map_write } for pid=1237 comm="systemd-fstab-g" scontext=system_u:system_r:systemd_fstab_generator_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=bpf permissive=1 ---- time->Fri May 10 00:24:35 2024 type=AVC msg=audit(1715293475.979:22): avc: denied { map_read map_write } for pid=1245 comm="systemd-gpt-aut" scontext=system_u:system_r:systemd_gpt_generator_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=bpf permissive=1 ---- time->Fri May 10 00:34:38 2024 type=AVC msg=audit(1715294078.083:118): avc: denied { unlink } for pid=1894 comm="bootctl" name="bfb41e21a4f34f10958f75adb1378666-6.8.7-1-default-75.conf" dev="nvme0n1p2" ino=43 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:dosfs_t:s0 tclass=file permissive=1 mitmanek:~ # I don’t see any actual negative effects. Also mentioned on https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1222450] New: Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222450 Bug ID: 1222450 Summary: Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: miika.alikirri(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874124 --> https://bugzilla.suse.com/attachment.cgi?id=874124&action=edit output of podman info On a fresh installation of tumbleweed (version 20240403), podman fails to run as a non-root user when `--memory` option is set. running: ``` podman run --rm --memory 4M tumbleweed echo it works ``` prints out: ``` Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found ``` And running it as sudo runs it correctly and prints: ``` it works ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213929] New: zypper-changelog-plugin lacks dependencies (No module named 'rpm')
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213929 Bug ID: 1213929 Summary: zypper-changelog-plugin lacks dependencies (No module named 'rpm') 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: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing the zypper-changelog-plugin in a TW container it says: > 21606fdb0e6d:/ # zypper changelog > Traceback (most recent call last): > File "/usr/bin/zypper-changelog", line 30, in <module> > import rpm > ModuleNotFoundError: No module named 'rpm' A bunch of dependencies were installed together with the package, but python311-rpm was missing. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223900] New: sddm: issue with XAUTHORITY
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223900 Bug ID: 1223900 Summary: sddm: issue with XAUTHORITY Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: gcomes.obs(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In xfce I use redshift to adjust the monitor night color. If I use lightdm as displaymanager, redshift works normally. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for current location to become available... etc... But if I use sddm as displaymanager, redshift doesn't work. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified `RANDR Query Version' returned error -1 Initialization of randr failed. Trying next method... Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified X request failed: XOpenDisplay Initialization of vidmode failed. Trying next method... No more methods to try. The output of: strace redshift -o contains: access("/tmp/xauth_WYBTin", R_OK) = 0 openat(AT_FDCWD, "/tmp/xauth_WYBTin", O_RDONLY) = -1 EACCES (Permission denied) The failure of redshift is due to the fact that somehow it cannot access /tmp/xauth_WYBTin (the value of $XAUTHORITY) However such file is readable by the user running redshift and other xprograms work fine. Leap 15.5 (sddm 0.19) works fine as did the previous versions. The issue started with sddm 0.20 (https://build.opensuse.org/package/show/openSUSE:Factory/sddm?rev=64) and is currently present in Leap 15.6 and tumbleweed. I could not figure out what exactly in sddm 0.20 is causing the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224773] New: Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Bug ID: 1224773 Summary: Cannot install NVIDIA drivers in latest Aeon RC2 Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sunscape1(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installing NVIDIA drivers in Aeon RC2 (https://en.opensuse.org/SDB:NVIDIA_drivers) fails because the MOK cannot be enrolled after boot. Error during installation using pkg is: SKIP: /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.78-22.1-default.der is not in MokList Without the nvidia-pubkeys folder it is impossible to enroll the MOK or try to enable it after reboot. The key doesn't exist :( -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1223838] New: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223838 Bug ID: 1223838 Summary: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de CC: kernel-bugs(a)suse.de, qa-bugs(a)suse.de, tiwai(a)suse.com, variable_valuables761(a)simplelogin.com Depends on: 1217750, 1217716 Target Milestone: --- Found By: --- Blocker: --- Created attachment 874641 --> https://bugzilla.suse.com/attachment.cgi?id=874641&action=edit current dmesg output +++ This bug was initially created as a clone of Bug #1217750 +++ It seems the brightness keys (Fn+F1,Fn+F2) do not work in Tumbleweed with current 6.8 kernel series. This should have been reported rather long time ago. This has started happening in ~6.5 series I've attached the output of "brightnessctl -l",> which only shows keyboard (caps lock) key and several non-existent LEDs on keyboard. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222190] New: cron job does not send email (error message about pam_kwallet5)
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222190 Bug ID: 1222190 Summary: cron job does not send email (error message about pam_kwallet5) 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: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I do not get email from cron jobs anymore. journalctl -u cron.service shows error message: pam_kwallet5(crond:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222189] New: kmail first uses wrong message header layout
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222189 Bug ID: 1222189 Summary: kmail first uses wrong message header layout Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873952 --> https://bugzilla.suse.com/attachment.cgi?id=873952&action=edit first attachment wrong layout of header KMail uses in View in the entry Headers the item Fancy Headers. However the header is shown a in the first attachment, without the blue band on top. After choosing Brief and back to Fancy Header, the second attachment shows the right layout of the header. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221576] New: Selecting Print in Okular or Kate only offers printing to PDF file
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221576 Bug ID: 1221576 Summary: Selecting Print in Okular or Kate only offers printing to PDF file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the upgrade to Plasma 6 of Tumbleweed when opening a PDF file in okular or a txt file in Kate and selecting Print the popup for printing only offers printing to a PDF file. When using YaST to configure the printer, a HP DeskJet 2720, I can print a test page. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224995] New: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224995 Bug ID: 1224995 Summary: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: radicalite(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875025 --> https://bugzilla.suse.com/attachment.cgi?id=875025&action=edit Filepicker comparsion between Native Firefox on TW and Flatpak Firefox When using the file picker from the native Firefox package, the file picker runs in XWayland, this isn't noticeable on non HiDPI displays unless there's a HiDPI display connected, or are simply using a HiDPI screen as the only screen, then this becomes instantly noticeable. This behaviour isn't consistent with applications from the rest of the system (moving aside VLC, but the app itself runs entirely under XWayland by default...), as they run the file picker under Wayland, following the correct scaling setting. the Firefox flatpak also runs the file picker under Wayland correctly (via Portal). This behaviour also doesn't happen with the native Firefox package on TWGNOME, running the GTK file picker under Wayland with respect to scaling, so I assume this happens from the OpenSUSE KDE patches added to Firefox? Install is a fresh TWKDE install. Comparison in image Operating System: openSUSE Tumbleweed 20240520 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 Display config is 2560x1600@175%@60hz (Built-in Screen) set to left 1920x1080@100%@120hz (Acer Technologies VG242Y) set to right, set as primary display. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225660] New: python311-pip package installs in /usr/lib by default
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225660 Bug ID: 1225660 Summary: python311-pip package installs in /usr/lib by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: daniel.garcia(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In tumbleweed installing a package with pip3 as root installs in the system path /usr/lib. It should install in /usr/local/lib instead. Possibly related to this patch: https://build.opensuse.org/projects/devel:languages:python:Factory/packages… -- You are receiving this mail because: You are on the CC list for the bug.

1 7