April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215172] New: VUL-0: croc: multiple security issues in croc
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215172 Bug ID: 1215172 Summary: VUL-0: croc: multiple security issues in croc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jsmithfpv(a)gmail.com Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have reviewed the Croc codebase during the past month and have found a series of security issues, mostly in the area of a receiver of files which can be harmed by a malicious sender. There are now public GitHub issues about the most pressing issues: - possible creation of files in dangerous path location: https://github.com/schollz/croc/issues/593 - Interactive File Overwrite Prompt can be Circumvented by Sending ZIP file: https://github.com/schollz/croc/issues/594 - Escape Sequences in Filenames are not Filtered: https://github.com/schollz/croc/issues/595 - Use of Parts of the Shared Secret as Room Name: https://github.com/schollz/croc/issues/596 - Unencrypted "ips?" Message Leaks Information from the Sender Side: https://github.com/schollz/croc/issues/597 - Shared Secret Passed on Command Line Possibly Leaks to other Local Users: https://github.com/schollz/croc/issues/598 Nothing of this is currently fixed and it sounds like they also won't be fixed for a longer time, because the upstream author is lacking time to take care of this. As maintainers of croc you may be able to help out upstream to fix these issues or you may consider dropping this package from openSUSE until it becomes better. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1222595] New: find-debuginfo.sh crash when build with kanidm
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222595 Bug ID: 1222595 Summary: find-debuginfo.sh crash when build with kanidm 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: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- find-debuginfo.sh crash when building with kanidm, the full build log openSUSE:Backports:SLE-15-SP6 staging[1] [ 1201s] + /usr/lib/rpm/find-debuginfo.sh -j4 --build-id-seed 1.1.0~rc16~git4.d407844-bp156.2.1 --unique-debug-suffix -1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --unique-debug-src-base kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /home/abuild/rpmbuild/BUILD/kanidm-1.1.0~rc16~git4.d407844 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/bin/kanidm [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/lib64/security/pam_kanidm.so [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/lib64/libnss_kanidm.so.2 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/sbin/kanidm-ipa-sync [ 1201s] Cannot handle 8-byte build ID [ 1201s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] /usr/lib/rpm/find-debuginfo.sh: line 521: /tmp/find-debuginfo.avVGqk/res.*: No such file or directory [1] https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215622] New: iscsiuio - Couldn't mmap registers: Invalid argument
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215622 Bug ID: 1215622 Summary: iscsiuio - Couldn't mmap registers: Invalid argument Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to set up an iscsi initiator (in yast) using a bnx2 offload engine, I wasn't getting very far, see bug#1215621. I kept getting this error: iscsiadm: Could not set host net params (err 29) I ran iscsiuio with debug level 4 and noticed the following error msg: Couldn't mmap registers: Invalid argument After some research, I rebooted the machine with "iomem=relaxed" - now it works: anton:~ # iscsiadm -m discovery -P 1 -t st -I eth4-bnx2i -p 10.42.8.10:3260 iscsiadm: Could not set host net params (err 29) iscsiadm: Connection to discovery portal 10.42.8.10 failed: operation failed but retry may succeed Target: iqn.2023-09.local.rz2:opensuse-mirror Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i Target: iqn.2023-09.local.rz2:webspace Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222269] New: LLVM run OOM while building typst for armv6/7 with 24G of RAM
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222269 Bug ID: 1222269 Summary: LLVM run OOM while building typst for armv6/7 with 24G of RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LLVM run OOM while building typst for armv6/7 with 24G of RAM while aarch64 requires 11.8G of RAM ********** [ 173s] Compiling typst-ide v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/crates/typst-ide) [ 429s] Compiling typst-fuzz v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/tests/fuzz) [ 658s] LLVM ERROR: out of memory [ 658s] Allocation failed [ 658s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 658s] called `Option::unwrap()` on a `None` value [ 658s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 658s] error: could not compile `typst-docs` (bin "typst-docs") [ 658s] warning: build failed, waiting for other jobs to finish... [ 663s] LLVM ERROR: out of memory [ 663s] Allocation failed [ 664s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 664s] called `Option::unwrap()` on a `None` value [ 664s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 664s] error: could not compile `typst-fuzz` (bin "compile") [ 694s] LLVM ERROR: out of memory [ 694s] Allocation failed [ 694s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 694s] called `Option::unwrap()` on a `None` value [ 694s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 694s] error: could not compile `typst-cli` (bin "typst") [ 694s] error: Bad exit status from /var/tmp/rpm-tmp.R2PFPX (%build) ********** See: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/typs… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214213] New: shadowsocks-rust: shadowsocks-rust-client.service should not use Type=forking
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1214213 Bug ID: 1214213 Summary: shadowsocks-rust: shadowsocks-rust-client.service should not use Type=forking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: darkgeekyang(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, The shadowsocks-rust-client.service provided by shadowsocks-rust has Type set to forking, which leads to the timeout of this service every minutes. Since the command sslocal used in ExecStart won't fork, so it's not correct to use forking, instead we should just remove the two lines in the unit service: >Type=forking >PIDFile=/var/run/shadowsocks-rust-client.pid After doing this, the service becomes stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222854] New: https subversion checkout fails
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222854 Bug ID: 1222854 Summary: https subversion checkout fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jonathan.brady(a)denbridgemarine.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh install of current beta, with just "subversion" package added. At the time of writing that is subversion-1.14.1-150400.3.8. Trying to checkout any https url fails. For example "svn co https://opensuse.org" (yes, I know there is no repository there, there doesn't need to be), the command never returns. tcpdump shows lots of activity on port 443, but the TLS connection never establishes. Other programs (w3m for example are able to establish TLS connection without problem). My expected result with that URL, would be: Redirecting to URL 'https://www.opensuse.org': svn: E170013: Unable to connect to a repository at URL 'https://www.opensuse.org' svn: E175003: The server at 'https://www.opensuse.org' does not support the HTTP/DAV protocol -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1216766] New: Weather app no longer fetches data - /usr/lib64/libmateweather.so.1.6.9 needs patch
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216766 Bug ID: 1216766 Summary: Weather app no longer fetches data - /usr/lib64/libmateweather.so.1.6.9 needs patch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- from https://github.com/mate-desktop/libmateweather/pull/79 We upgraded our website today. The old Java based Dataserver was retired. So the URL for the dataserver has changed. OLD: https://www.aviationweather.gov/adds/dataserver_current/httpparam NEW: https://www.aviationweather.gov/cgi-bin/data/dataserver.php I was able to hack the libmateweather.so file to change the URL and get Mate weather working again. I patched mine and weather works again -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223194] New: Empty battery reported after suspend
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 Bug ID: 1223194 Summary: Empty battery reported after suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following up on https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/… In between I have the impression that the battery status after a suspend is reported wrong from the system (so no drain ,as originally assumed). I had the laptop suspend and at the charger over night, in the morning it reported 8% charge left. Which is definitely wrong. Other than 'in earlier times' it does not get updated to the correct status. This is quite annoying as the laptop is my primary workhorse Let me know how I can debug/provide information on this. Thank you! Operating System: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: LENOVO Product Name: 20QWS0A8GE System Version: ThinkPad X1 Extreme 2nd -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212841] New: Lots of objtool warnings when building the nvidia driver
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1212841 Bug ID: 1212841 Summary: Lots of objtool warnings when building the nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- # rpm -qv nvidia-driver-G06-kmp-default nvidia-driver-G06-kmp-default-535.54.03_k6.3.7_1-10.1.x86_64 # zgrep -c objtool zypper.log-20230627.xz 213230 extracts: [rpm> LD [M] /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000675kms+0x46: 'naked' return found in RETHUNK build [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000676kms+0x46: 'naked' return found in RETHUNK build [cut] [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv040720rm+0xb9: return with modified stack frame [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv013581rm+0xd9: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-64 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv034058rm+0x83: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-56 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv024689rm+0xb: missing int3 after ret [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv043791rm+0x4: missing int3 after ret [cut] then it finishes building and prints a couple last warnings such as: [rpm> Skipping BTF generation for /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-peermem.ko due to unavailability of vmlinux -- You are receiving this mail because: You are on the CC list for the bug.

1 10