openSUSE Bugs July 2022

bugs@lists.opensuse.org

1 participants
2594 discussions

[Bug 1201101] New: Leap 15.4 removes certbot
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201101 Bug ID: 1201101 Summary: Leap 15.4 removes certbot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: archie.cobbs(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Leap 15.3 system I was using these RPMs to generate Let's Encrypt certificates: 2021-06-15 14:29:29 | install | 1.4.0-bp153.1.20 | python2-certbot 2021-06-15 14:29:31 | install | 1.4.0-bp153.1.19 | python2-certbot-dns-dnsimple 2021-06-15 14:31:13 | install | 1.4.0-bp153.1.18 | python2-certbot-apache when I upgraded to Leap 15.4, for some reason they got removed: 2022-06-27 12:52:26 | remove | 1.4.0-bp153.1.19 | python2-certbot-dns-dnsimple 2022-06-27 12:54:29 | remove | 1.4.0-bp153.1.18 | python2-certbot-apache 2022-06-27 12:54:29 | remove | 1.4.0-bp153.1.20 | python2-certbot Now I can't renew my SSL certificate. Searching for "certbot" on https://software.opensuse.org/ shows that there are results for 15.3 but none for 15.4. I thought things were supposed to get better with time, but here they are getting worse. What's the deal?? How do I get certbot back up and running again?? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190364] New: Leap 15.2 Repository is regnerating so fast zypper ref never completes
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190364 Bug ID: 1190364 Summary: Leap 15.2 Repository is regnerating so fast zypper ref never completes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: archie.cobbs(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper refresh is failing because for some unknown reason the repository is being regenerated every 3-5 minutes, and because zypper takes several minutes to download the meta-data, the files disappear before it can finish, resulting in the errors shown below. I'm watching the "Last Modified" timestamps visible here: http://download.opensuse.org/update/leap/15.2/oss/repodata/ and they are updating every few minutes. Obviously the repository meta-data shouldn't be regenerated that often. I'm sure the mirrors are creating a bunch of extra traffic due to this as well. Log of failures... $ zypper ref Repository 'openSUSE Leap Non-OSS (15.2)' is up to date. Repository 'openSUSE Leap OSS (15.2)' is up to date. Retrieving repository 'openSUSE Leap Update (15.2)' metadata ..........................................................................................................................................................................[error] Repository 'openSUSE Leap Update (15.2)' is invalid. [repo-update|http://download.opensuse.org/update/leap/15.2/oss/] Valid metadata not found at specified URL History: - File './repodata/81cf5f057ca38b532ac1123c445c36f4971cedb4e15833b5633057405d8926c0-primary.xml.gz' not found on medium 'http://download.opensuse.org/update/leap/15.2/oss/' - Can't provide ./repodata/81cf5f057ca38b532ac1123c445c36f4971cedb4e15833b5633057405d8926c0-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE Leap Update (15.2)' because of the above error. Repository 'openSUSE Leap Update Non-OSS (15.2)' is up to date. Some of the repositories have not been refreshed because of an error. $ zypper ref Repository 'openSUSE Leap Non-OSS (15.2)' is up to date. Repository 'openSUSE Leap OSS (15.2)' is up to date. Retrieving repository 'openSUSE Leap Update (15.2)' metadata ..........................................................................................................................................................................[error] Repository 'openSUSE Leap Update (15.2)' is invalid. [repo-update|http://download.opensuse.org/update/leap/15.2/oss/] Valid metadata not found at specified URL History: - File './repodata/bfa5c8e314980c6140de4b9f869b9470b2e5b6cdb1218617c148e289e710d571-primary.xml.gz' not found on medium 'http://download.opensuse.org/update/leap/15.2/oss/' - Can't provide ./repodata/bfa5c8e314980c6140de4b9f869b9470b2e5b6cdb1218617c148e289e710d571-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE Leap Update (15.2)' because of the above error. Repository 'openSUSE Leap Update Non-OSS (15.2)' is up to date. Some of the repositories have not been refreshed because of an error. $ zypper clean All repositories have been cleaned up. $ zypper ref Repository 'openSUSE Leap Non-OSS (15.2)' is up to date. Repository 'openSUSE Leap OSS (15.2)' is up to date. Retrieving repository 'openSUSE Leap Update (15.2)' metadata ..........................................................................................................................................................................[error] Repository 'openSUSE Leap Update (15.2)' is invalid. [repo-update|http://download.opensuse.org/update/leap/15.2/oss/] Valid metadata not found at specified URL History: - File './repodata/a90126512bf96e5d71ce7449b79687448777d27839d8f1a1003d1b388a0a1e91-primary.xml.gz' not found on medium 'http://download.opensuse.org/update/leap/15.2/oss/' - Can't provide ./repodata/a90126512bf96e5d71ce7449b79687448777d27839d8f1a1003d1b388a0a1e91-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE Leap Update (15.2)' because of the above error. Repository 'openSUSE Leap Update Non-OSS (15.2)' is up to date. Some of the repositories have not been refreshed because of an error. $ zypper ref Repository 'openSUSE Leap Non-OSS (15.2)' is up to date. Repository 'openSUSE Leap OSS (15.2)' is up to date. Retrieving repository 'openSUSE Leap Update (15.2)' metadata ..........................................................................................................................................................................[error] Repository 'openSUSE Leap Update (15.2)' is invalid. [repo-update|http://download.opensuse.org/update/leap/15.2/oss/] Valid metadata not found at specified URL History: - Location 'http://download.opensuse.org/update/leap/15.2/oss/repodata/679c33c618c30914…' is temporarily unaccessible. - Can't provide ./repodata/679c33c618c3091434628484b57de02379df52303d2000099ab72f00b8080e1e-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE Leap Update (15.2)' because of the above error. Repository 'openSUSE Leap Update Non-OSS (15.2)' is up to date. Some of the repositories have not been refreshed because of an error. $ zypper ref Repository 'openSUSE Leap Non-OSS (15.2)' is up to date. Repository 'openSUSE Leap OSS (15.2)' is up to date. Retrieving repository 'openSUSE Leap Update (15.2)' metadata ..........................................................................................................................................................................[error] Repository 'openSUSE Leap Update (15.2)' is invalid. [repo-update|http://download.opensuse.org/update/leap/15.2/oss/] Valid metadata not found at specified URL History: - Location 'http://download.opensuse.org/update/leap/15.2/oss/repodata/e8a3fe9b56d6d62f…' is temporarily unaccessible. - Can't provide ./repodata/e8a3fe9b56d6d62faa44136ab1349dab311724dd403ca3a1d952bfa84be56027-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE Leap Update (15.2)' because of the above error. Repository 'openSUSE Leap Update Non-OSS (15.2)' is up to date. Some of the repositories have not been refreshed because of an error. $ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201010] New: cloud-init hard requires wicked on Tumbleweed / MicroOS
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201010 Bug ID: 1201010 Summary: cloud-init hard requires wicked on Tumbleweed / MicroOS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- MicroOS switched to NetworkManager by default, but cloud-init has still a hard-requires on wicked-service, which is causing both stacks to be installed and wicked is being used by default. It would be better to switch it to requires service(network) instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1201010] cloud-init hard requires wicked on Tumbleweed / MicroOS
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201010 https://bugzilla.suse.com/show_bug.cgi?id=1201010#c5 --- Comment #5 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Robert Schweikert from comment #4) > Hold on that doesn't make any sense to me what so ever. NM does not handle > the underlying connections, i.e. NM does not make DHCP requests etc. It does. > That happens via wicked or via dhcpclient. You don't need wicked and you don't need dhcpclient. Neither of both is installed on my MicroOS systems. > If we are dropping wicked are we going back to dhcpclient? No, we are dropping wicked since we switched already to NetworkManager as default for openSUSE Tumbleweed and openSUSE MicroOS. SLE Micro will switch with 5.3 to NetworkManager, as often enough mentioned by Daniel and Jiri in the sync calls since half a year. Wicked does not provide the functionality our customers especially from the Edge require. > What happens to our sysconfig layout and the values we set in sysconfig? I would like to drop them sooner than later, because NetworkManager provides a much better interface. I don't understand why we limit ourself with netconfig to 14 year old technology? But currently it looks like it stays, and since sysconfig and sysconfig-netconfig are compatible with NetworkManager... > This is a much bigger topic than a "Require" statement in the spec file. For the majority of packages my team touched it was not much more than fixing the requires. > As a side note wicked is required by a lot of packages in the Public Cloud > area, we need a running network. Then you should start working on it... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201044] New: Linux Kernel Bug: Data Leakage: 2022
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201044 Bug ID: 1201044 Summary: Linux Kernel Bug: Data Leakage: 2022 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: drivalinux(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Linux Kernel Bug: Data Leakage: 2022 Mageia Linux 9 Final, suggestion: use the Linux Kernel LTS (released: 2022). Mageia Linux 9 Final, suggestion: use the Linux Kernel LTS (released: 2022), as it is more stable and secure. As a result, correction or mitigation: Linux Kernel Bug: Data Leakage: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0494 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0854 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1012 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1729 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1786 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1789 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1852 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1966 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1972 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1974 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1975 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21499 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28893 Source and more information: Governo adverte para vulnerabilidades no Kernel do Linux e alerta para vazamento de dados (Brasil: 14/06/2022): https://www.convergenciadigital.com.br/Seguranca/Governo-adverte-para-vulne… Thank you! Source and more information: Mageia Linux 9 Final, suggestion: use the Linux Kernel LTS (released: 2022). https://bugs.mageia.org/show_bug.cgi?id=30585 Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1188234] No graphics with default dtb on Pinebook Pro
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1188234 https://bugzilla.suse.com/show_bug.cgi?id=1188234#c22 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |msuchanek(a)suse.com Resolution|FIXED |--- --- Comment #22 from Michal Suchanek <msuchanek(a)suse.com> --- Sounds like it's still broken: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.18.6-1-default (geeko@buildhost) (gcc (SUSE Linux) 12.1.0, GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.38.20220525-6) #1 SMP PREEMPT_DYNAMIC Thu Jun 23 05:46:18 UTC 2022 (5aa0763) [ 0.000000] Machine model: Pine64 Pinebook Pro ... [ 8.165638] rockchip-dp ff970000.edp: no DP phy configured [ 8.175590] cdn-dp fec00000.dp: [drm:cdn_dp_probe [rockchipdrm]] *ERROR* missing extcon or phy [ 8.176671] cdn-dp: probe of fec00000.dp failed with error -22 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200949] New: kwin don't let setting two fingers tap for emule third mouse button
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200949 Bug ID: 1200949 Summary: kwin don't let setting two fingers tap for emule third mouse button Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: karlggest(a)yahoo.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! I upgrade Leap 15.4 from Leap 15.3 in a laptop (Lenovo) and when system was running with the upgrade I lost the touchpad setting that let the user emule the central button tapping with two fingers. When I run System Settings (Plasma) and select "touchpad" in "input devices", change Two fingers for tapping as middle button is disabled (both options, right or middle are disabled. Run Plasma as a new user or run Plasma with kwin_wayland solved (by now at least) the issue. Pass to reproduce: 1. Run the upgrade. Reboot in Plasma (X11). 2. Two fingers tapping is right mouse button. 3. Settings in systemsettings5 to change this are disabled. Workarounds: Both of follow works: a) 1. Create a new user. 2. Start Plasma. 3. Close session and init session as the right user. 4. Two fingers tapping as middle button works. b) 1. Init session with kwin_wayland 2. Use systemsettings5 to set the propper options to use tapping in the touchpad. 3. Close session and start session with kwin_X11 4. Two fingers tapping as middle button works. Thandks!! -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1201054] [Build 20220629] yast2_firewall: selecting Zone for interface fails
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201054 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[Build 20220629] |[Build 20220629] |yast2_firewall: selecting |yast2_firewall: selecting |Zone for interface fials |Zone for interface fails -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201084] New: neovim immediately crashes on start
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201084 Bug ID: 1201084 Summary: neovim immediately crashes on start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: johannes.m.hoffmann(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Both Neovim from packages and the one downloaded from the github releases page immediately crash on startup with the following error message: vim/_init_packages.lua: cannot load incompatible bytecode stack traceback: [C]: at 0x556cd42faade [C]: at 0x7f7d6c2aa730 E970: Failed to initialize builtin lua modules -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200228] ipython crash on tab completion
by bugzilla_noreply＠suse.com 01 Jul '22

01 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200228 https://bugzilla.suse.com/show_bug.cgi?id=1200228#c3 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcepl(a)suse.com, | |steven.kowalik(a)suse.com Flags| |needinfo?(steven.kowalik@su | |se.com) --- Comment #3 from Matej Cepl <mcepl(a)suse.com> --- Why is this not a duplicate of bug 1195830? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2022