July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213154] New: openSUSE/mariadb container stops with non-zero exit code when calling podman stop
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1213154 Bug ID: 1213154 Summary: openSUSE/mariadb container stops with non-zero exit code when calling podman stop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: khanich.opensource(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Steps to reproduce: 1. Start a container, for testing: podman run --detach --env MYSQL_ROOT_PASSWORD=p --name mariadb registry.opensuse.org/opensuse/mariadb:latest 2. wait until initialized 3. Stop the container: podman stop mariadb 4. Check the exit code: podman ls -a; Exited (143) 5. Look at logs: podman logs mariadb example output: -------------------------------------------------------------------------------- Session terminated, killing shell...2023-07-08 22:55:08 0 [Note] mysqld (initiated by: unknown): Normal shutdown 2023-07-08 22:55:08 0 [Note] InnoDB: FTS optimize thread exiting. 2023-07-08 22:55:08 0 [Note] InnoDB: Starting shutdown... 2023-07-08 22:55:08 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2023-07-08 22:55:08 0 [Note] InnoDB: Buffer pool(s) dump completed at 230708 22:55:08 2023-07-08 22:55:08 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2023-07-08 22:55:08 0 [Note] InnoDB: Shutdown completed; log sequence number 46456; transaction id 15 2023-07-08 22:55:08 0 [Note] mysqld: Shutdown complete ...killed. -------------------------------------------------------------------------------- This causes trouble when using the image with a systemd service unit since systemd is going to interpret this as a failed unit. The official image from Docker Hub does not experience this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218579] New: cargo_vendor serice fail
by bugzilla_noreply＠suse.com 11 Aug '24

11 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1218579 Bug ID: 1218579 Summary: cargo_vendor serice fail Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 871679 --> https://bugzilla.suse.com/attachment.cgi?id=871679&action=edit local cargo_vendor cargo_vendor work in local `osc service ra`, but failed in OBS. error: > Files could not be expanded: service error: 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) less info > service daemon error: > 400 remote error: cargo_vendor service parameter "srctar" is not defined (http://obs-gateway:5153/sourceupdate/home:Werwolf2517/Alfis?timeout=7200) i try src, srctar, srcdir. in my local machine all works, but in OBS always i get this error For a long time I thought I was doing something wrong, but now I'm sure it's not me. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1228200] New: postfix does not start after installation
by bugzilla_noreply＠suse.com 11 Aug '24

11 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228200 Bug ID: 1228200 Summary: postfix does not start after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 876194 --> https://bugzilla.suse.com/attachment.cgi?id=876194&action=edit output of command "journalctl -u postfix" When installing packet cronie, also postfix is installed and it is activated immediately. However it does not start. journalctl -u postfix gives (see attachment). The main reason mentioned is: fatal: bad string length 0 < 1: myhostname = I do have a value in /etc/hostname Only after giving the command: postconf "myhostname = $(cat /etc/hostname)" postfix starts OK, beside the warnings: postconf: warning: /etc/postfix/main.cf: support for parameter "smtpd_use_tls" will be removed; instead, specify "smtpd_tls_security_level" postconf: warning: /etc/postfix/main.cf: support for parameter "smtp_enforce_tls" will be removed; instead, specify "smtp_tls_security_level" postconf: warning: /etc/postfix/main.cf: support for parameter "smtpd_enforce_tls" will be removed; instead, specify "smtpd_tls_security_level" postconf: warning: /etc/postfix/main.cf: support for parameter "smtp_use_tls" will be removed; instead, specify "smtp_tls_security_level" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227961] New: Problem with kf6-kparts-6.4.0-1.1.x86_64.rpm & konqueror
by bugzilla_noreply＠suse.com 11 Aug '24

11 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227961 Bug ID: 1227961 Summary: Problem with kf6-kparts-6.4.0-1.1.x86_64.rpm & konqueror Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)btinternet.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The update of 'kparts' to KDE Frameworks 6.4.0 (file version ' kf6-kparts-6.4.0-1.1.x86_64.rpm') has given an issue with the konqueror web browsher . Whenever konqueror is used and a website chosen the view mode defaults to 'embedded Advanced Test Editor' (rather than 'webengine') is used and html code is shown. To temporary resolve, the konqueror setting can be changed on a webpage-by-webpage basis or (as I have done) switch kf6-kparts from KDE Frameworks 6.3.0. Using the latest Tumbleweed snapshop 15072024 Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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 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 1225992] New: Package ipmitool does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 08 Aug '24

08 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1225992 Bug ID: 1225992 Summary: Package ipmitool does not build with gcc14 because of new errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- GCC 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, package ipmitool fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc The (first) error (that halts the build) is: [ 15s] ipmi_fru.c: In function 'fru_area_print_multirec': [ 15s] ipmi_fru.c:1556:41: error: initialization of 'struct fru_multirec_mgmt *' from incompatible pointer type 'struct fru_multirect_mgmt *' [-Wincompatible-pointer-types] [ 15s] 1556 | (struct fru_multirect_mgmt *) -- You are receiving this mail because: You are on the CC list for the bug.

1 3