July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224003] New: after snapshot 20240424 core dump for named with samba-ad-dc
by bugzilla_noreply＠suse.com 11 Aug '24

11 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224003 Bug ID: 1224003 Summary: after snapshot 20240424 core dump for named with samba-ad-dc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874735 --> https://bugzilla.suse.com/attachment.cgi?id=874735&action=edit Coredump of named with samba-ad-dc I have a raspberry with samba-ad-dc and named. After snapshot 20240424 named doesn't start and I have a core dump for named; If I comment the instructions for samba-ad-dc in /etc/named.conf I can start named. the two instructions commented in named.confare include "/var/lib/samba/bind-dns/named.conf"; tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab"; Samba-ad-dc is running rasp:/etc # systemctl status samba-ad-dc ● samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/usr/lib/systemd/system/samba-ad-dc.service; enabled; preset: disabled) Active: active (running) since Wed 2024-04-03 09:04:17 CEST; 1 month 3 days ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Process: 1256 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 1318 (samba) Status: "samba: ready to serve connections..." Tasks: 51 (limit: 4471) CPU: 9min 54.827s CGroup: /system.slice/samba-ad-dc.service etc.... I attach the coredump Many thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223624] New: [Build 20240501] podman bats user integration fails test suites
by bugzilla_noreply＠suse.com 10 Aug '24

10 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1223624 Bug ID: 1223624 Summary: [Build 20240501] podman bats user integration fails test suites Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4145118/modules/bats -user-local_tap/steps/47 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Since the latest changes, the tests look better, but not yet completely fixed. Theese are the current failures: bats-user-local: not ok 47 [012] manifest list --add --artifact # (from function `run_podman' in file test/system/helpers.bash, line 416, # from function `manifestListAddArtifactOnce' in file test/system/012-manifest.bats, line 167, # in test file test/system/012-manifest.bats, line 262) # `manifestListAddArtifactOnce' failed not ok 367 [200] podman pod cleans cgroup and keeps limits # (in test file test/system/200-pod.bats, line 750) # `assert "$(< $memory_limit_file)" = "268435456" "Contents of $memory_limit_file"' failed not ok 378 [252] quadlet - basic # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/252-quadlet.bats, line 174) # `assert "$output" == "STARTED CONTAINER" "exact/full match when using the 'passthrough' driver"' failed not ok 427 [280] podman update - test all options # tags: distro-integration # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/280-update.bats, line 109) # `run_podman update "${opts[@]}" $cid' failed not ok 499 [505] No IPv4 # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/505-networking-pasta.bats, line 271) # `run_podman run --net=pasta:-6 $IMAGE ip -j -4 address show' failed not ok 506 [505] IPv6 default route # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/505-networking-pasta.bats, line 363) # `assert "${container_route}" = "${host_route}" \' failed openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_podman_testsuite@64bit fails in [bats-user-local_tap](https://openqa.opensuse.org/tests/4145118/modules/bats… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20240308](https://openqa.opensuse.org/tests/3999689) ## Expected result Last good: [20240307](https://openqa.opensuse.org/tests/3997809) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226112] New: Supersede kmozillahelper by xdg-desktop-portal integration
by bugzilla_noreply＠suse.com 10 Aug '24

10 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226112 Bug ID: 1226112 Summary: Supersede kmozillahelper by xdg-desktop-portal integration Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: fabian(a)ritter-vogt.de QA Contact: qa-bugs(a)suse.de CC: opensuse-kde-bugs(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- For some time now, Firefox (and Thunderbird I hope) can use xdg-desktop-portal APIs for DE integration. We should try to migrate away from kmozillahelper in favor of using the builtin xdg-desktop-portal integration. For that, we need to make sure that on Plasma it uses xdg-desktop-portal instead of GTK file dialogs out of the box. Currently this needs to be done manually by setting widget.use-xdg-desktop-portal.file-picker=1 widget.use-xdg-desktop-portal.mime-handler=1 I'm not sure about widget.use-xdg-desktop-portal.open-uri. Can we get FF and TB configured such that it uses xdg-desktop-portal by default if it detects a Plasma session? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227999] New: python reproducible builds
by bugzilla_noreply＠suse.com 10 Aug '24

10 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227999 Bug ID: 1227999 Summary: python reproducible builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- our python311 (and other versions) interpreter suffer from several issues that prevent reproducing the binary rpms: 1. PGO = profile guided optimization causes non-deterministic machine code, because the training run is not 100% deterministic. This should honor the %do_profiling macro instead of/in addition to its own profileopt. 2. python311:doc have 3 issues: 2.1: merged: https://github.com/python/cpython/pull/121872 date 2.2: https://github.com/python/cpython/pull/121883 parallelism/race 2.3: https://github.com/sphinx-doc/sphinxcontrib-devhelp/pull/13 gzip mtime I'd like to see variations of these backported to all our Factory python interpreter versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1228185] New: sealert hit an error (call python problem?)
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228185 Bug ID: 1228185 Summary: sealert hit an error (call python problem?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm on tumbleweed with KDE and I have activated SELinux in permissive mode. The sealert popup gives an error : Oops, sealert hit an error! "Traceback (most recent call last): File "/usr/bin/sealert", line 683, in <module> run_as_dbus_service(username) File "/usr/bin/sealert", line 128, in run_as_dbus_service app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/sealert", line 350, in __init__ from setroubleshoot.browser import BrowserApplet File "/usr/lib/python3.11/site-packages/setroubleshoot/browser.py", line 67, in <module> import report File "/usr/lib64/python3.11/site-packages/PIL/report.py", line 3, in <module> from .features import pilinfo ImportError: attempted relative import with no known parent package " Is this a bug or a bad configuration? Many thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226142] New: u-boot enabled with tpm2 and soft spi
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226142 Bug ID: 1226142 Summary: u-boot enabled with tpm2 and soft spi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: jonaski(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875402 --> https://bugzilla.suse.com/attachment.cgi?id=875402&action=edit tpm2 spoftspi patch To get the TPM2 PCR values filled in I need to enable some extra configuration options for u-boot: * Device Drivers * (y) SPI Support * (y) Enable Driver Model for SPI drivers (`DM_SPI`) * (y) Soft SPI driver (`SOFT_SPI`) * Library routines * Security Support * (y) Trusted Platform Module (TPM) support (`TPM`) * Device Drivers * TPM support * (y) TPMv2.x support (`TPM_V2`) * (y) Enable support for TPMv2.x SPI chips (`TPM2_TIS_SPI`) * Command line interface * Security commands * (y) Enable the 'tpm' command (`CMD_TPM`) https://github.com/joholl/rpi4-uboot-tpm/blob/ad31306ce2f2d52f0572385bfc8ba… Is this possible to enable for the u-boot-rpi4 package? I've attached a patch with the changes from "make rpi_4_defconfig". -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222505] New: ckermit: cannot create lock file in /var/lock
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226807] New: minicom cannot run as user due to /run/lock permissions
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226807 Bug ID: 1226807 Summary: minicom cannot run as user due to /run/lock permissions 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: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When running minicom as a user in the dialout group I now get an error message that it cannot create a lock file. This worked in 15.5. Minicom is attempting to create the lockfile in /run/lock but only root has write access to this directory. Minicom uses lockdev which requires access to /var/lock. One way to fix this is to build minicom without lockdev. Lockdev is fundamentally broken because it requires write access to /run/lock, which is a security nightmare. When minicom is built without lockdev the location of the lockfiles can be specified to be someplace other than /var/lock. See https://systemd-devel.freedesktop.narkive.com/vCJLfMo2/headsup-var-lock-and… for a discussion. As an interim solution, I added an ACL to allow the dialout group to write to /run/lock, though this is far from ideal. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 09 Aug '24

09 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226541] New: Cockpit Packagekit does not appear in UI
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226541 Bug ID: 1226541 Summary: Cockpit Packagekit does not appear in UI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: cody.henderson(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing cockpit-packagekit the Software Updates tab did not appear. After doing a little digging it appears to be caused by an incorrect path listed in the manifest for the plugin. In /usr/share/cockpit/packagekit/manifest.json it has the following conditions: > "conditions": [ > {"path-exists": "/lib/systemd/system/packagekit.service"}, > {"path-not-exists": "/sysroot/ostree"} > ], The path /lib/systemd/system/packagekit.service does not exist with packagekit installed on the system. Instead it is located at /usr/lib/systemd/system/packagekit.service. If I change that line to the corrected path the Software Update tab then appears and seems to function just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2