December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1187531] New: Ansible: missing python3-selinux requirement
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187531 Bug ID: 1187531 Summary: Ansible: missing python3-selinux requirement 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh Tumbleweed system, the ansible-playbook command fails due to missing python3-selinux dependencies as follows > ansible-playbook -i inventory duck-norris.yml > ERROR! Unexpected Exception, this is probably a bug: Failed to detect selinux python bindings at ['/usr/lib64/python3.8/site-packages', '/usr/lib64/python3.8/site-packages', '/usr/lib/python3.8/site-packages', '/usr/local/lib64/python3.8/site-packages', '/usr/local/lib64/python3.8/site-packages', '/usr/local/lib/python3.8/site-packages'] > the full traceback was: > > Traceback (most recent call last): > File "/usr/bin/ansible-playbook", line 92, in <module> > mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass) > File "/usr/lib/python3.8/site-packages/ansible/cli/__init__.py", line 25, in <module> > from ansible.parsing.dataloader import DataLoader > File "/usr/lib/python3.8/site-packages/ansible/parsing/dataloader.py", line 17, in <module> > from ansible.module_utils.basic import is_executable > File "/usr/lib/python3.8/site-packages/ansible/module_utils/basic.py", line 74, in <module> > import selinux > File "/home/phoenix/.local/lib/python3.8/site-packages/selinux/__init__.py", line 104, in <module> > check_system_sitepackages() > File "/home/phoenix/.local/lib/python3.8/site-packages/selinux/__init__.py", line 100, in check_system_sitepackages > raise Exception( > Exception: Failed to detect selinux python bindings at ['/usr/lib64/python3.8/site-packages', '/usr/lib64/python3.8/site-packages', '/usr/lib/python3.8/site-packages', '/usr/local/lib64/python3.8/site-packages', '/usr/local/lib64/python3.8/site-packages', '/usr/local/lib/python3.8/site-packages'] Simply installing python3-selinux fixes the issue and we should probably include this in the spec file. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1166616] New: Ansible requires rebuild to work with python3.8 upgrade
by bugzilla_noreply＠novell.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1166616 Bug ID: 1166616 Summary: Ansible requires rebuild to work with python3.8 upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: elimat(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- A rebuild of ansible is required for it to be work with python3.8 upgrade. Right now the only option is to deinstall ansible if I do a zypper dup -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1143725] New: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output)
by bugzilla_noreply＠novell.com 07 Oct '22

07 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1143725 Bug ID: 1143725 Summary: qemu-aarch64-binfmt, from qemu-linux-user, not working (no output) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Context: I want to run an ARM64 (aarch64) container on an x86 host. This is possible using qemu Linux user emulation and Linux binfmt. It is supposed to work like this: //Fetching an ARM container on x86 (long story) $ skopeo --override-arch arm64 copy docker://opensuse/leap docker-daemon:opensuse-arm64/leap:latest //Install qemu Linux user, and setup binfmt for aarch64 # zypper install qemu-linux-user $ cp /usr/bin/qemu-aarch64-binfmt . # echo -1 > /proc/sys/fs/binfmt_misc/qemu-aarch64 # echo ':qemu-aarch64:M:0:\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-aarch64-binfmt:POCF' > /proc/sys/fs/binfmt_misc/register //Build our container $ cat << EOF > Dockerfile FROM opensuse-arm64/leap COPY qemu-aarch64-binfmt /usr/bin/qemu-aarch64-binfmt EOF docker build -t qemu-leap . //Now I should be able to run the ARM container, like this: # docker run -it qemu-leap-aarch64-binfmt /bin/sh But, basically, nothing happens. No output at all, and I'm definitely not inside an ARM container. Actually, it appears the container exited: $ docker ps --all CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ea2252caf90a qemu-leap "/bin/sh" 4 seconds ago Exited (255) 3 seconds ago relaxed_goodall Now, if I, instead of qemu-aarch64-binfmt, use a qemu-aarch64-static binary copied from a Debian unstable box I have in my home network, i.e., this one: # ./qemu-aarch64-static -version qemu-aarch64 version 3.1.0 (Debian 1:3.1+dfsg-8) Things work! In fact: $ docker run -it --rm qemu-leap uname -a Linux bf12752f6a51 5.1.16-1-default #1 SMP Wed Jul 3 12:37:47 UTC 2019 (2af8a22) aarch64 aarch64 aarch64 GNU/Linux Note the *aarch64*. Of course, we need to change the aarch64 interpreter file too, in /proc/sys/fs/binfmt So, basically, it looks like the procedure is correct, or at least can work. But our qemu-linux-user packages contain binaries that are not adequate for being used for this use case. Things/differences to check: - QEMU version (the debian stolen from Debian, that makes things works is from QEMU 3.1.0, while we ship 4.0.0 - our patch queue - our configuration and compile options -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1189647] New: internal error when $Y2PROFILER=1
by bugzilla_noreply＠suse.com 07 Oct '22

07 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1189647 Bug ID: 1189647 Summary: internal error when $Y2PROFILER=1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: giecrilj(a)stegny.2a.pl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- { Y2PROFILER=1 yast2 view_anymsg /var/log/zypp/history; } Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require' Details: cannot load such file -- profiler -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1062518] New: x2gothinclient(d) is missing File/Path/Expand.pm perl module
by bugzilla_noreply＠novell.com 06 Oct '22

06 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1062518 Bug ID: 1062518 Summary: x2gothinclient(d) is missing File/Path/Expand.pm perl module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- Starting x2gothinclientd cause the message Can't locate File/Path/Expand.pm in @INC (you may need to install the File::Path::Expand module) (@INC contains: /usr/lib/perl5/site_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.26.1 /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.26.1 /usr/lib/perl5/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/5.26.1 /usr/lib/perl5/site_perl) at /usr/sbin/x2gothinclientd line 23. AFAICS there is no such file below /usr/lib/perl5/ nor any provides of 'perl(File::Path::Expand)' -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1174342] New: X2go can't connect to remote local desktop session (error invalid mit-magic-cookie-1)
by bugzilla_noreply＠suse.com 06 Oct '22

06 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1174342 Bug ID: 1174342 Summary: X2go can't connect to remote local desktop session (error invalid mit-magic-cookie-1) 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After last update x2go can't connect to remote local desktop session. Connect to lxde, KDE, ICEWM work fine, but if connect to local desktop session, then get the error Connection failed. Invalid mit-magic-cookie-1 keyNo protocol specified xwinfo: error: unable to open display ":0" -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1175475] New: VUL-0: CVE-2020-14352: librepo: missing path validation in repomd.xml may lead to directory traversal
by bugzilla_noreply＠suse.com 05 Oct '22

05 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175475 Bug ID: 1175475 Summary: VUL-0: CVE-2020-14352: librepo: missing path validation in repomd.xml may lead to directory traversal Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/265258/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: christian.voegl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de CC: pth(a)suse.com Found By: Security Response Team Blocker: --- rh#1866498 Librepo fails to sanitize paths in the 'repomd.xml' configuration file. Malformed or malicious repository metadata could allow a remote attacker to copy files outside of the destination directory via path traversal. Considering that DNF runs as root, this flaw could potentially result in system compromise via arbitrary file overwriting of critical system files. References: https://bugzilla.redhat.com/show_bug.cgi?id=1866498 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-14352 https://access.redhat.com/security/cve/CVE-2020-14352 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1041794] New: Recent update breaks some Youtube videos
by bugzilla_noreply＠novell.com 04 Oct '22

04 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1041794 Bug ID: 1041794 Summary: Recent update breaks some Youtube videos Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: james.knott(a)rogers.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- An update around mid May caused some Youtube videos to fail. When this happens, loading the video stops, leaving only the dot going around a circle showing. This happens with Firefox, Seamonkey and Chromium browsers. The videos that fail play OK in Windows. To verify the problem, I tried the videos with a VirtualBox VM or a fresh 42.2 install. The problem videos played. I then cloned the VM and ensured the videos played. I then updated the clone to the latest updates and now the videos fail. The original non-updated VM still continued to play the videos. It appears the problem is related to the type of codec used. For example, videos with the vp9 codec play, but those with avc1.4d400d now fail. Here are 2 links, this one plays OK: https://www.youtube.com/watch?v=Rzqq581Q3Us But this one doesn't: https://www.youtube.com/watch?v=t8tdmaEhMHE Again, this problem occurred recently. Videos that played a few weeks ago now fail. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1189457] New: fwup doesn't refresh update info
by bugzilla_noreply＠suse.com 04 Oct '22

04 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1189457 Bug ID: 1189457 Summary: fwup doesn't refresh update info Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- bash# fwupdmgr get-updates Firmware metadata has not been updated for 30 days and may not be up to date. I understood the data should be refreshed automatically, but aren't. Should some service be enabled by default? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1137997] New: Expert Partitioner: import multi-device Btrfs mount points
by bugzilla_noreply＠novell.com 04 Oct '22

04 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1137997 Bug ID: 1137997 Summary: Expert Partitioner: import multi-device Btrfs mount points Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jlopez(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When importing mount points from a system with a multi-device Btrfs filesystem, the multi-device Btrfs is imported as a single-device. It should reconstruct the multi-device Btrfs, if possible. -- You are receiving this mail because: You are on the CC list for the bug.

2 2