July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213701] New: VUL-0: CVE-2023-30577: amanda: Improper argument checking for runtar.c
by bugzilla_noreply＠suse.com 04 Aug '23

04 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213701 Bug ID: 1213701 Summary: VUL-0: CVE-2023-30577: amanda: Improper argument checking for runtar.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/373489/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: danilo.spinella(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- AMANDA (Advanced Maryland Automatic Network Disk Archiver) before tag-community-3.5.4 mishandles argument checking for runtar.c, a different vulnerability than CVE-2022-37705. References: https://github.com/zmanda/amanda/releases/tag/tag-community-3.5.4 https://github.com/zmanda/amanda/pull/228 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213769] New: Cannot create or import vpnc VPN connections in NetworkManager
by bugzilla_noreply＠suse.com 04 Aug '23

04 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213769 Bug ID: 1213769 Summary: Cannot create or import vpnc VPN connections in NetworkManager 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: Network Assignee: screening-team-bugs(a)suse.de Reporter: Jeff.Berntsen(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36 Build Identifier: Cannot create or import vpnc VPN connections in NetworkManager. The VPN creation form comes up normally, prefilled with information if importing a configuration, but the save button is always grayed out. Reproducible: Always Steps to Reproduce: 1. Create or import a vpnc VPN configuration in Network Manager 2. Attempt to save the configuration 3. Actual Results: Save button is grayed out preventing saving of the created or imported configuration. Expected Results: Save button should be active, allowing the configuration to be saved. Able to work around the problem by replacing the NetworkManager-vpnc and NetworkManger-vpnc-gnome packages by replacing them with the older packages from Leap 15.4. The save button works as expected in those versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213438] New: "green screen" after kernel-update to vmlinuz-5.14.21-150500.55.7-default
by bugzilla_noreply＠suse.com 03 Aug '23

03 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213438 Bug ID: 1213438 Summary: "green screen" after kernel-update to vmlinuz-5.14.21-150500.55.7-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: guenter.halt(a)halt-hoenow.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- after kernel-update and other packages from 18.07.2023 the system boots. The display-manger shows the list of users and without action the Display is green only (like blue screen of windows). The whole computer is frozen. No reaktion of <ctrl><alt><delete> , no reaktion of <ctrl><alt><F1> On the same PC a second installation of leap15.5 is installed. I copied the complete directory /boot from the 2.system to my work-system. Now it works, however all private services are removed from /etc/systemd/system. vmlinux is a link to vmlinuz-5.14.21-150500.55.7-default initrd a link to initrd-5.14.21-150500.55.7-default However uname -r showes 5.14.21-150500.53-default not 5.14.21-150500.55 ???? -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1213569] New: Crash before login
by bugzilla_noreply＠suse.com 03 Aug '23

03 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213569 Bug ID: 1213569 Summary: Crash before login Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: wsp(a)spickermann-d.de QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868381 --> https://bugzilla.suse.com/attachment.cgi?id=868381&action=edit journalctl, hwinfo and inxi Similar to https://bugzilla.opensuse.org/show_bug.cgi?id=1213304 but with different kernels and Leap 15.5: 5.14.21-150500.53-default (works) 5.14.21-150500.55.7-default (didn't work) Immediately after displaying the login screen of sddm the screen goes black or chaotic (like lost sync on old analog monitors) and sometimes the system reboots and often the keyboard LED don't react. Adding a second monitor (HDMI) made the system usable (two different ones tried). I'll add an "inxi -G -a" output. I'll add the "journalctl -b-1" of a 55.7-run and a "hwinfo --short" too Now I have a running 55.7-system again using the hint of "Comment 2" in id=1213304 (after adding a missing "amdgpu/" in the "cp" command) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213392] New: snapd (providing snap) causes long delay in boot process
by bugzilla_noreply＠suse.com 03 Aug '23

03 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213392 Bug ID: 1213392 Summary: snapd (providing snap) causes long delay in boot process Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868244 --> https://bugzilla.suse.com/attachment.cgi?id=868244&action=edit dmesg of hp i5 using wicked network service (other system using Network Manager is slightly better) A delay in boot process started to happen about a month or two. I was suspecting kernel however a similar post on Reddit shows it something related to snapd installation. (on a i5 system/8G RAM/802.11ac 5ghz connection using rtl8821cu-kmp-default) systemd-analyze blame 30.196s wicked.service 3.121s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.device 3.121s dev-disk-by\x2duuid-0A20\x2d0890.device 3.121s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device to reproduce: 1) install snapd using instructions at https://en.opensuse.org/Snap 2) reboot what happens: system starts to boot normally and at half of the boot process, it completely stops for at least 15 seconds, 30 seconds max observed. what should happen: system should boot normally, perhaps couple or a bit more seconds added to boot process (snapd uses squashfs containers) I reported it to snapd maintainers at: https://bugs.launchpad.net/snapd/+bug/2027915 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213366] New: Steam sync not working in Lutris on Leap 15.5 (and likely also 15.4)
by bugzilla_noreply＠suse.com 03 Aug '23

03 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213366 Bug ID: 1213366 Summary: Steam sync not working in Lutris on Leap 15.5 (and likely also 15.4) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: marix(a)marix.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Syncing the Steam library does not work in Lutris on Leap 15.5. I get the following error: 2023-07-16 17:47:05,984: Error while completing task <bound method BaseService.reload of <steam.SteamService object at 0x7f7b64cd87e0 (lutris+services+steam+SteamService at 0x557eb4432500)>>: <class 'KeyError'> 'contentstatsid' File "/usr/lib/python3.6/site-packages/lutris/util/jobs.py", line 34, in target result = self.function(*args, **kwargs) File "/usr/lib/python3.6/site-packages/lutris/services/base.py", line 85, in reload self.add_installed_games() File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 159, in add_installed_games for steamapps_path in self.steamapps_paths: File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 154, in steamapps_paths return get_steamapps_paths() File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line 170, in get_steamapps_paths return steam.steam().get_steamapps_dirs() File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 243, in get_steamapps_dirs library_config = self.get_library_config() File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 149, in get_library_config return read_library_folders(self.steam_data_dir) File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line 161, in read_library_folders library["libraryfolders"].pop("contentstatsid") Well, most users will only get a popup that says "contentstatsid" and notice the sync not working. But this backtrace is shown on the terminal when starting Lutris from there. The issue has been tracked upstream as https://github.com/lutris/lutris/issues/4175 and is fixed in 0.5.10. But Leap still ships 0.5.9. The specific commit fixing it seems to be https://github.com/lutris/lutris/commit/072e72a4aefd91101b79dd05d8ce9f100a4…. If I manually apply the fix from the commit on my system, the issue is resolved. We might want to consider applying the patch during packaging or just upgrading the Leap version. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213786] New: [kubeadm] openSUSE kubeReleaseBucket Server outdated
by bugzilla_noreply＠suse.com 03 Aug '23

03 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213786 Bug ID: 1213786 Summary: [kubeadm] openSUSE kubeReleaseBucket Server outdated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: All OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- Running 'kubeadm init' from kubernetes1.24-kubeadm fails with the error message: [ERROR KubeletVersion]: the kubelet version is higher than the control plane version. This is not a supported version skew and may lead to a malfunctional cluster. Kubelet version: "1.24.15" Control plane version: "1.23.4" Reason: kubeadm queries a release version server which resides at https://dl.k8s.io/release while for upstream but the Leap/TW kubeadm package has patched to https://kubic.opensuse.org/release. This responds to a requrest for https://kubic.opensuse.org/release/stable-1.txt with 1.23.4 although SUSE already provides version 1.27.3. Since this appears to announce that the containers provided by openSUSE are older than the kubeadm version, it refuses to work. Since the above URL is hard coded and cannot be overridden, the only way to overcome this obstacle was to rebuild the package with this patch removed. This made kubeadm query the upstream server which returned v1.27.4. Since here the minor number is higher than the one of kubeadm, the fallback mechanism kicked in querying for https://dl.k8s.io/release/stable-1.24.txt - which returned v1.24.16. Next problem: After dropping the fix,`init` proceeded attempting to download container images. This again failed with the error messages: error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/kube-apiserver:v1.24.16: output: time="2023-07-30T19:14:10+02:00" level=fatal msg="pulling image failed: rpc error: code , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/kube-controller-manager:v1.24.16: output: time="2023-07-30T19:14:12+02:00" level=fatal msg="pulling image failed: rpc err , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/kube-scheduler:v1.24.16: output: time="2023-07-30T19:14:13+02:00" level=fatal msg="pulling image failed: rpc error: code , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/kube-proxy:v1.24.16: output: time="2023-07-30T19:14:14+02:00" level=fatal msg="pulling image failed: rpc error: code = Un , error: exit status 1 [ERROR ImagePull]: failed to pull image registry.opensuse.org/kubic/coredns:v1.8.6: output: time="2023-07-30T19:14:28+02:00" level=fatal msg="pulling image failed: rpc error: code = Unknown , error: exit status 1 Obviously, it tried to download containers of the version advertised by upstream, however, these versions are not (yet) available on registry.opensuse.org - as can be checked using `podman search`: $ podman search --list-tags registry.opensuse.org/kubic/kube-apiserver NAME TAG registry.opensuse.org/kubic/kube-apiserver latest [..] registry.opensuse.org/kubic/kube-apiserver v1.24.3 registry.opensuse.org/kubic/kube-apiserver v1.24.3-3.1532 registry.opensuse.org/kubic/kube-apiserver v1.26.6 [..] registry.opensuse.org/kubic/kube-apiserver v1.27.3-5.91 registry.opensuse.org/kubic/kube-apiserver v1.27.3-5.93 The latest available version of v1.24 here is v1.24.3 - this should have been served querying https://kubic.opensuse.org/release/stable-1.24.txt, however, this URL returns 404. The last major.minor version combo served is: $ curl -L https://kubic.opensuse.org/release/stable-1.23.txt 1.23.4 i.e. the latest kubernetes-1.23 version available on registry.opensuse.org. It appears as if a script triggered by the build of new versions to update or newly create stable-1<N>.txt files is no longer running. Since the URL cannot be overridden it renders `kubernetes1.<X>-kubeadm` packages for <X> > 23 useless at least when running `kubeadm init`. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213440] New: Add ca-certificates-steamtricks to lutris recommended deps
by bugzilla_noreply＠suse.com 02 Aug '23

02 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213440 Bug ID: 1213440 Summary: Add ca-certificates-steamtricks to lutris recommended deps Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: 8z7lp689(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: So I spent a couple evenings hunting down a very frustating bug involving Lutris, Wine and EasyAntiCheat (EAC). The bug appears when trying to run Tom Clancy's The Division 2 using the Ubisoft Connect launcher through Lutris and Wine-GE v8.10. The game will install and launch fine, but upon selecting the character (i.e., logging into the game) the game will crash with a Delta error. This is indicative of a network problem. To rule out the problem was with the game itself I installed the game using the same runner in bottles (Flatpak) and the problem did not appear. However, I do not desire to use Flatpak and bottles for gaming on my system so I persisted to find the underlying problem. Google didn't offer much help until I stumbled across this recent thread by accident (from another game): https://forum.albiononline.com/index.php/Thread/177592-Disconnected-by-Easy… It appears EAC tries to establish a connection but fails due to missing CA certificates. Thus, other games using EAC may also be affected. Installing the ca-certificates-steamtricks package manually resolves the problem. It also appears to not affect users that have both steam and lutris installed, because steam pulls in steamtricks, which has ca-certificates-steamtricks as a recommended dependency. However, lutris should not depend on steam being installed for a specific subsection of games (using EAC) to work. Therefore, adding ca-certificates-steamtricks to lutris as a recommended dependency should suffice to resolve the bug. Reproducible: Always Steps to Reproduce: 1. Install lutris from official TW repos 2. Download and install Wine-GE 8.10 runner 3. Install Ubisoft Connect using the installer provided by Ubisoft and the Wine-GE v8.10 runner 4. Launch Ubisoft Connect, login and install Tom Clancy's The Division 2. 5. Launch the game and login Actual Results: The game crashes with a network related error Expected Results: The game loads normally without an error -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213829] New: [kublet v1.27.4] `/usr/bin/kubelet` contains not what it should
by bugzilla_noreply＠suse.com 02 Aug '23

02 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213829 Bug ID: 1213829 Summary: [kublet v1.27.4] `/usr/bin/kubelet` contains not what it should Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- The wrapper script `/usr/bin/kubelet` contains script code unrelated to it's task and without proper file magic see: https://build.opensuse.org/package/view_file/openSUSE:Factory/kubernetes1.2…) - it rather looks like a copy of genmanpages.sh - a script that's used during package build. AFAIKT, this has been broken since the advent of kubernetes 1.26. Version 1.25 still contains what one would expect. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213254] New: hwinfo --bios fails on locked down kernel
by bugzilla_noreply＠suse.com 02 Aug '23

02 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213254 Bug ID: 1213254 Summary: hwinfo --bios fails on locked down kernel 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: antonio.teixeira(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- As investigated in bsc#1212141, hwinfo --bios will not work in a locked down kernel (which will be enabled by default in tumbleweed) due to /dev/mem being restricted. -- You are receiving this mail because: You are on the CC list for the bug.

1 1