October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1230414] kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 https://bugzilla.suse.com/show_bug.cgi?id=1230414#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > I guess the -j1 hack is acceptable as a temporary solution for us, while we > should ping upstream devs for the more proper fix. I pushed the temporary fix with -j1 option to users/tiwai/master/for-next and */stable/for-next branches now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|sndirsch(a)suse.de | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231130] panic on boot with QEMU/KVM+UEFI for current openSUSE-Leap-15.6-NET-x86_64-Build710.3-Media.iso
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231130 https://bugzilla.suse.com/show_bug.cgi?id=1231130#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to David Disseldorp from comment #4) > (In reply to Takashi Iwai from comment #2) > > It couldn't load / expand the initrd: > > > > [ 2.284739][ T27] Initramfs unpacking failed: write error > > I've hit this a few times too. We should be able to do a little better by > providing a more informative error message for the case where memory is > exhausted. > > As a start I'm working on propagating kernel_write() and decompress_method > error codes via the existing init/initramfs.c:message global. That sounds helpful, go ahead! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 https://bugzilla.suse.com/show_bug.cgi?id=1230891#c14 --- Comment #14 from Michael Andres <ma(a)suse.com> --- (In reply to ks so from comment #10) > Hi, > can't execute it: > > localhost:/tmp> tar cvjf zypper-testcase.bz2 /var/log/zypper.solverTestCase > /var/log/zypper.log > tar: Eliminando la `/' inicial de los nombres > /var/log/zypper.solverTestCase/ > tar: /var/log/zypper.solverTestCase/y2log: No se puede efectuar open: > Permiso denegado You need to do it as root in order to allowed to read y2log and zypper.log. Both logs have mode 0640. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230843] Dell laptop latitude 7440, intel-ipu6 camera fails: Unexpected CSR 0x0
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230843 https://bugzilla.suse.com/show_bug.cgi?id=1230843#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Sorry for the late reply, as I was off in the last weeks. It seems that IPU6 stuff is still broken on those machines in the upstream, at least in 6.11 kernel. See a report for Arch: https://bbs.archlinux.org/viewtopic.php?id=297262 Interestingly, a user created workarounds for TW https://build.opensuse.org/project/show/home:ateixeira:xps13 It contains a kernel with an IOMMU workaround. In anyway, try the latest 6.11.x TW kernel at first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231381] AUDIT-0: libcgroup: permissions.d drop-in snippet, pam-file-unauthorize, non-standard-gid /usr/bin/cgexec cgred
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231381 https://bugzilla.suse.com/show_bug.cgi?id=1231381#c1 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.gerstner(a)suse.com --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Thank you for creating the AUDIT bug. Devel package is in Virtualization/libcgroup. This is blocked in OBS sr#1206062. So this package has been dropped from Factory in 2018 via sr#589236, stating that: ``` - the functionality is largely deprecated by systemd and the two actually clash in some ways which cause bug repo - the upstream is dead - for supportability reasons we are dropping it in SLE15 ``` Is upstream alive again? A check of the GitHub repo shows that Oracle engineers seems to be busy developing it. After this many years a proper revisit of the source code is in order. We have some backlog in code reviews currently so it may take a bit before we can tackle this one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c6 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Neil Brown <nfbrown(a)suse.com> --- I think this is simply an omission from the switch statement in xs_tcp_setup_socket(). -ENOTCONN should be handled the same way as -ECONNREFUSED set. If it was, the error would be passed to xprt_wake_pending_tasks which end up calling call_connect_status() which does handle -ENOTCONN. I'll look thorough the code again when I get a bit more time and ensure that makes sense - then will suggest a patch upstream. Thanks for the report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231363] Agama's impossible partitioning layout proposal
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231363 https://bugzilla.suse.com/show_bug.cgi?id=1231363#c4 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com --- Comment #4 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- There are several things to clarify. (In reply to Jan Engelhardt from comment #2) > That, or the 'at least 17.5' is too generous, in the sense it should be > 'at least 1.6 GB' (size reported under "Software" notebook page). Let's start here. The minimum required size for each filesystem is hardcoded for the "product" (Leap, in this case). It is not calculated from the software selection. That was also the case for Leap 15.X and YaST. The size limits for Leap likely need to be adjusted at Agama. Now they are here: https://github.com/agama-project/agama/blob/master/products.d/leap_160.yaml… That says: - For root use at least 5GiB (17.5GiB is Btrfs snapshots are used) - For swap use at least the RAM size or 1GiB That's what the UI reflects. I personally would start de-activating the "enlarge to RAM" feature of the swap since that's controversial and I would not expect anyone to try Leap 16.0 on real hardware for now. > Deleting the swap partition reveals that "at least 17.5" translates to > "19.99" for some reason - and then fits the disk exactly. Well, "at least 17.5 GiB" translates to 19.99 GiB... because that's the available size. If you want to create a single partition of "at least 17 GiB" in a disk of X size (for X > 17 GiB), I expect you end up with a partition of size X. Why is that hard to understand? It's a matter of wording? > Expected Results: > Propose something that fits in 20 GB. Well. We are trying to change the approach with Agama compared to YaST (not written in stone yet, just playing with the concept). YaST started with the same requisites (17.5 GiB for "/" and a swap as big as the RAM). If it was not possible to make a proposal with those requirements, it re-tried several time relaxing the requisites (smaller RAM so loosing ability to suspend, disabling snapshots so "/" could be smaller, and so on). In the end, it was able to propose an initial setup... but the feature set of the operating system (snapshots, suspend, separate home...) changed without user interaction. In these initial versions of Agama we are trying with a different approach in which the user has to explicitly disable the auto-swap and/or snapshots in order to adjust requirements and then fit on the disk. As said, nothing is set in stone and we still need to think how to expose all that usability-wise. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231363] Agama's impossible partitioning layout proposal
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231363 https://bugzilla.suse.com/show_bug.cgi?id=1231363#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- See also https://github.com/agama-project/agama/issues/1159 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231336] default-system-colors do not work in gnome-terminal
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231336 https://bugzilla.suse.com/show_bug.cgi?id=1231336#c7 --- Comment #7 from Alynx Zhou <alynx.zhou(a)suse.com> --- (In reply to Lubos Kocman from comment #5) > It seems to be adwaita. Perhaps we're missing some packages or config. Nope, this is not GTK theme, I think what we need is org.gnome.desktop.interface gtk-theme. -- You are receiving this mail because: You are on the CC list for the bug.

1 0