April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223342] New: Security issus in FreeRDP
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223342 Bug ID: 1223342 Summary: Security issus in FreeRDP Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2024-32039 CVE-2024-32040 CVE-2024-32041 CVE-2024-32458 CVE-2024-32459 CVE-2024-32460 Request is here: https://build.opensuse.org/request/show/1170000 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223145] New: [SELinux] AVC denial on tw + gnome startup relating to xdm_t
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223145 Bug ID: 1223145 Summary: [SELinux] AVC denial on tw + gnome startup relating to xdm_t Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: tumbleweed with gnome desktop SELinux policy version and repository: the one currently in security:SELinux containing the /var/run change (commit in factory branch: 7eb64de2191880e9d2207fa60c9605268d6fc8ce) The software (incl. version) that is affected by the SELinux issue and the error message: gnome 46 + wayland SELinux Audit log: ---- time->Fri Apr 19 13:58:55 2024 type=AVC msg=audit(1713527935.206:83): avc: denied { getattr } for pid=1019 comm="startproc" path=2F7573722F7362696E2F706C796D6F75746864202864656C6574656429 dev="rootfs" ino=2256 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=file permissive=0 Any other important details: install tumbleweed with gnome desktop over regular installer enable selinux, add security:SELinux repo, install selinux-policy + selinux-policy targeted from repo, reboot, AVC happens on every boot low prio, does not break functionality on a quick look -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1219545] New: sound hangs after zypper update; unable to play any sound
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219545 Bug ID: 1219545 Summary: sound hangs after zypper update; unable to play any sound Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Sound used to work fine until yesterday Feb 3 zypper update. Today after boot the sound configuration was non-existent. After yast2 sound Quick configuration the test sound produces no output. Set all volume controls to max. No improvement. Reboot doesn't help. Repeatedly deleting and recreating the sound configuration with yast2 in various ways doesn't help. When an application like aplay, audacious tries to play a sound it hangs. yast2 sound configuration info. 100 Series/C230 Series Chipset Family HD Audio Controller Configured as sound card number 0 Driver snd-hda-intel PulseAudio is enabled. aplay just hangs until it timeouts: $ ll /usr/share/sounds/purple/alert.wav -rw-r--r-- 1 root root 23314 May 9 2022 /usr/share/sounds/purple/alert.wav $ aplay /usr/share/sounds/purple/alert.wav Playing WAVE '/usr/share/sounds/purple/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono ALSA lib pcm_pulse.c:758:(pulse_prepare) PulseAudio: Unable to create stream: Timeout aplay: set_params:1416: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 16 CHANNELS: 1 RATE: 22050 PERIOD_TIME: 125000 PERIOD_SIZE: (2756 2757) PERIOD_BYTES: (5512 5513) PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 11025 BUFFER_BYTES: 22050 TICK_TIME: [0 0] -- You are receiving this mail because: You are on the CC list for the bug.

1 2

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

17 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 10

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