April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221715] New: GCC 14: liblogging package fails
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221715 Bug ID: 1221715 Summary: GCC 14: liblogging package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: thomas.blume(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building liblogging with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: beepframe.c:170:1: error: return type defaults to ‘int’ [-Wimplicit-int] 170 | sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beeplisten.c: In function ‘sbLstnInit’: beeplisten.c:1055:28: error: implicit declaration of function ‘sbSock_InitUXDOMSOCK’ [-Wimplicit-function-declaration] 1055 | if((iRet = sbSock_InitUXDOMSOCK(&(pThis->pSockUXDOMSOCKListening), pActualSockName, /*SOCK_DGRAM*/ SOCK_STREAM)) != SR_RET_OK) | ^~~~~~~~~~~~~~~~~~~~ Builds with: Index: liblogging-1.0.6/rfc3195/src/beepframe.c =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/beepframe.c +++ liblogging-1.0.6/rfc3195/src/beepframe.c @@ -167,6 +167,7 @@ srRetVal sbFramActualRecvFramCommonHdr(s * The channel object is updated, e.g. with a * new seqno. */ +int sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) { unsigned iToRcv; Index: liblogging-1.0.6/rfc3195/src/sockets.h =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/sockets.h +++ liblogging-1.0.6/rfc3195/src/sockets.h @@ -340,4 +340,8 @@ srRetVal sbSockRecvFrom(sbSockObj *pThis # define SOCKET_ERROR -1 #endif +#if FEATURE_UNIX_DOMAIN_SOCKETS == 1 +srRetVal sbSock_InitUXDOMSOCK(sbSockObj **ppThis, char *pszSockName, int iSockType); +#endif + #endif See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218694] New: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1218694 Bug ID: 1218694 Summary: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- After successfully setting up k8s (using `kubeadm init`), the coredns pod remains in a 'Pending' state: NAMESPACE NAME READY STATUS RESTARTS AG kube-system coredns-86ccd44ff8-24h9w 0/1 Pending 0 12 kube-system coredns-86ccd44ff8-rz5vq 0/1 Pending 0 12 kube-system etcd-k8s-head 1/1 Running 1 12 kube-system kube-apiserver-k8s-head 1/1 Running 1 12 kube-system kube-controller-manager-k8s-head 1/1 Running 1 12 kube-system kube-proxy-qprnj 1/1 Running 0 12 kube-system kube-scheduler-k8s-head 1/1 Running 1 13 This is due to a not yet installed network plugin. When installing `kubeadm` thru 'patterns-kubernetes-kubeadm', the package 'flannel-k8s-yaml' is installed alongside which contains a yaml file to set up Flannel as network plugin. Running `kubectl apply -f /usr/share/k8s-yaml/flannel/kube-flannel.yaml` using the supplied file fails, however after: | clusterrole.rbac.authorization.k8s.io/flannel created | clusterrolebinding.rbac.authorization.k8s.io/flannel created | serviceaccount/flannel created | configmap/kube-flannel-cfg created | daemonset.apps/kube-flannel-ds created with the error: | error: resource mapping not found for name: "psp.flannel.unprivileged" namespace: "" from "/usr/share/k8s-yaml/flannel/kube-flannel.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first When using the yaml file from https://github.com/flannel-io/flannel/blob/master/Documentation/kube-flanne… (wget https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/k…) it works, however, the flannel pod is still cycling thru a CrashLoopBackOff - it fails with (from log): | E0110 11:46:48.988799 1 main.go:332] Error registering network: failed to acquire lease: node "k8s-head" pod cidr not assigned -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[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 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 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

[Bug 1222461] New: VUL-0: CVE-2024-22189: TRACKERBUG: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222461 Bug ID: 1222461 Summary: VUL-0: CVE-2024-22189: TRACKERBUG: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22189 https://www.cve.org/CVERecord?id=CVE-2024-22189 https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c… https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme… https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s https://bugzilla.redhat.com/show_bug.cgi?id=2273513 -- You are receiving this mail because: You are on the CC list for the bug.

1 20