June 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212841] New: Lots of objtool warnings when building the nvidia driver
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1212841 Bug ID: 1212841 Summary: Lots of objtool warnings when building the nvidia driver 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- # rpm -qv nvidia-driver-G06-kmp-default nvidia-driver-G06-kmp-default-535.54.03_k6.3.7_1-10.1.x86_64 # zgrep -c objtool zypper.log-20230627.xz 213230 extracts: [rpm> LD [M] /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000675kms+0x46: 'naked' return found in RETHUNK build [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000676kms+0x46: 'naked' return found in RETHUNK build [cut] [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv040720rm+0xb9: return with modified stack frame [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv013581rm+0xd9: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-64 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv034058rm+0x83: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-56 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv024689rm+0xb: missing int3 after ret [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv043791rm+0x4: missing int3 after ret [cut] then it finishes building and prints a couple last warnings such as: [rpm> Skipping BTF generation for /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-peermem.ko due to unavailability of vmlinux -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1212897] New: Produce separate Aeon installation media
by bugzilla_noreply＠suse.com 18 May '24

18 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1212897 Bug ID: 1212897 Summary: Produce separate Aeon installation media Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Aeon requires install media separate from MicroOS -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212839] New: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212839 Bug ID: 1212839 Summary: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP test cve-2021-22555 setsockopt08.c fails with ENOENT [1], but it expects EINVAL on mostly all archs on Tumbleweed (all but s390x, i.e. aarch64, ppc64le, x86_64 and x86_64 compiled as 32bit). The test has been failing for very long time (our history goes to 6.3.2 20230517, but it's failing on my VM with 6.2.12-1-default 20230502). When test run more times (200x with -i200 [3]) it fails only on first time, the rest happily have EINVAL. And indeed, when verifying manually on VM, only first run fails dmesg on affected archs contains: [ 1514.789118][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.792200][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.795209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.798209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.801190][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.804092][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.807159][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.810210][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.813257][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.816227][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 But when running manually I see on first (failing): [ 208.455124] bpfilter: Loaded bpfilter_umh pid 1223 [ 208.456650] Started bpfilter (this is also in openQA jobs, but earlier, triggered by setsockopt03.c, which runs earlier). And x_tables run is reported on later (successful run): [ 221.292549] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 => Maybe there is a problem with loading x_tables on these 3 archs Interestingly x_tables is loaded on all archs, including s390x (which does not fail) and the same dmesg [4] FYI we stop and disable firewall in openQA install_ltp job (this qcow is then used for LTP tests) [5]: systemctl --no-pager disable firewalld Removed "/etc/systemd/system/multi-user.target.wants/firewalld.service". Removed "/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service". systemctl --no-pager stop firewalld [1] https://openqa.opensuse.org/tests/3390125#step/setsockopt08/7 [2] https://github.com/linux-test-project/ltp/blob/a564d3e1672e9cd7ac302d597ffa… [3] https://openqa.opensuse.org/tests/3391862#step/cve-2021-22555/7 [4] https://openqa.opensuse.org/tests/3380876/file/shutdown_ltp-dmesg.txt [5] https://openqa.opensuse.org/tests/3391842/file/serial_terminal.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[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 1212874] New: External Monitor on USB-C Docking station AMD Graphics
by bugzilla_noreply＠suse.com 13 Sep '23

13 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1212874 Bug ID: 1212874 Summary: External Monitor on USB-C Docking station AMD Graphics 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: j.g.joseph4884(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just reinstalled OpenSuse Tumbleweed to see if my install was impacting the external monitor connection on my docking station - Still occurs; Hardware * Laptop - Thinkoad E595 | AMD Ryzen 5 * Docking Station - Lenovo 40AS0090US * External Monitors - 1 High Refresh Rate 1080p (Displayport) & 1 UltraWide 1080p (HDMI) On Windows - The Laptop displays on all monitors with no issues at the highest refresh rates for both monitors Been having issues since the start of Kernel 6.0 where I cannot use both my external monitors with my laptop at 1080p. When I keep the laptop plugged into the docking station and let the device sleep, it crashes before it can fully sleep with the cursor still slightly visible on a dark background. If I keep the laptop plugged into the docking station on startup, it crashes right when the loading circle starts to spin above the Tumbleweed logo. Let me know what commands I need to enter to output info to assist the kernel developers -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1212835] New: make modules_install fails with kmod-30-4.1
by bugzilla_noreply＠suse.com 11 Sep '23

11 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1212835 Bug ID: 1212835 Summary: make modules_install fails with kmod-30-4.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: msuchanek(a)suse.com Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the usrmerge patches, depmod now accesses $base/usr/lib/modules instead of $base/lib/modules. Unfortunately, scripts/depmod.sh in the kernel sources cannot cope with that and fails with a slightly confusing message: depmod: ERROR: could not open directory /srv/research/dynswiotlb-9p/usr/lib/modules/99.98.6.5.0-devel+: No such file or directory I can see how this is fixed for RPM builds (https://github.com/SUSE/kernel-source/commit/da84579e78f4c4efa5b3b910484fda…) but I can no longer run "make modules_install" from the expanded kernel tree. -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1212853] New: GRUB2 asking for passphrase twice again
by bugzilla_noreply＠suse.com 18 Aug '23

18 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212853 Bug ID: 1212853 Summary: GRUB2 asking for passphrase twice again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: eyadlorenzo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday I reinstalled my Tumbleweed system, with crypted root and crypted swap. I now get again asked twice for my passphrase. I could follow what described in https://en.opensuse.org/SDB:Encrypted_root_file_system#Avoiding_to_type_the…, but last time I installed Tumbleweed there was no need (see https://bugzilla.opensuse.org/show_bug.cgi?id=1206710) for details. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1212906] New: fanotify23 randomly fails on Tumbleweed when run more times
by bugzilla_noreply＠suse.com 14 Aug '23

14 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212906 Bug ID: 1212906 Summary: fanotify23 randomly fails on Tumbleweed when run more times Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jack(a)suse.com Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP fanotify23 test (test for FAN_MARK_EVICTABLE from 5.19) fails, when run more times. I tested it on all archs on the current Tumbleweed kernel [2], it fails everywhere. It also fails when tested on VM with older 6.2.8-1-default kernel (where it mostly fails, I guess the behavior is the same on all recent version): # /opt/ltp/testcases/bin/fanotify23 -i5 tst_device.c:97: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1094: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after drop_caches fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:193: TPASS: got event: mask=4 fanotify23.c:112: TPASS: FAN_MARK_ADD failed with EEXIST as expected when trying to downgrade to evictable mark fanotify23.c:75: TPASS: FAN_MARK_REMOVE failed with ENOENT as expected after empty mask fanotify23.c:156: TPASS: Got no events as expected fanotify23.c:81: TFAIL: FAN_MARK_REMOVE did not fail with ENOENT as expected after drop_caches: SUCCESS (0) fanotify23.c:175: TBROK: read(3,0x5598cbfafc54,24524) failed, returned -1: EAGAIN/EWOULDBLOCK (11) Summary: passed 27 failed 1 broken 1 skipped 0 warnings 0 dmesg: [ 371.377308][T29983] loop: module loaded [ 371.380510][T29982] loop0: detected capacity change from 0 to 614400 [ 371.441931][ C1] clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large: [ 371.443816][ C1] clocksource: 'kvm-clock' wd_nsec: 515886747 wd_now: 5749149153 wd_last: 572a54c2b8 mask: ffffffffffffffff [ 371.445730][ C1] clocksource: 'tsc' cs_nsec: 30542623402 cs_now: cff3ae7e60 cs_last: c057e04270 mask: ffffffffffffffff [ 371.447768][ C1] clocksource: Clocksource 'tsc' skewed 30026736655 ns (30026 ms) over watchdog 'kvm-clock' interval of 515886747 ns (515 ms) [ 371.449822][ C1] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 371.451068][ C1] tsc: Marking TSC unstable due to clocksource watchdog [ 371.499239][ C1] operation not supported error, dev loop0, sector 614272 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.501256][ C0] operation not supported error, dev loop0, sector 524 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.503893][ C1] operation not supported error, dev loop0, sector 16908 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.506135][ C0] operation not supported error, dev loop0, sector 32774 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.508716][ C1] operation not supported error, dev loop0, sector 49676 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.511513][ C0] operation not supported error, dev loop0, sector 65542 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.514038][ C0] operation not supported error, dev loop0, sector 82444 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.516522][ C1] operation not supported error, dev loop0, sector 98310 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.519263][ C0] operation not supported error, dev loop0, sector 115212 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.521950][ C1] operation not supported error, dev loop0, sector 131078 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 371.545611][T29982] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.548719][T29982] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.787570][T30005] fanotify23 (30005): drop_caches: 3 [ 371.804729][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.810253][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.812114][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.820273][T30005] fanotify23 (30005): drop_caches: 3 [ 371.828227][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.830160][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.831957][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.841016][T30005] fanotify23 (30005): drop_caches: 3 [ 371.862288][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.864165][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.866232][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.872592][T30005] fanotify23 (30005): drop_caches: 3 [ 371.890441][T30005] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. [ 371.892294][T30005] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem [ 371.894159][T30005] EXT4-fs (loop0): mounted filesystem f9e6e295-a78d-4551-aff2-ce1663458053 without journal. Quota mode: none. [ 371.900270][T30005] fanotify23 (30005): drop_caches: 3 [ 371.919626][T29982] EXT4-fs (loop0): unmounting filesystem f9e6e295-a78d-4551-aff2-ce1663458053. When running on Debian 6.3.0-1-amd64 test does not fail and dmesg does not contain clocksource and tsc, therefore I suspect it's something our kernel specific (our configuration specific? We don't have any fanotify related patch, only something old patches.suse/vfs-add-super_operations-get_inode_dev, which is IMHO unrelated). I can report it to linux-fsdevel ML if it's a general problem. [1] https://github.com/linux-test-project/ltp/blob/353f0e4203139f3fc02fa2beb67c… [2] https://openqa.opensuse.org/tests/overview?build=fanotify23-10x -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1212824] New: [Build 20230627] apptainer: Write failed because no space left on device
by bugzilla_noreply＠suse.com 10 Aug '23

10 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1212824 Bug ID: 1212824 Summary: [Build 20230627] apptainer: Write failed because no space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3390518/modules/appt ainer/steps/42 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 today, the hpc_apptainer test is failing with 'no space on device' df shows sufficient space left: Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 728M 0 728M 0% /dev/shm tmpfs 292M 4.9M 287M 2% /run /dev/vda2 28G 2.3G 26G 9% / tmpfs 728M 24K 728M 1% /tmp /dev/vda2 28G 2.3G 26G 9% /.snapshots /dev/vda2 28G 2.3G 26G 9% /home /dev/vda2 28G 2.3G 26G 9% /var /dev/vda2 28G 2.3G 26G 9% /boot/grub2/i386-pc /dev/vda2 28G 2.3G 26G 9% /boot/grub2/x86_64-efi /dev/vda2 28G 2.3G 26G 9% /usr/local /dev/vda2 28G 2.3G 26G 9% /opt /dev/vda2 28G 2.3G 26G 9% /root /dev/vda2 28G 2.3G 26G 9% /srv tmpfs 146M 0 146M 0% /run/user/0 openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_hpc_apptainer@64bit fails in [apptainer](https://openqa.opensuse.org/tests/3390518/modules/apptainer/step… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module ## Reproducible Fails since (at least) Build [20230627](https://openqa.opensuse.org/tests/3389026) ## Expected result Last good: [20230626](https://openqa.opensuse.org/tests/3383456) (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 3

[Bug 1212891] New: Win11 installation fails with process stopping in firware
by bugzilla_noreply＠suse.com 31 Jul '23

31 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212891 Bug ID: 1212891 Summary: Win11 installation fails with process stopping in firware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- when trying to install a recent(!) image of Win11 in KVM in a machine with either paththrough of TPM or virtualized TPM the process stalls in "firmware Tiano Core". There is no error message, the iso simply stalls when loading the Tiano Core firmware. I tried also to download another image, I checked the checksum. But still, even if selecting correctly the iso, no luck. Operating System: openSUSE Tumbleweed 20230628 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon Pro W5500 Product Name: X570 Phantom Gaming 4 Image hit by this is: Win11_22H2_Italian_x64v2.iso -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212866] New: AUDIT-1: gromox: gromox-snapshot running as root
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212866 Bug ID: 1212866 Summary: AUDIT-1: gromox: gromox-snapshot running as root Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE:Factory/gromox was recently updated with a change to one of its systemd services: > -RPM: gromox-2.9-1.2.x86_64.rpm on x86_64 > +RPM: gromox-2.10-1.1.x86_64.rpm on x86_64 > Package: gromox > Service path: /usr/lib/systemd/system/gromox-snapshot.service > -Runs as: gromox:gromox > +Runs as: root:root > Exec lines: > ExecStart=/usr/libexec/gromox/gromox-snapshot The last version of gromox-snapshot did not require root, so we should consider if this is necessary at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212811] New: MokManager wants to remove needed cert
by bugzilla_noreply＠suse.com 10 Jul '23

10 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212811 Bug ID: 1212811 Summary: MokManager wants to remove needed cert Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: I'm currently using a kernel from Kernel:/stable:/Backport/standard/ (as explained in bug 1212808 ). Yesterday, I decided to update that kernel (from 6.3.9-lp154.2.1.g0df701d to 6.4.0-lp154.2.1.gd68cda5). To do this: I enabled the repo I used Yast software management I told it to install the newer kernel and remove the older one I then disabled the repo once again On reboot, I got a MokManager blue screen wanting to remove the cert that had been added for the older kernel. This seems a mistake, since it is still needed for the newer kernel. As best I can tell, Yast first removed the older kernel and that generated a request to remove the cert. It then installed the newer kernel, but because the cert was already loaded it did not generate a request to add the cert. (When I next update this kernel, I'll make sure to install the new kernel first, and then remove the old kernel afterwards to avoid this issue). Yes, I could have left it to the purge-kernels service to remove the old. But that would have instead removed the standard Leap 15.5 kernel, and I wanted to avoid that. Reproducible: Didn't try -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212848] New: System lock up - kernel null pointer dereference - page fault
by bugzilla_noreply＠suse.com 07 Jul '23

07 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212848 Bug ID: 1212848 Summary: System lock up - kernel null pointer dereference - page fault 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: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867882 --> https://bugzilla.suse.com/attachment.cgi?id=867882&action=edit journal-logs Booted up my laptop from full shutdown, logged in, Slack (Flatpak) started automatically, clicked on a few Slack channels and the system froze, couldn't switch between TTYs either. Forced shutdown with the power button. OS: openSUSE Tumbleweed 20230624 Kernel: 6.3.9-1-default DE: GNOME 44.2 Wayland Laptop: Lenovo ThinkPad T14s Gen 1 (AMD 4650U with integrated graphics) Attached some logs from the journal. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1212885] New: [Build20230627-1] openQA test fails in steamcmd, `steamcmd +login anonymous +app_update 90 validate +quit` command fails
by bugzilla_noreply＠suse.com 06 Jul '23

06 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212885 Bug ID: 1212885 Summary: [Build20230627-1] openQA test fails in steamcmd, `steamcmd +login anonymous +app_update 90 validate +quit` command fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: deepthi.venkatachala(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The execution of '/usr/bin/steamcmd +login anonymous +app_update 90 validate +quit' is failing with a below error and can observe coredump. [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1687387651 -- type 'quit' to exit -- Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory dlmopen libSDL3.so.0 failed: libSDL3.so.0: cannot open shared object file: No such file or directory OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Update state (0x3) reconfiguring, progress: 0.00 (0 / 0) Update state (0x61) downloading, progress: 8.50 (8357266 / 98310834) Error! App '90' state is 0x10E after update job. /usr/libexec/steamcmd/steamcmd.sh: line 39: 8284 Segmentation fault (core dumped) $DEBUGGER "$STEAMEXE" "$@" ## Observation openQA test in scenario opensuse-15.4-DVD-Updates-x86_64-Build20230627-1-extra_tests_textmode@64bit fails in [steamcmd](https://openqa.opensuse.org/tests/3383860#step/steamcmd/7) ## Reproducible Fails since (at least) Build [20230615-1](https://openqa.opensuse.org/tests/3358343) ## Expected result Last good: [20230614-2](https://openqa.opensuse.org/tests/3357508) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… #cat /root/Steam/logs/stderr.txt crash_20230627053617_41.dmp[14980]: Uploading dump (out-of-process) /tmp/dumps/crash_20230627053617_41.dmp crash_20230627053617_41.dmp[14980]: Finished uploading minidump (out-of-process): success = no crash_20230627053617_41.dmp[14980]: error: libcurl.so: cannot open shared object file: No such file or directory crash_20230627053617_41.dmp[14980]: file ''/tmp/dumps/crash_20230627053617_41.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory'' -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212837] New: zgrep complains about lua-lmod files permissions
by bugzilla_noreply＠suse.com 06 Jul '23

06 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212837 Bug ID: 1212837 Summary: zgrep complains about lua-lmod files permissions 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- # zgrep --help /usr/bin/zgrep: /usr/share/lmod/8.7.17/init/bash: Permission non accordée Usage: /usr/bin/zgrep [OPTION]... [-e] PATTERN [FILE]... [...] # ls -l /usr/share/lmod/8.7.17/init total 92 -rw-r--r-- 1 root root 5702 8 févr. 17:32 bash -rw-r--r-- 1 root root 6810 8 févr. 17:32 cmake -rw-r--r-- 1 root root 1822 8 févr. 17:32 csh -rw-r--r-- 1 root root 2251 8 févr. 17:32 cshrc -rw-r--r-- 1 root root 1431 8 févr. 17:32 env_modules_python.py -rw-r--r-- 1 root root 250 8 févr. 17:32 env_modules_ruby.rb -rw-r--r-- 1 root root 582 8 févr. 17:32 fish drwxr-xr-x 1 root root 22 6 juin 22:12 fish_tab_completion lrwxrwxrwx 1 root root 2 8 févr. 17:32 ksh -> sh drwxr-xr-x 1 root root 62 6 juin 22:12 ksh_funcs -rw-r--r-- 1 root root 3342 8 févr. 17:32 lisp -rw-r--r-- 1 root root 7990 8 févr. 17:32 lmod_bash_completions -rw-r--r-- 1 root root 1814 8 févr. 17:32 lmodrc.lua -rw-r--r-- 1 root root 161 8 févr. 17:32 perl -rw-r--r-- 1 root root 3106 8 févr. 17:32 profile -rw-r--r-- 1 root root 2099 8 févr. 17:32 profile.fish -rw-r--r-- 1 root root 2217 8 févr. 17:32 profile.rc -rw-r--r-- 1 root root 358 8 févr. 17:32 R -rw-r--r-- 1 root root 762 8 févr. 17:32 rc -rw-r--r-- 1 root root 853 8 févr. 17:32 sh lrwxrwxrwx 1 root root 3 8 févr. 17:32 tcsh -> csh lrwxrwxrwx 1 root root 4 8 févr. 17:32 zsh -> bash Looks like they should have the executable bit. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212860] New: Please revert nvidia driver to 525 branch or at least add 525 in addition to 535.
by bugzilla_noreply＠suse.com 05 Jul '23

05 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212860 Bug ID: 1212860 Summary: Please revert nvidia driver to 525 branch or at least add 525 in addition to 535. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: angulion(a)gmail.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Tumbleweed and Leap 15.4, 15.5 (at least) recently switched nvidia driver from 525 to 535 branch. This is unfortunate because at least with Xorg, 535 most likely will hang the entire system, especially with anything vulkan - it is not a good candidate for widespread use. Please consider reverting back to 525 or perhaps have both 525 and 535 available through nvidia's repo and let the users decide. As is the repo is at least for me not usable anymore and "the hard way" is the only option since 525 is solid but not available as rpm. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212833] New: Linux 6.3.9: Kernel panic at boot needing hard power-off
by bugzilla_noreply＠suse.com 04 Jul '23

04 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212833 Bug ID: 1212833 Summary: Linux 6.3.9: Kernel panic at boot needing hard power-off Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867873 --> https://bugzilla.suse.com/attachment.cgi?id=867873&action=edit Output from `journalctl -b -1 --no-hostname` At boot (usually after booting into Windows and rebooting), my ThinkPad P14s Gen2 laptop has started to freeze with the Caps Lock LED blinking on and off repeatedly indicative of a kernel panic. I have to eventually hard power off the machine and try booting again. This happens at boot often, but not always, since the update to Kernel 6.3.9 on Tumbleweed "20230626", and had never happened before. The following messages are logged to the journal (full journal attached): ---------------------------------------------------- > Jun 29 16:08:54 kernel: mt7921e 0000:03:00.0: WM Firmware Version: ____010000, Build Time: 20230526130958 > Jun 29 16:08:54 kernel: BUG: kernel NULL pointer dereference, address: 000000000000005a > Jun 29 16:08:54 kernel: #PF: supervisor read access in kernel mode > Jun 29 16:08:54 kernel: #PF: error_code(0x0000) - not-present page > Jun 29 16:08:54 kernel: PGD 0 P4D 0 > Jun 29 16:08:54 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI > Jun 29 16:08:54 kernel: CPU: 11 PID: 1119 Comm: irqbalance Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 > Jun 29 16:08:54 kernel: Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET54W (1.24 ) 05/15/2023 > Jun 29 16:08:54 kernel: RIP: 0010:show_interrupts+0x24c/0x340 > Jun 29 16:08:54 kernel: Code: 85 d2 74 0f 48 c7 c6 c1 1c fa b9 48 89 ef e8 db 0a 2c 00 49 8b 5c 24 70 48 85 db 74 29 48 8b 53 50 48 c7 c6 c7 1c fa b9 eb 0b <48> 8b 53 50 48 c7 c6 9c 49 fd b9 48 89 ef e8 b1 0a 2c 00 48 8b 5b > Jun 29 16:08:54 kernel: RSP: 0018:ffffa5e801b07cd8 EFLAGS: 00010006 > Jun 29 16:08:54 kernel: RAX: 0000000000000000 RBX: 000000000000000a RCX: ffff0a00ffffff04 > Jun 29 16:08:54 kernel: RDX: 0000000000001000 RSI: 0000000000000005 RDI: 0000000047c8f0a3 > Jun 29 16:08:54 kernel: RBP: ffff96fd07dd18e8 R08: 0000000000000005 R09: ffff96fc47c8f0a4 > Jun 29 16:08:54 kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffff96fb40185200 > Jun 29 16:08:54 kernel: R13: 0000000000000246 R14: ffff96fb401852a4 R15: ffffa5e801b07e10 > Jun 29 16:08:54 kernel: FS: 00007f4ab1feb780(0000) GS:ffff970152180000(0000) knlGS:0000000000000000 > Jun 29 16:08:54 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > Jun 29 16:08:54 kernel: CR2: 000000000000005a CR3: 0000000136220000 CR4: 0000000000750ee0 > Jun 29 16:08:54 kernel: PKRU: 55555554 > Jun 29 16:08:54 kernel: Call Trace: > Jun 29 16:08:54 kernel: <TASK> > Jun 29 16:08:54 kernel: ? __die+0x23/0x70 > Jun 29 16:08:54 kernel: ? page_fault_oops+0x14d/0x490 > Jun 29 16:08:54 kernel: ? number+0x320/0x3b0 > Jun 29 16:08:54 kernel: ? exc_page_fault+0x6e/0x150 > Jun 29 16:08:54 kernel: ? asm_exc_page_fault+0x26/0x30 > Jun 29 16:08:54 kernel: ? show_interrupts+0x24c/0x340 > Jun 29 16:08:54 kernel: ? show_interrupts+0x25f/0x340 > Jun 29 16:08:54 kernel: seq_read_iter+0x123/0x480 > Jun 29 16:08:54 kernel: ? apparmor_file_permission+0x70/0x170 > Jun 29 16:08:54 kernel: proc_reg_read_iter+0x51/0x90 > Jun 29 16:08:54 kernel: vfs_read+0x1f8/0x2d0 > Jun 29 16:08:54 kernel: ksys_read+0x67/0xe0 > Jun 29 16:08:54 kernel: do_syscall_64+0x60/0x90 > Jun 29 16:08:54 kernel: ? handle_mm_fault+0x11e/0x310 > Jun 29 16:08:54 kernel: ? do_user_addr_fault+0x1e0/0x720 > Jun 29 16:08:54 kernel: ? do_syscall_64+0x6c/0x90 > Jun 29 16:08:54 kernel: ? exc_page_fault+0x6e/0x150 > Jun 29 16:08:54 kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc > Jun 29 16:08:54 kernel: RIP: 0033:0x7f4ab219a091 > Jun 29 16:08:54 kernel: Code: 00 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 80 3d ed 2a 0f 00 00 74 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 c3 66 0f 1f 44 00 00 48 83 ec 28 48 89 54 > Jun 29 16:08:54 kernel: RSP: 002b:00007ffd49167138 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 > Jun 29 16:08:54 kernel: RAX: ffffffffffffffda RBX: 0000558d6c5592a0 RCX: 00007f4ab219a091 > Jun 29 16:08:54 kernel: RDX: 0000000000000400 RSI: 0000558d6c559500 RDI: 0000000000000003 > Jun 29 16:08:54 kernel: RBP: 00007f4ab227b660 R08: 0000558d6c55e7b0 R09: 00007f4ab227ece0 > Jun 29 16:08:54 kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 0000000000000000 > Jun 29 16:08:54 kernel: R13: 0000000000000a68 R14: 00007f4ab227ad60 R15: 0000000000000a68 > Jun 29 16:08:54 kernel: </TASK> > Jun 29 16:08:54 kernel: Modules linked in: uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc binfmt_misc nls_iso8859_1 nls_cp437 vfat fat mt7921e snd_acp3x_pdm_dma snd_soc_dmic snd_acp3x_rn mt7921_common snd_sof_amd_rembrandt mt76_connac_lib snd_sof_amd_renoir snd_sof_amd_acp mt76 snd_sof_pci snd_sof_xtensa_dsp snd_ctl_led snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core btusb btrtl snd_hda_intel btbcm btintel snd_intel_dspcfg snd_compress snd_intel_sdw_acpi btmtk snd_pcm_dmaengine snd_hda_codec mac80211 snd_pci_ps snd_rpl_pci_acp6x snd_hda_core bluetooth intel_rapl_msr snd_acp_pci snd_hwdep intel_rapl_common thinkpad_acpi snd_pci_acp6x r8169 snd_pcm ledtrig_audio libarc4 snd_pci_acp5x realtek edac_mce_amd snd_timer snd_rn_pci_acp3x platform_profile think_lmi(+) mdio_devres efi_pstore pcspkr snd_acp_config xfs ecdh_generic snd_soc_acpi snd nxp_nci_i2c nxp_nci firmware_attributes_class cfg80211 wmi_bmof tiny_power_button i2c_piix4 > Jun 29 16:08:54 kernel: snd_pci_acp3x k10temp libphy thermal nci soundcore ac nfc rfkill amd_pmc button i2c_scmi acpi_cpufreq joydev fuse configfs dmi_sysfs ip_tables x_tables mmc_block amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul i2c_algo_bit drm_ttm_helper ttm iommu_v2 ghash_clmulni_intel drm_buddy xhci_pci gpu_sched rtsx_pci_sdmmc sha512_ssse3 xhci_pci_renesas mmc_core xhci_hcd drm_display_helper nvme aesni_intel crypto_simd usbcore cryptd cec ucsi_acpi rtsx_pci nvme_core typec_ucsi sp5100_tco rc_core roles video typec battery wmi serio_raw btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_intel sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr kvm_amd ccp kvm irqbypass efivarfs > Jun 29 16:08:54 kernel: CR2: 000000000000005a > Jun 29 16:08:54 kernel: ---[ end trace 0000000000000000 ]--- > Jun 29 16:08:54 kernel: RIP: 0010:show_interrupts+0x24c/0x340 > Jun 29 16:08:54 kernel: Code: 85 d2 74 0f 48 c7 c6 c1 1c fa b9 48 89 ef e8 db 0a 2c 00 49 8b 5c 24 70 48 85 db 74 29 48 8b 53 50 48 c7 c6 c7 1c fa b9 eb 0b <48> 8b 53 50 48 c7 c6 9c 49 fd b9 48 89 ef e8 b1 0a 2c 00 48 8b 5b > Jun 29 16:08:54 kernel: RSP: 0018:ffffa5e801b07cd8 EFLAGS: 00010006 > Jun 29 16:08:54 kernel: RAX: 0000000000000000 RBX: 000000000000000a RCX: ffff0a00ffffff04 > Jun 29 16:08:54 kernel: RDX: 0000000000001000 RSI: 0000000000000005 RDI: 0000000047c8f0a3 > Jun 29 16:08:54 kernel: RBP: ffff96fd07dd18e8 R08: 0000000000000005 R09: ffff96fc47c8f0a4 > Jun 29 16:08:54 kernel: R10: ffffffffffffffff R11: 0000000000000000 R12: ffff96fb40185200 > Jun 29 16:08:54 kernel: R13: 0000000000000246 R14: ffff96fb401852a4 R15: ffffa5e801b07e10 > Jun 29 16:08:54 kernel: FS: 00007f4ab1feb780(0000) GS:ffff970152180000(0000) knlGS:0000000000000000 > Jun 29 16:08:54 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > Jun 29 16:08:54 kernel: CR2: 000000000000005a CR3: 0000000136220000 CR4: 0000000000750ee0 > Jun 29 16:08:54 kernel: PKRU: 55555554 > Jun 29 16:08:54 kernel: note: irqbalance[1119] exited with irqs disabled > Jun 29 16:08:54 kernel: note: irqbalance[1119] exited with preempt_count 1 > Jun 29 16:08:54 kernel: ------------[ cut here ]------------ > Jun 29 16:08:54 kernel: Voluntary context switch within RCU read-side critical section! > Jun 29 16:08:54 kernel: WARNING: CPU: 11 PID: 1119 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x5e6/0x640 > Jun 29 16:08:54 kernel: Modules linked in: uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc binfmt_misc nls_iso8859_1 nls_cp437 vfat fat mt7921e snd_acp3x_pdm_dma snd_soc_dmic snd_acp3x_rn mt7921_common snd_sof_amd_rembrandt mt76_connac_lib snd_sof_amd_renoir snd_sof_amd_acp mt76 snd_sof_pci snd_sof_xtensa_dsp snd_ctl_led snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core btusb btrtl snd_hda_intel btbcm btintel snd_intel_dspcfg snd_compress snd_intel_sdw_acpi btmtk snd_pcm_dmaengine snd_hda_codec mac80211 snd_pci_ps snd_rpl_pci_acp6x snd_hda_core bluetooth intel_rapl_msr snd_acp_pci snd_hwdep intel_rapl_common thinkpad_acpi snd_pci_acp6x r8169 snd_pcm ledtrig_audio libarc4 snd_pci_acp5x realtek edac_mce_amd snd_timer snd_rn_pci_acp3x platform_profile think_lmi(+) mdio_devres efi_pstore pcspkr snd_acp_config xfs ecdh_generic snd_soc_acpi snd nxp_nci_i2c nxp_nci firmware_attributes_class cfg80211 wmi_bmof tiny_power_button i2c_piix4 > Jun 29 16:08:54 kernel: snd_pci_acp3x k10temp libphy thermal nci soundcore ac nfc rfkill amd_pmc button i2c_scmi acpi_cpufreq joydev fuse configfs dmi_sysfs ip_tables x_tables mmc_block amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul i2c_algo_bit drm_ttm_helper ttm iommu_v2 ghash_clmulni_intel drm_buddy xhci_pci gpu_sched rtsx_pci_sdmmc sha512_ssse3 xhci_pci_renesas mmc_core xhci_hcd drm_display_helper nvme aesni_intel crypto_simd usbcore cryptd cec ucsi_acpi rtsx_pci nvme_core typec_ucsi sp5100_tco rc_core roles video typec battery wmi serio_raw btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_intel sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr kvm_amd ccp kvm irqbypass efivarfs > Jun 29 16:08:54 kernel: CPU: 11 PID: 1119 Comm: irqbalance Tainted: G D 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 > Jun 29 16:08:54 kernel: Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET54W (1.24 ) 05/15/2023 > Jun 29 16:08:54 kernel: RIP: 0010:rcu_note_context_switch+0x5e6/0x640 > Jun 29 16:08:54 kernel: Code: 00 00 00 00 0f 85 31 fd ff ff 49 89 84 24 a0 00 00 00 e9 24 fd ff ff 48 c7 c7 88 86 01 ba c6 05 a3 ef f2 01 01 e8 3a af f4 ff <0f> 0b e9 6d fa ff ff c6 43 11 00 48 8b 73 20 ba 01 00 00 00 48 8b > Jun 29 16:08:54 kernel: RSP: 0018:ffffa5e801b07c40 EFLAGS: 00010086 > Jun 29 16:08:54 kernel: RAX: 0000000000000000 RBX: ffff9701521bab40 RCX: 0000000000000027 > Jun 29 16:08:54 kernel: RDX: ffff9701521a74c8 RSI: 0000000000000001 RDI: ffff9701521a74c0 > Jun 29 16:08:54 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffa5e801b07ae8 > Jun 29 16:08:54 kernel: R10: 0000000000000003 R11: ffff970151afffe8 R12: ffff9701521b9d00 > Jun 29 16:08:54 kernel: R13: ffff96fb84762900 R14: ffffffffba9aec40 R15: ffff96fb43d69470 > Jun 29 16:08:54 kernel: FS: 0000000000000000(0000) GS:ffff970152180000(0000) knlGS:0000000000000000 > Jun 29 16:08:54 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > Jun 29 16:08:54 kernel: CR2: 000000000000005a CR3: 00000002c7636000 CR4: 0000000000750ee0 > Jun 29 16:08:54 kernel: PKRU: 55555554 > Jun 29 16:08:54 kernel: Call Trace: > Jun 29 16:08:54 kernel: <TASK> > Jun 29 16:08:54 kernel: ? rcu_note_context_switch+0x5e6/0x640 > Jun 29 16:08:54 kernel: ? __warn+0x81/0x130 > Jun 29 16:08:54 kernel: ? rcu_note_context_switch+0x5e6/0x640 > Jun 29 16:08:54 kernel: ? report_bug+0x171/0x1a0 > Jun 29 16:08:54 kernel: ? handle_bug+0x3c/0x80 > Jun 29 16:08:54 kernel: ? exc_invalid_op+0x17/0x70 > Jun 29 16:08:54 kernel: ? asm_exc_invalid_op+0x1a/0x20 > Jun 29 16:08:54 kernel: ? rcu_note_context_switch+0x5e6/0x640 > Jun 29 16:08:54 kernel: __schedule+0xb0/0x1490 > Jun 29 16:08:54 kernel: ? __slab_free+0xc4/0x300 > Jun 29 16:08:54 kernel: ? select_task_rq_fair+0x1ae/0x1a00 > Jun 29 16:08:54 kernel: schedule+0x5e/0xd0 > Jun 29 16:08:54 kernel: schedule_preempt_disabled+0x15/0x30 > Jun 29 16:08:54 kernel: __mutex_lock.constprop.0+0x403/0x710 > Jun 29 16:08:54 kernel: ? ttwu_queue_wakelist+0xef/0x110 > Jun 29 16:08:54 kernel: synchronize_rcu_expedited+0x432/0x740 > Jun 29 16:08:54 kernel: ? xas_load+0xe/0x50 > Jun 29 16:08:54 kernel: ? wake_up_q+0x4e/0x90 > Jun 29 16:08:54 kernel: ? rwsem_wake.isra.0+0x69/0x90 > Jun 29 16:08:54 kernel: namespace_unlock+0xd2/0x1a0 > Jun 29 16:08:54 kernel: put_mnt_ns+0x6d/0x90 > Jun 29 16:08:54 kernel: free_nsproxy+0x1b/0x1b0 > Jun 29 16:08:54 kernel: do_exit+0x334/0xa70 > Jun 29 16:08:54 kernel: make_task_dead+0x81/0x170 > Jun 29 16:08:54 kernel: rewind_stack_and_make_dead+0x17/0x20 > Jun 29 16:08:54 kernel: RIP: 0033:0x7f4ab219a091 > Jun 29 16:08:54 kernel: Code: Unable to access opcode bytes at 0x7f4ab219a067. > Jun 29 16:08:54 kernel: RSP: 002b:00007ffd49167138 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 > Jun 29 16:08:54 kernel: RAX: ffffffffffffffda RBX: 0000558d6c5592a0 RCX: 00007f4ab219a091 > Jun 29 16:08:54 kernel: RDX: 0000000000000400 RSI: 0000558d6c559500 RDI: 0000000000000003 > Jun 29 16:08:54 kernel: RBP: 00007f4ab227b660 R08: 0000558d6c55e7b0 R09: 00007f4ab227ece0 > Jun 29 16:08:54 kernel: R10: 0000000000000040 R11: 0000000000000246 R12: 0000000000000000 > Jun 29 16:08:54 kernel: R13: 0000000000000a68 R14: 00007f4ab227ad60 R15: 0000000000000a68 > Jun 29 16:08:54 kernel: </TASK> > Jun 29 16:08:54 kernel: ---[ end trace 0000000000000000 ]--- > Jun 29 16:08:54 polkitd[1128]: Finished loading, compiling and executing 6 rules > Jun 29 16:08:54 polkitd[1128]: Acquired the name org.freedesktop.PolicyKit1 on the system bus > Jun 29 16:08:54 (udev-worker)[702]: video2: Failed to create/update device symlink '/dev/video2', ignoring: File exists > Jun 29 16:08:55 kernel: mt7921e 0000:03:00.0 wlp3s0: renamed from wlan0 > Jun 29 16:08:57 kernel: Bluetooth: hci0: Device setup in 3177859 usecs > Jun 29 16:08:57 kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. > Jun 29 16:08:57 kernel: Bluetooth: hci0: AOSP extensions version v1.00 > Jun 29 16:08:57 kernel: Bluetooth: hci0: AOSP quality report is supported > Jun 29 16:09:12 nscd[1134]: 1134 checking for monitored file `/etc/services': No such file or directory > Jun 29 16:09:40 kernel: sysrq: This sysrq operation is disabled. > Jun 29 16:09:41 kernel: sysrq: Emergency Sync ---------------------------------------------------- At this point, I believe I try the magic keys reboot sequence: [Alt+SysRq] R S E I U B. Happy to provide any other info upon request. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212893] New: Update to build against liborcus-0.17
by bugzilla_noreply＠suse.com 03 Jul '23

03 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212893 Bug ID: 1212893 Summary: Update to build against liborcus-0.17 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- libreoffice fails to build in its devel project due to the update of liborcus to 0.17 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212899] New: nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657'
by bugzilla_noreply＠suse.com 02 Jul '23

02 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212899 Bug ID: 1212899 Summary: nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zeitlinie(a)yahoo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Updating to kernel 6.4.0-lp154.6.g192b657-default does not allow to update to kernel-default-devel-6.4.0-lp154.6.1.g192b657.x86_64 kernel-syms-6.4.0-lp154.8.1.g192b657.x86_64 also, because of #### YaST2 conflicts list - generated 2023-06-30 19:53:10 #### nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657' needed by the to be installed kernel-default-devel-6.4.0-lp154.6.1.g192b657.x86_64 nothing provides 'kernel-default-devel = 6.4.0-lp154.8.g192b657' needed by the to be installed kernel-syms-6.4.0-lp154.8.1.g192b657.x86_64 Consequentially virtualbox kernel modules cannot be compiled, breaking also virtualbox -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212822] New: Package python310-docutils-0.19-1699.5.pm.9.noarch not installed correctly
by bugzilla_noreply＠suse.com 01 Jul '23

01 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212822 Bug ID: 1212822 Summary: Package python310-docutils-0.19-1699.5.pm.9.noarch not installed correctly 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: arbichev(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867861 --> https://bugzilla.suse.com/attachment.cgi?id=867861&action=edit Screenshot Package python310-docutils-0.19-1699.5.pm.9.noarch not installed correctly. Screenshot attached -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212763] cifs: Content Duplication: <Windows share>Mounting Secondary Folder Shows Contents of First Folder in both the Mount Points
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212763 https://bugzilla.suse.com/show_bug.cgi?id=1212763#c2 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |Kernel Assignee|gnome-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|Content Duplication: |cifs: Content Duplication: |<Windows share>Mounting |<Windows share>Mounting |Secondary Folder Shows |Secondary Folder Shows |Contents of First Folder in |Contents of First Folder in |both the Mount Points |both the Mount Points Priority|P2 - High |P5 - None CC| |Andreas.Stieger(a)gmx.de --- Comment #2 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Do not touch the priority field unless you are a developer. Moving to kernel as cigs is in the kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212808] WiFi not available for Realtek device
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212808 https://bugzilla.suse.com/show_bug.cgi?id=1212808#c6 --- Comment #6 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- >1. Why not using a normal "txt"-File. It is basically a text file. But, looking at it, I see that "zypper" output includes lots of escape sequences to give colored output. I should probably have used "--terse" or "TERM=dumb" for that command. It's one of the annoying things about "zypper". I just used the "script" command to generate a transcript of the session. >2. I would delete the 6.4 kernel, delete the kernel:stable:backports Repo and use this Repo: I tried that, after your mention of the hardware repo. But still no WiFi. --- # dmesg | grep -i rtw [ 1.716152] rtw89core: loading out-of-tree module taints kernel. [ 1.855848] rtw89_8852be 0000:02:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2 [ 1.855854] rtw89_8852be 0000:02:00.0: Direct firmware load for rtw89/rtw8852b_fw.bin failed with error -2 [ 1.855855] rtw89_8852be 0000:02:00.0: failed to early request firmware: -2 [ 1.855940] rtw89_8852be 0000:02:00.0: Direct firmware load for rtw89/rtw8852b_fw.bin failed with error -2 [ 1.855946] rtw89_8852be 0000:02:00.0: enabling device (0000 -> 0003) [ 1.857161] rtw89_8852be 0000:02:00.0: failed to wait firmware completion [ 1.857172] rtw89_8852be 0000:02:00.0: failed to setup chip information [ 1.858012] rtw89_8852be: probe of 0000:02:00.0 failed with error -22 --- Seems to be a firmware problem. Similarly, booting with that 6.4 kernel, I got firmware problem messages. But it worked with a 6.3.9 kernel. And it works in Tumbleweed (6.3.9 kernel). I tried installing firmware from the kernel-backport repo, but that did not help. So I have reverted to the origin 15.5 firmware. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212824] [Build 20230627] apptainer: Write failed because no space left on device
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212824 https://bugzilla.suse.com/show_bug.cgi?id=1212824#c2 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com --- Comment #2 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Egbert Eich from comment #1) > Apparently, the command `apptainer build container.sif > apptainer_container.def` died while it tried to create the squashfs. It is > conceivable that apptainer temporarily needs some scratch space while > creating the sif file. If space on the test system is too scares this needs > to be remedied by QA. It is unrelated to the software. > Assigning to Ioannis. AS can be seen in the output of df in comment #0 we are on a 30GB disk with 2.3GB occupied. If we need more free space than that, everybody will be doomed (only chance would be for apptainer to use /tmp which is tmpfs and < 1GB free... but that should not have changed recently) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212837] zgrep complains about lua-lmod files permissions
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212837 https://bugzilla.suse.com/show_bug.cgi?id=1212837#c2 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Egbert Eich <eich(a)suse.com> --- /usr/share/lmod/8.7.17/init/bash is not a standalone shell script: it gets sourced - like the other files in this directory Therefore, none of these should have the execute bit set. Furthermore, I've just tested with a freshly updated TW, `zgrep --help` does not give me the strange error message you are seeing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212824] [Build 20230627] apptainer: Write failed because no space left on device
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212824 https://bugzilla.suse.com/show_bug.cgi?id=1212824#c1 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|cgoll(a)suse.com |ioannis.bonatakis(a)suse.com --- Comment #1 from Egbert Eich <eich(a)suse.com> --- Apparently, the command `apptainer build container.sif apptainer_container.def` died while it tried to create the squashfs. It is conceivable that apptainer temporarily needs some scratch space while creating the sif file. If space on the test system is too scares this needs to be remedied by QA. It is unrelated to the software. Assigning to Ioannis. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205947] Image downloads from downloadcontent-us1.opensuse.org not working
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1205947 https://bugzilla.suse.com/show_bug.cgi?id=1205947#c4 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- We switched to nginx as caching proxy, so I expect the problem to be gone. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207874] Firstboot User Setup for MicroOS Desktop Plasma
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1207874 https://bugzilla.suse.com/show_bug.cgi?id=1207874#c3 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Installation Product|openSUSE Tumbleweed |openSUSE Kalpa --- Comment #3 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208163] microOS Plasma - sddm wallpaper change is not possible
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1208163 https://bugzilla.suse.com/show_bug.cgi?id=1208163#c1 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|openSUSE Tumbleweed |openSUSE Kalpa Component|MicroOS |Desktop Environment --- Comment #1 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208162] Improve/setup kwallet first boot configuration to something more sensible
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1208162 https://bugzilla.suse.com/show_bug.cgi?id=1208162#c1 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|openSUSE Tumbleweed |openSUSE Kalpa Component|MicroOS |Installation --- Comment #1 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208255] No image or document viewer installed on MicroOS Plasma by default
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1208255 https://bugzilla.suse.com/show_bug.cgi?id=1208255#c2 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Installation Product|openSUSE Tumbleweed |openSUSE Kalpa --- Comment #2 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207873] kinfocenter in MicroOS Desktop Plasma displays incorrect information
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1207873 https://bugzilla.suse.com/show_bug.cgi?id=1207873#c5 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|openSUSE Tumbleweed |openSUSE Kalpa Component|MicroOS |Desktop Environment --- Comment #5 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212898] New: Kmail prints html mails by separating the header and the message body on two pages
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212898 Bug ID: 1212898 Summary: Kmail prints html mails by separating the header and the message body on two pages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When receiving an email with kmail (html) and you print it out, you get a header page and a separate only text page. This is odd because if you pint something as a documentation, you have the problem that you cannot show the two are related. The issue presents independently if printing from the preview, from an open message, to a printer or to a pdf does not matter. The pdf is actually exactly the same in output: header, rest a white page, second page with text, where the text is immediately at the beginning of the page without white "printborder" space. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210125] Unable to mount network Shares from within dolphin
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210125 https://bugzilla.suse.com/show_bug.cgi?id=1210125#c5 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|openSUSE Tumbleweed |openSUSE Kalpa Component|MicroOS |Desktop Environment --- Comment #5 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to new openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210975] MicroOSD Plasma: connecting USB stick with distro ISO shows duplicate entries
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210975 https://bugzilla.suse.com/show_bug.cgi?id=1210975#c8 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |sfalken(a)cloverleaf-linux.or | |g Product|openSUSE Tumbleweed |openSUSE Kalpa Component|MicroOS |Desktop Environment --- Comment #8 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to openSUSE Kalpa section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212560] language is after the installation is wrong (plasma)
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212560 https://bugzilla.suse.com/show_bug.cgi?id=1212560#c1 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfalken(a)cloverleaf-linux.or | |g Component|MicroOS |Installation Product|openSUSE Tumbleweed |openSUSE Kalpa Assignee|kubic-bugs(a)opensuse.org |sfalken(a)cloverleaf-linux.or | |g --- Comment #1 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to openSUSE Kalpa product section -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211561] MicroOS Plasma Discover crash opening flatpakref
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211561 https://bugzilla.suse.com/show_bug.cgi?id=1211561#c5 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |sfalken(a)cloverleaf-linux.or | |g Component|MicroOS |Flatpak Product|openSUSE Tumbleweed |openSUSE Kalpa --- Comment #5 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- Moving to openSUSE Kalpa Product -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197298] QEMU downstream patches break persistent binfmt registration by default
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1197298 https://bugzilla.suse.com/show_bug.cgi?id=1197298#c66 --- Comment #66 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1197298) was mentioned in https://build.opensuse.org/request/show/1096174 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206674] No network (wicked) after 23-12-2022 updates - bond change in kernel
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206674 https://bugzilla.suse.com/show_bug.cgi?id=1206674#c22 --- Comment #22 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:2747-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1194557, 1203300, 1206674, 1211026, 1211647 Sources used: openSUSE Leap 15.5 (src): wicked-0.6.72-150500.3.7.1 Basesystem Module 15-SP5 (src): wicked-0.6.72-150500.3.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211026] wicked failing with wpa-enterprise
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211026 https://bugzilla.suse.com/show_bug.cgi?id=1211026#c15 --- Comment #15 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:2747-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1194557, 1203300, 1206674, 1211026, 1211647 Sources used: openSUSE Leap 15.5 (src): wicked-0.6.72-150500.3.7.1 Basesystem Module 15-SP5 (src): wicked-0.6.72-150500.3.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194557] /var/run leftovers in wicked and/or netconfig
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1194557 https://bugzilla.suse.com/show_bug.cgi?id=1194557#c14 --- Comment #14 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:2747-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1194557, 1203300, 1206674, 1211026, 1211647 Sources used: openSUSE Leap 15.5 (src): wicked-0.6.72-150500.3.7.1 Basesystem Module 15-SP5 (src): wicked-0.6.72-150500.3.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206346] go1.20 release tracking
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206346 https://bugzilla.suse.com/show_bug.cgi?id=1206346#c32 --- Comment #32 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:2750-1: An update that has one fix can now be installed. Category: security (important) Bug References: 1206346 Sources used: Public Cloud Module 15-SP1 (src): terraform-provider-helm-2.9.0-150100.3.8.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206346] go1.20 release tracking
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206346 https://bugzilla.suse.com/show_bug.cgi?id=1206346#c31 --- Comment #31 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:2751-1: An update that has one fix can now be installed. Category: security (important) Bug References: 1206346 Sources used: openSUSE Leap 15.4 (src): terraform-provider-aws-3.11.0-150200.6.7.1 openSUSE Leap 15.5 (src): terraform-provider-aws-3.11.0-150200.6.7.1 SUSE Package Hub 15 15-SP5 (src): terraform-provider-aws-3.11.0-150200.6.7.1 Public Cloud Module 15-SP2 (src): terraform-provider-aws-3.11.0-150200.6.7.1 Public Cloud Module 15-SP3 (src): terraform-provider-aws-3.11.0-150200.6.7.1 Public Cloud Module 15-SP4 (src): terraform-provider-aws-3.11.0-150200.6.7.1 Public Cloud Module 15-SP5 (src): terraform-provider-aws-3.11.0-150200.6.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206346] go1.20 release tracking
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206346 https://bugzilla.suse.com/show_bug.cgi?id=1206346#c30 --- Comment #30 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:2752-1: An update that has one fix can now be installed. Category: security (important) Bug References: 1206346 Sources used: Public Cloud Module 15-SP4 (src): terraform-provider-helm-2.9.0-150200.6.12.1 Public Cloud Module 15-SP5 (src): terraform-provider-helm-2.9.0-150200.6.12.1 openSUSE Leap 15.4 (src): terraform-provider-helm-2.9.0-150200.6.12.1 openSUSE Leap 15.5 (src): terraform-provider-helm-2.9.0-150200.6.12.1 SUSE Package Hub 15 15-SP5 (src): terraform-provider-helm-2.9.0-150200.6.12.1 Public Cloud Module 15-SP2 (src): terraform-provider-helm-2.9.0-150200.6.12.1 Public Cloud Module 15-SP3 (src): terraform-provider-helm-2.9.0-150200.6.12.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206346] go1.20 release tracking
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206346 https://bugzilla.suse.com/show_bug.cgi?id=1206346#c29 --- Comment #29 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:2753-1: An update that has one fix can now be installed. Category: security (important) Bug References: 1206346 Sources used: openSUSE Leap 15.4 (src): terraform-provider-null-3.0.0-150200.6.7.1 openSUSE Leap 15.5 (src): terraform-provider-null-3.0.0-150200.6.7.1 SUSE Package Hub 15 15-SP5 (src): terraform-provider-null-3.0.0-150200.6.7.1 Public Cloud Module 15-SP2 (src): terraform-provider-null-3.0.0-150200.6.7.1 Public Cloud Module 15-SP3 (src): terraform-provider-null-3.0.0-150200.6.7.1 Public Cloud Module 15-SP4 (src): terraform-provider-null-3.0.0-150200.6.7.1 Public Cloud Module 15-SP5 (src): terraform-provider-null-3.0.0-150200.6.7.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212461] vlc hangs when tuning another channel
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212461 https://bugzilla.suse.com/show_bug.cgi?id=1212461#c8 Michael Zapf <Michael.Zapf(a)mizapf.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Michael Zapf <Michael.Zapf(a)mizapf.de> --- Confirmed, no hangs anymore with 6.3.9. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212627] NetworkManager: network interface not configured before SSH daemon is started
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c12 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #12 from Adam Majer <amajer(a)suse.com> --- (In reply to Jonathan Kang from comment #11) > In your setup, NetworkManager logs "startup complete" when ipv4 succeeds, > and this triggers NetworkManager-wait-online to quit. But at that moment, > NetworkManager is still at the process of setting manual ipv6 address. This > is caused by the "ipv6.may-fail" property defaulting to TRUE. So when dhcp4 > succeeded, NetworkManager thought it's time to finish the startup. > > Can you try setting "ipv6.may-fail" to FALSE and see if this makes any > difference? > > > nmcli connection modify Wired\ Connection\ 1 ipv6.may-fail no setting may-fail to false, seem to fix my problem. Thanks! The question is then, shouldn't manually defined settings automatically default to may-fail=no, if there is no specific value set in this field? I assume this probably should be discussed with upstream when may-fail should default to false and when to true. The current case when it always defaults to true is ... confusing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212775] go1.16 fails to build with new update kernel-sources 6.4
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212775 https://bugzilla.suse.com/show_bug.cgi?id=1212775#c8 --- Comment #8 from Jeff Kowalczyk <jkowalczyk(a)suse.com> --- Do newer Go versions build with 6.4? Currently go1.x bootstraps with an earlier go1.x toolchain, but gccgo is an option for bootstrapping. This change is already under consideration primarily to shorten the bootstrap chain. go1.16 and go1.17 are EOL for upstream updates: https://github.com/golang/go/wiki/Go-Release-Cycle The supported versions today are go1.19 and go1.20, and in August 2023 the supported versions shift to go1.20 and go1.21 (go1.21rc2 is in Factory). TBD if 6.4 compatibility fixes for recent Go versions backport to go1.16 and go1.17. go1.17 in particular is a designated bootstrap version: https://github.com/golang/go/issues/44505 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210186] python-zope.schema:test fails to build in Leap 15.5
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210186 https://bugzilla.suse.com/show_bug.cgi?id=1210186#c3 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|python-maintainers(a)suse.com |daniel.garcia(a)suse.com CC| |mcepl(a)suse.com --- Comment #3 from Matej Cepl <mcepl(a)suse.com> --- (In reply to Daniel Garcia from comment #2) > Should we just close this bug or could it better to create a maintenance > request to disable these tests? Certainly the later, when we build our package, it should never end with an error. Could you make honors, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212627] NetworkManager: network interface not configured before SSH daemon is started
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c11 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #11 from Jonathan Kang <songchuan.kang(a)suse.com> --- In your setup, NetworkManager logs "startup complete" when ipv4 succeeds, and this triggers NetworkManager-wait-online to quit. But at that moment, NetworkManager is still at the process of setting manual ipv6 address. This is caused by the "ipv6.may-fail" property defaulting to TRUE. So when dhcp4 succeeded, NetworkManager thought it's time to finish the startup. Can you try setting "ipv6.may-fail" to FALSE and see if this makes any difference? > nmcli connection modify Wired\ Connection\ 1 ipv6.may-fail no -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211397] VUL-0: CVE-2023-32784: In KeePass 2.x before 2.54, it is possible to recover the cleartext master password from a memory dump, even when a workspace is locked or no longer running. The memory dump can be a KeePass process dump, swap file (p
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211397 https://bugzilla.suse.com/show_bug.cgi?id=1211397#c10 --- Comment #10 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-SU-2023:0163-1: An update that fixes one vulnerability is now available.\n\nCategory: security (important)\nBug References: 1211397\nCVE References: CVE-2023-32784\nJIRA References: \nSources used:\nopenSUSE Backports SLE-15-SP5 (src): keepass-2.54-bp155.2.3.1\n\n -- You are receiving this mail because: You are on the CC list for the bug.

1 0