July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220731] New: Wayland KDE error messages about pipewire when hover about taskbar
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220731 Bug ID: 1220731 Summary: Wayland KDE error messages about pipewire when hover about taskbar Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a server with a Nvidia quadro K4200 GPU with two monitors connected on port DVI and DP-1 of the GPU. When I hover on the taskbar with the mouse pointer I see tha tI have error message in journalctl Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:53 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:56 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325fb8330: unknown peer 0x560325fba2e0 fd:64 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:56 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:27 hpprol2 pipewire[5524]: mod.client-node: 0x560326073d20: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:27 hpprol2 pipewire[5524]: mod.client-node: 0x56032614fb30: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x5603260ea5e0: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:30 hpprol2 pipewire[5524]: mod.client-node: 0x5603260ea5e0: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:32 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:32 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325f6c7b0 fd:56 Mar 01 09:21:36 hpprol2 pipewire[5524]: mod.client-node: 0x560325e2e150: unknown peer 0x560325f6c7b0 fd:57 Mar 01 09:21:41 hpprol2 pipewire[5524]: mod.client-node: 0x560325f92610: unknown peer 0x560325f6c8a0 fd:56 Mar 01 09:21:42 hpprol2 pipewire[5524]: mod.client-node: 0x560325e1d000: unknown peer 0x560325fb7250 fd:57 Mar 01 09:21:43 hpprol2 pipewire[5524]: mod.client-node: 0x560325f5a340: unknown peer 0x560325fb7250 fd:57 Also from time to time the monitor on the DP-1 flash: the background is shortly displayed. This also occurs only during the hower on the taskbar. Regards Philippe -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217853] New: kscreenlocker is broken on wayland with nvidia drivers
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217853 Bug ID: 1217853 Summary: kscreenlocker is broken on wayland with nvidia drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: yacha(a)orangefox.tech QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I use openSUSE Tumbleweed, the problem I'm having is that every time my PC wakes up from sleep or hibernation it shows me a broken screen locked. "The screen locker is broken and unlocking is not possible anymore..." If I press Super + L being in the KDE wayland session, it does show me kscreenlock without breaking. Only occurs after waking up. I use proprietary nvidia drivers and wayland. Reproducible: Always Steps to Reproduce: 1. Launch a wayland session 2. Go into suspend state 3. Wake it up. Here's the journalctl output of the kscreenlocker: Dec 04 20:01:29 localhost.localdomain kscreenlocker_greet[7134]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: kf.kirigami: Failed to find a Kirigami platform plugin Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed Dec 04 20:01:33 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:setcred): pam_kwallet5: pam_sm_setcred Is there anything I can do to fix or debug it? Thanks before. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225213] New: no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 Bug ID: 1225213 Summary: no sound on speakers, headphones work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- after yesterdays upgrade sound does not play on speakers, but works on headphones. tried to change volum on all devices but no luck. Plasma indicator shows sound playing but nothing is hearable. polrus  ~  inxi -A Audio: Device-1: Intel Comet Lake PCH cAVS driver: sof-audio-pci-intel-cnl API: ALSA v: k6.9.1-1-default status: kernel-api Server-1: PipeWire v: 1.0.6 status: active polrus  ~  dmesg |grep snd_hda [ 6.260721] [ T773] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 6.579988] [ T1408] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat snd_soc_rt715 snd_soc_rt1308_sdw snd_soc_rt711 snd_hda_codec_hdmi regmap_sdw snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm(+) snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_avs snd_soc_hda_codec mac80211 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi libarc4 snd_soc_core snd_compress snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core intel_uncore_frequency spi_nor intel_uncore_frequency_common snd_hwdep hid_sensor_als iTCO_wdt iwlwifi intel_tcc_cooling mtd intel_pmc_bxt hid_sensor_trigger snd_pcm processor_thermal_device_pci_legacy iTCO_vendor_support dell_laptop hid_sensor_iio_common x86_pkg_temp_thermal ee1004 processor_thermal_device industrialio_triggered_buffer intel_powerclamp -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1226280] New: No sound from speakers on Dell XPS laptop
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1226280 Bug ID: 1226280 Summary: No sound from speakers on Dell XPS laptop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: aleksey.rukhlenko(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The sound from speakers randomly appears and disappears after laptop reboot or sleep/wake. The sound from Bluetooth speakers and microphone work OK. If sound from speakers does work, there are no error messages in dmesg related to sound. If sound does not work, here are the error messages from dmesg: > sudo dmesg | grep -i error [ 0.730504] RAS: Correctable Errors collector initialized. [ 13.590627] ucsi_acpi USBC000:00: unknown error 0 [ 22.640402] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -110 [ 22.640406] SDW0-Playback: ASoC: error at __soc_pcm_open on SDW0-Playback: -110 [ 22.640409] Jack Out: ASoC: error at dpcm_be_dai_startup on Jack Out: -110 [ 22.640412] Jack Out: ASoC: error at dpcm_fe_dai_startup on Jack Out: -110 [ 23.187840] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.187846] SDW0-Playback: ASoC: error at __soc_pcm_open on SDW0-Playback: -22 [ 23.187849] Jack Out: ASoC: error at dpcm_be_dai_startup on Jack Out: -22 [ 23.187851] Jack Out: ASoC: error at dpcm_fe_dai_startup on Jack Out: -22 [ 23.187912] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.187916] SDW0-Capture: ASoC: error at __soc_pcm_open on SDW0-Capture: -22 [ 23.187918] Jack In: ASoC: error at dpcm_be_dai_startup on Jack In: -22 [ 23.187920] Jack In: ASoC: error at dpcm_fe_dai_startup on Jack In: -22 [ 23.750769] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.750777] SDW0-Playback: ASoC: error at __soc_pcm_open on SDW0-Playback: -22 [ 23.750779] Jack Out DeepBuffer: ASoC: error at dpcm_be_dai_startup on Jack Out DeepBuffer: -22 [ 23.750782] Jack Out DeepBuffer: ASoC: error at dpcm_fe_dai_startup on Jack Out DeepBuffer: -22 [ 23.759893] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.759902] SDW0-Playback: ASoC: error at __soc_pcm_open on SDW0-Playback: -22 [ 23.759906] Jack Out: ASoC: error at dpcm_be_dai_startup on Jack Out: -22 [ 23.759910] Jack Out: ASoC: error at dpcm_fe_dai_startup on Jack Out: -22 [ 23.791799] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.791806] SDW0-Playback: ASoC: error at __soc_pcm_open on SDW0-Playback: -22 [ 23.791809] Jack Out DeepBuffer: ASoC: error at dpcm_be_dai_startup on Jack Out DeepBuffer: -22 [ 23.791811] Jack Out DeepBuffer: ASoC: error at dpcm_fe_dai_startup on Jack Out DeepBuffer: -22 [ 23.792460] rt711 sdw:0:0:025d:0711:00: ASoC: error at snd_soc_pcm_component_pm_runtime_get on sdw:0:0:025d:0711:00: -22 [ 23.792467] SDW0-Capture: ASoC: error at __soc_pcm_open on SDW0-Capture: -22 [ 23.792471] Jack In: ASoC: error at dpcm_be_dai_startup on Jack In: -22 [ 23.792474] Jack In: ASoC: error at dpcm_fe_dai_startup on Jack In: -22 At my laptop all sound goes through pipewire, no other servers running: > inxi -Aa Audio: Device-1: Intel Comet Lake PCH cAVS vendor: Dell driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0401 API: ALSA v: k6.4.0-150600.21-default status: kernel-api with: aoss type: oss-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl Please help. Hardware: Dell XPS 17 9700 OS: Fresh install of OpenSUSE 15.6 64-bit. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1221501] New: Missing posttls-finger in postfix though changes mention it
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221501 Bug ID: 1221501 Summary: Missing posttls-finger in postfix though changes mention it 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: toganm(a)dinamizm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The change file of postfix 3.8.6 dated Mar 5 16:46:16 UTC 2024 has the following change. Cleanup: this fixes posttls-finger certificate match expectations for all TLS security levels, including warnings for levels that don't implement certificate matching. By Viktor Dukhovni. However posttls-finger is not available in the postfix package. Two questions arise 1. Why is posttls-finger not included? 2. If it is not included why bother to put the above entry to the changelog. Cut copy paste is meaningful only if what is pasted reflects the reality. I would rather see that posttls-finger is included in the package. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217257] New: qt6-webengine error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set'
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217257 Bug ID: 1217257 Summary: qt6-webengine error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello qt6-webengine does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' [ 7245s] 429 | source_.set(source.data(), source.size()); [ 7245s] | ^~~ [ 7245s] ./../../../../../src/3rdparty/chromium/extensions/browser/api/web_request/form_data_parser.cc: In member function 'virtual bool extensions::FormDataParserMultipart::SetSource(base::StringPiece)': [ 7245s] ./../../../../../src/3rdparty/chromium/extensions/browser/api/web_request/form_data_parser.cc:573:11: error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' [ 7245s] 573 | source_.set(source.data(), source.size()); [ 7245s] | ^~~ [ 7245s] At global scope: [ 7245s] cc1plus: note: unrecognized command-line option '-Wno-stringop-overread' may have been intended to silence earlier diagnostics [ 7248s] [24766/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_10.o [ 7250s] [24767/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_18.o [ 7254s] [24768/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_9.o [ 7254s] ninja: build stopped: subcommand failed. [ 7254s] FAILED: src/core/RelWithDebInfo/x86_64/QtWebEngineCore.stamp src/core/RelWithDebInfo/x86_64/QtWebEngineCore [ 7254s] cd /home/abuild/rpmbuild/BUILD/qtwebengine-everywhere-src-6.4.2/build/src/core && /usr/bin/ninja -j4 -C /home/abuild/rpmbuild/BUILD/qtwebengine-everywhere-src-6.4.2/build/src/core/RelWithDebInfo/x86_64 QtWebEngineCore [ 7254s] ninja: build stopped: subcommand failed. [ 7254s] error: Bad exit status from /var/tmp/rpm-tmp.KR5dFa (%build) [ 7254s] -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223533] New: cockpit: /nonexistent/libexec/cockpit-askpass
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223533 Bug ID: 1223533 Summary: cockpit: /nonexistent/libexec/cockpit-askpass 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: --- Created attachment 874558 --> https://bugzilla.suse.com/attachment.cgi?id=874558&action=edit nonexistent/libexec/cockpit-askpass On freshly installed Leap 15.6 + cockpit If you login to localhost:9090 as a standard user and you try to enable the admin view by clicking on the cockpit homescreen button, then cockpit will raise following error Problem becoming administrator Sudo: unable to run /nonexistent/libexec/cockpit-askpass: No such file or directory sudo: no password was provided sudo: a password is required lkocman@localhost:~/Workspace/obs> sudo zypper in cockpit [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Retrieving repository 'packman' metadata .....................................................................................................................................................[done] Building repository 'packman' cache ..........................................................................................................................................................[done] 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 2 recommended packages were automatically selected: cockpit-networkmanager cockpit-storaged The following package is recommended, but will not be installed due to conflicts or dependency issues: cockpit-packagekit The following 2 packages are suggested, but will not be installed: cockpit-pcp cockpit-selinux The following 8 NEW packages are going to be installed: cockpit cockpit-bridge cockpit-networkmanager cockpit-storaged cockpit-system cockpit-ws libpwquality-tools libudisks2-0_lvm2 8 new packages to install. Overall download size: 7.1 MiB. Already cached: 0 B. After the operation, additional 8.3 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: cockpit-bridge-309-bp156.1.2.x86_64 (repo-oss (15.6)) (1/8), 471.8 KiB Retrieving: cockpit-bridge-309-bp156.1.2.x86_64.rpm .............................................................................................................................[done (10.9 KiB/s)] Retrieving: cockpit-ws-309-bp156.1.2.x86_64 (repo-oss (15.6)) (2/8), 1.7 MiB Retrieving: cockpit-ws-309-bp156.1.2.x86_64.rpm ..................................................................................................................................[done (8.4 MiB/s)] Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64 (repo-oss (15.6)) (3/8), 19.4 KiB Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64.rpm ...................................................................................................................................[done] Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 (repo-oss (15.6)) (4/8), 57.0 KiB Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64.rpm .....................................................................................................................[done (93.5 KiB/s)] Retrieving: cockpit-system-309-bp156.1.2.noarch (repo-oss (15.6)) (5/8), 3.2 MiB Retrieving: cockpit-system-309-bp156.1.2.noarch.rpm ..............................................................................................................................[done (6.7 MiB/s)] Retrieving: cockpit-storaged-309-bp156.1.2.noarch (repo-oss (15.6)) (6/8), 850.0 KiB Retrieving: cockpit-storaged-309-bp156.1.2.noarch.rpm ............................................................................................................................[done (4.2 MiB/s)] Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch (repo-oss (15.6)) (7/8), 827.8 KiB Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch.rpm ......................................................................................................................[done (3.8 MiB/s)] Retrieving: cockpit-309-bp156.1.2.x86_64 (repo-oss (15.6)) (8/8), 45.5 KiB Retrieving: cockpit-309-bp156.1.2.x86_64.rpm .................................................................................................................................................[done] Checking for file conflicts: .................................................................................................................................................................[done] (1/8) Installing: cockpit-bridge-309-bp156.1.2.x86_64 ........................................................................................................................................[done] (2/8) Installing: cockpit-ws-309-bp156.1.2.x86_64 ............................................................................................................................................[done] (3/8) Installing: libpwquality-tools-1.4.5-150600.2.2.x86_64 .................................................................................................................................[done] (4/8) Installing: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 ................................................................................................................................[done] (5/8) Installing: cockpit-system-309-bp156.1.2.noarch ........................................................................................................................................[done] (6/8) Installing: cockpit-storaged-309-bp156.1.2.noarch ......................................................................................................................................[done] (7/8) Installing: cockpit-networkmanager-309-bp156.1.2.noarch ................................................................................................................................[done] (8/8) Installing: cockpit-309-bp156.1.2.x86_64 ...............................................................................................................................................[done] lkocman@localhost:~/Workspace/obs> sudo systemctl enable --now cockpit.socket Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket. lkocman@localhost:~/Workspace/obs> -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1225432] New: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text
by bugzilla_noreply＠suse.com 23 Sep '24

23 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225432 Bug ID: 1225432 Summary: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: locilka(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875149 --> https://bugzilla.suse.com/attachment.cgi?id=875149&action=edit Snippet of the log When iSCSI Targets are being discovered in Agama, the iSCSI library logs all the details. Sadly, also including passwords. How to reproduce? Easily -> Start Agama Installer -> Go to Storage details -> Click Prepare devices by configuring advanced storage technologies -> Choose iSCSI -> Click Discover iSCSI targets -> Fill-up some users/passwords -> Click Confirm This will be most probably the same in YaST as well because it uses the same library. BTW, there are two entries for user/password, but you can see only the first one in the log. That's most probably because the second one would be used later, if the first one succeeds (not my case). Additionally, even the save_y2logs script does not remove the passwords. maybe because the string in the log this: {"name"=>"discovery.sendtargets.auth.password", "value"=>"and their password", "kind"=>"value", "type"=>1, "comment"=>""} -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1222338] New: curl 8.7.1 and libzypp cause curl error 92 on fetching updates
by bugzilla_noreply＠suse.com 23 Sep '24

23 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222338 Bug ID: 1222338 Summary: curl 8.7.1 and libzypp cause curl error 92 on fetching updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I can no longer refresh some 3rd party repositories after the curl 8.7.1 upgrade in tumbleweed. curl 8.6.0 works fine. the errors point out a http/2 protocol error. here's the snippet from the log: 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Found bundle for host: 0x564be94f55c0 [can multiplex] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Re-using existing connection with host dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] OPENED stream for https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:method: GET] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:scheme: https] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:authority: dl.google.com] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:path: /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [user-agent: ZYpp 17.31.15 (curl 8.7.1)] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > GET /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml HTTP/2 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Host: dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > User-Agent: ZYpp 17.31.15 (curl 8.7.1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Request completely sent off 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < HTTP/2 200 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-length: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(headerfunction):653 0x564be956d140 Got Content-Length Header: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-security-policy: default-src 'none' 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < server: downloads 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-content-type-options: nosniff 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-frame-options: SAMEORIGIN 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-xss-protection: 0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < cache-control: public,max-age=0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < last-modified: Wed, 03 Apr 2024 16:46:55 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < date: Thu, 04 Apr 2024 17:44:16 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < etag: "26973aa" 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Invalid HTTP header field was received: frame type: 1, stream: 17, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * HTTP/2 stream 17 was not closed cleanly: PROTOCOL_ERROR (err 1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Connection #0 to host dl.google.com left intact 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] basicdownloader_p.cc(onRequestFinished):201 0x564be956d140 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml failed with error Server returned a HTTP/2 strea m error. Curl error (92) Invalid HTTP header field was received: frame type: 1, stream: 17, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(unlink):705 unlink /var/tmp/AP_0xzr4SK4/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(transitionToFinished):36 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml transition to final state. 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] final_p.cc(FinishedState):20 About to enter FinishedState for url https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(enter):20 Entering initial state 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(initiate):44 No zchunk data available but metalink requested, going to download metalink directly. 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(DlMetaLinkInfoState):25 Downloading metalink/zsync on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(exit):22 Leaving initial state 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(initializeRequest):51 Requesting Metadata info from server! 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(chmod):1099 assert_file_mode 00600 /var/lib/YaST2/cookieschmod /var/lib/YaST2/cookies 00600 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(aboutToStart):469 0x564be956d140 Setting activity timeout to: 180 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Found bundle for host: 0x564be94f55c0 [can multiplex] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Re-using existing connection with host dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] OPENED stream for https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:method: GET] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:scheme: https] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:authority: dl.google.com] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:path: /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [user-agent: ZYpp 17.31.15 (curl 8.7.1)] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > GET /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml HTTP/2 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Host: dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > User-Agent: ZYpp 17.31.15 (curl 8.7.1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Request completely sent off 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < HTTP/2 200 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-length: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(headerfunction):653 0x564be956d140 Got Content-Length Header: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-security-policy: default-src 'none' 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < server: downloads 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-content-type-options: nosniff 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-frame-options: SAMEORIGIN 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-xss-protection: 0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < cache-control: public,max-age=0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < last-modified: Wed, 03 Apr 2024 16:46:55 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < date: Thu, 04 Apr 2024 17:44:16 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < etag: "26973aa" 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Invalid HTTP header field was received: frame type: 1, stream: 19, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * HTTP/2 stream 19 was not closed cleanly: PROTOCOL_ERROR (err 1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Connection #0 to host dl.google.com left intact 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] basicdownloader_p.cc(onRequestFinished):201 0x564be956d140 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml failed with error Server returned a HTTP/2 stream error. Curl error (92) Invalid HTTP header field was received: frame type: 1, stream: 19, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(unlink):705 unlink /var/tmp/AP_0xzr4SK4/repodata/repomd.xml -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1217690] New: libcamera: reproducible builds vs signatures
by bugzilla_noreply＠suse.com 21 Sep '24

21 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217690 Bug ID: 1217690 Summary: libcamera: reproducible builds vs signatures Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: rfrohl(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jengelh(a)inai.de Blocks: 1062303 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE+ALP, I found that our libcamera package varies in every build because during build it creates a random keypair, embeds the pubkey adds .so.sign files When I asked upstream about it long ago, it was said to prevent smuggling in of 3rd party modules that shall not receive the same level of permissions as modules that are shipped as part of the main codebase. Can we patch src/libcamera/ipa_module.cpp to not use .sign files or is there another way to get reproducible build results for libcamera? -- You are receiving this mail because: You are on the CC list for the bug.

1 2