August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1049997] system:install:head/patterns-base: pattern minimal_base not available
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

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

1 0

[Bug 1212963] AUDIT-0: review of selinux policy for kanidm-unixd tools and clients
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1212963 https://bugzilla.suse.com/show_bug.cgi?id=1212963#c7 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Johannes Segitz <jsegitz(a)suse.com> --- lets close this bug here. It's not really an AUDIT and with the current state I would prefer individual bugs for different problems -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228728] system marked as tainted: unmerged-bin
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228728 https://bugzilla.suse.com/show_bug.cgi?id=1228728#c3 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Assignee|systemd-maintainers(a)suse.de |screening-team-bugs(a)suse.de --- Comment #3 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Marcus Rückert from comment #2) > but shouldnt it then be "unmerged-sbin" because our /{usr,}bin are merged. Yes, I could agree with you that this name would make more sense, but I doubt systemd upstream would change it at this point, since v256 was already released. > if that merge is useful is to be discussed ... Yes, changing the severity to enhancement. Also resetting the assignee, because we don't want to diverge from systemd upstream and avoiding this warning, and this work would require involvement at the distribution level. FTR, link to the Fedora proposal: https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226541] Cockpit Packagekit does not appear in UI
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226541 https://bugzilla.suse.com/show_bug.cgi?id=1226541#c2 Robert Simai <robert.simai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(cody.henderson@su | |se.com) CC| |robert.simai(a)suse.com --- Comment #2 from Robert Simai <robert.simai(a)suse.com> --- I can't duplicate and I'm a bit confused. On my TW systems /lib is a symbolic link to usr/lib which makes the path valid and the module appears as expected. You're saying this is different on your system? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227908] New: auditd obsolete built-in options
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227908 Bug ID: 1227908 Summary: auditd obsolete built-in options Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4344305/modules/jour nal_check/steps/15 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeos-internal(a)suse.de Target Milestone: --- Found By: openQA Blocker: No Created attachment 876065 --> https://bugzilla.suse.com/attachment.cgi?id=876065&action=edit first boot log ## Observation Messages reporting obsolete options used have been found in the journal after firstboot of openSUSE-Tumbleweed-Minimal-VM.x86_64-1.0.0-Cloud-Snapshot20240715.qcow2 image. > Jul 16 04:26:51.145571 localhost systemd[1]: Starting Update is Completed... > Jul 16 04:26:51.185487 localhost auditd[1255]: Option builtin_af_unix line 10 is obsolete - using /sbin/audisp-af_unix > Jul 16 04:26:51.185493 localhost auditd[1255]: Option builtin line 11 is obsolete - update it > Jul 16 04:26:51.186062 localhost systemd[1]: Finished Update is Completed. > Jul 16 04:26:51.186340 localhost auditd[1255]: No plugins found, not dispatching events > Jul 16 04:26:51.186555 localhost auditd[1255]: Init complete, auditd 3.1.1 listening for events (startup state enable) > Jul 16 04:26:51.187204 localhost systemd[1]: Started Security Auditing Service. openQA test in scenario opensuse-Tumbleweed-JeOS-for-OpenStack-Cloud-x86_64-jeos-no-cloud@64bit_virtio fails in [journal_check](https://openqa.opensuse.org/tests/4344305/modules/journal_ch… ## Reproducible Image was tested previously in openQA -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228659] Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c16 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kukuk(a)suse.com) --- Comment #16 from Richard Brown <rbrown(a)suse.com> --- > > * libsystemd v255 instead of v256 > > It is present in some systems, and not in others. I do not see it in this > bug report log. > > * No ESP detected. Legacy system? > > That is sdbootutil complaining when boot_root cannot be found. I am trying > to reproduce this one, and can be related with systemd 256 update, as is > fetched from bootctl. > > I can focused in this last one. In my situation both of the above quoted issues were resolved by first updating systemd & systemd-boot, then rebooting, then doing a dup with everything else So it might not be worthwhile trying to split the baby but could make sense to consider the issues interlinked As Thorsten cannot fix his issue with a workaround I’m going to ask - can you provide a log of your failing transactional-updates? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228659] Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c15 --- Comment #15 from Richard Brown <rbrown(a)suse.com> --- Also, as this issue seems to be affecting MicroOS sdboot systems as well as Aeon, plus considering I’m on vacation from tomorrow evening.. I’d like to invite someone more appropriate to take the bug assignment -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228659] Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c13 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aplanas(a)suse.com) --- Comment #13 from Richard Brown <rbrown(a)suse.com> --- (In reply to Thorsten Kukuk from comment #12) > (In reply to Richard Brown from comment #11) > > in addition to the /etc/sysconfig/bootloader workaround > > This workaround does not work for me. That’s good to know.. but then I’m at a loss as to how to workaround the blocked transactional-updates My suspicion is that the sdbootutil tukit plugin is still trying to call libsystemd v255 even though the snapshot now has v256 That would explain the 255 not found so errors But I’m no expert on sdbootutil nor the tukit plugin Alberto, any ideas? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228691] YaST2 cannot display Chinese characters properly.
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228691 https://bugzilla.suse.com/show_bug.cgi?id=1228691#c8 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #8 from Steffen Winterfeldt <snwint(a)suse.com> --- This is the font situation in TW-20240131: 1:vm4877:~ # fc-list :lang=zh /usr/share/fonts/misc/b16.pcf.gz: Efont Biwidth:style=Regular /usr/share/fonts/truetype/uming.ttc: AR PL UMing TW MBE:style=Light /usr/share/fonts/truetype/uming.ttc: AR PL UMing TW:style=Light /usr/share/fonts/truetype/uming.ttc: AR PL UMing CN:style=Light /usr/share/fonts/truetype/uming.ttc: AR PL UMing HK:style=Light But b16.pcf is now gone - this was the font used by fbiterm - which was dropped recently. TL;DR: the YaST UI does not reflect (in all places) the updated font config after adding the Chinese font package correctly. In the past, this led to a mix of bitmap and truetype glyphs. Now that the bitmap font is gone, this leads to missing glyphs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227912] New: agetty fails to open credentials directory
by bugzilla_noreply＠suse.com 01 Aug '24

01 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227912 Bug ID: 1227912 Summary: agetty fails to open credentials directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4344305/modules/jour nal_check/steps/23 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: No Created attachment 876066 --> https://bugzilla.suse.com/attachment.cgi?id=876066&action=edit first boot log ## Observation After starting getty on a new console for the first time, the aggety service reports _failed to open credentials directory_. The message can also be reproduced by running "agetty --reload". Comparing to my local running TW, after reloading agetty, I do not see that it would try to open "/run/credentials/getty(a)tty6.service" as it is in the failing tests. > openat(AT_FDCWD, "/run/credentials/getty(a)tty6.service", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) > Jul 16 04:26:56.196274 cucaracha systemd[1]: Reached target Cloud-init target. > Jul 16 04:26:56.198126 cucaracha systemd[1]: Startup finished in 968ms (kernel) + 18.903s (initrd) + 7.626s (userspace) = 27.499s. > Jul 16 04:26:56.208799 cucaracha echo[1683]: Test service has started > Jul 16 04:26:56.210492 cucaracha systemd[1]: just_a_test.service: Deactivated successfully. > Jul 16 04:26:56.223204 cucaracha agetty[1621]: failed to open credentials directory > Jul 16 04:26:56.224013 cucaracha agetty[1622]: failed to open credentials directory > Jul 16 04:26:56.224656 cucaracha agetty[1620]: failed to open credentials directory > Jul 16 04:26:57.726090 cucaracha systemd[1]: Started Getty on tty6. > Jul 16 04:26:57.730625 cucaracha agetty[1712]: failed to open credentials directory > Jul 16 04:26:57.742108 cucaracha kernel: clocksource: Long readout interval, skipping watchdog check: cs_nsec: 12595040318 wd_nsec: 506657651 > Jul 16 04:27:01.507143 cucaracha systemd[1]: Created slice User Slice of UID 0. > Jul 16 04:27:01.519654 cucaracha systemd[1]: Starting User Runtime Directory /run/user/0... > Jul 16 04:27:01.521565 cucaracha systemd-logind[1317]: New session 1 of user root. > Jul 16 04:27:01.529220 cucaracha systemd[1]: Finished User Runtime Directory /run/user/0. > -- > Jul 16 04:29:02.669256 cucaracha usermod[1873]: add 'bernhard' to group 'dialout' > Jul 16 04:29:08.135346 cucaracha usermod[1880]: add 'tester_ssh' to group 'tty' > Jul 16 04:29:08.135862 cucaracha usermod[1880]: add 'tester_ssh' to group 'dialout' > Jul 16 04:29:09.186586 cucaracha chronyd[1473]: Source 147.251.48.140 replaced with 162.159.200.123 (2.opensuse.pool.ntp.org) > Jul 16 04:29:09.299114 cucaracha systemd[1]: Started Getty on tty4. > Jul 16 04:29:09.314441 cucaracha agetty[1886]: failed to open credentials directory > Jul 16 04:29:13.079585 cucaracha systemd[1]: Created slice User Slice of UID 1000. > Jul 16 04:29:13.095544 cucaracha systemd[1]: Starting User Runtime Directory /run/user/1000... > Jul 16 04:29:13.097288 cucaracha systemd-logind[1317]: New session 3 of user bernhard. > Jul 16 04:29:13.102642 cucaracha systemd[1]: Finished User Runtime Directory /run/user/1000. > Jul 16 04:29:13.105587 cucaracha systemd[1]: Starting User Manager for UID 1000... > -- > Jul 16 04:31:20.156673 cucaracha login[1621]: ROOT LOGIN ON hvc0 > Jul 16 04:31:20.938274 cucaracha systemd[1]: Reloading requested from client PID 2772 ('systemctl') (unit session-5.scope)... > Jul 16 04:31:20.938491 cucaracha systemd[1]: Reloading... > Jul 16 04:31:21.160153 cucaracha systemd[1]: Reloading finished in 221 ms. > Jul 16 04:31:21.203686 cucaracha systemd[1]: Started Serial Getty on hvc1. > Jul 16 04:31:21.222165 cucaracha agetty[2800]: failed to open credentials directory openQA test in scenario opensuse-Tumbleweed-JeOS-for-OpenStack-Cloud-x86_64-jeos-no-cloud@64bit_virtio fails in [journal_check](https://openqa.opensuse.org/tests/4344305/modules/journal_ch… ## Affected package: util-linux-2.40.1-4.1.x86_64 ## Reproducible Image was not tested before in openQA -- You are receiving this mail because: You are on the CC list for the bug.

1 2