September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213446] New: connecting dock station network enables wifi - reverse behaviour
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213446 Bug ID: 1213446 Summary: connecting dock station network enables wifi - reverse behaviour Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Dell XPS 9700 I have a Dell WD19 dock. It used to work fine. Now when I have e dock station connected with the cable there WIFI is disabled as it should When I unplug Ethernet cable from the dock the wifi remains OFF and RFKILL shows hard block. When I plug the Ethernet cable back to the dock the wifi comes up for 2-3 seconds and sets up a connection and then I get e message that wifi gets disabled and connection is switched back to Ethernet. It used to work fine that unplugging the cable from dock would bring the wifi up. So having a dock station it is not possible to disconnect its ethernet and have laptop enable Wifi. It works ok in Ubuntu. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215701] New: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215701 Bug ID: 1215701 Summary: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/379815/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: rfrohl(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- yt-dlp is a youtube-dl fork with additional features and fixes. yt-dlp allows the user to provide shell command lines to be executed at various stages in its download steps through the `--exec` flag. This flag allows output template expansion in its argument, so that metadata values may be used in the shell commands. The metadata fields can be combined with the `%q` conversion, which is intended to quote/escape these values so they can be safely passed to the shell. However, the escaping used for `cmd` (the shell used by Python's `subprocess` on Windows) does not properly escape special characters, which can allow for remote code execution if `--exec` is used directly with maliciously crafted remote data. This vulnerability only impacts `yt-dlp` on Windows, and the vulnerability is present regardless of whether `yt-dlp` is run from `cmd` or from `PowerShell`. Support for output template expansion in `--exec`, along with this vulnerable behavior, was added to `yt-dlp` in version 2021.04.11. yt-dlp version 2023.09.24 fixes this issue by properly escaping each special character. `\n` will be replaced by `\r` as no way of escaping it has been found. It is recommended to upgrade yt-dlp to version 2023.09.24 as soon as possible. Also, always be careful when using --exec, because while this specific vulnerability has been patched, using unvalidated input in shell commands is inherently dangerous. For Windows users who are not able to upgrade: 1. Avoid using any output template expansion in --exec other than {} (filepath). 2. If expansion in --exec is needed, verify the fields you are using do not contain ", | or &. 3. Instead of using --exec, write the info json and load the fields from it instead. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40581 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214211] New: "Loading basic drivers" is printed twice on the screen when loading installation system
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214211 Bug ID: 1214211 Summary: "Loading basic drivers" is printed twice on the screen when loading installation system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: dheidler(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868778 --> https://bugzilla.suse.com/attachment.cgi?id=868778&action=edit screenshot Something like this is printed: Loading basic drivers...Loading basic drivers ok Expected: Loading basic drivers... ok -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215663] New: # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215663 Bug ID: 1215663 Summary: # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice(). Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vvedomil(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I tried to play over Steam on OpenSUSE Tumbleweed and the terminal reported the following error: Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice(). Autogroup scheduling needs to be enabled during kernel compilation. I checked that on https://github.com/SUSE/kernel-source/blob/15b4ad8fb5f18870bb9e4011a2bb53cb… I can see # CONFIG_SCHED_AUTOGROUP is not set, that's the origin of the issue. So many distros enable that by default and I've never seen this issue with Steam on distros where is set CONFIG_SCHED_AUTOGROUP=y Examples: Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main… CachyOS: https://github.com/CachyOS/linux-cachyos/blob/1d74c2037cd78f292fb6606708fa8… Could I ask to change that? Change config, build a kernel with CONFIG_SCHED_AUTOGROUP=y, and make the OpenSUSE kernel and the whole distro more friendly to gaming through Steam. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214406] New: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully
by bugzilla_noreply＠suse.com 19 Sep '24

19 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1214406 Bug ID: 1214406 Summary: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: priyanka.saggu(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- 1. The Kubernetes package on TW seems to require cri-o as runtime dependency, however, it requires containerd. Thus, - cri-o should not be installed as a dependency - containerd had to be installed enabled and started (containerd doesn't have an rccontainerd link) 2. kubelet.service does not start: It complains about the option `--container-runtime` not being known. This option is pulled in from /etc/sysconfig/kubelet. It needs to be deleted from this file. It is not clear who has created this file and which package owns it. The rpm database does not know it. Since it is pulled in by ..../systemd/system/kubelet.service.d/10-kubeadm.conf I suspect it comes from kubernetes1.27-kubeadem but it's hard to tell where it is created - at least not in a post-install script. It would be good if the file was '%ghost' in the %files section of the package it originates from. The same is true for the environment file /var/lib/kubelet/kubeadm-flags.env which is written by `kubeadm init`. 3. 'kubeadm init' checks if the kubelet service is enabled. 4. Moreover, it requires a reboot to start all dependent services and load all required kernel modules: - br_netfilter needs to be loaded - containerd needs to be started This was fine for kubic these packages were originally meant for as this had transactional updates and required a reboot. On a 'regular' system where this is not the case, these modules should probably be loaded and services be started from a 'postinstall' script. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1215463] New: VirtualBox shared folders no longer working in Tumbleweed 20230915
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215463 Bug ID: 1215463 Summary: VirtualBox shared folders no longer working in Tumbleweed 20230915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: nixuser(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates in the last two week or so have broken shared folders in VirtualBox. You can mount the shares, and "ls" the files, but any attempt to access a file results in "killed" as a response. If I launch Thunar in Xfce it locks up and must be killed. Video scaling is working, and copy/paste between the host and guest are also working. Issue exists for Tumbleweed guests with a Fedora or Win10 host. Other hosts not tested. Tumbleweed guest fully up to date 20230915. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1213181] New: ddclient dose not work for cloudflare
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213181 Bug ID: 1213181 Summary: ddclient dose not work for cloudflare Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE-HW:/home/hillwood # ddclient FATAL: Error loading the Perl module JSON::Any needed for cloudflare update. It's my config: # /etc/ddclient.conf daemon=300 # check every 300 seconds syslog=yes # log update msgs to syslog #mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/run/ddclient/ddclient.pid # record PID in file. ssl=yes protocol=cloudflare ttl=1 # use=web # web=checkip.dyndns.org usev6=if, if=br0 login=email password=API Key zone=hillwoodhome.net cloud.home.hillwoodhome.net ddclient 3.10.0 works fine with this config. We should provide an update for Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213521] New: shairport-sync: missing dependency: avahi
by bugzilla_noreply＠suse.com 05 Sep '24

05 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213521 Bug ID: 1213521 Summary: shairport-sync: missing dependency: avahi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE:Factory/shairport-sync shairport-sync.spec is missing: Requires: avahi Steps to reproduce on a minimal Tumbleweed installation: # zypper in shairport-sync # systemctl start shairport-sync > Failed to start shairport-sync.service: Unit avahi-daemon.service not found. `zypper in avahi` fixes this. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213486] New: [Build 44.3] openQA test fails in fanotify14
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213486 Bug ID: 1213486 Summary: [Build 44.3] openQA test fails in fanotify14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/3439183/modules/fano tify14/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@64bit_virtio fails in [fanotify14](https://openqa.opensuse.org/tests/3439183/modules/fanotify14/st… ## Test suite description ## Reproducible Fails since (at least) Build [44.2](https://openqa.opensuse.org/tests/3438422) ## Expected result Last good: [44.1](https://openqa.opensuse.org/tests/3436580) (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 8