August 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213915] New: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213915 Bug ID: 1213915 Summary: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jrivrain(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868604 --> https://bugzilla.suse.com/attachment.cgi?id=868604&action=edit serial output All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel panic. All the workers are on power8 cpus, this does not happen on a qemu emulated power9 cpu. Example of failing test: https://openqa.opensuse.org/tests/3476697 See attached serial output. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1214653] New: yast2 keyboard do not allow to set bépo (french)
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214653 Bug ID: 1214653 Summary: yast2 keyboard do not allow to set bépo (french) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jonathan(a)mercier.paris QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Dear, I give a try to OpenSuse Leap 15, but I am unable to go further as they any way to set bépo layout kexyboard. I try from: 1. Leap installer : as bépo was missing I choose the french layout once installation has finished: 2. sudo yast2 keyboard: same layout proposal than given from installer 3. sudo yast2/zypper search : nothing relevant found The point (2) and (3) was done by trying to find each letter as I own only bépo keyboard. This layout is present on RHEL, RockyLinux 7,8,9 and Fedora. It would be much appreciate to add it Thanks best regards -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1214013] New: Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 Bug ID: 1214013 Summary: Shutdown did not finish (PC was not powered off, no obvious error logged) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868645 --> https://bugzilla.suse.com/attachment.cgi?id=868645&action=edit Screenshot when shutdown should power off the PC Maybe the issue is related to an MD-RAID being verified (see Bug 1214004), but the system did not power off. The last message in journal were: Aug 05 01:47:01 pc.site systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Aug 05 01:47:01 pc.site systemd[1]: Stopping Device-mapper event daemon... Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd detected break while being idle for 0 second(s), exiting. Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd shutting down. Aug 05 01:47:01 pc.site systemd[1]: dm-event.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Stopped Device-mapper event daemon. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Shutdown. Aug 05 01:47:01 pc.site systemd[1]: Reached target Late Shutdown Services. Aug 05 01:47:01 pc.site systemd[1]: systemd-poweroff.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Finished System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Shutting down. Aug 05 01:47:01 pc.site systemd-shutdown[1]: Syncing filesystems and block devices. Aug 05 01:47:03 pc.site systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 05 01:47:03 pc.site haveged[1265]: haveged: Stopping due to signal 15 Aug 05 01:47:03 pc.site haveged[1265]: haveged starting up Aug 05 01:47:03 pc.site systemd-journald[1132]: Journal stopped I'm also adding a screenshot showing the last messages (that would last until I pressed the power button). Kernel was 5.14.21-150500.55.12-default The only other thing that looked unusual was this: ... Aug 05 01:46:59 pc.site systemd[1]: Stopped Record System Boot/Shutdown in UTMP. Aug 05 01:46:59 pc.site systemd[1]: Stopping Security Auditing Service... Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 is still in use. Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Failed to deactivate: Device or resource busy Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Control process exited, code=exited, status=1> Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Failed with result 'exit-code'. Aug 05 01:46:59 pc.site systemd[1]: Stopped Cryptography Setup for cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5. Aug 05 01:46:59 pc.site auditd[1679]: The audit daemon is exiting. Aug 05 01:46:59 pc.site kernel: kauditd_printk_skb: 50 callbacks suppressed Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.741:562): op=set audit_pid=0 old=1679 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site auditctl[3127]: enabled 0 Aug 05 01:46:59 pc.site auditctl[3127]: failure 1 Aug 05 01:46:59 pc.site auditctl[3127]: pid 0 Aug 05 01:46:59 pc.site auditctl[3127]: rate_limit 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_limit 64 Aug 05 01:46:59 pc.site auditctl[3127]: lost 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog 1 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time 15000 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time_actual 0 Aug 05 01:46:59 pc.site auditctl[3127]: No rules Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.853:563): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site systemd[1]: auditd.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Security Auditing Service. Aug 05 01:46:59 pc.site systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Create Volatile Files and Directories. Aug 05 01:47:00 pc.site systemd[1]: dracut-shutdown.service: Deactivated successfully. Aug 05 01:47:00 pc.site systemd[1]: Stopped Restore /run/initramfs on shutdown. Aug 05 01:47:00 pc.site systemd[1]: Stopped target Local File Systems. Aug 05 01:47:00 pc.site systemd[1]: Unmounting /home... ... The LUKS device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 contains the PV for the system VG, so it makes no sense trying to deactivate that before unmounting the system filesystems. Layout is like this: # pvs PV VG Fmt Attr PSize PFree /dev/mapper/cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 system lvm2 a-- 199,98g 3,88g # vgs VG #PV #LV #SN Attr VSize VFree system 1 6 0 wz--n- 199,98g 3,88g # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert android system Vwi-aotz-- 50,00g thinpool 55,19 floppies system Vwi-a-tz-- 1,00g thinpool 15,18 home system -wi-ao---- 50,00g root system -wi-ao---- 32,00g swap system -wi-ao---- 4,00g thinpool system twi-aotz-- 110,00g 25,23 22,76 (System was upgraded from Leap 15.4 where shutdown worked) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213055] New: locale problems in the default distrobox configuration
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213055 Bug ID: 1213055 Summary: locale problems in the default distrobox configuration Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: shadenk30011(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: When creating a new container using "distrobox-create" the container fails to display directory names properly. For example the directory named "Stažené" shows up as "'Sta'$'\305\276''en'$'\303\251'" when using ls. Reproducible: Always Steps to Reproduce: 1. Use the czech locale 2. Create a directory inside the home that uses one of the offending symbols 3. Create a new distrobox container and run "ls" Actual Results: Directory name isn't properly displayed. Expected Results: Directory name is properly displayed. A workaround is to install the "glibc-locale" package. This can be automated by adding 'container_additional_packages="glibc-locale"' into the distrobox configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1212897] New: Produce separate Aeon installation media
by bugzilla_noreply＠suse.com 18 May '24

18 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1212897 Bug ID: 1212897 Summary: Produce separate Aeon installation media Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Aeon requires install media separate from MicroOS -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213297] New: No clang-tools package needed by clang >=13 from PackageHub repo
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213297 Bug ID: 1213297 Summary: No clang-tools package needed by clang >=13 from PackageHub repo Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: oleksandr.shchirskyi(a)intel.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: No There is an issues with LLVM versions >=13 on SLES15 SP5. None of the Package Hub versions can be installed because the Clang-tool dependency is missing. For example, LLVM for SLES15 SP4 includes Clang-tool, but for SP5 it doesn't: https://packagehub.suse.com/packages/llvm13/ The same issue applies to LLVM 14. Here's a brief log example: # grep PRETTY /etc/os-release PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5" # zypper install clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'clang-tools >= 14.0.6' needed by the to be installed clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 1: do not install clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 2: break clang14-devel-14.0.6-bp155.4.10.x86_64 by ignoring some of its dependencies # zypper info clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Information for package clang14-devel: -------------------------------------- Repository : SUSE-PackageHub-15-SP5-Backports-Pool Name : clang14-devel Version : 14.0.6-bp155.4.10 Arch : x86_64 Vendor : openSUSE Support Level : unknown Installed Size : 17.3 MiB Installed : No Status : not installed Source package : llvm14-14.0.6-bp155.4.10.src Upstream URL : https://www.llvm.org/ Summary : CLANG frontend for LLVM (devel package) Description : This package contains the clang (C language) frontend for LLVM. (development files) # zypper search clang | grep tools # At the same moment it's possible to install LLVM >=13 from OpenSUSE repos, for example, adding this to repos config "http://download.opensuse.org/distribution/leap/15.5/repo/oss/" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213574] New: Thunderbird OAUTH2 broken
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213574 Bug ID: 1213574 Summary: Thunderbird OAUTH2 broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Thunderbird updates broke OAUTH2 and this seems to be a common problem with Thunderbird 102. With this update it no longer presents an OAUTH2 dialog for IMAP. My employer uses Microsoft Office365 and OAUTH2 is essential. This used to work. Even with a clean install and nuking the previous configuration it will never prompt for OAUTH2 authentication like it used to. Note that the OAUTH2 dialog DOES work with SMTP, but not IMAP. Searching the Internet reveals that this is a common problem with this release. Please upgrade Thunderbird to a newer release for 15.4. I'm not quite ready to upgrade to 15.5 just yet since I use this machine for heavy development work. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213500] New: [trackerbug] docker 24.0.4-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213500 Bug ID: 1213500 Summary: [trackerbug] docker 24.0.4-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.4-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/24.0/#2404>. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213537] New: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960)
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213537 Bug ID: 1213537 Summary: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: medwards-suse(a)mirkwood.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868350 --> https://bugzilla.suse.com/attachment.cgi?id=868350&action=edit dmesg Booting opensuse leap 15.5 fails on this machine - shortly after the myrb and myrs drivers load and detect the AcceleRAID 170 and drives connected to this card, booting simply stops. Waiting for a few minutes will let me see kernel warnings about hung processes, but booting never completes at this point. Adding modprobe.blacklist=myrb and modprobe.blacklist=myrs to the kernel commandline lets boot complete, though obviously without the AcceleRAID card in use. Once booted, I was able to enable dyndbg for these two drivers: # for d in myr{s,b}; do echo 'file drivers/scsi/${d}.c +p' > /sys/kernel/debug/dynamic_debug/control; done Loading the drivers manually caused the modprobe for myrs to hang (myrb loaded w/o issue), leading me to believe the problem lies within the myrs driver. dyndbg of myrb + myrs: drivers/scsi/myrs.c:2114 [myrs]myrs_monitor =_ "monitor tick\012" drivers/scsi/myrs.c:1822 [myrs]myrs_slave_alloc =_ "Logical device mapping %d:%d:%d -> %d\012" drivers/scsi/myrs.c:471 [myrs]myrs_get_fwstatus =_ "Sending GetHealthStatus\012" drivers/scsi/myrs.c:338 [myrs]myrs_get_pdev_info =_ "Sending GetPhysicalDeviceInfoValid for pdev %d:%d:%d\012" drivers/scsi/myrs.c:249 [myrs]myrs_get_ldev_info =_ "Sending GetLogicalDeviceInfoValid for ldev %d\012" drivers/scsi/myrs.c:189 [myrs]myrs_get_ctlr_info =_ "Sending GetControllerInfo\012" drivers/scsi/myrb.c:2445 [myrb]myrb_monitor =_ "reschedule monitor\012" drivers/scsi/myrb.c:2436 [myrb]myrb_monitor =_ "new enquiry\012" drivers/scsi/myrb.c:2432 [myrb]myrb_monitor =_ "get background init status\012" drivers/scsi/myrb.c:2427 [myrb]myrb_monitor =_ "get consistency check progress\012" drivers/scsi/myrb.c:2421 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2415 [myrb]myrb_monitor =_ "get logical drive info\012" drivers/scsi/myrb.c:2409 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2403 [myrb]myrb_monitor =_ "get error table\012" drivers/scsi/myrb.c:2397 [myrb]myrb_monitor =_ "get event log no %d/%d\012" drivers/scsi/myrb.c:2390 [myrb]myrb_monitor =_ "monitor tick\012" drivers/scsi/myrb.c:2360 [myrb]myrb_handle_scsi =_ "Device nonresponsive\012" drivers/scsi/myrb.c:2355 [myrb]myrb_handle_scsi =_ "Attempt to Access Beyond End of Logical Drive" drivers/scsi/myrb.c:2350 [myrb]myrb_handle_scsi =_ "Logical Drive Nonexistent or Offline" drivers/scsi/myrb.c:2331 [myrb]myrb_handle_scsi =_ "Bad Data Encountered\012" drivers/scsi/myrb.c:1699 [myrb]myrb_pdev_slave_alloc =_ "slave alloc pdev %d:%d state %x\012" drivers/scsi/myrb.c:1693 [myrb]myrb_pdev_slave_alloc =_ "device not present, skip\012" drivers/scsi/myrb.c:1687 [myrb]myrb_pdev_slave_alloc =_ "Failed to get device state, status %x\012" drivers/scsi/myrb.c:1639 [myrb]myrb_ldev_slave_alloc =_ "slave alloc ldev %d state %x\012" drivers/scsi/myrb.c:1438 [myrb]myrb_ldev_queuecommand =_ "ldev %u in state %x, skip\012" drivers/scsi/myrb.c:1414 [myrb]myrb_read_capacity =_ "Capacity %u, blocksize %u\012" See attachment for dmesg output. myrs was loaded around timestamp 16372.039529. -- You are receiving this mail because: You are on the CC list for the bug.

1 4