May 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1198626] New: bluez-obex not available by default
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198626 Bug ID: 1198626 Summary: bluez-obex not available by default 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: beppe85(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It was noticed [1] that transferring files via Bluetooth stopped working. This feature can be reinstated with: $ sudo zypper in bluez-obex $ systemctl --user start obex This report is to ask to add the obex package at least as a recommends, and globally enable the service for users, automatically. [1] https://forums.opensuse.org/showthread.php/566965-bluetooth-no-file-transfer -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1195676] New: Ability to specify mkfs.btrfs options
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1195676 Bug ID: 1195676 Summary: Ability to specify mkfs.btrfs options Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: lmb(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I wanted to specify mkfs.btrfs options (specifically, '--csum xxhash') because that can't be changed later at runtime. The installer did not offer the opportunity to specify custom options or modify the command. (My apologies if it does and I missed this. I did see the fstab options, but that isn't what I need here.) (Looks like this is possible in autoyast2, but not the interactive installer?) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1198869] New: [Tumbleweed][postfix][Build_20220423] Postfix relay failed to send when sending mail from vm3 to vm2 via a relay server(vm1)
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198869 Bug ID: 1198869 Summary: [Tumbleweed][postfix][Build_20220423] Postfix relay failed to send when sending mail from vm3 to vm2 via a relay server(vm1) 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: weixuan.hao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Summary Postfix working as a relay server failed to relay mail to recipient server, while sending/receiving mail directly works fine for both server. ## Observation Setting up 3 vms, vm1 works as mail server and relay server, vm2 works as mail server and vm3 is the client. Mails sent directly from vm3 to vm1 and vm2 are successful while mails sent from vm3 to vm2 with vm1 as the relay server failed. Similar issue also observed in sle15-sp4 under fips mode. I'm not sure if this is a misconfiguration issue or some other reason caused this. ## Environment # uname -m x86_64 # cat /etc/*release NAME="openSUSE Tumbleweed" # VERSION="20220423" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20220423" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20220423" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ## Reproducible Basically follow all steps in: https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769966 Note that: 1. 'hash' is not supported in postfix configurations in main.cf now, default replacement is using 'lmdb' 2. Additional dependencies are required, for sle15sp4 cyrus-sasl-saslauthd need to be installed along with metamail installed via package hub; for tumbleweed cyrus-sasl-saslauthd and cyrus-sasl-plain need to be installed Other detailed configurations: VM01: # postconf -n alias_maps = lmdb:/etc/aliases biff = no canonical_maps = lmdb:/etc/postfix/canonical command_directory = /usr/sbin compatibility_level = 3.6 content_filter = daemon_directory = /usr/lib/postfix/bin/ data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 defer_transports = delay_warning_time = 1h disable_dns_lookups = yes disable_mime_output_conversion = no disable_vrfy_command = yes html_directory = /usr/share/doc/packages/postfix-doc/html inet_interfaces = all inet_protocols = all mail_owner = postfix mail_spool_directory = /var/mail mailbox_command = mailbox_size_limit = 0 mailbox_transport = mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man masquerade_classes = envelope_sender, header_sender, header_recipient masquerade_domains = masquerade_exceptions = root message_size_limit = 0 message_strip_characters = \0 mydestination = $myhostname, localhost mydomain = example1.com myhostname = mail.example1.com mynetworks_style = subnet newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/packages/postfix-doc/README_FILES relay_clientcerts = relay_domains = $mydestination, lmdb:/etc/postfix/relay relay_recipient_maps = lmdb:/etc/postfix/relay_recipients relayhost = relocated_maps = lmdb:/etc/postfix/relocated sample_directory = /usr/share/doc/packages/postfix-doc/samples sender_canonical_maps = lmdb:/etc/postfix/sender_canonical sendmail_path = /usr/sbin/sendmail setgid_group = maildrop smtp_enforce_tls = yes smtp_sasl_auth_enable = no smtp_sasl_password_maps = smtp_sasl_security_options = smtp_tls_CAfile = /etc/ssl/ca-bundle.pem smtp_tls_CApath = smtp_tls_cert_file = smtp_tls_key_file = smtp_tls_loglevel = 2 smtp_tls_session_cache_database = smtp_use_tls = yes smtpd_banner = $myhostname ESMTP smtpd_client_restrictions = smtpd_delay_reject = yes smtpd_helo_required = no smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_path = smtpd smtpd_sasl_type = cyrus smtpd_sender_restrictions = lmdb:/etc/postfix/access smtpd_tls_CAfile = smtpd_tls_CApath = smtpd_tls_ask_ccert = no smtpd_tls_cert_file = /etc/postfix/ssl/server1_crt.pem smtpd_tls_exclude_ciphers = RC4 smtpd_tls_key_file = /etc/postfix/ssl/server1_key.pem smtpd_tls_loglevel = 2 smtpd_tls_received_header = yes smtpd_use_tls = yes strict_8bitmime = no strict_rfc821_envelopes = no transport_maps = lmdb:/etc/postfix/transport unknown_local_recipient_reject_code = 550 virtual_alias_maps = lmdb:/etc/postfix/virtual VM02: # postconf -n alias_maps = lmdb:/etc/aliases biff = no canonical_maps = lmdb:/etc/postfix/canonical command_directory = /usr/sbin compatibility_level = 3.6 content_filter = daemon_directory = /usr/lib/postfix/bin/ data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 defer_transports = delay_warning_time = 1h disable_dns_lookups = yes disable_mime_output_conversion = no disable_vrfy_command = yes html_directory = /usr/share/doc/packages/postfix-doc/html inet_interfaces = all inet_protocols = all mail_owner = postfix mail_spool_directory = /var/mail mailbox_command = mailbox_size_limit = 0 mailbox_transport = mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man masquerade_classes = envelope_sender, header_sender, header_recipient masquerade_domains = masquerade_exceptions = root message_size_limit = 0 message_strip_characters = \0 mydestination = $myhostname, localhost mydomain = example2.com myhostname = mail.example2.com mynetworks_style = subnet newaliases_path = /usr/bin/newaliases queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/packages/postfix-doc/README_FILES relay_clientcerts = relay_domains = $mydestination lmdb:/etc/postfix/relay relay_recipient_maps = lmdb:/etc/postfix/relay_recipients relayhost = relocated_maps = lmdb:/etc/postfix/relocated sample_directory = /usr/share/doc/packages/postfix-doc/samples sender_canonical_maps = lmdb:/etc/postfix/sender_canonical sendmail_path = /usr/sbin/sendmail setgid_group = maildrop smtp_enforce_tls = no smtp_sasl_auth_enable = no smtp_sasl_password_maps = smtp_sasl_security_options = smtp_tls_CAfile = smtp_tls_CApath = smtp_tls_cert_file = smtp_tls_key_file = smtp_tls_session_cache_database = smtp_use_tls = no smtpd_banner = $myhostname ESMTP smtpd_client_restrictions = smtpd_delay_reject = yes smtpd_helo_required = no smtpd_helo_restrictions = smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_path = smtpd smtpd_sasl_type = cyrus smtpd_sender_restrictions = lmdb:/etc/postfix/access smtpd_tls_CAfile = smtpd_tls_CApath = smtpd_tls_ask_ccert = no smtpd_tls_cert_file = /etc/postfix/ssl/server2_crt.pem smtpd_tls_exclude_ciphers = RC4 smtpd_tls_key_file = /etc/postfix/ssl/server2_key.pem smtpd_tls_loglevel = 2 smtpd_tls_received_header = yes smtpd_use_tls = yes strict_8bitmime = no strict_rfc821_envelopes = no transport_maps = lmdb:/etc/postfix/transport unknown_local_recipient_reject_code = 550 virtual_alias_maps = lmdb:/etc/postfix/virtual ## Error result Log from vm01: # journactl -u postfix.service Apr 26 15:15:56 vm01 postfix/smtp[14526]: certificate verification failed for mail.example2.com[]:25: self-signed certificate Apr 26 15:15:56 vm01 postfix/smtp[14526]: mail.example2.com[]:25: subject_CN=Shawn, issuer_CN=Shawn, fingerprint=, pkey_fingerpr> Apr 26 15:15:56 vm01 postfix/smtp[14526]: Untrusted TLS connection established to mail.example2.com[]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) se> Apr 26 15:15:56 vm01 postfix/smtp[14526]: CB7AE32CB: to=<root(a)example2.com>, relay=mail.example2.com[]:25, delay=0.11, delays=0.07/0.02/0.02/0, dsn=4.7.5, status=deferred (Server certificate not verified) ## Expected result mail should be sent to vm02 successfully -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1170409] New: update-test-trivial: TW test maintenance updates do not work
by bugzilla_noreply＠novell.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170409 Bug ID: 1170409 Summary: update-test-trivial: TW test maintenance updates do not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The test maintenance update is broken in openSUSE:Factory:Update. Installing update-test-trivial from the TW OSS repository does make the zypper maintenance update available/needed, despite it being in the repository. This indicates that the maintenance update stack is not being tested in Tumbleweed. Same for (at least) update-test-security. Install the non-updated package: $ zypper in --from tw-oss update-test-trivial $ zypper search -s -t package update-test-trivial.x86_64 S | Name | Type | Version | Arch | Repository ---+---------------------+---------+---------+--------+----------- v | update-test-trivial | package | 5-5.1 | x86_64 | tw-update i+ | update-test-trivial | package | 5-4.11 | x86_64 | tw-oss v | update-test-trivial | package | 5-4.1 | x86_64 | tw-update Update is not available: $ zypper lp No updates found. But a newer packages is available: $ zypper lu S | Repository | Name | Current Version | Available Version | Arch --+------------+---------------------+-----------------+-------------------+------- v | tw-update | update-test-trivial | 5-4.11 | 5-5.1 | x86_64 The patch seems to refer a previous package $ zypper info -t patch update-test-trivial Information for patch update-test-trivial: ------------------------------------------ Repository : tw-update Name : update-test-trivial Version : 1 Arch : noarch Vendor : BenniBrunner Status : applied Category : recommended Severity : low Created On : Thu Mar 1 11:28:21 2018 Interactive : --- Summary : Test-update for openSUSE Tumbleweed Description : This is a trivial test-update for openSUSE Tumbleweed. Provides : patch:update-test-trivial = 1 Conflicts : [4] update-test-trivial.src < 5-4.1 update-test-trivial.noarch < 5-4.1 update-test-trivial.x86_64 < 5-4.1 update-test-trivial.i586 < 5-4.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1189003] New: Yast is unable to handle encrypted disk
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 Bug ID: 1189003 Summary: Yast is unable to handle encrypted disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 851486 --> http://bugzilla.opensuse.org/attachment.cgi?id=851486&action=edit Screenshot showing problem and details When trying an update or installation, Yast detects an encrypted disk, asks for the password, and unlocks it, but then is unable to continue (see attachment). The device /dev/mapper/cr-auto-1 is there when Yast claims it is not. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1179492] New: Test grub booting using pe/coff boot entry to support shim and MOK
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1179492 Bug ID: 1179492 Summary: Test grub booting using pe/coff boot entry to support shim and MOK Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: mchang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To support shim lock protocol and use MOK (Machine Owner Key), grub has to load and boot the kernel on it's own without resorting to firmware protocols, namely UEFI LoadImage and StartImage protocols, which would only know about keys in db and dbx and thus would reject image with signature of MOK. To finalize UEFI Secure Boot to fully utilize the capability of shim, the grub package with needed implementation to achieve that is available here. https://build.opensuse.org/package/show/home:michael-chang:arm64-linuxefi/g… In a nut shell, it will call out shim_lock protocol to verify the image, and then jump directly to the PE/COFF entry to boot the image if preceding verification goes successfully. This ticket is opened to track any issue in grub with respect to needed change to adopt shim and MOK on aarch64. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1188363] New: windows:mingw:win{32|64}/mingw{32|64}-python3 missing
by bugzilla_noreply＠suse.com 11 Nov '22

11 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188363 Bug ID: 1188363 Summary: windows:mingw:win{32|64}/mingw{32|64}-python3 missing Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- It would be nice to have a mingw build for Python3 that can be used by mingwxx-gdb and other packages wanting Python3 support. There could be two sources for such a package: 1. https://build.opensuse.org/package/show/home%3Ajayvdb%3Awine-python3%3Apy37… 2. https://github.com/python-cmake-buildsystem/python-cmake-buildsystem The first one uses a custom python build system that is native to the obs project and looks like it would be a lot of work to understand and maintain. Since the build system of the second proposal is based on a known build system (cmake) and it is managed on github, it is suspected that maintenance will be easier here, but may still need adjustments to add mingw based cross-compile functionality and package that. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1191084] New: ocfs2-tools: finish UsrMerge, install to /usr
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1191084 Bug ID: 1191084 Summary: ocfs2-tools: finish UsrMerge, install to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: renzhengeek(a)gmail.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ghe(a)suse.com Blocks: 1191054 Found By: --- Blocker: --- Following up on the discussion on the Factory list https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… All packages installing files into /bin, /sbin, /lib and /lib64 should change the location to the counterpart in /usr instead. Please consider doing that for ocfs2-tools. If ocfs2-tools still needs to build for released distros you may keep the legacy locations within a "%if %suse_version < 1550" block of course. If you do that, please do *NOT* install symlinks from/to /usr as it was done with some packages in the past. Move the files in question instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1129466] New: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129466 Bug ID: 1129466 Summary: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fwdupd 1.2.3-2.1 cannot update the BIOS on my laptop because of this error: $fwupdmgr get-devices ... 20MBCTO1WW System Firmware DeviceId: 65b6a9dc7b7df18bdff003584b51bf21373e3aa6 Guid: 1e1fe415-74e8-49e1-9508-106b3d13d50d Guid: 230c8b18-8d9b-53ec-838b-6cfc0383493a Guid: 171800c9-1a51-5fd9-a32b-7b3999cb1c4e Plugin: uefi Flags: internal|require-ac|supported|registered|needs-reboot Version: 0.1.18 VersionLowest: 0.1.0 Icon: computer Created: 2019-03-15 UpdateError: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found Apparently, if Secure Boot is enabled (my case and I believe TW default on UEFI installs), it looks for /usr/lib/fwupd/efi/fwupdx64.efi.signed. This file is missing but it turns out that /usr/lib/fwupd/efi/fwupdx64.efi is present AND signed: $pesign -S -i /usr/lib/fwupd/efi/fwupdx64.efi --------------------------------------------- certificate address is 0x7f0e55679f78 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is openSUSE Secure Boot Signkey The signer's email address is build(a)opensuse.org Signing time: Tue Mar 05, 2019 There were certs or crls included. --------------------------------------------- So the fix is simply so make a symlink and restart fwupd so it sees the change: $ln -s /usr/lib/fwupd/fwupdx64.efi /usr/lib/fwupd/fwupdx64.efi.signed $systemctl restart fwupd Then the error goes away in 'fwupdmgr get-devices' and you can supposedly update with 'fwupdmgr update' (didn't try it at updating the BIOS is rather scary and I do not absolutely need this update currently). So I think the package should be updated to make the symlink (or rename the file if keeping fwupdx64.efi is unecessary). -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1161823] New: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported"
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1161823 Bug ID: 1161823 Summary: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported" 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: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 828281 --> http://bugzilla.opensuse.org/attachment.cgi?id=828281&action=edit Step 1 of installation When installing OpenSUSE TW, by adding compress=zstd in fstab arbitrary option value will result in broken grub "compression type 0x3 not supported" even it grub already support zstd compression on btrfs. Or maybe I did something wrong. Installation process photos were attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 37