October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1118564] New: flatpak: upgrade to version 1.0.5
by bugzilla_noreply＠novell.com 30 Jun '22

30 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1118564 Bug ID: 1118564 Summary: flatpak: upgrade to version 1.0.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Leap 15 comes with an older flatpak version, and as result one cannot install VLC app from flathub, because it need at least version 1.0.5. By installing the flatpak package from tumbleweed (version 1.0.5) in Leap 15 works out of the box, without issues, and making possible to install VLC. As there isn't any hard dependency from flatpak regarding different library versions between Leap 15 and Tumbleweed, it would be easy to update the current version of flatpak in Leap 15. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1028460] New: grub2 ignores active_devices
by bugzilla_noreply＠novell.com 30 Jun '22

30 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028460 Bug ID: 1028460 Summary: grub2 ignores active_devices Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: rw(a)suse.de Reporter: bg(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- after doing the latest update, I found that /boot/zipl/active_devices.txt was emptied. Even after copying the old data in there, the newly generated initrd ignores active_devices.txt which results in an unbootable system. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1146427] New: VUL-1: CVE-2019-14751: python-nltk: Natural Language Toolkit (NLTK) prior to version 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash)
by bugzilla_noreply＠novell.com 29 Jun '22

29 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1146427 Bug ID: 1146427 Summary: VUL-1: CVE-2019-14751: python-nltk: Natural Language Toolkit (NLTK) prior to version 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/240518/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: wolfgang.frisch(a)suse.com QA Contact: security-team(a)suse.de CC: sleep_walker(a)opensuse.org Found By: Security Response Team Blocker: --- CVE-2019-14751 Natural Language Toolkit (NLTK) prior to version 3.4.5 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in an NLTK package (ZIP archive) that is mishandled during extraction. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14751 http://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-14751.html -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1092326] New: Plasma Wayland does not use the configured system keyboard layout and freezes when trying to set a keyboard layout
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1092326 Bug ID: 1092326 Summary: Plasma Wayland does not use the configured system keyboard layout and freezes when trying to set a keyboard layout Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This bug report is related to bug #1091816 but behaves different in Leap 15.0. Also in this case during installation US keyboard with dead keys is configured. But there is no layout configured in systemsettings5. However starting konsole and pressing the accent key or another dead key gives a popup showing spectacle and asks to select something to make a screen copy. When trying to configure a keyboard layout in systemsettings5 the screen freezes. The mouse pointer does not move anymore. After a minute or so, I get the login screen again, but this may be caused by pressing <Ctrl><Alt>+<Backspace>+<Backspace>. I did not try to wait if without pressing these keys the login screen still appears. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1091818] New: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091818 Bug ID: 1091818 Summary: After starting a Wayland Plasma session and leaving the session, login into a normal Plasma session does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started a Wayland Plasma session. Because being unable to enter certain characters in that session I finished that session and got the login screen. I changed the type of session to a classic Plasma session and entered the password. After a while I did not enter the session, but the system returned to the login screen. I needed to reboot, to be able to start a normal Plasma session. -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1080842] New: plasma with wayland gives flickering applications
by bugzilla_noreply＠novell.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1080842 Bug ID: 1080842 Summary: plasma with wayland gives flickering applications Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried Leap 15.0 updated to Build 128.1 using Plasma with Wayland. Having a few application windows open. These windows appear partly behind each other in a flickering way. The screen is constantly changing showing part of one window in front of another, but disappearing a bit later behind that window. There is no stable screen. The window with focus may be partly behind another window. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1123345] New: Certbot does not seem ready for TLS-SNI-01 reaching end-of-life
by bugzilla_noreply＠novell.com 23 Jun '22

23 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1123345 Bug ID: 1123345 Summary: Certbot does not seem ready for TLS-SNI-01 reaching end-of-life Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jwagner(a)computing.dcu.ie QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap 15.0 comes with certbot 0.24.0, which is not ready for TLS-SNI-01 validation reaching end-of-life in 2019Q1 according to https://community.letsencrypt.org/t/how-to-stop-using-tls-sni-01-with-certb… Package version suffix and zypper log/history does not suggest that functionality has been backported recently and I received a warning e-mail yesterday that I used ACME TLS-SNI-01 domain validation on 2019-01-19 (subject line "Action required: Let's Encrypt certificate renewals"). I use `certbot --apache certonly` for a single virtual domain and call `/usr/bin/certbot renew --quiet` weekly via crontab. Briefly scanning the certbot log for "sni", tls-sni-01 seems to have been used for the renewal on 2019-01-19. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1115001] New: susefirewall2-to-firewalld: Fails to determine default zone
by bugzilla_noreply＠novell.com 23 Jun '22

23 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1115001 Bug ID: 1115001 Summary: susefirewall2-to-firewalld: Fails to determine default zone Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://github.com/openSUSE/susefirewall2-to-firewalld /issues/4 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: markos.chandras(a)suse.com Reporter: markos.chandras(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 0.0.3 has a regression that prevents default zone from being detected properly https://github.com/openSUSE/susefirewall2-to-firewalld/issues/4 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1042528] New: security/keepassx: Segfault for search
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1042528 Bug ID: 1042528 Summary: security/keepassx: Segfault for search 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: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After pressing Ctrl+F it shortly (~0.2s) shows the search view and then gave me a Segfault. Running it with gdb gave me another error: > gdb keepass keepassx keepassxc ele@melekess:~> gdb keepassx GNU gdb (GDB; openSUSE Tumbleweed) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from keepassx...Reading symbols from /usr/lib/debug/usr/bin/keepassx.debug...done. done. (gdb) r Starting program: /usr/bin/keepassx Missing separate debuginfo for /usr/lib64/libQtCore.so.4 Try: zypper install -C "debuginfo(build-id)=aae09ee6055dc186575945fad62f28e198a9d356" Missing separate debuginfo for /usr/lib64/libQtGui.so.4 Try: zypper install -C "debuginfo(build-id)=be91c0bccafd94ecc5fd1a4437e2de5b77696ca1" Missing separate debuginfo for /usr/lib64/libgcrypt.so.20 Try: zypper install -C "debuginfo(build-id)=4e0a9294838b3fb3dac12e68cb00f2e4f397b2e9" Missing separate debuginfo for /lib64/libz.so.1 Try: zypper install -C "debuginfo(build-id)=21b301d5592177bf542e8d8c41c0b27df7e2440d" Missing separate debuginfo for /usr/lib64/libstdc++.so.6 Try: zypper install -C "debuginfo(build-id)=ee9fd8cc6fbbf42cc79e4924f6118b496b45b3a8" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=561783b5517f6a4c17726f96ef692597377d9fc8" Missing separate debuginfo for /lib64/libgcc_s.so.1 Try: zypper install -C "debuginfo(build-id)=d2a8238991eb9ac4afa570da0419d6188b64a546" Missing separate debuginfo for /usr/lib64/libpng16.so.16 Try: zypper install -C "debuginfo(build-id)=22de6f0dd806ef44469f30509bd7c1919730cdbd" Missing separate debuginfo for /usr/lib64/libfreetype.so.6 Try: zypper install -C "debuginfo(build-id)=ddfced10958280dc5cbc5031dda671a6bd0ecd70" Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=64f04f5c97010448c3a51b03bb9fa2b437888e57" Missing separate debuginfo for /usr/lib64/libSM.so.6 Try: zypper install -C "debuginfo(build-id)=488ce271a4e9b76d429602888b6e2cd766e4d4bd" Missing separate debuginfo for /usr/lib64/libICE.so.6 Try: zypper install -C "debuginfo(build-id)=95e0e706f873fbd16c643ec072b3e7f21a48138c" Missing separate debuginfo for /usr/lib64/libXi.so.6 Try: zypper install -C "debuginfo(build-id)=04842b5af5cbfdca656d65ed3e2f69f3f078d9c5" Missing separate debuginfo for /usr/lib64/libXrender.so.1 Try: zypper install -C "debuginfo(build-id)=dbd5711f34b7cfa50f28059240da17240894187e" Missing separate debuginfo for /usr/lib64/libXrandr.so.2 Try: zypper install -C "debuginfo(build-id)=cc3f4cf227f8e8d5ddec9ae0dfea02e450ae45e1" Missing separate debuginfo for /usr/lib64/libXfixes.so.3 Try: zypper install -C "debuginfo(build-id)=446be2aebf53829fe05f0257d4b94765639e218b" Missing separate debuginfo for /usr/lib64/libXcursor.so.1 Try: zypper install -C "debuginfo(build-id)=b589fe995a2a95a9e8b4a1404466c24186c2647c" Missing separate debuginfo for /usr/lib64/libXinerama.so.1 Try: zypper install -C "debuginfo(build-id)=a9dd93da989813b45ffed48101f4e69f8f5f3b79" Missing separate debuginfo for /usr/lib64/libfontconfig.so.1 Try: zypper install -C "debuginfo(build-id)=1657bc30ca61f5a5165b0a1bf4c14ea432d740c6" Missing separate debuginfo for /usr/lib64/libXext.so.6 Try: zypper install -C "debuginfo(build-id)=9825de0ced273155a4f9cbed9c35aa6219fd2311" Missing separate debuginfo for /usr/lib64/libX11.so.6 Try: zypper install -C "debuginfo(build-id)=261d9592a95e4724a3d7019faa591320ec3834d0" Missing separate debuginfo for /usr/lib64/libgpg-error.so.0 Try: zypper install -C "debuginfo(build-id)=9985ccc9f6380b4be688069ae226dfbd77013f9b" Missing separate debuginfo for /usr/lib64/libpcre.so.1 Try: zypper install -C "debuginfo(build-id)=8b15c8089ae69924185eb89f09c0b4d2c4178e59" Missing separate debuginfo for /usr/lib64/libbz2.so.1 Try: zypper install -C "debuginfo(build-id)=6e4dee957505d111d0eb00fe0830394c3dd44f6a" Missing separate debuginfo for /usr/lib64/libffi.so.7 Try: zypper install -C "debuginfo(build-id)=b93e3c6f234f62f861d6a429bc3672a85ae22c95" Missing separate debuginfo for /usr/lib64/libuuid.so.1 Try: zypper install -C "debuginfo(build-id)=4c7dba3b81d600005bc342e1b31982eb259349f5" Missing separate debuginfo for /usr/lib64/libexpat.so.1 Try: zypper install -C "debuginfo(build-id)=6de3c39118914851895f9af7c9abf737d717aa13" Missing separate debuginfo for /usr/lib64/libxcb.so.1 Try: zypper install -C "debuginfo(build-id)=b3a1aeb7294c2b5503d2401b1317bfddc34220c7" Missing separate debuginfo for /usr/lib64/libXau.so.6 Try: zypper install -C "debuginfo(build-id)=86d79656851311fd78521e28b18cf88b7f7ffec0" Cannot find user-level thread for LWP 12821: generic error (gdb) Not sure how to debug it further. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1137383] New: python-virtualenv: creating virtualenvs fails in directories with colons
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137383 Bug ID: 1137383 Summary: python-virtualenv: creating virtualenvs fails in directories with colons Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sebix+novell.com(a)sebix.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was unable to add the address of the maintainer (according to OBS) as assignee. With colons -> error: ----- username@computername:~/tmp/path:with:colons> python3 -m virtualenv -p python3 testingvenv Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/username/tmp/path:with:colons/testingvenv/bin/python3 Also creating executable in /home/username/tmp/path:with:colons/testingvenv/bin/python Fatal Python error: initfsencoding: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x00007ff630c0e680 (most recent call first): ERROR: The executable /home/username/tmp/path:with:colons/testingvenv/bin/python3 is not functioning ERROR: It thinks sys.prefix is '/home/username/tmp/path:with:colons' (should be '/home/username/tmp/path:with:colons/testingvenv') ERROR: virtualenv is not compatible with this system or executable ----- username@computername:~/tmp/path:with:colons> python2 -m virtualenv -p python2 testingvenv2 Already using interpreter /usr/bin/python2 New python executable in /home/username/tmp/path:with:colons/testingvenv2/bin/python2 Also creating executable in /home/username/tmp/path:with:colons/testingvenv2/bin/python ImportError: No module named site ERROR: The executable /home/username/tmp/path:with:colons/testingvenv2/bin/python2 is not functioning ERROR: It thinks sys.prefix is u'/home/username/tmp/path:with:colons' (should be u'/home/username/tmp/path:with:colons/testingvenv2') ERROR: virtualenv is not compatible with this system or executable ------ Without colons -> no error: ----- username@computername:~/tmp/pathwithoutcolons> python3 -m virtualenv -p python3 testingvenv Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/username/tmp/pathwithoutcolons/testingvenv/bin/python3 Also creating executable in /home/username/tmp/pathwithoutcolons/testingvenv/bin/python Installing setuptools, pip, wheel... done. ----- -- You are receiving this mail because: You are on the CC list for the bug.

2 1