July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201474] sway is missing dependency on mesa
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201474 http://bugzilla.opensuse.org/show_bug.cgi?id=1201474#c18 --- Comment #18 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1201474) was mentioned in https://build.opensuse.org/request/show/989448 Factory / Mesa -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162014] [staging] libcap 2.30 breaks fakeroot
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1162014 https://bugzilla.suse.com/show_bug.cgi?id=1162014#c15 --- Comment #15 from Ismael Luceno <ismael.luceno(a)suse.com> --- Upstream commit: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=c75e832067… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201552] New: os-autoinst-devel fails to upgrade with "the to be installed os-autoinst-devel-4.6.1639403953.ae94c4bd-bp154.1.137.x86_64 requires 'pkgconfig(opencv)'"
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201552 Bug ID: 1201552 Summary: os-autoinst-devel fails to upgrade with "the to be installed os-autoinst-devel-4.6.1639403953.ae94c4bd-bp154.1.137. x86_64 requires 'pkgconfig(opencv)'" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: okurz(a)suse.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation See https://progress.opensuse.org/issues/111863 as related issues https://progress.opensuse.org/issues/113662 for details ## Steps to reproduce ``` podman run --rm -it registry.opensuse.org/opensuse/leap:15.3 /bin/sh -c 'zypper -n up && zypper -n in os-autoinst && zypper --releasever=15.4 -n dup' ``` ## Problem According to https://build.opensuse.org/package/show/openSUSE:Leap:15.3:Update/opencv we had opencv3 in Leap15.3, in https://build.opensuse.org/package/show/openSUSE:Leap:15.4:Update/opencv we have opencv4, same as in Tumbleweed. In https://github.com/os-autoinst/os-autoinst/blob/master/dist/rpm/os-autoinst… line 28 and following we have: ``` %if 0%{?suse_version} > 1500 # openSUSE Tumbleweed %define opencv_require pkgconfig(opencv4) %else %define opencv_require pkgconfig(opencv) %endif ``` so we need to update this according to https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto#Det… to make sure users upgrading from Leap 15.3 to 15.4 have an automatic resolution. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1162014] [staging] libcap 2.30 breaks fakeroot
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1162014 Olaf Hering <ohering(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ohering(a)suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] Kernel 5.18.9-2.1 with enabled simpledrm breaks nvidia driver (use kernel boot option 'nosimplefb=1' as workaround)
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c50 --- Comment #50 from Marcus R�ckert <mrueckert(a)suse.com> --- Upstream issue for this https://github.com/NVIDIA/open-gpu-kernel-modules/issues/228 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1162014] [staging] libcap 2.30 breaks fakeroot
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1162014 https://bugzilla.suse.com/show_bug.cgi?id=1162014#c14 Ismael Luceno <ismael.luceno(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |ismael.luceno(a)suse.com Resolution|FIXED |--- --- Comment #14 from Ismael Luceno <ismael.luceno(a)suse.com> --- Fix needs backporting to SLES-15-SP3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] [SELinux] Upgrading Tumbleweed fails due to SELinux package issues
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 https://bugzilla.suse.com/show_bug.cgi?id=1201348#c8 --- Comment #8 from Johannes Segitz <jsegitz(a)suse.com> --- I think it will help in this case as container-selinux is already included in selinux-policy. But I see your point. Maybe we should drop container-selinux altogether as it had to be included with the main policy anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] [SELinux] Upgrading Tumbleweed fails due to SELinux package issues
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 https://bugzilla.suse.com/show_bug.cgi?id=1201348#c7 --- Comment #7 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Johannes Segitz from comment #6) > I've sent an updated container-selinux (and selinux-policy) package. I > currently don't see a way to automate this dependency, as the versions are > not in sync. So that leaves "not forgetting" as an option, which isn't great > (for me) Updating the packages won't help, it's the installation order which is the issue. AFAIU the issue is: Once the updated selinux-policy-targeted is installed, RPM tries to apply the file contexts of the new policy on package installation. Its %post script tries to load the policy, but this fails because at that point container-selinux is still the old version and incompatible. So if any package which is not compatible with the old loaded policy is updated in between those (in this case NetworkManager), it fails. On top of that, there are the issues that loading a policy during the update process also affects the running system and writes into /var, which is shared among snapshots. That's not the cause of this particular failure though. If that weren't the case, it would be valid to unload the container module from the selinux policy until it's updated, but as it affects the running system that is not a good idea. So the only option I see is to merge container-selinux into the selinux-policy-targeted package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193250] [META] Fully switch TW to DRM graphics drivers and disable fbdev drivers
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1193250 Bug 1193250 depends on bug 1201392, which changed state. Bug 1201392 Summary: Kernel 5.18.9-2.1 with enabled simpledrm breaks nvidia driver (use kernel boot option 'nosimplefb=1' as workaround) https://bugzilla.suse.com/show_bug.cgi?id=1201392 What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] Kernel 5.18.9-2.1 with enabled simpledrm breaks nvidia driver (use kernel boot option 'nosimplefb=1' as workaround)
by bugzilla_noreply＠suse.com 15 Jul '22

15 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c49 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #49 from Stefan Dirsch <sndirsch(a)suse.com> --- Closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0