August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1229555] New: Wicked dummy interfaces no longer come up / "no-device"
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229555 Bug ID: 1229555 Summary: Wicked dummy interfaces no longer come up / "no-device" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876866 --> https://bugzilla.suse.com/attachment.cgi?id=876866&action=edit asgard2.i.o.o journal after boot Hi, we have various interfaces of type `dummy` configured on our openSUSE infrastructure firewall VMs, so far with no issues. They are all configured equally, here is one example: ``` # more /etc/sysconfig/network/ifcfg-d-os-code # ... comments ... STARTMODE='auto' BOOTPROTO='none' INTERFACETYPE='dummy' ``` Since installing updates and rebooting today, they no longer come up (neither automatically nor manually through ifup), returning "no-device". I will attach some information which I hope is useful .. .. from after boot: - `journalctl` .. from after enabling WICKED_DEBUG=all/WICKED_LOG_LEVEL=debug and restarting wickedd: - `wicked --debug all ifup d-os-code` # again just one example interface - `wicked show-config` - `wicked ifstatus --verbose all` - `grep 2024-08-21 /var/log/zypp/history` Let me know if anything of interest is missing. Would appreciate any ideas! I'm reluctant to update the second machine in the pair with this issue. There is another (presumably kernel) issue after the update, which I think is not related and hence reported separately at https://bugzilla.opensuse.org/show_bug.cgi?id=1229552. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1229124] New: firefox, fonts-config: wide spaces on pages with emoji fonts from Apple or Microsoft
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229124 Bug ID: 1229124 Summary: firefox, fonts-config: wide spaces on pages with emoji fonts from Apple or Microsoft Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: draskmont(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've noticed the classic issue of large gaps between word on Firefox while trying to use Notion. Not really a new issue in Firefox (fontconfig giving preference to "Noto Color Emoji" is almost always the culprit), but it only affects openSUSE this time. It happens when it tries to render the fonts "Apple Color Emoji" or "Segoe UI Emoji" instead of falling back to another font. Having tried Flatpak, and live ISOs of other distributions; none of them (besides openSUSE) have this problem. Chromium-based browsers also don't have this problem. Removing /etc/fonts/conf.d/49-family-default-emoji.conf fixed the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225142] New: Kernel oops in nfs
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225142 Bug ID: 1225142 Summary: Kernel oops in nfs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875055 --> https://bugzilla.suse.com/attachment.cgi?id=875055&action=edit Kernel oops log As I already mentioned in bug 1223640 I'm getting oops in NFS (see the attached log) It happens in both kernel-default-5.14.21-150500.55.59.1.x86_64 kernel-default-5.14.21-150500.55.62.2.x86_64 Until and including the previous one it's been fine: kernel-default-5.14.21-150500.55.52.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1229042] New: Enable kernel-default-livepatch-devel for TW since it's already enabled on Leap
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229042 Bug ID: 1229042 Summary: Enable kernel-default-livepatch-devel for TW since it's already enabled on Leap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Remove the condition that currently only applies to openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1229721] New: journal is not saved to persistent storage since august 20 2024
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229721 Bug ID: 1229721 Summary: journal is not saved to persistent storage since august 20 2024 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a few unexpected reboots/powerdowns (hardware battery controller of my thinkpad locked up and needed reset), I found that there are no journal entries persisted since I rebooted on august 20: ``` mixi:~ # journalctl --since "2024-08-20 20:54:57"|head Aug 20 20:54:57 mixi systemd[1]: Unmounted /opt. Aug 20 20:54:57 mixi systemd[1]: root.mount: Deactivated successfully. Aug 20 20:54:57 mixi systemd[1]: Unmounted /root. Aug 20 20:54:57 mixi systemd[1]: srv.mount: Deactivated successfully. Aug 20 20:54:57 mixi systemd[1]: Unmounted /srv. Aug 20 20:54:57 mixi systemd[1]: tmp.mount: Deactivated successfully. -- Boot 5ab5c43121a740329f4a0b3dfb160b65 -- Aug 25 10:32:45 mixi kernel: Linux version 6.11.0-rc4-4.g884d35d-default (geeko@buildhost) (gcc (SUSE Linux) 13.3.1 20240807 [revision 9d368828bd4d04ce507e02a581be850fca849fae], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.43.0.20240806-1) #1 SMP PREEMPT_DYNAMIC Fri A ug 23 20:02:05 UTC 2024 (884d35d) Aug 25 10:32:45 mixi kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.11.0-rc4-4.g884d35d-default root=/dev/mapper/system-root rd.lvm. lv=system/swap resume=/dev/system/swap mitigations=auto security=apparmor splash=silent Aug 25 10:32:45 mixi kernel: BIOS-provided physical RAM map: ``` I did reboot a few times already today: ``` mixi:~ # last reboot|head reboot system boot 6.11.0-rc4-4.g88 Sun Aug 25 10:32 - still running reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:22 - 10:32 (00:10) reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:16 - 10:20 (00:04) reboot system boot 6.11.0-rc4-2.g59 Sun Aug 25 10:08 - 10:12 (00:03) reboot system boot 6.11.0-rc4-2.g59 Sat Aug 24 23:28 - crash reboot system boot 6.11.0-rc4-2.g59 Tue Aug 20 20:55 - crash reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:19 - 20:54 (2+06:35) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:11 - 14:18 (00:07) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:09 - 14:11 (00:01) reboot system boot 6.11.0-rc3-3.g66 Sun Aug 18 14:04 - 14:07 (00:02) ``` But journalctl does not know about those: ``` mixi:~ # journalctl --list-boots |tail -9 3eb9bb2611184870a1ed229d864a69b8 Sat 2024-07-27 10:36:35 CEST Sat 2024-07-27 10:45:05 CEST -8 4bf6bb115cfc4ab4b3126b1a00c6c9b7 Sat 2024-07-27 10:45:20 CEST Mon 2024-07-29 16:13:28 CEST -7 8286230fe28344c59fa48996fd0807a7 Mon 2024-07-29 16:14:34 CEST Tue 2024-08-13 11:29:22 CEST -6 1a4645e76c634668bce7dce043b72833 Tue 2024-08-13 11:31:06 CEST Tue 2024-08-13 11:32:44 CEST -5 eebf61e09fe24938ad85d14aa7727d9c Tue 2024-08-13 11:33:00 CEST Sun 2024-08-18 14:04:40 CEST -4 2c1c576c22d84d82b8373c6df2a57d42 Sun 2024-08-18 14:04:57 CEST Sun 2024-08-18 14:07:02 CEST -3 855b89b2e857488fa542912da26616b8 Sun 2024-08-18 14:09:33 CEST Sun 2024-08-18 14:11:05 CEST -2 210c7a03d56a4d3e8f316b3c5feb0691 Sun 2024-08-18 14:11:20 CEST Sun 2024-08-18 14:18:36 CEST -1 d131d91a089e4de6ba71c982e7a97167 Sun 2024-08-18 14:19:38 CEST Tue 2024-08-20 20:54:57 CEST 0 5ab5c43121a740329f4a0b3dfb160b65 Sun 2024-08-25 10:32:45 CEST Sun 2024-08-25 11:23:23 CEST ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1215976] New: Hawk fails to build in Factory
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215976 Bug ID: 1215976 Summary: Hawk fails to build in Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the update in the Factory, there has disappeared the useradd and groupadd commands. Adding the shadow package in the BuildRequires has fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220891] New: HAWK: Update sanity check for passwd existance
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220891 Bug ID: 1220891 Summary: HAWK: Update sanity check for passwd existance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The /etc/pam.d/passwd is optional in fact, for example there is none in the tumbleeweed. So let's relax the condition: if there is no /etc/pam.d/passwd, check if there is a passwd binary in /usr/bin of /usr/sbin. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220890] New: Update validation for the newer versions of rails
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220890 Bug ID: 1220890 Summary: Update validation for the newer versions of rails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with Rails6.1 there has changed the validation. Namely, the ActiveModel::Errors has changed it's structure. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223862] New: Packages with explicit x86_v3 target fail to build
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223862 Bug ID: 1223862 Summary: Packages with explicit x86_v3 target fail to build Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: cgoll(a)suse.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Packages with optimized code for AVX2 (x86_v3) or AVX (x86_v4) need this code streams explicitly enabled during the build process (faiss or gpt4all) so its not possible to use the %{?suse_build_hwcaps_libs} macro. When doing this, the packages are built, but some final scripts fail cleaning up the build root fail with the error: ``` [ 51s] find: cannot delete '//.build.packages/RPMS/x86_64_v3': Directory not empty [ 51s] ``` A failed example can found under: https://build.opensuse.org/package/show/home:mslacken:ml/faiss_bug where the two codestream build for AVX2 and AVX512 fail to build. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed:<br/><br/>[...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 6