September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215556] New: [Build 20230920] gnome-control-center: Add User button not showing
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215556 Bug ID: 1215556 Summary: [Build 20230920] gnome-control-center: Add User button not showing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3592012/modules/chan ge_password/steps/15 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Test runs g-c-c, unlocks the interface, but we still do not see the 'Add User' button. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-gnome@64bit fails in [change_password](https://openqa.opensuse.org/tests/3592012/modules/change_p… ## Test suite description ## Reproducible Fails since (at least) Build [20230920](https://openqa.opensuse.org/tests/3591088) ## Expected result Last good: [20230917](https://openqa.opensuse.org/tests/3589533) (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 1

[Bug 1214834] New: [Build 20230830] tvm failed to rebuild against libSpriv 2023.4
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214834 Bug ID: 1214834 Summary: [Build 20230830] tvm failed to rebuild against libSpriv 2023.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3538969/modules/tvm/ steps/18 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenStack Assignee: cloud-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation https://build.opensuse.org/package/live_build_log/openSUSE:Factory/tvm/stan… [ 1209s] + /usr/bin/python3.9 setup.py build '--executable=/usr/bin/python3.9 -s' [ 1211s] [ 1211s] Error compiling Cython file: [ 1211s] ------------------------------------------------------------ [ 1211s] ... [ 1211s] if self.c_is_view != 0: [ 1211s] raise ValueError("to_dlpack do not work with memory views") [ 1211s] with nogil: [ 1211s] c_api_ret_code = TVMArrayToDLPack(self.chandle, &dltensor) [ 1211s] CHECK_CALL(c_api_ret_code) [ 1211s] return pycapsule.PyCapsule_New(dltensor, _c_str_dltensor, _c_dlpack_deleter) [ 1211s] ^ [ 1211s] ------------------------------------------------------------ [ 1211s] [ 1211s] tvm/_ffi/_cython/./ndarray.pxi:116:66: Cannot assign type 'void (object) except *' to 'PyCapsule_Destructor' [ 1211s] Compiling tvm/_ffi/_cython/core.pyx because it changed. [ 1211s] [1/1] Cythonizing tvm/_ffi/_cython/core.pyx [ 1211s] Traceback (most recent call last): [ 1211s] File "/home/abuild/rpmbuild/BUILD/tvm-0.11.0/python/setup.py", line 238, in <module> [ 1211s] ext_modules=config_cython(), [ 1211s] File "/home/abuild/rpmbuild/BUILD/tvm-0.11.0/python/setup.py", line 154, in config_cython [ 1211s] return cythonize(ret, compiler_directives={"language_level": 3}) [ 1211s] File "/usr/lib64/python3.9/site-packages/Cython/Build/Dependencies.py", line 1134, in cythonize [ 1211s] cythonize_one(*args) [ 1211s] File "/usr/lib64/python3.9/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one [ 1211s] raise CompileError(None, pyx_file) [ 1211s] Cython.Compiler.Errors.CompileError: tvm/_ffi/_cython/core.pyx [ 1211s] error: Bad exit status from /var/tmp/rpm-tmp.rVxERl (%build) [ 1211s] [ 1211s] RPM build errors: openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_ai_ml@64bit fails in [tvm](https://openqa.opensuse.org/tests/3538969/modules/tvm/steps/18) ## Test suite description Test AI/ML software ## Reproducible Fails since (at least) Build [20230830](https://openqa.opensuse.org/tests/3538569) ## Expected result Last good: [20230828](https://openqa.opensuse.org/tests/3533967) (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 1

[Bug 1215078] New: debhelper: Initialization of state variables in list context currently forbidden
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215078 Bug ID: 1215078 Summary: debhelper: Initialization of state variables in list context currently forbidden 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: Development Assignee: screening-team-bugs(a)suse.de Reporter: t.lee.davidson(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Executing `dh`, and other commands, from the debhelper package produces the following, or similar, error: Initialization of state variables in list context currently forbidden at /usr/lib/perl5/vendor_perl/5.26.1/Debian/Debhelper/Dh_Lib.pm line 2100, near ");" BEGIN not safe after errors--compilation aborted at /usr/lib/perl5/vendor_perl/5.26.1/Debian/Debhelper/Dh_Lib.pm line 2885. Compilation failed in require at /usr/bin/dh line 15. BEGIN failed--compilation aborted at /usr/bin/dh line 15. https://bugzilla.opensuse.org/show_bug.cgi?id=1198346 indirectly touches on this issue but does not identify the root cause, ie. an issue with the debhelper package. As far as I know, Perl >= 5.28 is required to be able to initialize state variables in list context. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214409] New: bluetooth file transfer not working
by bugzilla_noreply＠suse.com 12 Oct '23

12 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214409 Bug ID: 1214409 Summary: bluetooth file transfer not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Leap 15.4 I'm able to transfer files via bluetooth from my android phone to the plasma desktop. In Leap 15.5 it is not possible. After some investigation I found two different causes for such failure. 1) In order to transfer files to the desktop, the obexd daemon must be running. In Leap 15.4 such program was part of the bluez rpm. In Leap 15.5 obexd is part of the bluez-obexd rpm but such package is not installed during the plasma installation. I guess the fix should be that the package bluedevil5 should require bluez-obexd. This is a plasma bug I think. 2) Once bluez-obexd is installed, the file transfer via bluetooth still doesn't work. And that's because the obexd daemon is not running. It is supposed to be started by systemd but it is not. After I run manually /usr/lib/bluetooth/obexd then the file transfer via bluetooth to the plasma desktop works. This is either a bluez bug (incorrect systemd configuration) or a systemd bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1214540] New: NFS mount doesn't succeed any more
by bugzilla_noreply＠suse.com 11 Oct '23

11 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214540 Bug ID: 1214540 Summary: NFS mount doesn't succeed any more Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: lopa(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After one of the last Tumbleweed updates, the nfs kernel server doesn't work correctly any more. An nfs mount command from another machine doesn't return, it hangs forever and nothing is mounted. Old working configuration ------------------------- nfs-client-2.6.2-38.1 nfs-kernel-server-2.6.2-38.1 Syslog: Aug 23 17:08:36 orion rpc.mountd[19233]: v4.0 client attached: 0x131b2e4a64e620dc from "192.168.1.21:991" The mount command on the client machine returns immediately and the remote directory is mounted correctly. New non working configuration ----------------------------- nfs-client-2.6.3-39.4 nfs-kernel-server-2.6.3-39.4 Syslog: Aug 23 16:47:37 orion rpc.mountd[18307]: auth_unix_ip: inbuf 'nfsd 192.168.1.21' Aug 23 16:47:37 orion rpc.mountd[18307]: successful authentication for IP 192.168.1.21 as 192.168.1.0/24 Aug 23 16:47:37 orion rpc.mountd[18307]: auth_unix_ip: client 0x5619032d0770 '192.168.1.0/24' Aug 23 16:47:37 orion rpc.mountd[18307]: v4.0 client attached: 0x131b2e4764e61c00 from "192.168.1.21:717" Aug 23 16:47:37 orion rpc.mountd[18307]: nfsd_fh: inbuf '192.168.1.0/24 1 \x00000000' Aug 23 16:47:37 orion rpc.mountd[18307]: nfsd_fh: found 0x5619032d2410 path / The mount command on the client machine doesn't return and nothing is mounted. After killing the mount command, this line appears in the servers syslog: Aug 23 16:53:55 orion rpc.mountd[18307]: v4.0 client detached: 0x131b2e4764e61c00 from "192.168.1.21:717" There's no difference, whether NFSv4 or NFSv3 is used and there's no message in the syslog of the client machine. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212816] New: salt-minions from some machines do not return "Minion did not return. [No response]" since salt-3006.0-150400.8.34.2
by bugzilla_noreply＠suse.com 11 Oct '23

11 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1212816 Bug ID: 1212816 Summary: salt-minions from some machines do not return "Minion did not return. [No response]" since salt-3006.0-150400.8.34.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ## Observation We observed that in our salt managed infrastructure the salt-minion from some machines do not return any result reproducibly since the upgrade salt-3004-150400.8.25.1->salt-3006.0-150400.8.34.2 salt-minions from some machines do not return "Minion did not return. [No response]" since salt-3006.0-150400.8.34.2. In our infrastructure we currently have 31 machines controlled by salt. Out of those 31 machines reproducibly 6 machines do not return with a response after some time regardless of the salt command used. The other 25 machines are not affected, all have the most up-to-date salt package version installed and an up-to-date Leap 15.4. We run machines with architectures x86_64, aarch64, ppc64le and have affected as well as non-affected machines of each architecture so this can not be an architecture-specific issue. The issue is visible when executing any salt command like `test.ping` as well as in `salt-run manage.down` showing the unresponsive salt minion nodes. ## Steps to reproduce In our infrastructure we reproduce the problem with: ``` for i in {1..7200}; do echo "### Run $i -- $(date -Is)" && salt --no-color \* test.ping ; df -i / ; salt-run jobs.list_jobs | wc -l && salt --no-color \* saltutil.kill_all_jobs && sleep 60 && rm -rf /var/cache/salt/master/jobs/*; done | tee -a log_salt_test_ping_poo131249_$(date -Is).log ``` showing the problem for the affected machines after roughly one hour. The command can be simplified by removing counting, logging, cleanup: ``` while :; do salt \* test.ping; done ``` Note that without sleeping between each loop iteration this eventually exhausted free inodes on our salt master node. ## Problem We could narrow down the problem to the salt packages upgrade salt-3004-150400.8.25.1 to salt-3006.0-150400.8.34.2 . Full changelog of the package for the above mentioned upgrade step: ``` * Mon Jun 19 2023 pablo.suarezhernandez(a)suse.com - Make master_tops compatible with Salt 3000 and older minions (bsc#1212516) (bsc#1212517) - Added: * make-master_tops-compatible-with-salt-3000-and-older.patch * Mon May 29 2023 yeray.gutierrez(a)suse.com - Avoid failures due transactional_update module not available in Salt 3006.0 (bsc#1211754) - Added: * define-__virtualname__-for-transactional_update-modu.patch * Wed May 24 2023 pablo.suarezhernandez(a)suse.com - Avoid conflicts with Salt dependencies versions (bsc#1211612) - Added: * avoid-conflicts-with-dependencies-versions-bsc-12116.patch * Fri May 05 2023 alexander.graul(a)suse.com - Update to Salt release version 3006.0 (jsc#PED-4360) * See release notes: https://docs.saltproject.io/en/latest/topics/releases/3006.0.html - Add missing patch after rebase to fix collections Mapping issues - Add python3-looseversion as new dependency for salt - Add python3-packaging as new dependency for salt - Allow entrypoint compatibility for "importlib-metadata>=5.0.0" (bsc#1207071) - Create new salt-tests subpackage containing Salt tests - Drop conflictive patch dicarded from upstream - Fix SLS rendering error when Jinja macros are used - Fix version detection and avoid building and testing failures - Prevent deadlocks in salt-ssh executions - Require python3-jmespath runtime dependency (bsc#1209233) - Added: * 3005.1-implement-zypper-removeptf-573.patch * control-the-collection-of-lvm-grains-via-config.patch * fix-version-detection-and-avoid-building-and-testing.patch * make-sure-the-file-client-is-destroyed-upon-used.patch * skip-package-names-without-colon-bsc-1208691-578.patch * use-rlock-to-avoid-deadlocks-in-salt-ssh.patch - Modified: * activate-all-beacons-sources-config-pillar-grains.patch * add-custom-suse-capabilities-as-grains.patch * add-environment-variable-to-know-if-yum-is-invoked-f.patch * add-migrated-state-and-gpg-key-management-functions-.patch * add-publish_batch-to-clearfuncs-exposed-methods.patch * add-salt-ssh-support-with-venv-salt-minion-3004-493.patch * add-sleep-on-exception-handling-on-minion-connection.patch * add-standalone-configuration-file-for-enabling-packa.patch * add-support-for-gpgautoimport-539.patch * allow-vendor-change-option-with-zypper.patch * async-batch-implementation.patch * avoid-excessive-syslogging-by-watchdog-cronjob-58.patch * bsc-1176024-fix-file-directory-user-and-group-owners.patch * change-the-delimeters-to-prevent-possible-tracebacks.patch * debian-info_installed-compatibility-50453.patch * dnfnotify-pkgset-plugin-implementation-3002.2-450.patch * do-not-load-pip-state-if-there-is-no-3rd-party-depen.patch * don-t-use-shell-sbin-nologin-in-requisites.patch * drop-serial-from-event.unpack-in-cli.batch_async.patch * early-feature-support-config.patch * enable-passing-a-unix_socket-for-mysql-returners-bsc.patch * enhance-openscap-module-add-xccdf_eval-call-386.patch * fix-bsc-1065792.patch * fix-for-suse-expanded-support-detection.patch * fix-issue-2068-test.patch * fix-missing-minion-returns-in-batch-mode-360.patch * fix-ownership-of-salt-thin-directory-when-using-the-.patch * fix-regression-with-depending-client.ssh-on-psutil-b.patch * fix-salt-ssh-opts-poisoning-bsc-1197637-3004-501.patch * fix-salt.utils.stringutils.to_str-calls-to-make-it-w.patch * fix-the-regression-for-yumnotify-plugin-456.patch * fix-traceback.print_exc-calls-for-test_pip_state-432.patch * fixes-for-python-3.10-502.patch * include-aliases-in-the-fqdns-grains.patch * info_installed-works-without-status-attr-now.patch * let-salt-ssh-use-platform-python-binary-in-rhel8-191.patch * make-aptpkg.list_repos-compatible-on-enabled-disable.patch * make-setup.py-script-to-not-require-setuptools-9.1.patch * pass-the-context-to-pillar-ext-modules.patch * prevent-affection-of-ssh.opts-with-lazyloader-bsc-11.patch * prevent-pkg-plugins-errors-on-missing-cookie-path-bs.patch * prevent-shell-injection-via-pre_flight_script_args-4.patch * read-repo-info-without-using-interpolation-bsc-11356.patch * restore-default-behaviour-of-pkg-list-return.patch * return-the-expected-powerpc-os-arch-bsc-1117995.patch * revert-fixing-a-use-case-when-multiple-inotify-beaco.patch * run-salt-api-as-user-salt-bsc-1064520.patch * run-salt-master-as-dedicated-salt-user.patch * save-log-to-logfile-with-docker.build.patch * switch-firewalld-state-to-use-change_interface.patch * temporary-fix-extend-the-whitelist-of-allowed-comman.patch * update-target-fix-for-salt-ssh-to-process-targets-li.patch * use-adler32-algorithm-to-compute-string-checksums.patch * use-salt-bundle-in-dockermod.patch * x509-fixes-111.patch * zypperpkg-ignore-retcode-104-for-search-bsc-1176697-.patch - Removed: * 3003.3-do-not-consider-skipped-targets-as-failed-for.patch * 3003.3-postgresql-json-support-in-pillar-423.patch * add-amazon-ec2-detection-for-virtual-grains-bsc-1195.patch * add-missing-ansible-module-functions-to-whitelist-in.patch * add-rpm_vercmp-python-library-for-version-comparison.patch * add-support-for-name-pkgs-and-diff_attr-parameters-t.patch * adds-explicit-type-cast-for-port.patch * align-amazon-ec2-nitro-grains-with-upstream-pr-bsc-1.patch * backport-syndic-auth-fixes.patch * batch.py-avoid-exception-when-minion-does-not-respon.patch * check-if-dpkgnotify-is-executable-bsc-1186674-376.patch * clarify-pkg.installed-pkg_verify-documentation.patch * detect-module.run-syntax.patch * do-not-crash-when-unexpected-cmd-output-at-listing-p.patch * enhance-logging-when-inotify-beacon-is-missing-pyino.patch * fix-62092-catch-zmq.error.zmqerror-to-set-hwm-for-zm.patch * fix-crash-when-calling-manage.not_alive-runners.patch * fixes-pkg.version_cmp-on-openeuler-systems-and-a-few.patch * fix-exception-in-yumpkg.remove-for-not-installed-pac.patch * fix-for-cve-2022-22967-bsc-1200566.patch * fix-inspector-module-export-function-bsc-1097531-481.patch * fix-ip6_interface-grain-to-not-leak-secondary-ipv4-a.patch * fix-issues-with-salt-ssh-s-extra-filerefs.patch * fix-jinja2-contextfuntion-base-on-version-bsc-119874.patch * fix-multiple-security-issues-bsc-1197417.patch * fix-salt-call-event.send-call-with-grains-and-pillar.patch * fix-salt.states.file.managed-for-follow_symlinks-tru.patch * fix-state.apply-in-test-mode-with-file-state-module-.patch * fix-test_ipc-unit-tests.patch * fix-the-regression-in-schedule-module-releasded-in-3.patch * fix-wrong-test_mod_del_repo_multiline_values-test-af.patch * fixes-56144-to-enable-hotadd-profile-support.patch * fopen-workaround-bad-buffering-for-binary-mode-563.patch * force-zyppnotify-to-prefer-packages.db-than-packages.patch * ignore-erros-on-reading-license-files-with-dpkg_lowp.patch * ignore-extend-declarations-from-excluded-sls-files.patch * ignore-non-utf8-characters-while-reading-files-with-.patch * implementation-of-held-unheld-functions-for-state-pk.patch * implementation-of-suse_ip-execution-module-bsc-10999.patch * improvements-on-ansiblegate-module-354.patch * include-stdout-in-error-message-for-zypperpkg-559.patch * make-pass-renderer-configurable-other-fixes-532.patch * make-sure-saltcacheloader-use-correct-fileclient-519.patch * mock-ip_addrs-in-utils-minions.py-unit-test-443.patch * normalize-package-names-once-with-pkg.installed-remo.patch * notify-beacon-for-debian-ubuntu-systems-347.patch * refactor-and-improvements-for-transactional-updates-.patch * retry-if-rpm-lock-is-temporarily-unavailable-547.patch * set-default-target-for-pip-from-venv_pip_target-envi.patch * state.apply-don-t-check-for-cached-pillar-errors.patch * state.orchestrate_single-does-not-pass-pillar-none-4.patch * support-transactional-systems-microos.patch * wipe-notify_socket-from-env-in-cmdmod-bsc-1193357-30.patch ``` ## Workaround Restarting the salt-minion systemd service on affected machines mitigates the problem for one to multiple hours until the minion becomes unresponsive again. `systemctl restart salt-minion`. For now we have downgraded the affected machines except for one which we keep as purposely broken machine which we can offer with some limitations applied to anyone interested in investigating further. ## Further details Please find our internal investigation issue on https://progress.opensuse.org/issues/131249 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215460] New: urxvt and GNU screen don't work well together (on recent Tumbleweed)
by bugzilla_noreply＠suse.com 11 Oct '23

11 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215460 Bug ID: 1215460 Summary: urxvt and GNU screen don't work well together (on recent Tumbleweed) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869579 --> https://bugzilla.suse.com/attachment.cgi?id=869579&action=edit Screen shot of yast in screen in urxvt After upgrading TW to version 20230828 (from some July version), urxvt (from rxvt-unicode) does not display things correctly in GNU screen. To reproduce: 1. open urxvt terminal and in it... 2. run screen and in it... 3. run /for example /sbin/yast the result is garbled display (see attachments). But that is not the only case, even GCC error and warning messages are messed up and sprinkled with "â" characters all over the place. My locale is: LANG=C LC_CTYPE=en_US.UTF-8 LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL= screen sets TERM to "screen-256color" urxvt itself sets TERM to rxvt-unicode xterm seems to work OK (with the limited capabilities it has). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214191] New: cannot disable IPv6 persistent
by bugzilla_noreply＠suse.com 11 Oct '23

11 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214191 Bug ID: 1214191 Summary: cannot disable IPv6 persistent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868766 --> https://bugzilla.suse.com/attachment.cgi?id=868766&action=edit yast logs check at first: rpi4mb:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host proto kernel_lo valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether dc:a6:32:61:23:d8 brd ff:ff:ff:ff:ff:ff inet 192.168.8.148/24 brd 192.168.8.255 scope global dynamic noprefixroute end0 valid_lft 42767sec preferred_lft 42767sec inet6 ddc2:9f5e:9e08::8823/128 scope global dynamic noprefixroute valid_lft 42771sec preferred_lft 42771sec inet6 ddc2:9f5e:9e08:0:b68c:4f73:974b:22b9/64 scope global temporary dynamic valid_lft 4556sec preferred_lft 4556sec inet6 ddc2:9f5e:9e08:0:af7a:2fda:16bd:2985/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 4556sec preferred_lft 4556sec inet6 fe80::a365:bf94:1892:25c5/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether fe:18:92:a6:4d:30 brd ff:ff:ff:ff:ff:ff permaddr dc:a6:32:61:23:da rpi4mb:~ # ping heise.de PING heise.de(redirector.heise.de (2a02:2e0:3fe:1001:302::)) 56 data bytes ^C --- heise.de ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1012ms In the file /etc/sysctl.conf add the following lines: net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 rpi4mb:~ # sysctl -p net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 rpi4mb:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether dc:a6:32:61:23:d8 brd ff:ff:ff:ff:ff:ff inet 192.168.8.148/24 brd 192.168.8.255 scope global dynamic noprefixroute end0 valid_lft 42676sec preferred_lft 42676sec 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether fe:18:92:a6:4d:30 brd ff:ff:ff:ff:ff:ff permaddr dc:a6:32:61:23:da -- so far it looks good, ipv6 got disabled, but after reboot ipv6 got enabled again. it won't change even I disable ipv6 for network device via yast network. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214933] New: obs-service-go_modules: not support go1.N.0 version format
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214933 Bug ID: 1214933 Summary: obs-service-go_modules: not support go1.N.0 version format Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: shenghuang147(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- According to https://tip.golang.org/doc/go1.21: Go 1.21 introduces a small change to the numbering of releases. In the past, we used Go 1.N to refer to both the overall Go language version and release family as well as the first release in that family. Starting in Go 1.21, the first release is now Go 1.N.0. Today we are releasing both the Go 1.21 language and its initial implementation, the Go 1.21.0 release. These notes refer to “Go 1.21”; tools like go version will report “go1. 21.0” (until you upgrade to Go 1.21.1). See “Go versions” in the “Go Toolchains” documentation for details about the new version numbering. This means that obs-service-go_modules can not correctly identify or process the application source code of Go 1.N.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215709] New: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215709 Bug ID: 1215709 Summary: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dirk.datzert(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869748 --> https://bugzilla.suse.com/attachment.cgi?id=869748&action=edit Hardcopy of the segfault messages After Upgrading to MicroOS-20230921 I see such segfaults pasted in the hardcopy on serveral VM Machines. I can revert to a snapshot from 20230918 and disable transactional-update.timer. Has this segfault seen somewhere else ? I'm running different k3s-version-branches on top of MicroOS and reverted also this to an older release. -- You are receiving this mail because: You are on the CC list for the bug.

1 3