November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188023] New: GNOME:Apps/fractal:
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188023 Bug ID: 1188023 Summary: GNOME:Apps/fractal: Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: william.brown(a)suse.com QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- I've recently started a project to automatically scan for potential security issues in rust packages with cargo audit. I noticed the following on fractal: * RUSTSEC-2021-0026 -> crate: comrak, cvss: None, class: ['format-injection'] * RUSTSEC-2021-0063 -> crate: comrak, cvss: None, class: ['format-injection'] * RUSTSEC-2020-0060 -> crate: futures-task, cvss: None, class: ['code-execution', 'memory-corruption'] * RUSTSEC-2020-0059 -> crate: futures-util, cvss: None, class: ['thread-safety'] * RUSTSEC-2020-0146 -> crate: generic-array, cvss: None, class: ['memory-corruption'] * RUSTSEC-2021-0020 -> crate: hyper, cvss: None, class: ['format-injection'] Most of these should be able to be resolved with cargo update and re-vendoring the dependencies. Alternately upstream may have released a Cargo.toml/Cargo.lock with updates for this. It would be great if you could look into updating and resolving these :) Thank you! -- more info https://github.com/openSUSE/obs-service-cargo_audit/blob/main/README.md https://en.opensuse.org/Packaging_Rust_Software -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1201804] New: Building the GNOME text editor for PCRE2 usage
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201804 Bug ID: 1201804 Summary: Building the GNOME text editor for PCRE2 usage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The dependencies for the software package ��gnome-text-editor 42.2-1.1�� contain the information ��Requires: libpcre.so.1()(64bit)��. How are the chances to support the API ��PCRE2�� (with library versions �� 10.40)? https://github.com/PCRE2Project/pcre2 https://build.opensuse.org/package/view_file/openSUSE:Factory/gnome-text-ed… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1196707] New: lxqt-config-appearance fails to open due to missing liblxqt-config-cursor.so
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196707 Bug ID: 1196707 Summary: lxqt-config-appearance fails to open due to missing liblxqt-config-cursor.so Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: slemke(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- slemke@notebook:~> zypper info lxqt-config Loading repository data... Reading installed packages... Information for package lxqt-config: ------------------------------------ Repository : Main Repository Name : lxqt-config Version : 1.0.0-bp154.1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 1.3 MiB Installed : Yes (automatically) Status : up-to-date Source package : lxqt-config-1.0.0-bp154.1.1.src Upstream URL : http://www.lxqt.org Summary : LXQt Control Center Description : System Configuration and Control Center for LXQt slemke@notebook:~> slemke@notebook:~> lxqt-config-appearance lxqt-config-appearance: error while loading shared libraries: liblxqt-config-cursor.so: cannot open shared object file: No such file or directory slemke@notebook:~> Some maybe useful outputs: slemke@notebook:~> rpm -qa |grep -i lxqt |grep -c 1.0.0 25 slemke@notebook:~> rpm -qa |grep -ic lxqt 35 slemke@notebook:~> rpm -qa |grep -i lxqt |grep -v 1.0.0 patterns-lxqt-lxqt-20170319-lp154.1.2.x86_64 lxqt-theme-openSUSE-default-0.1-bp154.1.2.noarch lxqt-globalkeys-1.0.1-bp154.1.1.x86_64 lxqt-theme-openSUSE-leaper-0.1-bp154.1.2.noarch lxqt-globalkeys-lang-1.0.1-bp154.1.1.noarch lxqt-archiver-0.5.0-bp154.1.1.x86_64 lxqt-archiver-lang-0.5.0-bp154.1.1.noarch liblxqt-globalkeys-ui1-1.0.1-bp154.1.1.x86_64 liblxqt-globalkeys1-1.0.1-bp154.1.1.x86_64 lxqt-theme-openSUSE-light-0.1-bp154.1.2.noarch slemke@notebook:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200182] New: systemd-resolved cannot bind port 53
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200182 Bug ID: 1200182 Summary: systemd-resolved cannot bind port 53 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: paul(a)pbarker.dev QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh installation of OpenSUSE MicroOS, I have attempted to switch to systemd-networkd and systemd-resolved to manage my network connections following the instructions in https://en.opensuse.org/Network_Management_With_Systemd. However, when trying to enable systemd-resolved I hit an error: alpha:~ # systemctl enable --now systemd-resolved Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service �� /usr/lib/systemd/system/systemd-resolved.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service �� /usr/lib/systemd/system/systemd-resolved.service. Job for systemd-resolved.service failed because the control process exited with error code. See "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details. alpha:~ # journalctl -xeu systemd-resolved.service �� Subject: Automatic restarting of a unit has been scheduled �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for �� the configured Restart= setting for the unit. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Stopped Network Name Resolution. �� Subject: A stop job for unit systemd-resolved.service has finished �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A stop job for unit systemd-resolved.service has finished. �� The job identifier is 1376 and the job result is done. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Starting Network Name Resolution... �� Subject: A start job for unit systemd-resolved.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit systemd-resolved.service has begun execution. �� The job identifier is 1376. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Positive Trust Anchors: Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.> Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Using system hostname 'alpha.cephei.uk'. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to listen on UDP socket 127.0.0.53:53: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to start manager: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit systemd-resolved.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Failed to start Network Name Resolution. It appears that the permission denied errors when systemd-resolved tried to bind port 53 are caused by SELinux. I confirmed that this is the case by disabling SELinux and retrying the command - this resulted in systemd-resolved successfully starting. Therefore I think there is an error in the SELinux policy here - systemd-resolved should be able to bind port 53 on localhost to offer DNS resolution services. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205456] New: patch "openSUSE-SLE-15.4-2022-2969" conflicts with packman packages
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205456 Bug ID: 1205456 Summary: patch "openSUSE-SLE-15.4-2022-2969" conflicts with packman packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862909 --> https://bugzilla.suse.com/attachment.cgi?id=862909&action=edit screenshot from gpk-update-viewer Patch openSUSE-SLE-15.4-2022-2969 breaks updating Leap 15.4 because of a conflict with libswresample. The graphical update tool gpk-update-viewer runs into an error that unexperienced users might not understand. "zypper patch --with-optional" would install the patch, changing a bunch of ffmpeg and avcodec related packages from Packman to SUSE LLC, which is most probably not what the users want. "zypper update" skips these updates instead. It is unclear to me why these conflicts are in the patch meta data. It's obviously possible to update the other packages (non-ffmpeg) without breaking any package-level dependencies. Several users have posted about this in the Forum: https://www.opensuse-forum.de/thread/65990-softwareaktualisierung-funktioni… https://forums.opensuse.org/showthread.php/574888-openSUSE-SLE-15-4-2022-29… Is there a deeper reason for creating this artificial conflict? -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1202351] New: dracut: remove mkinitrd wrapper
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202351 Bug ID: 1202351 Summary: dracut: remove mkinitrd wrapper Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…). ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1203019] New: yast2: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203019 Bug ID: 1203019 Summary: yast2: replace mkinitrd wrapper with native dracut Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: jsrain(a)suse.com Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…). ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. References: - yast2 /usr/share/YaST2/modules/Initrd.rb:72: # parametr for mkinitrd because of splash screen /usr/share/YaST2/modules/Initrd.rb:75: # Additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:391: "/lib/mkinitrd/scripts/setup-splash.sh" /usr/share/YaST2/modules/Initrd.rb:400: "/sbin/mkinitrd %1 %2 >> %3 2>&1", /usr/share/YaST2/modules/Initrd.rb:405: File.join(Directory.logdir, "y2logmkinitrd").shellescape /usr/share/YaST2/modules/Initrd.rb:411: Ops.add(Directory.logdir, "/y2logmkinitrd") /usr/share/YaST2/modules/Initrd.rb:434: # Set the -s parameter of mkinitrd /usr/share/YaST2/modules/Initrd.rb:463: # Get additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:464: # @return [String] additional mkinitrd parameters /usr/share/YaST2/modules/Initrd.rb:469: # Set additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:470: # @param [String] params string additional mkinitrd parameters # rpm -qf /usr/share/YaST2/modules/Initrd.rb yast2-4.5.10-1.1.x86_64 - yast2-country /usr/share/YaST2/modules/Timezone.rb:85: # if mkinitrd should be called at the end /usr/share/YaST2/modules/Timezone.rb:86: @call_mkinitrd = false /usr/share/YaST2/modules/Timezone.rb:467: Builtins.y2milestone("calling mkinitrd...") /usr/share/YaST2/modules/Timezone.rb:470: "/sbin/mkinitrd >> /var/log/YaST2/y2logmkinitrd 2>> /var/log/YaST2/y2logmkinitrd" /usr/share/YaST2/modules/Timezone.rb:860: CallMkinitrd() if @call_mkinitrd && !Stage.initial /usr/share/YaST2/modules/Timezone.rb:1081: publish :variable => :call_mkinitrd, :type => "boolean" # rpm -qf /usr/share/YaST2/modules/Timezone.rb yast2-country-4.5.1-1.1.x86_64 - yast2-kdump /usr/share/YaST2/modules/Kdump.rb:419: update_command = (using_fadump? ? "/usr/sbin/mkdumprd -f" : "/sbin/mkinitrd") /usr/share/YaST2/modules/Kdump.rb:426: update_logfile = File.join(Directory.logdir, "y2logmkinitrd") # rpm -qf /usr/share/YaST2/modules/Kdump.rb yast2-kdump-4.5.3-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1205162] New: PHP mysqli not load from web after upgrade
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205162 Bug ID: 1205162 Summary: PHP mysqli not load from web after upgrade Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: novell(a)regproctor.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Everything is described here: https://forums.opensuse.org/showthread.php/576937-mysqli-doesnt-work?highli… however in short: Once having done a distribution upgrade from leap 15.3 to 15.4 the PHP MySQLi module won't load when running from the web unless you add the line: extension=mysqlnd somewhere in a used php.ini. However, when running PHP from the command line (CLI mode) the module loads correctly which also means that when you add the line then from then on in CLI mode you will get the warning: PHP Warning: Module 'mysqlnd' already loaded in Unknown on line 0 I guess you could avoid the warning by adding the line in: /etc/php7/apache/php.ini which I should add the fact into the above referenced forum post. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1175219] New: OpenVPN fails with certificates on smart cards on Leap 15.2 and TW
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1175219 Bug ID: 1175219 Summary: OpenVPN fails with certificates on smart cards on Leap 15.2 and TW Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from Leap 15.1 to Leap 15.2 working OpenVPN setups with PKCS11 certificates on Yubikeys are failing. The same applies to openSUSE Tumbleweed. Also other smart card devices may be affected. OpenVPN does not show many details, even with highest logging level. # openvpn --cd /etc/openvpn --config openvpn-yubikey-test.ovpn [...] Thu Aug 13 10:21:21 2020 VERIFY OK: depth=1, CN=Test CA Thu Aug 13 10:21:21 2020 VERIFY KU OK Thu Aug 13 10:21:21 2020 Validating certificate extended key usage Thu Aug 13 10:21:21 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Thu Aug 13 10:21:21 2020 VERIFY EKU OK Thu Aug 13 10:21:21 2020 VERIFY OK: depth=0, CN=host1.example.com Thu Aug 13 10:21:21 2020 OpenSSL: error:141F0006:SSL routines:tls_construct_cert_verify:EVP lib Thu Aug 13 10:21:21 2020 TLS_ERROR: BIO read tls_read_plaintext error Thu Aug 13 10:21:21 2020 TLS Error: TLS object -> incoming plaintext read error Thu Aug 13 10:21:21 2020 TLS Error: TLS handshake failed Thu Aug 13 10:21:21 2020 Fatal TLS error (check_tls_errors_co), restarting Thu Aug 13 10:21:21 2020 SIGUSR1[soft,tls-error] received, process restarting Thu Aug 13 10:21:21 2020 Restart pause, 5 second(s) The bug can be resolved by upgrading the pkcs11-helper packages from pkcs11-helper-1.25.1 to pkcs11-helper-devel-1.26.0. # openvpn --cd /etc/openvpn --config openvpn-yubikey-test.ovpn [...] Thu Aug 13 10:32:36 2020 VERIFY OK: depth=1, CN=Test CA Thu Aug 13 10:32:36 2020 VERIFY KU OK Thu Aug 13 10:32:36 2020 Validating certificate extended key usage Thu Aug 13 10:32:36 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Thu Aug 13 10:32:36 2020 VERIFY EKU OK Thu Aug 13 10:32:36 2020 VERIFY OK: depth=0, CN=host1.example.com Enter user1 token Password: (press TAB for no echo) There is a problem with inconsistent padding between OpenSSL 1.1.1 and pkcs11-helper-1.25.1. The details are described here: http://openssl.6102.n7.nabble.com/Issue-with-smartcard-authentication-for-o… The pkcs11-helper-devel-1.26.0 Changelog contains this line: - openssl: support RSA_NO_PADDING padding, thanks to Selva Nair -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1205603] New: bpf lsm enabled but not included in LSM list
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205603 Bug ID: 1205603 Summary: bpf lsm enabled but not included in LSM list 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: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During my system upgrades i noticed the following message: ```systemd[1]: bpf-lsm: BPF LSM hook not enabled in the kernel, BPF LSM not supported``` but we have: ```CONFIG_BPF_LSM=y``` i asked Frank Bui what it checks for. it checks for the string "bpf" in this list: ``` cat /sys/kernel/security/lsm lockdown,capability,apparmor ``` it seems ```CONFIG_LSM="integrity,apparmor"``` needs an update. -- You are receiving this mail because: You are on the CC list for the bug.

1 7