June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226107] New: PackageKit "openSUSE-SLE-15.6-2024-1950-1" ("glib2") throws error
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226107 Bug ID: 1226107 Summary: PackageKit "openSUSE-SLE-15.6-2024-1950-1" ("glib2") throws error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: Gunner.Gewiss(a)posteo.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hello! I have openSUSE Leap 15.6, almost current patch level. There is PackageKit showing update "openSUSE-SLE-15.6-2024-1950-1" ("security update for glib2") — but when running it throws error: "das installierte gio-branding-openSUSE-42.1-lp156.8.3.noarch erfordert 'libgio-2_0-0 = 2.78.3', aber diese Anforderung kann nicht bereitgestellt werden". Details of system: gunnersson@tulicube:~> sudo zypper pa -i | grep -i 'libgio-2_0-0' v | openSUSE-Update-SLE | libgio-2_0-0 | 2.78.6-150600.4.3.1 | x86_64 i+ | openSUSE-Distribution-OSS | libgio-2_0-0 | 2.78.3-150600.2.2 | x86_64 I am wondering… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222534] No wired network after hibernation
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222534 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226014] "zypper ps -s" is confused by snaps
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226014 https://bugzilla.suse.com/show_bug.cgi?id=1226014#c5 Vadim Krevs <vkrevs(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(vkrevs(a)yahoo.com) | --- Comment #5 from Vadim Krevs <vkrevs(a)yahoo.com> --- Created attachment 875382 --> https://bugzilla.suse.com/attachment.cgi?id=875382&action=edit Requested zypper debug file Done. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226105] Snapshot 20240606 breaks libvirt NAT networks
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226105 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |santiago.zarate(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226105] New: Snapshot 20240606 breaks libvirt NAT networks
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226105 Bug ID: 1226105 Summary: Snapshot 20240606 breaks libvirt NAT networks Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: eyadlorenzo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Found after updating and trying to use a VM. The VM is connected to the NAT network but it can't connect to the external net. It does not happen on 20240605. I suspect it's apparmor fault. On the new snapshot (which, by the way, had apparmor profiles updates) I get these error on the journal: --- mag 28 22:12:57 xxx virtqemud[15293]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied mag 28 22:12:57 xxx virtqemud[15293]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied mag 28 22:12:57 xxx virtqemud[15293]: Failed to open file '/sys/kernel/security/apparmor/profiles': Permission denied mag 28 22:12:57 xxx virtqemud[15293]: Failed to read AppArmor profiles list '/sys/kernel/security/apparmor/profiles': Permission denied --- While I don't get them on the 20240605 snapshot. I rolled back and it works again. On the old snapshot, running zypper dup I get: --- The following 111 packages are going to be upgraded: apparmor-abstractions apparmor-docs apparmor-parser apparmor-parser-lang apparmor-profiles apparmor-utils apparmor-utils-lang chrony chrony-pool-openSUSE corepack21 crun dialog dialog-lang fakeroot gnome-control-center gnome-control-center-color gnome-control-center-goa gnome-control-center-lang gnome-control-center-user-faces gnome-control-center-users gnome-shell-search-provider-seahorse go1.21-doc go1.21-libstd hugo hugo-bash-completion just just-bash-completion just-fish-completion libapparmor-devel libapparmor1 libbpf1 libcjson1 libdialog15 libfreerdp2-2 libkrun1 libndctl6 libsamba-policy0-python3 libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 libsvn_auth_gnome_keyring-1-0 libtelepathy-glib0 libtommath1 libtommath1-x86-64-v3 libvirt libvirt-client libvirt-client-qemu libvirt-daemon libvirt-daemon-common libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-storage-core libvirt-daemon-driver-storage-disk libvirt-daemon-driver-storage-iscsi libvirt-daemon-driver-storage-iscsi-direct libvirt-daemon-driver-storage-logical libvirt-daemon-driver-storage-mpath libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-scsi libvirt-daemon-lock libvirt-daemon-log libvirt-daemon-plugin-lockd libvirt-daemon-proxy libvirt-daemon-qemu libvirt-libs libwinpr2-2 man nodejs21 nodejs21-devel npm21 openSUSE-release openSUSE-release-appliance-custom patterns-base-apparmor patterns-base-base patterns-base-basesystem patterns-base-basic_desktop patterns-base-documentation patterns-base-enhanced_base patterns-base-minimal_base patterns-base-sw_management patterns-base-x11 patterns-base-x11_enhanced podman python3-apparmor python311-jaraco.functools python311-libvirt-python python311-platformdirs ruby3.3-rubygem-ruby-augeas samba samba-ad-dc-libs samba-client samba-client-libs samba-libs samba-libs-python3 samba-python3 seahorse seahorse-lang subversion subversion-bash-completion subversion-perl typelib-1_0-TelepathyGlib-0_12 xen-libs xwayland The following 10 patterns are going to be upgraded: apparmor base basesystem basic_desktop documentation enhanced_base minimal_base sw_management x11 x11_enhanced The following product is going to be upgraded: openSUSE Tumbleweed 20240605-0 -> 20240606-0 The following NEW package is going to be installed: libkrunfw4 The following package is going to be REMOVED: libkrunfw3 --- Let me know if you need any more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226055] NVIDIA driver 550.90 broken, plus no boot option for kernel 6.9.3
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226055 https://bugzilla.suse.com/show_bug.cgi?id=1226055#c9 Gerald Chen <gerald_chen(a)foxmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #9 from Gerald Chen <gerald_chen(a)foxmail.com> --- Hey guys! I worked this out! And the real cause behind these are truly bizarre. As the title mentioned, there was no boot option for kernel 6.9.3, albeit it had been installed, and I had done `dracut -f`. And the NVIDIA driver 550.90 was made for kernel 6.9.3, as the full name of the package mentioned in #3 by Mr. Dirsch was "nvidia-driver-G06-kmp-default-550.90.07_k6.9.3_1-23.1.x86_64". I was always guided to boot in kernel 6.9.1, so the NVIDIA driver could not be properly loaded, I guess. So while investigating the output of `update-bootloader` as mentioned in the original post, I happened to notice that grub menu could not be updated because of an error of /etc/grub.d/00_tuned, which requires /etc/tuned, which was deleted by me because I don't use tuned, which prevented boot option for kernel 6.9.3 to be generated. So I reinstalled tuned to recreate /etc/tuned and did `update-bootloader` and `dracut` things and rebooted. Voilà! My system went back to normal and the NVIDIA driver got properly loaded. Thanks go to Mr. Dirsch and Mr. Bradnick for helping these out. I'm changing the status to FIXED. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226106] New: [Build 20240607] openQA test fails in bci_test_podman
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226106 Bug ID: 1226106 Summary: [Build 20240607] openQA test fails in bci_test_podman Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4257401/modules/bci_ test_podman/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation wait_serial expected: qr/nEDE1-\d+-/u # Result: dns v1.0.0\ngo: downloading github.com/phayes/freeport v0.0.0-20220201140144-74d24b5ae9f5\ngo: downloading github.com/DATA-DOG/go-sqlmock v1.5.2\ngo: downloading github.com/pmezard/go-difflib v1.0.0\ngo: downloading github.com/Shopify/logrus-bugsnag v0.0.0-20171204204709-577dee27f20d\ngo: downloading github.com/bshuster-repo/logrus-logstash-hook v1.0.0\ngo: downloading github.com/bugsnag/bugsnag-go v0.0.0-20141110184014-b1d153021fcd\ngo: downloading github.com/docker/libtrust v0.0.0-20150114040149-fa567046d9b1\ngo: downloading github.com/gorilla/handlers v1.5.1\ngo: downloading github.com/yvasiyarov/gorelic v0.0.0-20141212073537-a9bba5b9ab50\ngo: downloading github.com/miekg/dns v1.1.25\ngo: downloading github.com/docker/go-events v0.0.0-20190806004212-e31b211e4f1c\ngo: downloading github.com/gomodule/redigo v1.8.2\ngo: downloading github.com/bugsnag/panicwrap v0.0.0-20151223152923-e2c28503fcd0\ngo: downloading github.com/yvasiyarov/go-metrics v0.0.0-20140926110328-57bccd1ccd43\ngo: downloading github.com/yvasiyarov/newrelic_platform_go v0.0.0-20140908184405-b21fdbd4370f\ngo: downloading github.com/hashicorp/golang-lru v0.5.4\ngo: downloading github.com/bugsnag/osext v0.0.0-20130617224835-0dd3f918b21b\nmake: *** [Makefile:107: test-unit] Error 1\n') --------------------------- Captured stderr teardown --------------------------- time="2024-06-07T19:54:54-04:00" level=warning msg="StopSignal SIGTERM failed to stop container distracted_poincare in 10 seconds, resorting to SIGKILL" ---------------------------- Captured log teardown ----------------------------- DEBUG pytest_container:plugin.py:55 logs from container fa7589f1f012f74e335c1e7024b30f0dfe1ca9ce977538b4608f8b431508ccd4: DEBUG pytest_container:container.py:1199 Removing container fa7589f1f012f74e335c1e7024b30f0dfe1ca9ce977538b4608f8b431508ccd4 via podman --------------------------- Captured stderr teardown --------------------------- time="2024-06-07T19:58:40-04:00" level=warning msg="StopSignal SIGTERM failed to stop container charming_matsumoto in 10 seconds, resorting to SIGKILL" ---------------------------- Captured log teardown ----------------------------- DEBUG pytest_container:plugin.py:55 logs from container 03490cf6f1ad0370abe57c9492cc8d42198af2d5e73b13356cb296cf22d3c5d3: DEBUG pytest_container:container.py:1199 Removing container 03490cf6f1ad0370abe57c9492cc8d42198af2d5e73b13356cb296cf22d3c5d3 via podman --------------------------- Captured stderr teardown --------------------------- time="2024-06-07T20:02:31-04:00" level=warning msg="StopSignal Rerunning previous successful snapshots results in the same error openQA test in scenario opensuse-Tumbleweed-BCI-x86_64-bci_golang_podman@64bit fails in [bci_test_podman](https://openqa.opensuse.org/tests/4257401/modules/bci_test… ## Test suite description The base test suite is used for job templates defined in YAML documents. It has no settings of its own. ## Reproducible Fails since (at least) Build [20240607](https://openqa.opensuse.org/tests/4256690) ## Expected result Last good: [20240606](https://openqa.opensuse.org/tests/4254174) (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 0

[Bug 1225943] New: [Build 20240603] systemd_nspawn: systemd-run -tM test1 /bin/bash -c date returns 1
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225943 Bug ID: 1225943 Summary: [Build 20240603] systemd_nspawn: systemd-run -tM test1 /bin/bash -c date returns 1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4247521/modules/syst emd_nspawn/steps/134 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 This test is newly failing since the update to systemd 255.7 The test code leading up to this is: systemctl start systemd-nspawn@test1 systemctl status systemd-nspawn@test1 # Wait for container to boot systemd-run -tM test1 /bin/bash -c date" openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in [systemd_nspawn](https://openqa.opensuse.org/tests/4247521/modules/systemd_n… ## Test suite description Maintainer: slindomansilla(a)suse.de. Mainly post-installation console extra tests. ## Reproducible Fails since (at least) Build [20240603](https://openqa.opensuse.org/tests/4246337) ## Expected result Last good: [20240531](https://openqa.opensuse.org/tests/4242031) (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 2

[Bug 1225809] [Build 20240531] latest glibc changes makes steam uninstallable
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225809 https://bugzilla.suse.com/show_bug.cgi?id=1225809#c10 Roman <romans32401(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Roman <romans32401(a)gmail.com> --- The last update fixed the dependency issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226055] New: NVIDIA driver 550.90 broken, plus no boot option for kernel 6.9.3
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226055 Bug ID: 1226055 Summary: NVIDIA driver 550.90 broken, plus no boot option for kernel 6.9.3 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: gerald_chen(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi. So NVIDIA driver 550.90 came out in Tumbleweed repo so I upgraded (system in snapshot 20240531) and things broke. Rebooted and NVIDIA drivers could not be loaded. `nvidia-smi` said `NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.`, though NVIDIA drivers were indeed installed. No `nvidia_drm` in `lsmod`. Tried `dracut --force --regenerate-all` and no improvement. Tried re-installing the drivers and re-enrolling the public key but no help. Also tried disabling secure boot to sadly see no difference. Went back to the pre snapshot before the update and found that even the read-only snapshot selection menu in grub reported the kernel version to be 6.9.3, `uname -r` after booting into the snapshot still said 6.9.1. In fact that's the case in several snapshots. And 6.9.3 could not be found in `YaST Boot Loader` > `Bootloader Options` > `Default Boot Section`. Tried `update-bootloader --reinit` and `update-bootloader --refresh` then reboot and no improvement. I’ve updated to 20240605 snapshot and it's still broken. -- You are receiving this mail because: You are on the CC list for the bug.

1 4