September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1154753] New: screen stays dark on boot unless I specify nouveau.modeset=0
by bugzilla_noreply＠novell.com 17 Sep '22

17 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154753 Bug ID: 1154753 Summary: screen stays dark on boot unless I specify nouveau.modeset=0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: estellnb(a)elstel.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel modesetting does not seem to work with 4.12.14-lp151.28.20-default. My screens (integrated+external) stay dark without nouveau.modeset=0. I have a dual boot option with Debian 9, kernel 4.20.0-rc4 and there it works well with nouveau.hdmimhz=225. Strange. I remember that always having worked without any additional parameter (4K only with hdmimhz). Would you believe it to be possible that this is caused by openSUSE kernel extensions? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1174239] New: KDE Software Updater Applet: "Reboot needed / reboot now?" notification before Kernel update is installed
by bugzilla_noreply＠suse.com 17 Sep '22

17 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174239 Bug ID: 1174239 Summary: KDE Software Updater Applet: "Reboot needed / reboot now?" notification before Kernel update is installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: thomas-formella(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If a kernel update is available, the "KDE Software Updater Applet" notifies a "reboot needed / reboot now?" BEFORE the delta-rpm is downloaded and installed. It worked already as intended in a previous release before 15.0 (download kernel delta-rpm -> install -> notification "reboot needed / reboot now?"). Currently, the notification may confuse new users or desktop users, who don't use YaST or zypper to install updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1181029] New: racket: /usr/share/racket/pkgs/.LOCKpkgs.rktd cannot open output file
by bugzilla_noreply＠suse.com 16 Sep '22

16 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1181029 Bug ID: 1181029 Summary: racket: /usr/share/racket/pkgs/.LOCKpkgs.rktd cannot open output file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: petr(a)cervinka.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When you run drracket (current version 7.8) on Tumbleweed and open Package Manager to see Currently Installed (click menu: File->Package Manager->Currently installed) it will end with following error. open-output-file: cannot open output file path: /usr/share/racket/pkgs/.LOCKpkgs.rktd system error: Permission denied; errno=13 context...: /usr/share/racket/collects/racket/file.rkt:429:8 /usr/share/racket/collects/racket/file.rkt:424:0: call-with-file-lock /usr/share/racket/collects/racket/contract/private/arrow-val-first.rkt:555:3 /usr/share/racket/pkgs/gui-pkg-manager-lib/pkg/gui/private/by-installed.rkt:139:12: for-loop /usr/share/racket/pkgs/gui-pkg-manager-lib/pkg/gui/private/by-installed.rkt:137:4: reset-installed-list! method in by-installed-panel% /usr/share/racket/collects/racket/private/more-scheme.rkt:148:2: call-with-break-parameterization /usr/share/racket/collects/racket/private/more-scheme.rkt:266:2: call-with-exception-handler /usr/share/racket/pkgs/gui-lib/mred/private/wx/common/queue.rkt:435:6 /usr/share/racket/pkgs/gui-lib/mred/private/wx/common/queue.rkt:486:32 /usr/share/racket/pkgs/gui-lib/mred/private/wx/common/queue.rkt:634:3 When you manually create file by "sudo touch /usr/share/racket/pkgs/.LOCKpkgs.rktd", it will work fine. It seems to be easy to fix, but racket.changes file in OBS contains manipulation (related to this file) in the past, so my suggestion may not be correct one. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1168447] New: Please build Blender 2.8x with OptiX support
by bugzilla_noreply＠novell.com 16 Sep '22

16 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1168447 Bug ID: 1168447 Summary: Please build Blender 2.8x with OptiX support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: cfeck(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Blender has improved support for RTX cards since version 2.81. The official Blender download supports these Cycles engines: CPU, CUDA, OptiX, and OpenCL. In the Tumbleweed build of Blender, only CPU, CUDA, and OpenCL are selectable. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1188415] New: After installation, the name of the Wi-Fi connection, bears the name of the interface.
by bugzilla_noreply＠suse.com 16 Sep '22

16 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188415 Bug ID: 1188415 Summary: After installation, the name of the Wi-Fi connection, bears the name of the interface. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: 79625490833(a)yandex.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello. I noticed such a bug that after installation, the name of the Wi-Fi connection bears the name of the interface, namely wlan0 instead of the name of the connection point (the name to which the device connected), in this case it is a router with the sssid " SkyNET" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1121578] New: python-aiohttp Factory version unable to build on Leap
by bugzilla_noreply＠novell.com 15 Sep '22

15 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1121578 Bug ID: 1121578 Summary: python-aiohttp Factory version unable to build on Leap Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In order to fix python-aiohttp build failure in Leap 15.1, python-aiohttp's Factory version has submitted to Leap, however this version unable to build on Leap due to missing deps, https://build.opensuse.org/package/show/openSUSE:Leap:15.1:Staging:adi:21/p… Note that, a problem is, python-Cython is one of the dep does not have greater enough version in Leap, and python-Cython is from SLE. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1181849] New: VUL-0: nim: Insecure SSL/TLS Defaults, MitM, and nimble shell command injection
by bugzilla_noreply＠suse.com 14 Sep '22

14 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1181849 Bug ID: 1181849 Summary: VUL-0: nim: Insecure SSL/TLS Defaults, MitM, and nimble shell command injection Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: anicka(a)suse.com Reporter: atoptsoglou(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian.glaubitz(a)suse.com Found By: --- Blocker: --- through oss title: "Nim - Insecure SSL/TLS Defaults, MitM, and nimble shell command injection" date: 2021-02-04T14:13:23+01:00 cve: vendor: nim-lang vendorUrl: https://nim-lang.org/ authors: tintinweb affectedVersions: [ "<= 1.2.6", "nimble <=v0.12.0"] vulnClass: CWE-295, CWE-78, CWE-348 Vulnerability Note: https://consensys.net/diligence/vulnerabilities/nim-insecure-ssl-tls-defaul… Vulnerability Note: https://github.com/tintinweb/pub/ Group: https://consensys.net/diligence/research/ # Vulnerability Note ## Summary We found a couple of critical security issues in the defaults for one of the standard-lib components that allows peer-impersonation (MitM) on secure transports. This also affects the languages package manager. Additionally, the package manager is vulnerable to shell command injection when fetching remote repositories before installing packages: * 2.1 - `httpClient` does no validate peer certificates by default (appears to be fixed in 1.4.x) * 2.2 - the package manager `nimble` relies on the insecure `httpClient` defaults (unfixed; latest 0.12.0 has not been re-compiled with a fixed nim-c) * 2.3 - `nimble` falls back to insecure transports if `https` is blocked (unfixed) * 2.4 - `nimble` shell command injection when fetching a package for installation (unfixed) **TLDR;** The Nim (`at least <=1.2.6`) `httpClient` default SSL/TLS configuration does not enforce peer certificate verification by default. Non-secure settings should not be the default as this might unexpectedly expose other projects to security risks. If you're using `nimble <= 0.12.0` anyone can block your TLS session and it will fall back to an insecure transport. Because of the insecure `httpClient` defaults, one can also just intercept your TLS session as the peer verification is too lax. Additionally, nimble appears to be vulnerable to a direct shell command injection when installing a package (but one can as well just provide a malicious package). ## Details see https://consensys.net/diligence/vulnerabilities/nim-insecure-ssl-tls-defaul… ## Proof of Concept see https://consensys.net/diligence/vulnerabilities/nim-insecure-ssl-tls-defaul… ### Timeline ``` JUL/09/2020 - contact nim developers @telegram; provided details, PoC FEB/04/2021 - deadline met. full disclosure. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1185882] New: /etc/resolv.conf not restored after NetworkManager VPN connection terminates
by bugzilla_noreply＠suse.com 14 Sep '22

14 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1185882 Bug ID: 1185882 Summary: /etc/resolv.conf not restored after NetworkManager VPN connection terminates 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: doug(a)uq.edu.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For NetworkManager VPN plugins that use pppd, netconfig seems to be getting run twice (once by NetworkManager and once by pppd) resulting in /etc/resolv.conf not being restored after the VPN connection is terminated. Apparently with https://bugzilla.suse.com/show_bug.cgi?id=1079793 there was a netconfig policy change to permit non-NM settings : * Do Mai 17 2018 mt(a)suse.de - version 0.84.3 - netconfig: change policy to permit non-NM settings (bsc#1079793) As requested and approved by NetworkManager maintainer, the 'auto' policy permits now also per interface settings provided by other services when NetworkManager is enabled. That is, the auto policy resolving has been changed from "STATIC_FALLBACK NetworkManager" to "STATIC_FALLBACK * NetworkManager". So changes to pppd's ip-up script and netconfig behavior can't be accepted due to that policy change as they would override the policy change behavior. More details: https://github.com/openSUSE/sysconfig/issues/31 -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1146856] New: security/fail2ban: Bug - failtoban breaks restarting firewalld
by bugzilla_noreply＠novell.com 14 Sep '22

14 Sep '22

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.

2 8

[Bug 1189045] New: windows:mingw:win{32|64}/mingw{32|64}-gcc: gdb pretty printers for libstdc++ are not installed
by bugzilla_noreply＠suse.com 13 Sep '22

13 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189045 Bug ID: 1189045 Summary: windows:mingw:win{32|64}/mingw{32|64}-gcc: gdb pretty printers for libstdc++ are not installed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- The gcc sources provide gdb pretty printers for libstdc++ (see https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=libstdc%2B%2B-v3/python;h=6da54…) which are not currently installed by the mingwxx-gcc package. The presence of gdb pretty printers is useful for debugging cross-compiled applications with gdb. -- You are receiving this mail because: You are on the CC list for the bug.

1 2