November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205222] YaST2 RPMs not available on download.opensuse.org
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205222 https://bugzilla.suse.com/show_bug.cgi?id=1205222#c8 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Stefan Hundhammer <shundhammer(a)suse.com> --- I can access every single one of those URLs just fine. No VPN, no special credentials; just normal Internet access as an anonymous user). Are you in a corporate network with a special filter / proxy / firewall that blocks certain sites? But one way or the other, this is certainly not a YaST installer bug. If it were, we'd receive hundreds, if not thousands of similar reports; but there were none. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203481] AUDIT-1: libcap: consider re-introducing pam_cap for explicit opt-in
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203481 https://bugzilla.suse.com/show_bug.cgi?id=1203481#c10 --- Comment #10 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- (In reply to jsegitz(a)suse.com from comment #9) > we have that, it's the open build service ;) I don't think we should officially add it back to the distribution, but have it as a package there. Users that need it can install it from there. The description of the package should link to both bugs and contain a warning that this is likely a bad idea I don't know if it is easily possible to activate this sub-package in the devel project but *not* include it in Factory or other distribution projects. Basically we would need a branched version of the package that includes this, no? What I meant regarding a separate repository was more the thought of a more integrated and simple solution, like other distros have unstable repositories we could gather such software in an insecure repository that can easily be enabled for those that dare. If I'm not mistaken then the OBS signing keys are tied to the projects i.e. somebody wishing to e.g. add a package from the libcap devel project would need to import and trust the Base:System project, which has quite some repercussions. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c27 --- Comment #27 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Created attachment 862754 --> https://bugzilla.suse.com/attachment.cgi?id=862754&action=edit config: Disable SYSFB on Arm FYI this is the config change I'll do for ARM systems. Fixes the problem for me. The firmware framebuffer is still supported via DT. From the DT node, a device will be created to which simpledrm binds. The duplicate device that comes from the EFI stub and SYSFB is being removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tzimmermann(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203481] AUDIT-1: libcap: consider re-introducing pam_cap for explicit opt-in
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203481 https://bugzilla.suse.com/show_bug.cgi?id=1203481#c9 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsegitz(a)suse.com --- Comment #9 from Johannes Segitz <jsegitz(a)suse.com> --- we have that, it's the open build service ;) I don't think we should officially add it back to the distribution, but have it as a package there. Users that need it can install it from there. The description of the package should link to both bugs and contain a warning that this is likely a bad idea -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195887] intel/radeon graphics doesn't work due to simpledrm enablement in Kernel 5.16.8
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1195887 https://bugzilla.suse.com/show_bug.cgi?id=1195887#c74 --- Comment #74 from S��awomir Lach <slawek(a)lach.art.pl> --- Hi. I've removed nosimplefb=1 parameter from Linux cmdline. System start and seems working. XDM started, I could login to Plasma5 Wayland session. But not enhancement boot was visible. And it should be, because simplefb should help booting process, as I remember. How to test if simplefb is active? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193064] New: Touchpad doesn't work on Lenovo Yoga Slim7
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1193064 Bug ID: 1193064 Summary: Touchpad doesn't work on Lenovo Yoga Slim7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Touchpad doesn't work on Lenovo Yoga Slim7 That problem on Leap 15.3 and Tumbleweed (also in RHEL 9 beta) And some bugs on Fedora (it failed to start after sleep, but at all is working), so probably problem more on kernel side -- You are receiving this mail because: You are on the CC list for the bug.

1 44

[Bug 1205172] [Staging] mdadm 4.2 fails installation on RAID1 with YaST
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205172 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205172] [Staging] mdadm 4.2 fails installation on RAID1 with YaST
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205172 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205172] [Staging] mdadm 4.2 fails installation on RAID1 with YaST
by bugzilla_noreply＠suse.com 09 Nov '22

09 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205172 https://bugzilla.suse.com/show_bug.cgi?id=1205172#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- Of course libstorage-ng still needs to make sure not to pass a chunk size argument to the command for RAID 1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0