January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234993] Installation failed at partitioning
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234993 https://bugzilla.suse.com/show_bug.cgi?id=1234993#c6 --- Comment #6 from gilles renault <utilisateur.test(a)free.fr> --- Not better with an external HD. I can install windows 10 and Bazzite without problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234405] devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234405 https://bugzilla.suse.com/show_bug.cgi?id=1234405#c15 --- Comment #15 from pallas wept <pallaswept(a)proton.me> --- (In reply to Stefan Schubert from comment #14) > Is this the right setting ? > https://github.com/openSUSE/libeconf/pull/229 Perhaps it is different between /usr/etc/environment.d and /etc/environment.d ? If that does not work in CI, I will test it here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c27 --- Comment #27 from Michal Kubeček <mkubecek(a)suse.com> --- OK, pushed into master now (with a cleanup of dependent options). Let's see how it goes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c26 --- Comment #26 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi > e8cb5712703d Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" > (bsc#1232727) > 89074471a397 Revert "Reapply "config: Disable CONFIG_FB_DEVICE > (boo#1212947)" (bsc#1232727)" This inner cycle looks like a mistake and probably happened before the Plymouth bug reports came in. At least that's what I take from the commit messages. The fix for bsc#1232727 has been released in [1] ~3 weeks ago. That appears long enough to me to give some confidence in it. For the kernel config change I can prepare a test kernel and leave it out for another month or so. Let me also say that these interfaces are a constant source of bugs and security issues. [2] We have regular reports and no one seems to be able to get a hold on them. Dropping these interfaces is an improvement. [1] https://build.opensuse.org/request/show/1228732 [2] https://lore.kernel.org/linux-fbdev/674dac63.050a0220.ad585.0050.GAE@google… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228173] sssd: getsubids throws `libsubid_sss.so did not provide @subid_free@`
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228173 https://bugzilla.suse.com/show_bug.cgi?id=1228173#c6 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(scabrero(a)suse.com | |) | --- Comment #6 from Samuel Cabrero <scabrero(a)suse.com> --- (In reply to Dylan Meysmans from comment #5) > (In reply to Samuel Cabrero from comment #4) > > (In reply to Dylan Meysmans from comment #3) > > > (In reply to Samuel Cabrero from comment #2) > > > > Fixed in sssd 2.10 beta2. > > > > > > When can we expect sssd 2.10 to arrive for Tumbleweed? I see it is already > > > in network:ldap. > > > > It will arrive soon, the OBS request is in place: > > https://build.opensuse.org/requests/1222104. Will need to wait for > > https://bugzilla.suse.com/show_bug.cgi?id=1230051, though. > > It seems that bug has been closed for some time now. Which other issues > prevent sssd 2.10 from arriving for Tumbleweed? Hi Dylan, we have to adjust the location of the permissions file for Tumbleweed (https://src.opensuse.org/jengelh/sssd/pulls/5) and the whitelist for the new permissions file needs to be updated after the 2.10.1 release (bsc#1233131). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234995] libvirt: libvirt: virtimetest failing with the change to year 2025
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234995 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold(a)suse.com Assignee|virt-bugs(a)suse.de |jfehlig(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222748] RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] and RIP: 0033:0x7fac1690f3df - virtualbox host
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222748 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234782] New: Kernel 6.12.6 with amdgpu breaks brightness control after resume
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234782 Bug ID: 1234782 Summary: Kernel 6.12.6 with amdgpu breaks brightness control after resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Given TW20241220 with kernel 6.12.6 and resuming after suspend, the display brightness starts to increase until reaching its maximum value, and then switches off (Thinkpad T14 with AMD Ryzen 7 PRO 4750U). Since kernel version 6.12.4 works fine, I suspect that this was introduced with 6.12.5 and is due to commit 99a02eab82515343d536796aa917dee50aec1551 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Mon Nov 25 13:59:09 2024 -0500 drm/amdgpu: rework resume handling for display (v2) commit 73dae652dcac776296890da215ee7dec357a1032 upstream. Split resume into a 3rd step to handle displays when DCC is enabled on DCN 4.0.1. Move display after the buffer funcs have been re-enabled so that the GPU will do the move and properly set the DCC metadata for DCN. v2: fix fence irq resume ordering -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

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

1 0

[Bug 1212947] Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1212947 https://bugzilla.suse.com/show_bug.cgi?id=1212947#c25 --- Comment #25 from Michal Kubeček <mkubecek(a)suse.com> --- (In reply to Thomas Zimmermann from comment #23) > What are you talking about? This kernel option has been disabled exactly > once, which resulted in bsc#1232727. Apparently I mixed it with earlier FB related changes where we had similar apply/revert cycle pattern. But even for this option, this is actually third attempt to disable it: 7ce7d10b6941 config: Disable CONFIG_FB_DEVICE (boo#1212947) 86e3964b14ac Revert "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727) e8cb5712703d Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727) 89074471a397 Revert "Reapply "config: Disable CONFIG_FB_DEVICE (boo#1212947)" (bsc#1232727)" 6a2cbc6bdb98 config: Disable CONFIG_FB_DEVICE (boo#1212947) I don't think it should be so surprising that I have some doubts seeing the same claim (nobody needs this enabled any more) for the third time within few weeks after first two quickly turned out to be wrong. -- You are receiving this mail because: You are on the CC list for the bug.

1 0