October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231210] New: :btusb_suspend: kernel NULL pointer dereference
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231210 Bug ID: 1231210 Summary: :btusb_suspend: kernel NULL pointer dereference Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: michal.vyskocil(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877688 --> https://bugzilla.suse.com/attachment.cgi?id=877688&action=edit LC_ALL=C sudo journalctl --boot 0 uname -a Linux zelva 6.11.0-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 25 07:09:20 UTC 2024 (b87e886) x86_64 x86_64 x86_64 GNU/Linux rpm -q kernel-default kernel-default-6.11.0-1.1.x86_64 cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.11.0-1-default root=UUID=36543fa2-c67b-444d-b09b-71e6fe5020fd rd.timeout=60 rd.retry=45 splash=silent swapaccount=1 mitigations=auto security=selinux selinux=1 enforcing=1 On boot the scary NULL pointer deference appeared, but laptop started. The trace is BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 UID: 0 PID: 585 Comm: kworker/3:2 Not tainted 6.11.0-1-default #1 openSUSE Tumbleweed 461f7965cd54a3c599f269012cdb3d6ce81b3260 Hardware name: LENOVO 20XK007JCK/20XK007JCK, BIOS R1MET44W (1.14 ) 01/21/2022 Workqueue: pm pm_runtime_work RIP: 0010:btusb_suspend+0x18/0x1c0 [btusb] Code: 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 55 89 f5 53 48 8b 9f c8 00 00 00 66 90 <48> 8b 13 8b 82 bc 09 00 00 03 82 b8 09 00 00 03 82 c4 09 00 00 03 RSP: 0018:ffffa299c206fc90 EFLAGS: 00010206 RAX: ffffffffc2223970 RBX: 0000000000000000 RCX: 0000000000000007 RDX: 0000000000000003 RSI: 0000000000000402 RDI: ffff9383ca238400 RBP: 0000000000000402 R08: ffff9383ca20d800 R09: ffff9383ca23f8b0 R10: ffff938a8ee2c3a0 R11: 0000000000000003 R12: ffff9383ca238400 R13: 0000000000000402 R14: 0000000000000003 R15: ffff9383d1142900 FS: 0000000000000000(0000) GS:ffff938a8eb80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000001a01f8000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> ? __die_body.cold+0x19/0x26 ? page_fault_oops+0x132/0x2a0 ? exc_page_fault+0x73/0x170 ? asm_exc_page_fault+0x26/0x30 ? __pfx_btusb_suspend+0x10/0x10 [btusb 600bb609afa33d01c8b8c647a1af5542146201a9] ? btusb_suspend+0x18/0x1c0 [btusb 600bb609afa33d01c8b8c647a1af5542146201a9] usb_suspend_both+0xad/0x240 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] usb_runtime_suspend+0x2e/0x70 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] ? __pfx_usb_runtime_suspend+0x10/0x10 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] __rpm_callback+0x44/0x170 ? __pfx_usb_runtime_suspend+0x10/0x10 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] rpm_callback+0x55/0x60 ? __pfx_usb_runtime_suspend+0x10/0x10 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] rpm_suspend+0xe6/0x5f0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? finish_task_switch.isra.0+0x99/0x2e0 ? __pfx_usb_runtime_idle+0x10/0x10 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] __pm_runtime_suspend+0x3a/0xc0 usb_runtime_idle+0x35/0x40 [usbcore 15db8bf8f9a7858a5a1db1b8e42a51063eadfac5] rpm_idle+0xc0/0x290 pm_runtime_work+0x84/0xb0 process_one_work+0x16b/0x320 worker_thread+0x2ea/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0xd2/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: mhi_wwan_ctrl mhi_wwan_mbim snd_acp_legacy_mach snd_acp_mach snd_soc_nau8821 snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps snd_amd_sdw_acpi soundwire_amd soundwire_generic_allocation soundwire_bus snd_hda_codec_realtek snd_ctl_led mt7921e snd_hda_codec_generic snd_soc_core mt7921_common snd_hda_scodec_component mt792x_lib nls_iso8859_1 snd_compress intel_rapl_msr snd_hda_codec_hdmi mt76_connac_lib amd_atl snd_pcm_dmaengine intel_rapl_common nls_cp437 snd_rpl_pci_acp6x mt76 snd_hda_intel btusb edac_mce_amd snd_intel_dspcfg snd_acp_pci snd_usb_audio vfat btrtl snd_intel_sdw_acpi uvcvideo btintel snd_acp_legacy_common fat snd_usbmidi_lib videobuf2_vmalloc btbcm snd_hda_codec uvc mac80211 snd_pci_acp6x snd_ump btmtk videobuf2_memops videobuf2_v4l2 snd_pci_acp5x snd_rawmidi snd_hda_core libarc4 kvm_amd snd_seq_device snd_hwdep ee1004 videodev snd_pcm snd_rn_pci_acp3x thinkpad_acpi r8169 snd_acp_config bluetooth videobuf2_common platform_profile snd_soc_acpi think_lmi sparse_keymap snd_timer realtek i2c_piix4 pcspkr firmware_attributes_class mc wmi_bmof efi_pstore mdio_devres kvm tiny_power_button k10temp nxp_nci_i2c cfg80211 i2c_smbus snd_pci_acp3x mhi_pci_generic nxp_nci snd libphy thermal nci mhi soundcore ac nfc rfkill i2c_scmi amd_pmc button joydev loop fuse dm_mod configfs dmi_sysfs ip_tables x_tables hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic amdxcp i2c_algo_bit drm_ttm_helper ttm ghash_clmulni_intel drm_exec sha512_ssse3 gpu_sched sha256_ssse3 xhci_pci drm_suballoc_helper rtsx_pci_sdmmc xhci_pci_renesas drm_buddy sha1_ssse3 mmc_core xhci_hcd drm_display_helper nvme aesni_intel ucsi_acpi gf128mul cec crypto_simd cryptd typec_ucsi usbcore nvme_core ccp roles rc_core sp5100_tco video rtsx_pci typec nvme_auth battery wmi serio_raw overlay btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq br_netfilter bridge stp llc msr efivarfs CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- RIP: 0010:btusb_suspend+0x18/0x1c0 [btusb] Code: 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 55 89 f5 53 48 8b 9f c8 00 00 00 66 90 <48> 8b 13 8b 82 bc 09 00 00 03 82 b8 09 00 00 03 82 c4 09 00 00 03 RSP: 0018:ffffa299c206fc90 EFLAGS: 00010206 RAX: ffffffffc2223970 RBX: 0000000000000000 RCX: 0000000000000007 RDX: 0000000000000003 RSI: 0000000000000402 RDI: ffff9383ca238400 RBP: 0000000000000402 R08: ffff9383ca20d800 R09: ffff9383ca23f8b0 R10: ffff938a8ee2c3a0 R11: 0000000000000003 R12: ffff9383ca238400 R13: 0000000000000402 R14: 0000000000000003 R15: ffff9383d1142900 FS: 0000000000000000(0000) GS:ffff938a8eb80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000001a01f8000 CR4: 0000000000750ef0 PKRU: 55555554 note: kworker/3:2[585] exited with irqs disabled Attached a full system log. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231052] Nvidia driver versions mismatch
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231052 https://bugzilla.suse.com/show_bug.cgi?id=1231052#c3 Clément Mathieu--Drif <cmdetu(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cmdetu(a)gmail.com) | --- Comment #3 from Clément Mathieu--Drif <cmdetu(a)gmail.com> --- I'm using the packages from the Tumbleweed repos. Here are the versions I have currently: nvidia-gl-G06-550.107.02-26.1.x86_64 nvidia-video-G06-550.107.02-26.1.x86_64 kernel-firmware-nvidia-gspx-G06-550.100-3.1.x86_64 kernel-firmware-nvidia-gspx-G06-550.107.02-3.1.x86_64 nvidia-open-driver-G06-signed-kmp-default-550.120_k6.11.0_1-1.2.x86_64 kernel-firmware-nvidia-gspx-G06-550.107.02-2.1.x86_64 kernel-firmware-nvidia-20240913-1.1.noarch nvidia-video-G06-32bit-550.107.02-26.1.x86_64 nvidia-utils-G06-550.107.02-26.1.x86_64 nvidia-compute-G06-550.107.02-26.1.x86_64 nvidia-compute-G06-32bit-550.107.02-26.1.x86_64 nvidia-compute-utils-G06-550.107.02-26.1.x86_64 nvidia-gl-G06-32bit-550.107.02-26.1.x86_64 kernel-firmware-nvidia-gspx-G06-550.120-2.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230115] New: kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Direct firmware load for intel/sof/sof-rpl-s.ri failed with error -2
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230115 Bug ID: 1230115 Summary: kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Direct firmware load for intel/sof/sof-rpl-s.ri failed with error -2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- (Note: Bugzilla's description for "Kernel:Drivers" says "Bugs pertaining to Kernel filesystems"; copied from Kernel:Filesystems? Could be I reported this several years ago already ;-)) It seems the sound system of the Lenovo ThinkPad P16 Gen2 (Board 21FA000AGE, Intel Corporation Raptor Lake High Definition Audio Controller) isn't supported, or if it's supported, it's broken: Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: use msi interrupt mode Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: hda codecs found, mask 5 Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DMICs detected in NHLT tables: 2 Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Direct firmware load for intel/sof/sof-rpl-s.ri failed with error -2 Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof firmware file is missing, you might need to Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: download it from https://github.com/thesofproject/sof-bin/ Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load DSP firmware -2 Sep 03 23:00:41 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -2 Shouldn't the firmware be part of the distribution? -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1231174] New: std::chrono::zoned_time runtime error
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231174 Bug ID: 1231174 Summary: std::chrono::zoned_time runtime error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: Gerhard(a)Dr-Lorbeer.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877674 --> https://bugzilla.suse.com/attachment.cgi?id=877674&action=edit Example Project summary: No timezone computation possible Latest tumbleweed. kdevelop, c++ Example: https://en.cppreference.com/w/cpp/chrono/zoned_time compile OK. run: Error: std::chrono::tzdb: cannot locate zone: Africa/Casablanca Error: std::chrono::tzdb: cannot locate zone: America/Argentina/Buenos_Aires Error: std::chrono::tzdb: cannot locate zone: America/Barbados Error: std::chrono::tzdb: cannot locate zone: America/Indiana/Petersburg Error: std::chrono::tzdb: cannot locate zone: America/Tarasco_Bar Error: std::chrono::tzdb: cannot locate zone: Antarctica/Casey Error: std::chrono::tzdb: cannot locate zone: Antarctica/Vostok Error: std::chrono::tzdb: cannot locate zone: Asia/Magadan Error: std::chrono::tzdb: cannot locate zone: Asia/Manila Error: std::chrono::tzdb: cannot locate zone: Asia/Shanghai Error: std::chrono::tzdb: cannot locate zone: Asia/Tokyo Error: std::chrono::tzdb: cannot locate zone: Atlantic/Bermuda Error: std::chrono::tzdb: cannot locate zone: Australia/Darwin Error: std::chrono::tzdb: cannot locate zone: Europe/Isle_of_Man Error: std::chrono::tzdb: cannot locate zone: Europe/Laputa Error: std::chrono::tzdb: cannot locate zone: Indian/Christmas Error: std::chrono::tzdb: cannot locate zone: Indian/Cocos Error: std::chrono::tzdb: cannot locate zone: Pacific/Galapagos -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1184272] MozillaFirefox should recommend what is needed to support WebAuthn with U2F by default
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1184272 https://bugzilla.suse.com/show_bug.cgi?id=1184272#c10 --- Comment #10 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:3507-1: An update that solves 32 vulnerabilities can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-su-20243507-1 Category: security (important) Bug References: 1184272, 1226316, 1228648, 1229821 CVE References: CVE-2024-6600, CVE-2024-6601, CVE-2024-6602, CVE-2024-6603, CVE-2024-6604, CVE-2024-6606, CVE-2024-6607, CVE-2024-6608, CVE-2024-6609, CVE-2024-6610, CVE-2024-6611, CVE-2024-6612, CVE-2024-6613, CVE-2024-6614, CVE-2024-6615, CVE-2024-7518, CVE-2024-7519, CVE-2024-7520, CVE-2024-7521, CVE-2024-7522, CVE-2024-7525, CVE-2024-7526, CVE-2024-7527, CVE-2024-7528, CVE-2024-7529, CVE-2024-8381, CVE-2024-8382, CVE-2024-8384, CVE-2024-8385, CVE-2024-8386, CVE-2024-8387, CVE-2024-8394 Maintenance Incident: [SUSE:Maintenance:35850](https://smelt.suse.de/incident/35850/) Sources used: openSUSE Leap 15.5 (src): MozillaThunderbird-128.2.3-150200.8.177.1 openSUSE Leap 15.6 (src): MozillaThunderbird-128.2.3-150200.8.177.1 SUSE Package Hub 15 15-SP5 (src): MozillaThunderbird-128.2.3-150200.8.177.1 SUSE Package Hub 15 15-SP6 (src): MozillaThunderbird-128.2.3-150200.8.177.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): MozillaThunderbird-128.2.3-150200.8.177.1 SUSE Linux Enterprise Workstation Extension 15 SP5 (src): MozillaThunderbird-128.2.3-150200.8.177.1 SUSE Linux Enterprise Workstation Extension 15 SP6 (src): MozillaThunderbird-128.2.3-150200.8.177.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222919] criterion fails to build on Leap 15.6 - ImportError: cannot import name 'builder'
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1222919 https://bugzilla.suse.com/show_bug.cgi?id=1222919#c9 Younes Manton <younes.m(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |younes.m(a)gmail.com --- Comment #9 from Younes Manton <younes.m(a)gmail.com> --- I ran into this problem when trying to build and install CRIU from source. I'm guessing anything trying to use protobuf-devel and python3-protobuf together is going to be similarly broken. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231174] UTC computation incorrect
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231174 https://bugzilla.suse.com/show_bug.cgi?id=1231174#c3 Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|std::chrono::zoned_time |UTC computation incorrect |runtime error | --- Comment #3 from Gerhard Lorbeer <Gerhard(a)Dr-Lorbeer.de> --- Sorry for wasting your time. Linux version 6.11.0-1-default (geeko@buildhost) (gcc (SUSE Linux) 14.2.0, GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.43.1.20240828-2) #1 SMP PREEMPT_DYNAMIC Wed Sep 25 07:09:20 UTC 2024 (b87e886) I'm programming my home-automation in c++. The program uses the std::chrono functions. It uses functions computing my local time and the UTC-time; lights are turned on/off at specific times. It's running since over 2 years without problems. The timer was off during 16-28.09.2024 (vacation); until this point all was OK. Turning on at 30.09.2024 i found failing calculation the UTC-time. My guess is the patch timezone 2024b (29.09.2024). "Do 12 Sep 2024 14:00:00 CEST Martin Schreiner <martin.schreiner(a)suse.com>" justification below. Because my program is very complex, i build an example to test, if it is an program-bug or other not. The simplest example i could build was the original example of cppreference. I attached this example. Everyone can build this example and see the bug. My originally problem was false computing of UTC/local: so i build a further example to demonstrate (from https://www.heise.de/blog/Zeit-in-C-20-Details-zu-der-Arbeit-mit-Zeitzonen-…) Output of the programm: /home/gerhard/develop/Test2/build> /home/gerhard/develop/Test2/build/test2 UTC time 2024-10-01 15:00:53.451276556 2024-10-01 15:00:53 Local time 2024-10-01 15:00:53.451276556 UTC 2024-10-01 15:00:53 UTC offset: 0s *** Beendet *** you see "UTC offset: 0s" i have a pc without patch "timezone". Here the output of the program: UTC time 2024-10-01 15:24:49.078005857 2024-10-01 15:24:49 Local time 2024-10-01 17:24:49.078005857 CEST 2024-10-01 17:24:49 UTC offset: 7200s you see the correct "UTC offset: 7200s" at this unpatched pc the first program test runs correct even. Thanks for your help. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230631] New: zypper update called from ansible hangs with ZYPP_SINGLE_RPMTRANS
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230631 Bug ID: 1230631 Summary: zypper update called from ansible hangs with ZYPP_SINGLE_RPMTRANS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- A zypper update process is hanging for more than an hour. I'm using the ansible zypper module to update a system. The playbook is as simple as it gets: --- - name: Update and reboot hosts: home become: yes gather_facts: yes tasks: - name: update all packages community.general.zypper: name: '*' state: latest update_cache: yes The update task is hanging for one of the hosts. Note: ZYPP_SINGLE_RPMTRANS is set on this host. libzypp 17.34.1-150600.3.4.6 zypper 1.14.71-150600.10.2.7 Last lines in /var/log/zypp/history: 2024-09-17 10:26:53|command|root@ares|'/usr/bin/zypper' '--quiet' '--non-interactive' '--xmlout' 'update' '--type' 'package' '--auto-agree-with-licenses' '--no-recommends'| 2024-09-17 10:26:55|install|glibc-extra|2.38-150600.14.8.2|x86_64||repo-sle-update|9b79c4b8215408fadb96713529ba340b8e32e6331210a3d6bde79740df5c39ab| # 2024-09-17 10:26:55 glibc-extra installed ok 2024-09-17 10:26:55|install|glibc|2.38-150600.14.8.2|x86_64||repo-sle-update|b48788acf37cf950c73ce0f6b9ef49cabe372841045d773e0d18eac312a7b298| # 2024-09-17 10:26:55 glibc installed ok 2024-09-17 10:26:55|install|glibc-32bit|2.38-150600.14.8.2|x86_64||repo-sle-update|7ee6524dfb18e81854e1b4ccbec16f1bddc6a787d305f9028e5c13ff78a0cb63| # 2024-09-17 10:26:55 glibc-32bit installed ok 2024-09-17 10:26:55|install|libexpat1|2.4.4-150400.3.22.1|x86_64||repo-sle-update|372db388086c3f4dc9057b876272f8e6f5ecfb4ecaf80719fe2dcc1b738815e9| # 2024-09-17 10:26:55 libexpat1 installed ok 2024-09-17 10:26:55|install|libuuid1|2.39.3-150600.4.12.2|x86_64||repo-sle-update|3b3fbdcb9e25068fcf0129723f5a8636d4463a7b16b5d75ea54f7c00d3eb7878| # 2024-09-17 10:26:55 libuuid1 installed ok 2024-09-17 10:26:55|install|libopenssl3|3.1.4-150600.5.15.1|x86_64||repo-sle-update|a00145c1de9f3875b2d43d7df9488727fcd3f7821793bdddd3628d6297b9cba3| # 2024-09-17 10:26:55 libopenssl3 installed ok 2024-09-17 10:26:55|install|libblkid1|2.39.3-150600.4.12.2|x86_64||repo-sle-update|7c099998d5c5652dfd019a08e0bb3505ce13d645d33bc4fa23fa7d8b17501236| # 2024-09-17 10:26:55 libblkid1 installed ok 2024-09-17 10:26:55|install|libjpeg8|8.3.2-lp156.236.1|x86_64||graphics|474e415043a57881528e7e7494c5423cea5de82f5bd25cb0ce0685469110fac2| # 2024-09-17 10:26:55 libjpeg8 installed ok Last lines in zypper.log: 2024-09-17 10:26:53 <1> ares(22706) [zypp] TargetImpl.cc(commitInSingleTransaction):1966 TargetImpl::commit(<list>CommitPolicy( DownloadInHeaps ))586 2024-09-17 10:26:54 <1> ares(22706) [zypp::exec++] forkspawnengine.cc(start):274 Executing '/usr/lib/zypp/zypp-rpm' 2024-09-17 10:26:54 <1> ares(22706) [zypp::exec++] forkspawnengine.cc(start):427 pid 23678 launched 2024-09-17 10:26:54 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#1|Executing pretrans script for: ImageMagick-config-7-SUSE-7.1.1.38-lp156.757.1.x86_64} START 2024-09-17 10:26:54 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#1|Executing pretrans script for: ImageMagick-config-7-SUSE-7.1.1.38-lp156.757.1.x86_64} END 2024-09-17 10:26:54 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#2|Preparing} START 2024-09-17 10:26:54 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#2|Preparing} END 2024-09-17 10:26:54 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#3|Installing: glibc-extra-2.38-150600.14.8.2.x86_64} START 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#3|Installing: glibc-extra-2.38-150600.14.8.2.x86_64} END 2024-09-17 10:26:55 <1> ares(22706) [zypp-core] PathInfo.cc(unlink):711 unlink /var/cache/zypp/packages/repo-sle-update/x86_64/glibc-extra-2.38-150600.14.8.2.x86_64.rpm 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#4|Installing: glibc-2.38-150600.14.8.2.x86_64} START 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#4|Installing: glibc-2.38-150600.14.8.2.x86_64} END 2024-09-17 10:26:55 <1> ares(22706) [zypp-core] PathInfo.cc(unlink):711 unlink /var/cache/zypp/packages/repo-sle-update/x86_64/glibc-2.38-150600.14.8.2.x86_64.rpm [ ... some more packages ... ] 2024-09-17 10:26:55 <1> ares(22706) [zypp-core] PathInfo.cc(unlink):711 unlink /var/cache/zypp/packages/repo-sle-update/x86_64/libblkid1-2.39.3-150600.4.12.2.x86_64.rpm 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#15|Executing postin script for: libblkid1-2.39.3-150600.4.12.2.x86_64} START 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#15|Executing postin script for: libblkid1-2.39.3-150600.4.12.2.x86_64} END 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):75 {#16|Installing: libjpeg8-8.3.2-lp156.236.1.x86_64} START 2024-09-17 10:26:55 <1> ares(22706) [Progress++] progressdata.cc(report):95 {#16|Installing: libjpeg8-8.3.2-lp156.236.1.x86_64} END 2024-09-17 10:26:55 <1> ares(22706) [zypp-core] PathInfo.cc(unlink):711 unlink /var/cache/zypp/packages/graphics/x86_64/libjpeg8-8.3.2-lp156.236.1.x86_64.rpm Local process tree: |-sshd,2493 | `-sshd,21676 | `-sshd,21714 | `-sh,22336 -c su root -c '/bin/sh -c '"'"'echo BECOME-SUCCESS-nitvvgwxsoijrshepjskqvafwibxpvha ; /usr/bin/python3 /home/martin/.ansible/tmp/ansible-tmp-1726561374.1568432-22131-10361590113718/AnsiballZ_zypper.py'"'"'' && sleep 0 | `-su,22380 root -c /bin/sh -c 'echo BECOME-SUCCESS-nitvvgwxsoijrshepjskqvafwibxpvha ; /usr/bin/python3 /home/martin/.ansible/tmp/ansible-tmp-1726561374.1568432-22131-10361590113718/AnsiballZ_zypper.py' | `-sh,22381 -c echo BECOME-SUCCESS-nitvvgwxsoijrshepjskqvafwibxpvha ; /usr/bin/python3 /home/martin/.ansible/tmp/ansible-tmp-1726561374.1568432-22131-10361590113718/AnsiballZ_zypper.py | `-python3,22382 /home/martin/.ansible/tmp/ansible-tmp-1726561374.1568432-22131-10361590113718/AnsiballZ_zypper.py | `-Zypp-main,22706 --quiet --non-interactive --xmlout update --type package --auto-agree-with-licenses --no-recommends | |-Zypp-main,23678 | | |-systemd-inhibit,23680 --what=sleep:shutdown:idle --who=zypp-rpm --mode=block --why=Zypp commit running. /usr/bin/cat | | | `-cat,23681 | | `-{Zypp-main},23679 | |-btrfs-defrag-pl,22770 /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh | |-snapper-zypp-pl,22776 | |-systemd-inhibit,22768 --what=sleep:shutdown:idle --who=zypp --mode=block --why=Zypp commit running. /usr/bin/cat | | `-cat,22769 | |-{Zypp-main},22712 | |-{Zypp-main},22753 | |-{Zypp-main},22754 | `-{Zypp-main},22755 strace over ID 22706 and all children shows that only 22706 is active: [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=222637363}) = 0 [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=222779630}) = 0 [pid 22706] poll([{fd=53, events=POLLIN|POLLERR|POLLHUP}], 1, 100) = 0 (Timeout) [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=323566963}) = 0 [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=323697986}) = 0 [pid 22706] poll([{fd=53, events=POLLIN|POLLERR|POLLHUP}], 1, 100) = 0 (Timeout) [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=424317979}) [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=424476310}) = 0 [pid 22706] poll([{fd=53, events=POLLIN|POLLERR|POLLHUP}], 1, 100) = 0 (Timeout) [pid 22706] clock_gettime(CLOCK_MONOTONIC, {tv_sec=1293344, tv_nsec=525107967}) = 0 22706 is polling on fd 53, the other end of which is owned by PID 23678: /proc/22706/fd lr-x------ 1 root root 64 Sep 17 11:05 53 -> pipe:[6204057] /proc/23678/fd l-wx------ 1 root root 64 Sep 17 11:05 13 -> pipe:[6204057] l-wx------ 1 root root 64 Sep 17 11:05 4 -> pipe:[6204057] PID 23678 is writing to a different pipe: root@ares:~ # strace -s 512 -p 23678 strace: Process 23678 attached write(3, "\n!zypp.proto.target.PackageProgress\22\4\10k\20'", 41 /proc/22706 lr-x------ 1 root root 64 Sep 17 11:05 49 -> pipe:[6204056] /proc/23678 l-wx------ 1 root root 64 Sep 17 11:05 3 -> pipe:[6204056] cat /proc/23678/stack [<0>] pipe_write+0x2c3/0x630 [<0>] vfs_write+0x2e4/0x380 [<0>] ksys_write+0x50/0xe0 [<0>] do_syscall_64+0x5b/0x80 [<0>] entry_SYSCALL_64_after_hwframe+0x7c/0xe6 Apparently PID 23678 hangs because the other end of the pipe doesn't read it. PID 22706, which is the process supposed to read the pipe, doesn't poll it's fd. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1216177] cockpit-ws: motd not updated when IP address changes
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1216177 https://bugzilla.suse.com/show_bug.cgi?id=1216177#c3 Robert Simai <robert.simai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Robert Simai <robert.simai(a)suse.com> --- As it is tracked upstream (while apparently with low priority) I suggest to close the bug on our side. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224336] Missing packages in microos_cockpit pattern
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

1 0