June 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1200104] autoyast error message "failed to add product from" is blocking unattended installations
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200104 https://bugzilla.suse.com/show_bug.cgi?id=1200104#c6 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner(a)suse.com --- Comment #6 from Martin Vidner <mvidner(a)suse.com> --- Thanks for the report! Let me summarize: 1. this is a regression in openSUSE-Leap-15.4-DVD-x86_64-Build236.1 The installation was working with openSUSE-Leap-15.4-DVD-x86_64-Build130.2 2. when autoinst.xml is fetched from the network, it works 3. the products in question are in remote (http) repositories It looks like there's a problem with the logic to activate networking before the repos are accessed, but I haven't checked in the logs yet. Thorsten, you are saying that "the errors are blocking unattended installations". An easy way out would be to configure error reports not to block, by adding a timeout: https://documentation.suse.com/sles/15-SP3/single-html/SLES-autoyast/#Creat… But I assume that you do not consider the errors harmless and want them actually fixed, right? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200112] Cannot install rpmlint-Factory on Leap 15.4, nothing provides 'rpmlint-mini'
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200112 https://bugzilla.suse.com/show_bug.cgi?id=1200112#c1 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Development Assignee|yast2-maintainers(a)suse.de |mliska(a)suse.cz Summary|Cannot install |Cannot install |rpmlint-Factory on Leap |rpmlint-Factory on Leap |15.4 |15.4, nothing provides | |'rpmlint-mini' QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #1 from Martin Vidner <mvidner(a)suse.com> --- Thanks for the report! Reassigning to rpmlint maintainer, to fix the dependencies or the distribution of packages into repos. Over to Martin L. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195821] New: /usr/lib/modules/ contains old kernel directories
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1195821 Bug ID: 1195821 Summary: /usr/lib/modules/ contains old kernel directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ioannis.bonatakis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- inspecting my TW i noticed the following ``` �� rpm -qa | grep -i kernel-default kernel-default-devel-5.16.2-1.1.x86_64 kernel-default-devel-5.16.4-1.1.x86_64 kernel-default-5.16.4-1.1.x86_64 kernel-default-devel-5.16.5-1.4.x86_64 kernel-default-5.16.5-1.4.x86_64 kernel-default-devel-5.15.12-1.3.x86_64 kernel-default-5.15.12-1.3.x86_64 kernel-default-5.16.2-1.1.x86_64 kernel-default-devel-5.16.1-1.1.x86_64 kernel-default-5.16.1-1.1.x86_64 �� ll /boot/vm* lrwxrwxrwx 1 root root 24 Feb 10 02:05 /boot/vmlinuz -> vmlinuz-5.16.5- 1-default lrwxrwxrwx 1 root root 44 Jan 10 04:24 /boot/vmlinuz-5.15.12-1-default -> ../usr/lib/modules/5.15.12-1-default/vmlinuz lrwxrwxrwx 1 root root 43 Jan 24 13:20 /boot/vmlinuz-5.16.1-1-default - > ../usr/lib/modules/5.16.1-1-default/vmlinuz lrwxrwxrwx 1 root root 43 Feb 1 02:09 /boot/vmlinuz-5.16.2-1-default - > ../usr/lib/modules/5.16.2-1-default/vmlinuz lrwxrwxrwx 1 root root 43 Feb 7 10:57 /boot/vmlinuz-5.16.4-1-default - > ../usr/lib/modules/5.16.4-1-default/vmlinuz lrwxrwxrwx 1 root root 43 Feb 10 02:05 /boot/vmlinuz-5.16.5-1-default - > ../usr/lib/modules/5.16.5-1-default/vmlinuz �� ll /usr/lib/modules/ | wc -l 52 �� ll /usr/lib/modules/ total 0 drwxr-xr-x 1 root root 12 Jun 3 2019 4.20.4-1-default drwxr-xr-x 1 root root 14 Mar 7 2021 5.10.12-1-default drwxr-xr-x 1 root root 14 May 9 2021 5.11.12-1-default drwxr-xr-x 1 root root 14 May 9 2021 5.11.15-1-default drwxr-xr-x 1 root root 14 May 9 2021 5.11.16-1-default drwxr-xr-x 1 root root 14 Apr 6 2021 5.11.2-1-default drwxr-xr-x 1 root root 14 May 9 2021 5.11.4-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.1.15-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.12.0-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.12.12-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.12.13-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.12.9-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.13.0-1-default drwxr-xr-x 1 root root 14 Aug 9 2021 5.13.1-1-default drwxr-xr-x 1 root root 14 Sep 1 10:42 5.13.12-1-default drwxr-xr-x 1 root root 14 Sep 30 09:41 5.13.13-1-default drwxr-xr-x 1 root root 14 Aug 18 06:35 5.13.4-1-default drwxr-xr-x 1 root root 14 Aug 24 08:14 5.13.6-1-default drwxr-xr-x 1 root root 14 Aug 31 08:37 5.13.8-1-default drwxr-xr-x 1 root root 14 Sep 30 09:43 5.14.0-1-default drwxr-xr-x 1 root root 14 Nov 8 15:41 5.14.11-1-default drwxr-xr-x 1 root root 14 Sep 30 09:46 5.14.1-1-default drwxr-xr-x 1 root root 14 Oct 15 11:13 5.14.6-1-default drwxr-xr-x 1 root root 14 Oct 25 15:11 5.14.6-2-default drwxr-xr-x 1 root root 14 Oct 25 15:15 5.14.9-1-default drwxr-xr-x 1 root root 676 Feb 7 11:00 5.15.12-1-default drwxr-xr-x 1 root root 14 Dec 16 2019 5.1.5-1-default drwxr-xr-x 1 root root 14 Jan 31 12:58 5.15.2-1-default drwxr-xr-x 1 root root 14 Jan 31 12:58 5.15.3-1-default drwxr-xr-x 1 root root 14 Jan 31 12:59 5.15.5-1-default drwxr-xr-x 1 root root 14 Jan 31 12:59 5.15.6-1-default drwxr-xr-x 1 root root 14 Jan 31 13:00 5.15.7-1-default drwxr-xr-x 1 root root 14 Jan 31 13:01 5.15.8-1-default drwxr-xr-x 1 root root 666 Feb 7 11:00 5.16.1-1-default drwxr-xr-x 1 root root 666 Feb 7 11:00 5.16.2-1-default drwxr-xr-x 1 root root 666 Feb 7 11:03 5.16.4-1-default drwxr-xr-x 1 root root 666 Feb 10 02:05 5.16.5-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.3.12-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.5.13-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.5.2-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.5.7-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.6.0-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.6.14-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.7.1-1-default drwxr-xr-x 1 root root 14 Sep 14 2020 5.7.5-1-default drwxr-xr-x 1 root root 14 Nov 24 2020 5.7.7-1-default drwxr-xr-x 1 root root 14 Dec 11 2020 5.8.12-1-default drwxr-xr-x 1 root root 14 Nov 24 2020 5.8.7-1-default drwxr-xr-x 1 root root 14 Feb 11 2021 5.9.1-1-default drwxr-xr-x 1 root root 14 Mar 7 2021 5.9.12-1-default drwxr-xr-x 1 root root 14 Mar 7 2021 5.9.14-1-default ``` i have already double checked that this can occur with someone else machine however in another tumbleweed, at least when i run `sudo zypper purge-kernels` the results were different ``` �� ll /usr/lib/modules/ total 0 drwxr-xr-x 1 root root 622 Feb 10 02:11 5.16.0-1-default drwxr-xr-x 1 root root 646 Feb 10 02:11 5.16.1-1-default drwxr-xr-x 1 root root 646 Feb 10 02:12 5.16.2-1-default drwxr-xr-x 1 root root 622 Feb 10 02:12 5.16.4-1-default drwxr-xr-x 1 root root 622 Feb 10 02:12 5.16.5-1-default �� rpm -qa | grep -i kernel-default kernel-default-5.16.2-1.1.x86_64 kernel-default-5.16.0-1.1.x86_64 kernel-default-5.16.1-1.1.x86_64 kernel-default-5.16.4-1.1.x86_64 kernel-default-5.16.5-1.4.x86_64 sudo zypper purge-kernels Reading installed packages... Preparing to purge obsolete kernels... Configuration: latest,latest-1,running Running kernel release: 5.16.1-1-default Running kernel arch: x86_64 Resolving package dependencies... The following 4 packages are going to be REMOVED: bbswitch-kmp-default-0.8_k5.16.0_1-11.51 bbswitch-kmp-default-0.8_k5.16.2_1-11.53 kernel-default-5.16.0-1.1 kernel-default-5.16.2-1.1 .... �� ll /usr/lib/modules/ total 0 drwxr-xr-x 1 root root 646 Feb 11 09:42 5.16.1-1-default drwxr-xr-x 1 root root 622 Feb 10 02:12 5.16.4-1-default drwxr-xr-x 1 root root 622 Feb 10 02:12 5.16.5-1-default �� rpm -qa | grep -i kernel-default kernel-default-5.16.1-1.1.x86_64 kernel-default-5.16.4-1.1.x86_64 kernel-default-5.16.5-1.4.x86_64 ``` Reproduce: Compare installed kernels and corresponding dirs in _/usr/lib/modules/_ i am not sure whether this is reproducible in every case. The reason is that in another machine (TW again), i had different results with `sudo zypper purge-kernels` Expected: _/usr/lib/modules/_ should be cleaned up by the update scripts. Additional info: - zypper 1.14.51 - RPM version 4.17.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1198552] systemd-udevd: USB devices fails to probe. Cant suspend/reboot/shutdown
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1198552 https://bugzilla.suse.com/show_bug.cgi?id=1198552#c26 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(matias.nicolas.zc | |(a)gmail.com) --- Comment #26 from Oliver Neukum <oneukum(a)suse.com> --- Could please test the following sequence: 1. rmmod xhci_hcd 2. Unplug AC 3. Wait 10s 4. Replug AC 5. Wait 10s 6. modprobe xhci_hcd This will show whether the firmware makes the HC unavailable without AC in a reversable manner or whether something crashes the HC Please provide dmesg of the test. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183642] x2go cannot connect after last update on tumbleweed
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183642 http://bugzilla.opensuse.org/show_bug.cgi?id=1183642#c6 --- Comment #6 from Tristan Miller <psychonaut(a)nothingisreal.com> --- (In reply to Jan Engelhardt from comment #5) > x2goserver had failed to build since a week or so. Now that's fixed. The > Xresources file (symlink) was pointing in the wrong direction, maybe that > was the cause. Not in my case, since I wasn't using your packages, and in any case they were not updated in the upgrade. Your packages failing to build for a week can't be the cause of Igor's problem either, since he had been experiencing the problem for a lot longer than a week. I don't think that the X2Go packages (either yours or mine) are at fault here. As both Igor and I mentioned upthread, the problem must lie with some other networking- or security-related package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198552] systemd-udevd: USB devices fails to probe. Cant suspend/reboot/shutdown
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1198552 https://bugzilla.suse.com/show_bug.cgi?id=1198552#c25 --- Comment #25 from Oliver Neukum <oneukum(a)suse.com> --- For the record: There is no unprocessed hotplug event, yet if this runtime PM, it is unclear why the patch does not affect the outcome -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200131] s390-tools build fails with gcc12
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200131 https://bugzilla.suse.com/show_bug.cgi?id=1200131#c2 --- Comment #2 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From Jan.Hoeppner(a)de.ibm.com 2022-06-02 06:06 EDT------- Hi Mark, this problem was resolved in the following GitHub issue: https://github.com/ibm-s390-linux/s390-tools/issues/130 And with this upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/9e620058184cfdf026241b9… The fix will be available also through the next s390-tools release v2.22.0 next week (Friday 10.06.). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199052] amd iommu- warning after resume
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199052 https://bugzilla.suse.com/show_bug.cgi?id=1199052#c5 Joerg Roedel <jroedel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Joerg Roedel <jroedel(a)suse.com> --- Fix is merged into these branches: * master via backport * stable via backport * SLE15-SP4 via backport * SLE15-SP3 via backport Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199510] Navigating in gedit and meld doesn't work correctly
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199510 https://bugzilla.suse.com/show_bug.cgi?id=1199510#c5 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |alynx.zhou(a)suse.com Resolution|--- |FIXED --- Comment #5 from Alynx Zhou <alynx.zhou(a)suse.com> --- Let's close this since it's fixed by the upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183642] x2go cannot connect after last update on tumbleweed
by bugzilla_noreply＠suse.com 02 Jun '22

02 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183642 http://bugzilla.opensuse.org/show_bug.cgi?id=1183642#c5 --- Comment #5 from Jan Engelhardt <jengelh(a)inai.de> --- x2goserver had failed to build since a week or so. Now that's fixed. The Xresources file (symlink) was pointing in the wrong direction, maybe that was the cause. -- You are receiving this mail because: You are on the CC list for the bug.

1 0