September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 1214915] New: Please build Qt5 with configure option -xcb-native-painting
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214915 Bug ID: 1214915 Summary: Please build Qt5 with configure option -xcb-native-painting 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: Woebbeking(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, this is an experimental feature to let Qt5 paint as Qt4 did. This improves performance of Qt5 applications under X2Go a lot. First this option was enabled by default but some years later it was disabled to reduce the size of the platform plugin libqxcb.so a little bit. You don't have to worry that you brake something if you enable this option as the user also have to set the environment variable QT_XCB_NATIVE_PAINTING to make it work. Thanks in advance! Cheers, André -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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

[Bug 1215465] New: [Build 20230917] groff / "man -P cat docker build | grep … => troff:<standard input>:80: warning: cannot select font 'C'
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215465 Bug ID: 1215465 Summary: [Build 20230917] groff / "man -P cat docker build | grep … => troff:<standard input>:80: warning: cannot select font 'C' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3584565/modules/dock er/steps/212 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem 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 The test code runs: man -P cat docker build | grep 'docker-build - Build'; echo 4Kdp0-$?- this then returns troff:<standard input>:80: warning: cannot select font 'C' … troff:<standard input>:511: warning: cannot select font 'C' troff:<standard input>:513: warning: cannot select font 'C' troff:<standard input>:518: warning: cannot select font 'C' troff:<standard input>:518: warning: cannot select font 'C' 4Kdp0-1- i.e error spewn out and the grep fails (the actual search string not found) openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_docker@64bit fails in [docker](https://openqa.opensuse.org/tests/3584565/modules/docker/steps/212) ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20230917](https://openqa.opensuse.org/tests/3583658) ## Expected result Last good: [20230915](https://openqa.opensuse.org/tests/3580146) (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 4

[Bug 1213931] New: Sushi quick previewer for GNOME Files/Nautilus not working on fresh Leap 15.5 install
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213931 Bug ID: 1213931 Summary: Sushi quick previewer for GNOME Files/Nautilus not working on fresh Leap 15.5 install 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: GNOME Assignee: gnome-bugs(a)suse.de Reporter: bjurg.orsku(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi all, I've just installed Leap 15.5 on a new VM and I'm not getting file previews when I press the space bar but the following messages appear with "journalctl -f" : Aug 03 14:21:37 lp155 dbus-daemon[1636]: [session uid=1000 pid=1636] Activating service name='org.gnome.NautilusPreviewer' requested by ':1.90' (uid=1000 pid=4251 comm="/usr/bin/nautilus --gapplication-service ") Aug 03 14:21:37 lp155 org.gnome.Nauti[4290]: JS ERROR: SyntaxError: expected property name, got '{' @ resource:///org/gnome/NautilusPreviewer/js/viewers/html.js:63 Aug 03 14:21:37 lp155 org.gnome.Nauti[4290]: Script /usr/lib/org.gnome.NautilusPreviewer threw an exception Aug 03 14:21:37 lp155 dbus-daemon[1636]: [session uid=1000 pid=1636] Activated service 'org.gnome.NautilusPreviewer' failed: Process org.gnome.NautilusPreviewer exited with status 1 Information for package sushi: ------------------------------ Repository : Main Repository Name : sushi Version : 43.0-bp155.1.6 Arch : x86_64 Vendor : openSUSE Installed Size : 296.1 KiB Installed : Yes Status : up-to-date Information for package gjs: ---------------------------- Repository : Main Repository Name : gjs Version : 1.70.2-150400.3.3.1 Arch : x86_64 Vendor : SUSE LLC <https://www.suse.com/> Installed Size : 146.2 KiB Installed : Yes Status : up-to-date Maybe related to https://gitlab.gnome.org/GNOME/sushi/-/issues/81 ? Thanks for your help. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215480] New: [gdb/symtab] build-id debuginfo link doesn't work when debugging from outside container
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215480 Bug ID: 1215480 Summary: [gdb/symtab] build-id debuginfo link doesn't work when debugging from outside container Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [ This might be a dup of PR1197415. ] Consider this upstream PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=30866 ): "[gdb/symtab] symbolic links to debuginfo not followed when debugging from outside container". It exercises 4 scenarios for finding debug info: 2 from inside the container, two from outside. For the former both work, for the latter the build-id case works but the .gnu_debuglink case doesn't (which is the subject of the upstream PR). The latter cases are with gdb build from current source, and the results reproduce with the gdb-12-branch. However, when using system gdb (12.1 based), also the build-id case doesn't work: ... Looking for separate debug info (build-id) for target:/lib64-symlink/libc.so.6 Trying /usr/lib/debug/.build-id/76/7aa1e4d4fc7c106971b202b6b00e92f47411dc.debug... Trying target:/usr/lib/debug/.build-id/76/7aa1e4d4fc7c106971b202b6b00e92f47411dc.debug... Looking for separate debug info (debug link) for target:/lib64-symlink/libc.so.6 Trying target:/lib64-symlink/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/lib64-symlink/.debug/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/usr/lib/debug//lib64-symlink/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/usr/lib/debug/lib64-symlink//libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:target:/usr/lib/debug/lib64-symlink//libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Missing separate debuginfo for target:/lib64-symlink/libc.so.6 ... This looks like a problem with one of the fedora patches. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215817] New: tcsh completion for 'ln' is incorrect
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215817 Bug ID: 1215817 Summary: tcsh completion for 'ln' is incorrect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hendersj(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When entering 'ln -s' and hitting tab to get a list of directories, I'm prompted for a <link_name> instead of getting completion from the filesystem. A comparison with the upstream project shows that their pattern in /etc/profile.d/complete.tcsh works, whereas what we have doesn't. I originally reported this issue upstream as I missed the differences between upstream's version of the file and ours. Using their file didn't work as-is (not sure why), but replacing our entry for 'ln' with theirs did. The upstream reported bug confirmed that it's an issue in our setup. That bug is at https://github.com/tcsh-org/tcsh/issues/80 This has been a longstanding issue, and I know it also exists in Leap (all versions, including 15.6 alpha). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215226] New: Yast2 "Active Directory Domain Controller" module fails on start-up
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215226 Bug ID: 1215226 Summary: Yast2 "Active Directory Domain Controller" module fails on start-up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: alanhants(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 869431 --> https://bugzilla.suse.com/attachment.cgi?id=869431&action=edit Screen shot showing the error message. In Yast2, when the "Active Directory Domain Controller" module is started, it promptly fails with a Ruby error. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213854] New: zypper still using /etc/bash_completion.d/
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213854 Bug ID: 1213854 Summary: zypper still using /etc/bash_completion.d/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- zypper is still using /etc/bash_completion.d/ This directory is for admin made changes, distribution packages should install in /usr/share/bash-completion/completions/ This is for Factory, ALP and SLE15 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214658] New: I No Longer Can Monitor Computer Speaker Output
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214658 Bug ID: 1214658 Summary: I No Longer Can Monitor Computer Speaker Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869045 --> https://bugzilla.suse.com/attachment.cgi?id=869045&action=edit Where monitoring output would normally be selected I used to stream audio to my computer's speakers, with the audio device configured as "Analog Stereo Duplex", and monitor the output and record it in Audacity. The process is described at https://manual.audacityteam.org/man/tutorial_recording_computer_playback_on…. This process still does work on this computer when I boot into and use Leap 15.5. But sometime between July 31 and August 6, it stopped working under Tumbleweed. I can no longer select "Monitor of Built-In Audio Analog Stereo" in pavucontrol-qt (see SelectingMonitor.png). The option is listed, but clicking it does not change the recording source. Under TW, I can record the speaker output by changing the audio playback device to "Analog Stereo Output". Also, I can no longer monitor output from the HDMI audio device, either, under TW. Selecting it does not "stick." I do not know what other information (e.g. logs, etc.) would be helpful, but am happy to provide anything that is asked for. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215837] New: [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215837 Bug ID: 1215837 Summary: [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost 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: varun.ojha(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869843 --> https://bugzilla.suse.com/attachment.cgi?id=869843&action=edit Support Config KVM ## Description [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost In the logs, there's a recurring issue with NetworkManager, which is triggering a "Started Process Core Dump" error in the system journals on the localhost. This issue is causing the NetworkManager service to fail with a core dump. The issue seems to be affecting the stability of the network management service on the system. NetworkManager Version: 1.44.0-1.1 Architecture: x86_64 Operating System: openSUSE-20230927-0 ## Information blackbauhinia:~ # zypper info NetworkManager Loading repository data... Reading installed packages... Information for package NetworkManager: --------------------------------------- Repository : openSUSE-20230927-0 Name : NetworkManager Version : 1.44.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 5.9 MiB Installed : Yes Status : up-to-date Source package : NetworkManager-1.44.0-1.1.src Upstream URL : https://networkmanager.dev/ Summary : Standard Linux network configuration tool suite Description : NetworkManager attempts to keep an active network connection available at all times. The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is intended to replace default routes, obtain IP addresses from a DHCP server, and change name servers whenever it sees fit. blackbauhinia:~ # coredumpctl --all TIME PID UID GID SIG COREFILE EXE SIZE Fri 2023-09-29 09:40:48 EDT 1787 0 0 SIGABRT present /usr/sbin/NetworkManager 522.1K blackbauhinia:~ # ## Reproduce steps The exact steps to reproduce the issue are not provided in the bug report. However, the issue has been observed in the logs of the system. Possible steps 1. Install openSUSE Tumbleweed with Latest build 2. After Autoyast installation, file: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data… 3. During virt_autotest/login_console, after KVM modules are loaded and NetworkManager is seen with Core dump in journalctl Can be seen here: https://openqa.opensuse.org/tests/3609023#step/login_console/17 https://openqa.opensuse.org/tests/3608243#step/login_console/34 https://openqa.opensuse.org/tests/3603405#step/login_console/19 Expected result: The NetworkManager service should run without errors and manage network connections as expected. Real result: The NetworkManager service is encountering a critical error and failing with a core dump. ## Reproducibility seen multiple times, frequently: Not 100% Was seen in build 20230927 ## Last good build was 20230922, 20230925 Now Seen at recent builds, 20230927 20230926 ## Environment(optional) Linux blackbauhinia 6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) x86_64 x86_64 x86_64 GNU/Linux Linux Kernel Version: 6.5.4-1-default Hostname: blackbauhinia ## Testsuite description(optional, apply for complex scenarios) Test suit: virt-guest-installation-kvm@64bit-ipmi & virt-guest-installation-xen@64bit-ipmi ## Error https://openqa.opensuse.org/tests/3597532#step/login_console/19 Sep 25 00:03:57 blackbauhinia systemd[1]: Started Process Core Dump (PID 2366/UID 0). Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=> Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'. Sep 25 00:03:57 blackbauhinia systemd[1]: Failed to start Network Manager Wait Online. Sep 25 00:03:57 blackbauhinia systemd[1]: Reached target Network is Online. Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Login and scanning of iSCSI devices... Sep 25 00:03:57 blackbauhinia iscsiadm[2369]: iscsiadm: No records found Sep 25 00:03:57 blackbauhinia iscsiadm[2371]: iscsiadm: No records found Sep 25 00:03:57 blackbauhinia iscsiadm[2373]: iscsiadm: Could not get list of targets from firmware. (err 21) Sep 25 00:03:57 blackbauhinia systemd-coredump[2367]: [🡕] Process 1781 (NetworkManager) of user 0 dumped core. Stack trace of thread 1781: #0 0x00007f42f2691e0c __pthread_kill_implementation (libc.so.6 +> #1 0x00007f42f263f0e6 raise (libc.so.6 + 0x3f0e6) #2 0x00007f42f26268d7 abort (libc.so.6 + 0x268d7) #3 0x00007f42f2e58b1d g_mutex_clear (libglib-2.0.so.0 + 0xb7b1d) #4 0x00007f42f30094a2 n/a (libgio-2.0.so.0 + 0xbe4a2) #5 0x00007f42f3005b4c n/a (libgio-2.0.so.0 + 0xbab4c) #6 0x00007f42f2f05970 g_object_unref (libgobject-2.0.so.0 + 0x1c> #7 0x00007f42f2dfaf89 n/a (libglib-2.0.so.0 + 0x59f89) #8 0x00007f42f2dfcb46 n/a (libglib-2.0.so.0 + 0x5bb46) #9 0x00007f42f2dfcf6f n/a (libglib-2.0.so.0 + 0x5bf6f) #10 0x00007f42f2dfeb18 n/a (libglib-2.0.so.0 + 0x5db18) #11 0x00007f42f2dff3ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3e> #12 0x00005643adfd6493 n/a (NetworkManager + 0x3f493) #13 0x00007f42f26281b0 __libc_start_call_main (libc.so.6 + 0x281b> #14 0x00007f42f2628279 __libc_start_main@@GLIBC_2.34 (libc.so.6 +> #15 0x00005643adfd6915 n/a (NetworkManager + 0x3f915) Stack trace of thread 1791: #0 0x00007f42f2709d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f42f2dfeabf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f42f2dff1cc g_main_context_iteration (libglib-2.0.so.0> #3 0x00007f42f2dff211 n/a (libglib-2.0.so.0 + 0x5e211) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1792: #0 0x00007f42f271616d syscall (libc.so.6 + 0x11616d) #1 0x00007f42f2e58cb0 g_cond_wait (libglib-2.0.so.0 + 0xb7cb0) #2 0x00007f42f2dc902b n/a (libglib-2.0.so.0 + 0x2802b) #3 0x00007f42f2e2ba92 n/a (libglib-2.0.so.0 + 0x8aa92) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1793: #0 0x00007f42f2709d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f42f2dfeabf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f42f2dff3ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3e> #3 0x00007f42f30708e6 n/a (libgio-2.0.so.0 + 0x1258e6) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 2365: #0 0x00007f42f271616d syscall (libc.so.6 + 0x11616d) #1 0x00007f42f2e58e5c g_cond_wait_until (libglib-2.0.so.0 + 0xb7> #2 0x00007f42f2dc9003 n/a (libglib-2.0.so.0 + 0x28003) #3 0x00007f42f2e2be0a n/a (libglib-2.0.so.0 + 0x8ae0a) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) ELF object binary architecture: AMD x86-64 Sep 25 00:03:57 blackbauhinia systemd[1]: Finished Login and scanning of iSCSI devices. Sep 25 00:03:57 blackbauhinia systemd[1]: systemd-coredump(a)0-2366-0.service: Deactivated successfully. Sep 25 00:03:57 blackbauhinia systemd[1]: Reached target Remote File Systems. Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Autoyast2 Init Scripts... Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Virtualization qemu daemon... Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Virtualization storage daemon... Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager.service: Failed with result 'core-dump'. ## Logs/ crash # /bin/coredumpctl info 1787 PID: 1787 (NetworkManager) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Fri 2023-09-29 09:40:48 EDT (53min ago) Command Line: /usr/sbin/NetworkManager --no-daemon Executable: /usr/sbin/NetworkManager Control Group: /system.slice/NetworkManager.service Unit: NetworkManager.service Slice: system.slice Boot ID: 752a88f1ac2b4381b0fc7591961e743a Machine ID: 629cb90a95bb451e9026683e7cb65723 Hostname: blackbauhinia Storage: /var/lib/systemd/coredump/core.NetworkManager.0.752a88f1ac2b4381b0fc7591961e743a.1787.1695994848000000.zst (present) Size on Disk: 522.1K Message: Process 1787 (NetworkManager) of user 0 dumped core. Stack trace of thread 1787: #0 0x00007f4ed8491e0c __pthread_kill_implementation (libc.so.6 + 0x91e0c) #1 0x00007f4ed843f0e6 raise (libc.so.6 + 0x3f0e6) #2 0x00007f4ed84268d7 abort (libc.so.6 + 0x268d7) #3 0x00007f4ed8bcdb1d g_mutex_clear (libglib-2.0.so.0 + 0xb7b1d) #4 0x00007f4ed8d7e4a2 n/a (libgio-2.0.so.0 + 0xbe4a2) #5 0x00007f4ed8d7ab4c n/a (libgio-2.0.so.0 + 0xbab4c) #6 0x00007f4ed8c7a970 g_object_unref (libgobject-2.0.so.0 + 0x1c970) #7 0x00007f4ed8b6ff89 n/a (libglib-2.0.so.0 + 0x59f89) #8 0x00007f4ed8b71b46 n/a (libglib-2.0.so.0 + 0x5bb46) #9 0x00007f4ed8b71f6f n/a (libglib-2.0.so.0 + 0x5bf6f) #10 0x00007f4ed8b73b18 n/a (libglib-2.0.so.0 + 0x5db18) #11 0x00007f4ed8b743ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3ef) #12 0x00005652d1963493 n/a (NetworkManager + 0x3f493) #13 0x00007f4ed84281b0 __libc_start_call_main (libc.so.6 + 0x281b0) #14 0x00007f4ed8428279 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28279) #15 0x00005652d1963915 n/a (NetworkManager + 0x3f915) Stack trace of thread 1796: #0 0x00007f4ed8509d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f4ed8b73abf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f4ed8b741cc g_main_context_iteration (libglib-2.0.so.0 + 0x5e1cc) #3 0x00007f4ed8b74211 n/a (libglib-2.0.so.0 + 0x5e211) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1797: #0 0x00007f4ed851616d syscall (libc.so.6 + 0x11616d) #1 0x00007f4ed8bcdcb0 g_cond_wait (libglib-2.0.so.0 + 0xb7cb0) #2 0x00007f4ed8b3e02b n/a (libglib-2.0.so.0 + 0x2802b) #3 0x00007f4ed8ba0a92 n/a (libglib-2.0.so.0 + 0x8aa92) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 2369: #0 0x00007f4ed851616d syscall (libc.so.6 + 0x11616d) #1 0x00007f4ed8bcde5c g_cond_wait_until (libglib-2.0.so.0 + 0xb7e5c) #2 0x00007f4ed8b3e003 n/a (libglib-2.0.so.0 + 0x28003) #3 0x00007f4ed8ba0e0a n/a (libglib-2.0.so.0 + 0x8ae0a) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1798: #0 0x00007f4ed8509d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f4ed8b73abf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f4ed8b743ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3ef) #3 0x00007f4ed8de58e6 n/a (libgio-2.0.so.0 + 0x1258e6) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) ELF object binary architecture: AMD x86-64 The stack trace of the core dump is also provided in the logs. ## Workaround No Please note that resolving this issue may require further investigation, debugging, and potentially collaboration with the NetworkManager development team. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215227] New: Clementine/Strawberry crash on startup due to updated protobuf version
by bugzilla_noreply＠suse.com 08 Oct '23

08 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215227 Bug ID: 1215227 Summary: Clementine/Strawberry crash on startup due to updated protobuf version 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: zrenfire(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > strawberry: symbol lookup error: strawberry: undefined symbol: _ZN6google8protobuf8internal17AssignDescriptorsEPFPKNS1_15DescriptorTableEvEPN4absl12lts_202301259once_flagERKNS0_8MetadataE Also affects another user who's also tried Clementine. https://old.reddit.com/r/openSUSE/comments/16fr3wr/lookup_error/ I noticed that libprotobuf recently updated. > Sep 11 13:47:17 Client-57 plasmashell[1531]: plasma-pk-updates: Got update package: "libprotobuf-lite23_4_0;23.4-6.3;x86_64;repo-oss" , summary: "Protocol Buffers - Google's data interchange format" , type: "enhancement" > Sep 11 13:47:17 Client-57 plasmashell[1531]: plasma-pk-updates: Got update package: "libprotobuf23_4_0;23.4-6.3;x86_64;repo-oss" , summary: "Protocol Buffers - Google's data interchange format" , type: "enhancement" And I noticed that both players have not updated in two months. https://build.opensuse.org/package/show/openSUSE:Factory/clementine https://build.opensuse.org/package/show/openSUSE:Factory/strawberry I assume all these packages need is a rebuild. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1214046] New: Please Add "Thunderbird" or Other Additional Language to Component Description For Firefox
by bugzilla_noreply＠suse.com 08 Oct '23

08 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214046 Bug ID: 1214046 Summary: Please Add "Thunderbird" or Other Additional Language to Component Description For Firefox Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: bill_wayson(a)yahoo.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868665 --> https://bugzilla.suse.com/attachment.cgi?id=868665&action=edit Current description for the Firefox component Currently, if I create a bug report openSUSE -> openSUSE Distribution, and then select the component Firefox, the Component Description box says "Firefox Web Browser" (see the attached screenshot). Apparently, Firefox is also the component to choose when reporting bugs in Thunderbird (e.g. bug 1213962). So, at the least, the description should also include "Thunderbird." At most, this may be the component to choose for any Mozilla product (so, maybe it should be called "Mozilla"?). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215651] New: VPN helper does not add a VPN
by bugzilla_noreply＠suse.com 07 Oct '23

07 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215651 Bug ID: 1215651 Summary: VPN helper does not add a VPN Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: illigarium(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869716 --> https://bugzilla.suse.com/attachment.cgi?id=869716&action=edit Screen Record VPN helper does not add a VPN. It just doesn't appear. GNOME Settings version `gnome-control-center 45.0` There is nothing in stdout/stderr Steps to reproduce: 1. Open GNOME Settings; 2. Try to add any VPN by any means; 3. It does not appear. Also filed a bug here: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214853] New: Add Mageia 9 distribution repository to OBS
by bugzilla_noreply＠suse.com 07 Oct '23

07 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214853 Bug ID: 1214853 Summary: Add Mageia 9 distribution repository to OBS Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: ugal12v(a)gmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Mageia 9 distribution has been released. https://www.mageia.org/en/9/ Could you please add the distribution repository to OBS. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215523] New: kernel 5.14.21.150400.24.84.1 amdgpu critical error
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215523 Bug ID: 1215523 Summary: kernel 5.14.21.150400.24.84.1 amdgpu critical error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugs(a)clearingstelle-eeg-kwkg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the kernel update today to 5.14.21.150400.24.84.1 the system boots, but due to constantly repeated amdgpu error the files /var/log/messages and /var/log/warn grows up to gigabytes in a few minutes and the root file system gets exhausted and no space is left on the device. switching back to the previous kernel 5.14.21.150400.24.81.1 "solves" the issue. GIT Branch: SLE15-SP4_EMBARGO Distribution: SUSE Linux Enterprise 15 Name : kernel-default Version : 5.14.21 Release : 150400.24.84.1 Architecture: x86_64 /var/log/messages is full of errors like this ------------[ cut here ]------------ WARNING: CPU: 10 PID: 8062 at ../include/linux/dma-fence.h:478 amdgpu_sync_keep_later+0xab/0xc0 [amdgpu] 2023-09-20T15:06:06.968445+02:00 fermium kernel: [ 219.037070][ T8062] Modules linked in: rfcomm nf_nat_sip nft_objref nf_conntrack_sip nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib af_packet nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject cmac algif_hash alg if_skcipher af_alg nft_ct bnep nft_chain_nat nf_tables btusb btrtl btbcm btintel ebtable_nat ebtable_broute bluetooth ip6table_nat uvcvideo snd_usb_audio videobuf2_vmalloc ip6table_mangle videobuf2_memops videobuf2_v4l2 ip6table_raw videobuf2_common ip6table_security sn d_usbmidi_lib videodev snd_rawmidi ecdh_generic snd_seq_device mc iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfil ter vboxnetadp(OEN) vboxnetflt(OEN) vboxdrv(OEN) dmi_sysfs iwlmvm joydev sunrpc mac80211 libarc4 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi intel_rapl_msr intel_rapl_common edac_mce_amd snd_hda_intel 2023-09-20T15:06:06.968538+02:00 fermium kernel: [ 219.037204][ T8062] snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd nls_iso8859_1 snd_hda_core iwlwifi hid_multitouch nls_cp437 snd_hwdep vfat kvm snd_pcm r8169 fat snd_timer cfg80211 acer_wmi irqbypass real tek sparse_keymap snd mdio_devres rfkill pcspkr ucsi_acpi snd_pci_acp5x wmi_bmof efi_pstore(N) i2c_piix4 libphy snd_rn_pci_acp3x typec_ucsi soundcore k10temp snd_pci_acp3x thermal typec roles acer_wireless(N) button acpi_cpufreq i2c_designware_platform i2c_designware_co re amd_pmc ac fuse configfs ip_tables x_tables ext4 crc16 mbcache jbd2 dm_crypt essiv authenc hid_generic usbhid amdgpu crc32_pclmul crc32c_intel ghash_clmulni_intel drm_ttm_helper ttm iommu_v2 gpu_sched i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper mmc_core syscopyarea sy sfillrect sysimgblt fb_sys_fops aesni_intel cec rc_core xhci_pci crypto_simd xhci_pci_renesas xhci_hcd drm cryptd nvme usbcore serio_raw nvme_core ccp rtsx_pci sp5100_tco(N) nvme_common t10_pi mfd_core battery video wmi i2c_hid_acpi 2023-09-20T15:06:06.968543+02:00 fermium kernel: [ 219.037378][ T8062] i2c_hid dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs 2023-09-20T15:06:06.968547+02:00 fermium kernel: [ 219.037403][ T8062] Supported: No, Unsupported modules are loaded 2023-09-20T15:06:06.968551+02:00 fermium kernel: [ 219.037406][ T8062] CPU: 10 PID: 8062 Comm: kwin_x11:cs0 Tainted: G W OE N 5.14.21-150400.24.84-default #1 SLE15-SP4 2d2aae51046e63e9f8c5f181ee9c884ea3512c4e 2023-09-20T15:06:06.968554+02:00 fermium kernel: [ 219.037414][ T8062] Hardware name: Acer TravelMate P215-41/Bassdrum_RC, BIOS V1.02 02/18/2021 2023-09-20T15:06:06.968557+02:00 fermium kernel: [ 219.037417][ T8062] RIP: 0010:amdgpu_sync_keep_later+0xab/0xc0 [amdgpu] 2023-09-20T15:06:06.968561+02:00 fermium kernel: [ 219.037602][ T8062] Code: d1 0f 92 c2 eb b4 e8 04 ae bb ed 48 85 db 75 ca eb e1 be 01 00 00 00 e8 83 3a 97 ed eb d5 be 03 00 00 00 e8 77 3a 97 ed eb ab <0f> 0b eb 90 be 02 00 00 00 e8 67 3a 97 ed eb b9 0f 1f 44 00 00 0 f 2023-09-20T15:06:06.968564+02:00 fermium kernel: [ 219.037607][ T8062] RSP: 0018:ffffa76502227ac8 EFLAGS: 00010206 2023-09-20T15:06:06.968567+02:00 fermium kernel: [ 219.037612][ T8062] RAX: ffffffffb0afffc0 RBX: ffff9c1263211940 RCX: 0000000000000000 2023-09-20T15:06:06.968570+02:00 fermium kernel: [ 219.037616][ T8062] RDX: ffff9c1244b00e18 RSI: ffff9c1263211940 RDI: ffff9c1327f51cf8 2023-09-20T15:06:06.968573+02:00 fermium kernel: [ 219.037619][ T8062] RBP: ffff9c1327f51cf8 R08: 0000000000000020 R09: 0000000000000000 2023-09-20T15:06:06.968575+02:00 fermium kernel: [ 219.037622][ T8062] R10: ffff9c1244b00e38 R11: 0000000000000003 R12: 0000000000000000 2023-09-20T15:06:06.968578+02:00 fermium kernel: [ 219.037625][ T8062] R13: 0000000000000000 R14: 0000000000000000 R15: ffff9c12556e9948 2023-09-20T15:06:06.968582+02:00 fermium kernel: [ 219.037629][ T8062] FS: 00007fbac6fa8700(0000) GS:ffff9c153f880000(0000) knlGS:0000000000000000 2023-09-20T15:06:06.968584+02:00 fermium kernel: [ 219.037634][ T8062] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2023-09-20T15:06:06.968587+02:00 fermium kernel: [ 219.037637][ T8062] CR2: 00007f773801e0b0 CR3: 0000000178bfc000 CR4: 0000000000350ee0 2023-09-20T15:06:06.968590+02:00 fermium kernel: [ 219.037641][ T8062] Call Trace: 2023-09-20T15:06:06.968594+02:00 fermium kernel: [ 219.037645][ T8062] <TASK> 2023-09-20T15:06:06.968596+02:00 fermium kernel: [ 219.037649][ T8062] amdgpu_sync_vm_fence+0x1e/0x40 [amdgpu 28d5a9707e1f6057a70f2fd1d73854000d464e2e] 2023-09-20T15:06:06.968599+02:00 fermium kernel: [ 219.037834][ T8062] amdgpu_cs_ioctl+0x1574/0x1ca0 [amdgpu 28d5a9707e1f6057a70f2fd1d73854000d464e2e] 2023-09-20T15:06:06.968603+02:00 fermium kernel: [ 219.038037][ T8062] ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu 28d5a9707e1f6057a70f2fd1d73854000d464e2e] 2023-09-20T15:06:06.968606+02:00 fermium kernel: [ 219.038249][ T8062] drm_ioctl_kernel+0xb6/0x100 [drm b72f874ec848c4be9b8c39c6d4b6cda18e282a1a] 2023-09-20T15:06:06.968609+02:00 fermium kernel: [ 219.038285][ T8062] drm_ioctl+0x35a/0x400 [drm b72f874ec848c4be9b8c39c6d4b6cda18e282a1a] 2023-09-20T15:06:06.968612+02:00 fermium kernel: [ 219.038318][ T8062] ? amdgpu_cs_find_mapping+0x110/0x110 [amdgpu 28d5a9707e1f6057a70f2fd1d73854000d464e2e] 2023-09-20T15:06:06.968615+02:00 fermium kernel: [ 219.038500][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968618+02:00 fermium kernel: [ 219.038505][ T8062] ? try_to_wake_up+0x177/0x550 2023-09-20T15:06:06.968740+02:00 fermium kernel: [ 219.038519][ T8062] amdgpu_drm_ioctl+0x49/0x80 [amdgpu 28d5a9707e1f6057a70f2fd1d73854000d464e2e] 2023-09-20T15:06:06.968743+02:00 fermium kernel: [ 219.038694][ T8062] __x64_sys_ioctl+0x92/0xd0 2023-09-20T15:06:06.968746+02:00 fermium kernel: [ 219.038702][ T8062] do_syscall_64+0x5b/0x80 2023-09-20T15:06:06.968750+02:00 fermium kernel: [ 219.038708][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968753+02:00 fermium kernel: [ 219.038711][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968756+02:00 fermium kernel: [ 219.038715][ T8062] ? __x64_sys_futex+0x5e/0x1d0 2023-09-20T15:06:06.968760+02:00 fermium kernel: [ 219.038721][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968762+02:00 fermium kernel: [ 219.038725][ T8062] ? syscall_exit_to_user_mode+0x28/0x40 2023-09-20T15:06:06.968765+02:00 fermium kernel: [ 219.038731][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968768+02:00 fermium kernel: [ 219.038735][ T8062] ? syscall_exit_to_user_mode+0x28/0x40 2023-09-20T15:06:06.968771+02:00 fermium kernel: [ 219.038740][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968775+02:00 fermium kernel: [ 219.038743][ T8062] ? do_syscall_64+0x67/0x80 2023-09-20T15:06:06.968780+02:00 fermium kernel: [ 219.038747][ T8062] ? syscall_exit_to_user_mode+0x28/0x40 2023-09-20T15:06:06.968783+02:00 fermium kernel: [ 219.038752][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968786+02:00 fermium kernel: [ 219.038756][ T8062] ? do_syscall_64+0x67/0x80 2023-09-20T15:06:06.968789+02:00 fermium kernel: [ 219.038760][ T8062] ? do_syscall_64+0x67/0x80 2023-09-20T15:06:06.968792+02:00 fermium kernel: [ 219.038764][ T8062] ? do_syscall_64+0x67/0x80 2023-09-20T15:06:06.968795+02:00 fermium kernel: [ 219.038768][ T8062] ? srso_return_thunk+0x5/0x10 2023-09-20T15:06:06.968798+02:00 fermium kernel: [ 219.038772][ T8062] entry_SYSCALL_64_after_hwframe+0x61/0xcb 2023-09-20T15:06:06.968801+02:00 fermium kernel: [ 219.038778][ T8062] RIP: 0033:0x7fbae5d02437 2023-09-20T15:06:06.968804+02:00 fermium kernel: [ 219.038782][ T8062] Code: 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 90 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 29 da 0d 00 f7 d8 64 89 01 48 2023-09-20T15:06:06.968807+02:00 fermium kernel: [ 219.038786][ T8062] RSP: 002b:00007fbac6fa7888 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 2023-09-20T15:06:06.968811+02:00 fermium kernel: [ 219.038791][ T8062] RAX: ffffffffffffffda RBX: 00007fbac6fa79e8 RCX: 00007fbae5d02437 2023-09-20T15:06:06.968813+02:00 fermium kernel: [ 219.038794][ T8062] RDX: 00007fbac6fa7900 RSI: 00000000c0186444 RDI: 0000000000000009 2023-09-20T15:06:06.968817+02:00 fermium kernel: [ 219.038797][ T8062] RBP: 00007fbac6fa7900 R08: 00007fbac6fa7a40 R09: 0000000000000020 2023-09-20T15:06:06.968822+02:00 fermium kernel: [ 219.038800][ T8062] R10: 00007fbac6fa7a40 R11: 0000000000000246 R12: 00000000c0186444 2023-09-20T15:06:06.968826+02:00 fermium kernel: [ 219.038802][ T8062] R13: 0000000000000009 R14: 00005636906067b0 R15: 0000000000000020 2023-09-20T15:06:06.968830+02:00 fermium kernel: [ 219.038813][ T8062] </TASK> 2023-09-20T15:06:06.968833+02:00 fermium kernel: [ 219.038815][ T8062] ---[ end trace 3d22bee0ff27a2c8 ]--- -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215844] New: Adding ACS override patch
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215844 Bug ID: 1215844 Summary: Adding ACS override patch 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: m.szczepaniak.000(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello I would like to request addition of acs override patch https://github.com/zen-kernel/zen-kernel/commit/e1b127aa22601f9cb2afa3daad4… It's not enabled by default so it doesn't affect users whatsoever but it would be useful to me and maybe some other people rather than going through effort of adding patch myself. Optionally it could be just in like separate kernel flavour https://build.opensuse.org/project/show/home:Mister_Magister:branches:Kerne… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215007] New: Zypper - Patch openSUSE-SLE-15.5-2023-3514 killed CLI completion
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215007 Bug ID: 1215007 Summary: Zypper - Patch openSUSE-SLE-15.5-2023-3514 killed CLI completion Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The change from Zypper version 1.14.61 to version 1.14.63 has killed the CLI completion of the Zypper commands. For example: "zypper patch[Tab]" no longer allows the selection of the Zypper command “patch-info”. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213822] New: invalid grub.cfg created with INITRD_IN_POSTTRANS=1
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213822 Bug ID: 1213822 Summary: invalid grub.cfg created with INITRD_IN_POSTTRANS=1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Invalid boot entry is generated with latest TW update and INITRD_IN_POSTTRANS=1 set: echo 'Loading Linux 6.4.6-1-default ...' linux /boot/vmlinuz-6.4.6-1-default root=/dev/sda7 /dev/sda5 ${extra_cmdline} sysrq_always_enabled panic=100 ignore_loglevel unknown_nmi_panic resume=/dev/sda6 crashkernel=128M@256M showopts The root device in question is a btrfs device with two members, where grub2-probe prints this: # grub2-probe --target=device / /dev/sda7 /dev/sda5 The issue happened because the update transaction comprised both a grub2 update and a kernel-default update. With INITRD_IN_POSTTRANS=1, if the posttrans script of grub2-x86_64-efi is executed before the posttrans script of kernel-default, the initrd will not exist at the time grub2-mkconfig is run, and the following code from /etc/grub.d/10_linux will be executed: if test -z "${initramfs}" && test -z "${initrd_real}" ; then # "UUID=" and "ZFS=" magic is parsed by initrd or initramfs. Since there's # no initrd or builtin initramfs, it can't work here. if [ "x${GRUB_DEVICE_PARTUUID}" = "x" ] \ || [ "x${GRUB_DISABLE_LINUX_PARTUUID}" = "xtrue" ]; then linux_root_device_thisversion=${GRUB_DEVICE} else linux_root_device_thisversion=PARTUUID=${GRUB_DEVICE_PARTUUID} fi fi This will cause the wrong grub.cfg entry shown above. The script assumes that if no initrd exists at the time it is running, there will be none later, either. This assumption is arguably wrong under SUSE and openSUSE, where we always have an initrd — it would be smarter to assume that if no initrd exists, it will be created later. Also, it's very questionable to create a syntactically wrong boot entry rather than a (possibly) unparseable UUID= entry. The initramfs is created later in the installation process, when the posttrans script of kernel-default is run; but that won't cause the grub.cfg file to be regenerated. We need to make sure that grub2-mkconfig is run after initrd creation. This needs to be fixed in suse-module-tools. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213754] New: liblinphone_tester and linphone do not start: undefined symbol
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213754 Bug ID: 1213754 Summary: liblinphone_tester and linphone do not start: undefined symbol Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: b-h-dra(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I start linphone,, I get the error message linphone: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol: _ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEE The same applies for liblinphone_tester: liblinphone_tester: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol: _ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEE -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215786] New: VUL-0: CVE-2023-42116: exim: SMTP Challenge Stack-based Buffer Overflow Remote Code Execution Vulnerability
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215786 Bug ID: 1215786 Summary: VUL-0: CVE-2023-42116: exim: SMTP Challenge Stack-based Buffer Overflow Remote Code Execution Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380211/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows remote attackers to execute arbitrary code on affected installations of Exim. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of NTLM challenge requests. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. 06/06/22 – ZDI requested a PSIRT contact. 06/14/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42116 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215785] New: VUL-0: CVE-2023-42115: exim: AUTH Out-Of-Bounds Write Remote Code Execution Vulnerability
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215785 Bug ID: 1215785 Summary: VUL-0: CVE-2023-42115: exim: AUTH Out-Of-Bounds Write Remote Code Execution Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380212/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Sound Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows remote attackers to execute arbitrary code on affected installations of Exim. Authentication is not required to exploit this vulnerability. The specific flaw exists within the smtp service, which listens on TCP port 25 by default. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of a buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. 06/06/22 – ZDI requested a PSIRT contact. 06/14/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42115 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215784] New: VUL-0: CVE-2023-42114: exim: NTLM Challenge Out-Of-Bounds Read Information Disclosure Vulnerability
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215784 Bug ID: 1215784 Summary: VUL-0: CVE-2023-42114: exim: NTLM Challenge Out-Of-Bounds Read Information Disclosure Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380213/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows remote attackers to disclose sensitive information on affected installations of Exim. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of NTLM challenge requests. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated data structure. An attacker can leverage this vulnerability to disclose information in the context of the service account. 06/06/22 – ZDI requested a PSIRT contact. 06/14/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42114 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215809] New: [Tumbleweed][XEN] miss required virtlogd modular libvirt daemons
by bugzilla_noreply＠suse.com 05 Oct '23

05 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215809 Bug ID: 1215809 Summary: [Tumbleweed][XEN] miss required virtlogd modular libvirt daemons Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: xguo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869815 --> https://bugzilla.suse.com/attachment.cgi?id=869815&action=edit supportconfig_logs from openSUSE Tumbleweed XEN domain0 vm host with Snapshot20230926 ## Summary Figure out that miss required virtlogd modular libvirt daemons in openSUSE Tumbleweed XEN domain0 vm host with Snapshot20230926 # for drv in log; do systemctl status virt${drv}d.service; systemctl status virt${drv}d{,-ro,-admin}.socket; done Unit virtlogd.service could not be found. Unit virtlogd.socket could not be found. Unit virtlogd-ro.socket could not be found. Unit virtlogd-admin.socket could not be found. Meanwhile, the same problem does not reproduce in openSUSE Tumbleweed KVM vm host with Snapshot20230926 and SLE15SP6 KVM | XEN vm host with build20.1. ## Reproduce steps 1. Deploy openSUSE Tumbleweed XEN domain0 vm host with Snapshot20230926 built image 2. Check with required virtlogd modular libvirt daemons # for drv in log; do systemctl status virt${drv}d.service; systemctl status virt${drv}d{,-ro,-admin}.socket; done Expected result: There should be required virtlogd modular libvirt daemons in openSUSE Tumbleweed XEN domain0 vm host Real result: Miss required virtlogd modular libvirt daemons in openSUSE Tumbleweed XEN domain0 vm host ## Reproducibility 100% ## Logs Attach required supportconfig log file from openSUSE Tumbleweed XEN domain0 vm host with Snapshot20230926 ## Workaround no -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214163] New: No Sound over HDMI, Intel 13th Generation Framework Laptop
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214163 Bug ID: 1214163 Summary: No Sound over HDMI, Intel 13th Generation Framework Laptop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: me(a)cubiclenate.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is no sound output over HDMI. This includes sound over USB-C devices as well. Forum post: https://forums.opensuse.org/t/no-hdmi-audio-13th-gen-intel-framework-laptop… > aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: 92HD95 Analog [92HD95 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 http://alsa-project.org/db/?f=fae7c5f0dd97fca8274a4f4c135840c441960dfc When I conduct a speaker test on an available HDMI device here are the results: > speaker-test -c2 -l5 -twav -D hdmi:CARD=PCH,DEV=0 speaker-test 1.2.9 Playback device is hdmi:CARD=PCH,DEV=0 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad state. I am hoping I can help provide information to work out the sound issue. Not sure if it is an openSUSE issue, a Kernel issue, lack of support for the 13th Gen Intel or maybe something else. I am not interested in using any other distro so I would rather just do what I can to help work through the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1214835] New: 15.5 patch cant get handled automatically? - openSUSE-SLE-15.5-2023-3413-1
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214835 Bug ID: 1214835 Summary: 15.5 patch cant get handled automatically? - openSUSE-SLE-15.5-2023-3413-1 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: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 15.5, today, yet another undecidable unapplicable patch automatically? also found at: <https://ubuntuforums.org/showthread.php?t=2490356> # zypper patch Reading installed packages... Patch 'openSUSE-SLE-15.5-2023-3413-1' is optional. Use 'zypper in patch:openSUSE-SLE-15.5-2023-3413' to install it, or '--with-optional' to include all optional patches. Resolving package dependencies... Problem: the installed WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch requires 'WebKit2GTK-4.0 = 2.38.6', but this requirement cannot be provided not installable providers: libwebkit2gtk-4_0-37-2.38.6-150400.4.39.1.x86_64[https-download.opensuse.org-788d01d4] libwebkit2gtk-4_0-37-2.38.6-150400.4.39.1.x86_64[repo-oss] Solution 1: deinstallation of WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch Solution 2: do not install patch:openSUSE-SLE-15.5-2023-3419-1.noarch Solution 3: break WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): ^C -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1215498] New: cross-arm-none-newlib-devel got _close() in it but it should not
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215498 Bug ID: 1215498 Summary: cross-arm-none-newlib-devel got _close() in it but it should not Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)welleweerd.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0 Build Identifier: When I use the package to compile my arm none binary, I get: /usr/lib64/gcc/arm-none-eabi/13/ld: /usr/lib64/gcc/arm-none-eabi/13/../../../../arm-none-eabi/lib/thumb/v8-m.main+fp/hard/libg.a(libc_a-syscalls.o): in function `_close': /home/abuild/rpmbuild/BUILD/newlib-4.3.0.20230120/build-regular-dir/arm-none-eabi/thumb/v8-m.main+fp/hard/newlib/../../../../../../newlib/libc/sys/arm/syscalls.c:443: multiple definition of `_close'; CMakeFiles/main.dir/main/system_calls.c.obj:<snip>200/main/system_calls_override.c:28: first defined here I have done some searching but as fare I understand this Unix functions should not be included in this newlib variant. Reproducible: Always Steps to Reproduce: 1.run make dev #with cross-arm-none-newlib-devel and cross-arm-none-gcc13 installed Actual Results: cmake ./CMakeLists.txt -DCMAKE_BUILD_TYPE=Development -Bbuild/build_development -DCMAKE_TOOLCHAIN_FILE=/opt/development/HPC200_TEMP/HPC200/main/cmake/arm-none-eabi-gcc.cmake -GNinja && \ cmake --build build/build_development --parallel 18 --target main -- The C compiler identification is GNU 13.2.1 -- The CXX compiler identification is GNU 13.2.1 -- The ASM compiler identification is GNU -- Found assembler: /usr/bin/arm-none-eabi-gcc -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/arm-none-eabi-gcc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/arm-none-eabi-g++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Srcs: main.cpp;system_calls_override.c -- Configuring done (0.2s) -- Generating done (0.0s) -- Build files have been written to: /opt/development/HPC200_TEMP/HPC200/main/build/build_development [3/3] Linking CXX executable hpc200.elf FAILED: hpc200.elf : && /usr/bin/arm-none-eabi-g++ -mcpu=cortex-m33 -mthumb -mfpu=fpv4-sp-d16 -mfloat-abi=hard -Og -g -gdwarf-2 -Wall -Werror -fdata-sections -ffunction-sections -DUSE_HAL_DRIVER -DSTM32U575xx -mcpu=cortex-m33 -mthumb -mfpu=fpv4-sp-d16 -mfloat-abi=hard -Og -g -gdwarf-2 -Wall -Werror -fdata-sections -ffunction-sections -DUSE_HAL_DRIVER -DSTM32U575xx -mcpu=cortex-m33 -mthumb -mfpu=fpv4-sp-d16 -mfloat-abi=hard -specs=nosys.specs -T/opt/development/HPC200_TEMP/HPC200/main/STM32U575.ld -Wl,-Map=hpc200.map,--cref -Wl,--gc-sections,--no-warn-rwx-segments CMakeFiles/main.dir/main.cpp.obj CMakeFiles/main.dir/system_calls_override.c.obj -o hpc200.elf && : /usr/lib64/gcc/arm-none-eabi/13/ld: /usr/lib64/gcc/arm-none-eabi/13/../../../../arm-none-eabi/lib/thumb/v8-m.main+fp/hard/libg.a(libc_a-syscalls.o): in function `_close': /home/abuild/rpmbuild/BUILD/newlib-4.3.0.20230120/build-regular-dir/arm-none-eabi/thumb/v8-m.main+fp/hard/newlib/../../../../../../newlib/libc/sys/arm/syscalls.c:443: multiple definition of `_close'; CMakeFiles/main.dir/system_calls_override.c.obj:/opt/development/HPC200_TEMP/HPC200/main/system_calls_override.c:1: first defined here /usr/lib64/gcc/arm-none-eabi/13/ld: warning: cannot find entry symbol Reset_Handler; defaulting to 08020000 collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. make: *** [Makefile:10: dev] Fout 1 Results are output of a reduced project and also got: /usr/lib64/gcc/arm-none-eabi/13/ld: warning: cannot find entry symbol Reset_Handler; defaulting to 08020000 Warning that can be ignored I can supply a tarball of the reduced project -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215787] New: VUL-0: CVE-2023-42117: exim: Improper Neutralization of Special Elements Remote Code Execution Vulnerability
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215787 Bug ID: 1215787 Summary: VUL-0: CVE-2023-42117: exim: Improper Neutralization of Special Elements Remote Code Execution Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380210/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows remote attackers to execute arbitrary code on affected installations of Exim. Authentication is not required to exploit this vulnerability. The specific flaw exists within the smtp service, which listens on TCP port 25 by default. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. 06/06/22 – ZDI requested a PSIRT contact. 06/14/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42117 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215789] New: VUL-0: CVE-2023-42119: exim: dnsdb Out-Of-Bounds Read Information Disclosure Vulnerability
by bugzilla_noreply＠suse.com 04 Oct '23

04 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215789 Bug ID: 1215789 Summary: VUL-0: CVE-2023-42119: exim: dnsdb Out-Of-Bounds Read Information Disclosure Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380208/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of Exim. Authentication is not required to exploit this vulnerability. The specific flaw exists within the smtp service, which listens on TCP port 25 by default. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the service account. 06/22/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42119 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212962] New: caja file manager not launching
by bugzilla_noreply＠suse.com 03 Oct '23

03 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1212962 Bug ID: 1212962 Summary: caja file manager not launching Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: balping314(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When using the MATE desktop (with marco window manager) and trying to start caja, I get the following error: Could not register the application: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying $ caja --version MATE caja 1.26.1 I'm running Tumbleweed 20230701. Without caja, the DE is basically unusable. Possibly the same bug in Ubuntu: https://bugs.launchpad.net/ubuntu-mate/+bug/2013284 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215636] New: virtlxcd dying constantly killing all containers with it
by bugzilla_noreply＠suse.com 03 Oct '23

03 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215636 Bug ID: 1215636 Summary: virtlxcd dying constantly killing all containers with it Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: m.szczepaniak.000(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, since couple of updates I've been having issue with lxd containers in libvirt/virtmanager. At random times, previously once per day now even more often, they're being killed for no reason. No significant errors in logs whatsoever. While investigating i came across virtlxcd and noticed it has 2 hour timeout, and every time the service dies it takes all containers with it. I don't know why it has timeout, but I think it's intentional what I don't think is intentional is killing all containers so please advise -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1215641] New: XDG Portal File Picker not working on latest snapshot
by bugzilla_noreply＠suse.com 03 Oct '23

03 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215641 Bug ID: 1215641 Summary: XDG Portal File Picker not working on latest snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: socvirnyl.estela(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Snapshot 20230921 has a bug where a user cannot open a filechooser/filepicker. A snippet of the log through `journalctl -f` is shown below: ``` Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Server is missing xdg_foreign support Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Failed to export handle, could not set transient for Sep 24 12:29:37 sentient-slate firefox-bin[3253]: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.FileChooser” on object at path /org/freedesktop/portal/desktop ``` I have to rollback for now to a previous snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1214704] New: partprobe not included in kiwi-partitions-lib.sh
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214704 Bug ID: 1214704 Summary: partprobe not included in kiwi-partitions-lib.sh Classification: openSUSE Product: openSUSE Leap Micro Version: 5.5 Hardware: aarch64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kjong+lists(a)neobits.nl QA Contact: jalausuch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 869053 --> https://bugzilla.suse.com/attachment.cgi?id=869053&action=edit Photo of failed installation of MicroOS I flashed the "RaspberryPi Container Host (777.3 MiB)" and after booting it failed with the following error (see attached photo). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215805] New: keine Authentifizierung per dovecot nach update; PAM adding faulty module
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215805 Bug ID: 1215805 Summary: keine Authentifizierung per dovecot nach update; PAM adding faulty module Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: Robert(a)Divko.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- nach update heute früh ca. 7.00 MET (glib, ….) keine Authentifizierung per dovecot mehr möglich. Senden von Mail und login per shell möglich. in /var/log/ 2023-09-28T12:21:18.311949+02:00 outof auth: PAM adding faulty module: /lib64/security/pam_umask.so 2023-09-28T12:21:18.311979+02:00 outof auth: PAM unable to dlopen(/lib64/security/pam_warn.so): /lib64/security/pam_warn.so: failed to map segment from shared object sicherheitshalber apparmor gestoppt, disabled, reboot, kein Effekt -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1214391] New: vbox:kmp fails with kernel 6.4.10
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214391 Bug ID: 1214391 Summary: vbox:kmp fails with kernel 6.4.10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: Larry.Finger(a)gmail.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: llrainey15(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- It looks like since commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… (present in 6.4.10), virtualbox needs to include net/gso.h too: > vboxnetflt/linux/VBoxNetFlt-linux.c:1577:40: error: implicit declaration of function 'skb_gso_segment'; did you mean 'skb_gso_reset'? in: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Can you take care of it? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213986] New: SeaMonkey: update to 2.53.17
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213986 Bug ID: 1213986 Summary: SeaMonkey: update to 2.53.17 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: Andreas.Stieger(a)gmx.de, factory-mozilla(a)lists.opensuse.org, maintenance(a)opensuse.org, meissner(a)suse.com, qa-bugs(a)suse.de, security-team(a)suse.de, wolfgang.engel(a)suse.com Depends on: 1207332, 1209994 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1209994 +++ Please update the SeaMonkey package in Leap 15.4 and 15.5 to the SeaMonkey 2.53.17 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey> The latest version of SeaMonkey, 2.53.17, released on 4 August 2023, contains new backports of important security fixes from Firefox 102.11 and Thunderbird 102.11 ESR. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215845] New: displaymanager.service does not restart on failure
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215845 Bug ID: 1215845 Summary: displaymanager.service does not restart on failure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: seife(a)novell.slipkontur.de QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- seife@strolchi:~> rpm -qf /usr/lib/systemd/system/display-manager.service xdm-1.1.14-4.3.x86_64 seife@strolchi:~> grep OnFai /usr/lib/systemd/system/display-manager.service OnFailure=plymouth-quit.service I killed the lightdm login screen with ctrl-alt-backspace and it did not come back again. Investigating, I found this in the journal: Sep 30 18:34:57 strolchi lightdm[1475]: pam_unix(lightdm-greeter:session): session closed for user lightdm Sep 30 18:34:57 strolchi systemd[1]: session-1.scope: Deactivated successfully. Sep 30 18:34:57 strolchi systemd[1]: session-1.scope: Consumed 1.622s CPU time. Sep 30 18:34:57 strolchi systemd-logind[1135]: Session 1 logged out. Waiting for processes to exit. Sep 30 18:34:57 strolchi systemd-logind[1135]: Removed session 1. Sep 30 18:34:57 strolchi display-manager[1353]: Starting service lightdm Sep 30 18:34:57 strolchi systemd[1]: display-manager.service: Main process exited, code=exited, status=1/FAILURE Sep 30 18:34:57 strolchi systemd[1]: display-manager.service: Failed with result 'exit-code'. Sep 30 18:34:58 strolchi systemd[1]: display-manager.service: Triggering OnFailure= dependencies. Sep 30 18:34:58 strolchi systemd[1]: display-manager.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found. Sep 30 18:34:58 strolchi systemd[1]: display-manager.service: Consumed 1.290s CPU time. I think however that the OnFailure failure is not the reason for the problem but that the display-manager.service should have a "Restart=on-failure" line. current tumbleweed, xfce4 desktop, lightdm login manager strolchi:~ # head -3 /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20230927" ID="opensuse-tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215812] New: cross-ppc64le-gcc no longer built for SLE
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215812 Bug ID: 1215812 Summary: cross-ppc64le-gcc no longer built for SLE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The devel:gcc project no longer has cross-compilers built for SLE. We use these cross-compilers to test building the kernel on different platforms. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215444] New: Tracking bug: split libQgpsmm from gpsd-devel
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215444 Bug ID: 1215444 Summary: Tracking bug: split libQgpsmm from gpsd-devel 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: --- gpsd-devel pulls Qt5 devel packages for linking to libQgpsmm.so. This also means pulling Qt5 when building (what will become) Plasma 6. In most dependent packages, the library is unneeded. Preliminary work to split the headers and libraries needing Qt is done in https://build.opensuse.org/package/show/home:krop:branches:Application:Geo/… Dependent packages: From Application:Geo - foxtrotgps: It doesn't need Qgpsmm but uses %make_jobs, which is incorrect. - merkaartor: the package split revealed merkaartor it has a dependency on QtNetwork for 3rdparty/qtsingleapplication-2.6_1-opensource/ - navit: unresolvable in Application:Geo - viking: builds fine From openSUSE:Factory - collectd: builds fine - gpredict: builds fine - ntpsec: builds fine - ocli: builds fine - stellarium: needs a BuildRequires: pkgconfig(Qgpsmm) - uhd: builds fine -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215285] New: [RPi3] dwc2 3f980000.usb: dwc2_hc_halt() Channel can't be halted
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215285 Bug ID: 1215285 Summary: [RPi3] dwc2 3f980000.usb: dwc2_hc_halt() Channel can't be halted Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3568327/modules/jour nal_check/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: ivan.ivanov(a)suse.com Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [journal_check](https://openqa.opensuse.org/tests/3568327/modules/journal_ch… New kernel 6.5.2 shows the following trace in journal on RPi3: dwc2 3f980000.usb: dwc2_hc_halt() Channel can't be halted ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20221024](https://openqa.opensuse.org/tests/2833524) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215788] New: VUL-0: CVE-2023-42118: exim: libspf2 Integer Underflow Remote Code Execution Vulnerability
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215788 Bug ID: 1215788 Summary: VUL-0: CVE-2023-42118: exim: libspf2 Integer Underflow Remote Code Execution Vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/380209/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: wullinger(a)rz.uni-kiel.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Exim libspf2. Authentication is not required to exploit this vulnerability. The specific flaw exists within the parsing of SPF macros. When parsing SPF macros, the process does not properly validate user-supplied data, which can result in an integer underflow before writing to memory. An attacker can leverage this vulnerability to execute code in the context of the service account. 06/06/22 – ZDI requested a PSIRT contact. 06/14/22 – ZDI reported the vulnerability to the vendor. 04/25/23 – ZDI asked for an update. 04/25/23 – The vendor asked us to re-send the reports. 05/10/23 – ZDI sent the vulnerability to the vendor. 09/25/23 – ZDI asked for an update and informed the vendor that we intend to publish the case as a zero-day advisory on 09/27/23. -- Mitigation: Given the nature of the vulnerability, the only salient mitigation strategy is to restrict interaction with the application. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42118 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215819] New: Kaffeine fails to reproduce sat card output after recent update (fails with FE_SET_TONE). Also claims "firmware did not run".
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215819 Bug ID: 1215819 Summary: Kaffeine fails to reproduce sat card output after recent update (fails with FE_SET_TONE). Also claims "firmware did not run". Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed 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: --- entropy@localhost:~> kaffeine 28-09-23 20:36:30.739 [Warning ] QCommandLineParser: already having an option named "h" 28-09-23 20:36:30.739 [Warning ] QCommandLineParser: already having an option named "help-all" 28-09-23 20:36:30.739 [Warning ] QCommandLineParser: already having an option named "v" entropy@localhost:~> kaffeine 28-09-23 20:37:01.002 [Warning ] QCommandLineParser: already having an option named "h" 28-09-23 20:37:01.002 [Warning ] QCommandLineParser: already having an option named "help-all" 28-09-23 20:37:01.002 [Warning ] QCommandLineParser: already having an option named "v" 28-09-23 20:37:01.267 [Info ] kaffeine.dvb: Using built-in dvb device manager 28-09-23 20:37:02.924 [Info ] kaffeine.dev: Found dvb device P14f188800070f038: Montage Technology M88RS6000 28-09-23 20:37:02.934 [Info ] kaffeine.dev: Found dvb device P14f188800070f038: Silicon Labs Si2168 28-09-23 20:37:07.496 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile [00007f8484001140] mjpeg demux error: cannot peek Registering, reproducing, etc, does not work, no sound either. Because of "cannot peek" I suspect a Mesa issue, but I am not sure. From journalctl: set 28 20:34:25 localhost plasmashell[5043]: [00005587843c14a0] main playlist: playlist is empty set 28 20:34:25 localhost systemd[2946]: Started Lettore multimediale VLC - Lettore multimediale. set 28 20:34:25 localhost plasmashell[5043]: [0000558784327ae0] main libvlc: Esecuzione di vlc con l'interfaccia predefinita. Usa 'cvlc' per utilizzare vlc senza interfaccia. set 28 20:34:21 localhost systemd[2946]: app-org.kde.kaffeine-4f441e95ac734179a763b5507078154e.scope: Consumed 9.919s CPU time. set 28 20:34:21 localhost kded5[3142]: Service ":1.95" unregistered set 28 20:34:21 localhost ksmserver[3576]: [00007fd02c007420] mjpeg demux error: cannot peek set 28 20:34:17 localhost ksmserver[3576]: [00007fd02c007420] mjpeg demux error: cannot peek set 28 20:34:17 localhost ksmserver[3576]: 28-09-23 20:34:17.396 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:34:16 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:34:15 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:34:15 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:34:14 localhost ksmserver[3576]: [00007fd02c007420] mjpeg demux error: cannot peek set 28 20:34:14 localhost ksmserver[3576]: 28-09-23 20:34:14.896 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:34:13 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:34:12 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:34:12 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:34:11 localhost ksmserver[3576]: [00007fd02c007420] mjpeg demux error: cannot peek set 28 20:34:11 localhost ksmserver[3576]: 28-09-23 20:34:11.796 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:34:10 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:34:09 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:34:09 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:33:43 localhost ksmserver[3576]: [00007fd02d00d200] mjpeg demux error: cannot peek set 28 20:33:43 localhost ksmserver[3576]: 28-09-23 20:33:43.696 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:33:42 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:33:41 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:33:41 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:33:38 localhost ksmserver[3576]: [00007fd02c007700] mjpeg demux error: cannot peek set 28 20:33:38 localhost ksmserver[3576]: 28-09-23 20:33:38.896 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:33:37 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:33:36 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:33:36 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:33:34 localhost ksmserver[3576]: [00007fd0140015e0] mjpeg demux error: cannot peek set 28 20:33:34 localhost ksmserver[3576]: 28-09-23 20:33:34.696 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:33:33 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:33:32 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:33:32 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state set 28 20:33:28 localhost ksmserver[3576]: 28-09-23 20:33:28.196 [Critical] kaffeine.dev: FE_SET_TONE: Risorsa temporaneamente non disponibile set 28 20:33:27 localhost kernel: m88ds3103 13-0069: firmware did not run set 28 20:33:25 localhost kernel: m88ds3103 13-0069: downloading firmware from file 'dvb-demod-m88rs6000.fw' set 28 20:33:25 localhost kernel: m88ds3103 13-0069: found a 'Montage Technology M88RS6000' in cold state -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215826] New: kernel-default-6.5.4 won't boot; can't activate swap
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215826 Bug ID: 1215826 Summary: kernel-default-6.5.4 won't boot; can't activate swap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869836 --> https://bugzilla.suse.com/attachment.cgi?id=869836&action=edit Output of hwinfo (with 6.4.12) I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. The new kernel has problems booting or resuming from suspend. In particular, when booting, about half the time the kernel is unable to activate the swap device. The last message printed to the console is "a start job is running for /dev/sda2" (the device in question being my swap partition) and a timer that counts up. I've let it run for as long as 10 hours but it never finishes. Resuming from suspend also doesn't work. In this case the computer simply locks up or powers off. (I haven't tested hibernate.) I had a similar problem (only with resuming from suspend, not with activating swap space) with kernel-default-5.19.1; not sure if this is related. See Bug 1202571. Downgrading to the 6.4.12 kernel works around the issue. I am attaching the output of hwinfo (using the 6.4.12 kernel). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215774] New: during installation of pitivi you run into librosa requirements which cannot be fullfilled because a dependency is missing
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215774 Bug ID: 1215774 Summary: during installation of pitivi you run into librosa requirements which cannot be fullfilled because a dependency is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Problem: nothing provides '(python311-pooch >= 1.0 with python311-pooch < > 1.7)' needed by the to be installed python311-librosa-0.10.1-1.4.noarch > Solution 1: do not install pitivi-2023.03-1.3.x86_64 > Solution 2: break python311-librosa-0.10.1-1.4.noarch by ignoring some of its > dependencies the issue for me is minor and mainly due to the fact that I do not know if the functionality would be afflicted if I ignore. But other users may appreciate if this will be fixed (apparently the reason explained by a user (arvidjaar(a)gmail.com) is that "librosa failed to build against current pooch". So maybe this will be corrected automatically during future updates.) Feel free to indicate one solution of the above (one or two), so that other users may find it and know what to do and how to proceed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215741] New: Warning/error message "Transport endpoint is not connected" in journald after cron job run by root
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215741 Bug ID: 1215741 Summary: Warning/error message "Transport endpoint is not connected" in journald after cron job run by root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: claude.diderich(a)sigmadream.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a cron job owned by root finishes, a warning + failure message is logged to the journal file: Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir(a)0.service: Failed with result 'exit-code'. Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir(a)0.service: Control process exited, code=exited, status=1/FAILURE Sep 27 00:15:12 jasper systemd-user-runtime-dir[40960]: Failed to remove runtime directory /run/user/0 (after unmounting): Transport endpoint is not connected Sep 27 00:15:01 jasper CRON[40871]: pam_unix(crond:session): session closed for user root Sep 27 00:15:01 jasper CRON[40871]: (root) CMDEND (/usr/lib/cron/run-crons >/dev/null 2>&1) Sep 27 00:15:01 jasper CRON[40912]: (root) CMD (/usr/lib/cron/run-crons >/dev/null 2>&1) The cron job is executed correctly. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212486] Deja-dup (Gnome backup) insists on installing an already installed duplicity
by bugzilla_noreply＠suse.com 30 Sep '23

30 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1212486 https://bugzilla.suse.com/show_bug.cgi?id=1212486#c8 elhoy <bugs(a)elhoy.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs(a)elhoy.co.uk --- Comment #8 from elhoy <bugs(a)elhoy.co.uk> --- Just another user-experience.... same problem for possibly almost year now (sorry, I've not tracked exact time). Successful temporary workaround today per comment 1 (rpm -e --nodeps duplicity, then run backup and allow install of duplicity). https://bugzilla.opensuse.org/show_bug.cgi?id=1212486#c1 However, this needs repeating for each run of backup. -- You are receiving this mail because: You are on the CC list for the bug.

1 0