openSUSE Bugs July 2021

bugs@lists.opensuse.org

1 participants
2405 discussions

[Bug 1184430] New: Kdenlive does not provide motion tracking - OpenCV issue

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184430 Bug ID: 1184430 Summary: Kdenlive does not provide motion tracking - OpenCV issue 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: hendric.stattmann(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package of kdenlive provided by Tumbleweed is not including the motion tracker effect. The underlying reason for this omission seems to be the missing inclusion of OpenCV library, which should provide the required capabilities for this effect. OpenCV library itself is installed on my system, though. It might therefore be necessary to rebuild this package with inclusion of the OpenCV library, so that this function becomes available. Package details: Name : kdenlive Version : 20.12.3 Release : 1.1 Architecture: x86_64 Install Date: Sa 13 M�r 2021 21:43:48 Group : Productivity/Multimedia/Video/Editors and Convertors Size : 54691735 License : GPL-3.0-or-later Signature : RSA/SHA256, Mi 10 M�r 2021 14:00:55, Key ID b88b2fd43dbdc284 Source RPM : kdenlive-20.12.3-1.1.src.rpm Build Date : Mi 10 M�r 2021 13:53:16 Build Host : lamb52 Packager : https://bugs.opensuse.org Vendor : openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

2 hours, 33 minutes

[Bug 1013687] New: KMail 5.3.0 - search index not being rebuild

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1013687 Bug ID: 1013687 Summary: KMail 5.3.0 - search index not being rebuild Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 704846 --> http://bugzilla.opensuse.org/attachment.cgi?id=704846&action=edit building search index After upgrade of Leap 42.1 to 42.2 and from Kmail 4.14.10 to 5.3.0 the search is not working properly. I tried: akonadictl fsck akonadictl vaccum akonadictl restart. Despite the KMail search always complains that no index is build (see attachment). There is no progress on index building, and search results are frankly speaking wrong -- You are receiving this mail because: You are on the CC list for the bug.

2 hours, 47 minutes

[Bug 1013550] New: plasmashell freezing

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1013550 Bug ID: 1013550 Summary: plasmashell freezing Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: On one of my machines (Lenovo T420 notebook) I have a problem with plasmashell freezing often when a notification is shown. The notification frame shows up, but no content and then the complete desktop freezes. Killing and restarting plasmashell cures the problem for a short time - til one of the the next notifications wants to display something. It doesn't happen for all notifications, though. Using tools like notify-send the problem can not be reproduced, but notifications stemming from plasma-nm and plasma-workspace itself (like the one for a removed plasmoid) always lead to the freeze. The system originally was openSuSE Leap 42.2, but because of the problem I upgraded step by step to - the latest kernel from the kernel stable repo, - the latest X server plus everyting from the X11:Xorg repo - and the latest plasma workspace including everything from the KDE:Framework5 repo. The problem remained unchanged, though. A few more facts: - The X server is xf86-video-intel. - Switching off the compositor doesn't help either. - Everything worked with Leap 42.1 - No according entry in the journal or .xsession-errors* can be found. - And a curiosity: After removing .config/plasmarc and restarting plasmashell the problem vanishes for a few hours or even a day, before it comes back. - Logging off or restarting the machine doesn't help in case the problems exists at that time. In found a few bug reports for plasma freezes, but none of them seems to fit exactly. Reproducible: Sometimes Steps to Reproduce: 1. unlock widgets 2. remove widget 3. a notification tries to popup 4. plasmashell freezes 1. wait for a plasma-nm notification 2. plasmashell freezes Actual Results: plasmashell freezes Expected Results: plasmashell should not freeze, the notification shoold popup see details -- You are receiving this mail because: You are on the CC list for the bug.

2 hours, 54 minutes

[Bug 1085619] New: Softlockup with btrfs and kubic (CaaSP on openSUSE)

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1085619 Bug ID: 1085619 Summary: Softlockup with btrfs and kubic (CaaSP on openSUSE) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: jeffm(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, lpechacek(a)suse.com Found By: --- Blocker: --- With current openSUSE Kubic builds (CaaSP based on openSUSE Tumbleweed), we seem to run into the same issue as with CaaSP v1: bsc#1041296 - admin node freezes - no shell after putting password into login prompt Could it be that the fixes are missing in the upstream kernel? -- You are receiving this mail because: You are on the CC list for the bug.

4 hours, 44 minutes

[Bug 1187416] New: php-composer needs php8-mbstring

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1187416 Bug ID: 1187416 Summary: php-composer needs php8-mbstring 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: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fails otherwise -- You are receiving this mail because: You are on the CC list for the bug.

6 hours, 20 minutes

[Bug 1185376] New: VUL-0: CVE-2021-29472: php-composer: crafted URL values allow code to be executed in the HgDriver

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1185376 Bug ID: 1185376 Summary: VUL-0: CVE-2021-29472: php-composer: crafted URL values allow code to be executed in the HgDriver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/282997/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: i(a)guoyunhe.me Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-29472 Composer is a dependency manager for PHP. URLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow code to be executed in the HgDriver if hg/Mercurial is installed on the system. The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins. The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote code execution. The vulnerability has been patched on Packagist.org and Private Packagist within 12h of receiving the initial vulnerability report and based on a review of logs, to the best of our knowledge, was not abused by anyone. Other services/tools using VcsRepository/VcsDriver or derivatives may also be vulnerable and should upgrade their composer/composer dependency immediately. Versions 1.10.22 and 2.0.13 include patches for this issue. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29472 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29472 https://github.com/composer/composer/security/advisories/GHSA-h5h8-pc6h-jvvx https://getcomposer.org/ -- You are receiving this mail because: You are on the CC list for the bug.

6 hours, 21 minutes

[Bug 1176934] New: mozilla-nss update fails to build on aarch64

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1176934 Bug ID: 1176934 Summary: mozilla-nss update fails to build on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: mozilla-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com Found By: --- Blocker: --- the mozilla-nss update fails to build in openSUSE:Factory:ARM with: [ 137s] /home/abuild/rpmbuild/BUILD/nss-3.56/nss/lib/freebl/gcm.c:493: undefined reference to `gcm_HashWrite_hw' [ 137s] /usr/lib64/gcc/aarch64-suse-linux/10/../../../../aarch64-suse-linux/bin/ld: /tmp/libfreeblpriv3.so.2YfxM6.ltrans1.ltrans.o: in function `gcm_InitCounter': [ 137s] /home/abuild/rpmbuild/BUILD/nss-3.56/nss/lib/freebl/gcm.c:364: undefined reference to `gcm_HashZeroX_hw' [ 137s] /usr/lib64/gcc/aarch64-suse-linux/10/../../../../aarch64-suse-linux/bin/ld: /home/abuild/rpmbuild/BUILD/nss-3.56/nss/lib/freebl/gcm.c:364: undefined reference to `gcm_HashZeroX_hw' [ 137s] /usr/lib64/gcc/aarch64-suse-linux/10/../../../../aarch64-suse-linux/bin/ld: /tmp/libfreeblpriv3.so.2YfxM6.ltrans2.ltrans.o: in function `AES_InitContext': [ 137s] /home/abuild/rpmbuild/BUILD/nss-3.56/nss/lib/freebl/gcm.c:111: undefined reference to `gcm_HashInit_hw' [ 137s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

6 hours, 37 minutes

[Bug 1146856] New: security/fail2ban: Bug - failtoban breaks restarting firewalld

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1146856 Bug ID: 1146856 Summary: security/fail2ban: Bug - failtoban breaks restarting firewalld Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: meissner(a)suse.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- on a system with fail2ban installed and activated it is impossible to use systemctl restart to restart firewalld: nextcloud:~ # systemctl restart firewalld Failed to restart firewalld.service: Transaction contains conflicting jobs 'restart' and 'stop' for fail2ban.service. Probably contradicting requirement dependencies configured. See system logs and 'systemctl status firewalld.service' for details. the sequence "systemctl stop fail2ban; systemctl restart firewalld; systemctl start fail2ban" works as exected. the same used to happen when I still used SuSEfirewall2 instead of firewalld, so I'm pretty sure the issue is with fail2ban and not with either of the two firewalls... for more info: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871993 https://bugzilla.redhat.com/show_bug.cgi?id=1379141 https://lists.freedesktop.org/archives/systemd-devel/2016-March/036011.html -- You are receiving this mail because: You are on the CC list for the bug.

7 hours, 17 minutes

[Bug 1180738] New: fail2ban don't work with firewalld

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1180738 Bug ID: 1180738 Summary: fail2ban don't work with firewalld Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ae(a)ae-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the change to firewalld fail2ban is not adding the IPs to the firewall. You see messages in the fail2ban log: Warning 0.0.0.0 already banned. See https://serverfault.com/questions/852755/fail2ban-doesnt-add-ips-to-ipset-f… I added /etc/fail2ban/action.d/custom-firewalld.conf with ----------------------------- START ----------------------------- #/etc/fail2ban/action.d/custom-firewalld.conf [INCLUDES] before = [Definition] actionstart = actionstop = actioncheck = #actionflush = sed -i '/<source address=/d' /etc/firewalld/zones/public.xml actionban = firewall-cmd --change-source=<ip> --zone=drop && firewall-cmd --change-source=<ip> --zone=drop --permanent actionunban = firewall-cmd --remove-source=<ip> --zone=drop && firewall-cmd --remove-source=<ip> --zone=drop --permanent || echo 0 [Init] ----------------------------- END ----------------------------- /etc/fail2ban/jail.conf ----------------------------- START ----------------------------- [...] # # Action shortcuts. To be used to define action parameter banaction = custom-firewalld banaction_allports = firewallcmd-allports [....] ----------------------------- END ----------------------------- -- You are receiving this mail because: You are on the CC list for the bug.

7 hours, 18 minutes

[Bug 1188610] New: VUL-0: CVE-2021-32749: fail2ban: Command injection via mail comand

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1188610 Bug ID: 1188610 Summary: VUL-0: CVE-2021-32749: fail2ban: Command injection via mail comand Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/304472/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1983222 fail2ban is a daemon to ban hosts that cause multiple authentication errors. In versions 0.9.7 and prior, 0.10.0 through 0.10.6, and 0.11.0 through 0.11.2, there is a vulnerability that leads to possible remote code execution in the mailing action mail-whois. Command `mail` from mailutils package used in mail actions like `mail-whois` can execute command if unescaped sequences (`\n~`) are available in "foreign" input (for instance in whois output). To exploit the vulnerability, an attacker would need to insert malicious characters into the response sent by the whois server, either via a MITM attack or by taking over a whois server. The issue is patched in versions 0.10.7 and 0.11.3. As a workaround, one may avoid the usage of action `mail-whois` or patch the vulnerability manually. https://github.com/fail2ban/fail2ban/commit/410a6ce5c80dd981c22752da034f252… https://github.com/fail2ban/fail2ban/commit/2ed414ed09b3bb4c478abc9366a1ff2… https://github.com/fail2ban/fail2ban/security/advisories/GHSA-m985-3f3v-cwmm References: https://bugzilla.redhat.com/show_bug.cgi?id=1983222 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32749 https://github.com/fail2ban/fail2ban/commit/410a6ce5c80dd981c22752da034f252… https://github.com/fail2ban/fail2ban/security/advisories/GHSA-m985-3f3v-cwmm http://www.cvedetails.com/cve/CVE-2021-32749/ https://github.com/fail2ban/fail2ban/commit/2ed414ed09b3bb4c478abc9366a1ff2… http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32749 -- You are receiving this mail because: You are on the CC list for the bug.

7 hours, 18 minutes

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2021