January 2024 - openSUSE Factory - openSUSE Mailing Lists

Re: Leap 16??? Why am I finding this out on Fosstodon??
by Eric Schirra 16 Jan '24

16 Jan '24

Am 16. Januar 2024 17:15:27 MEZ schrieb "Dan Čermák" <dcermak(a)suse.com>: >Hi Eric, > >Eric Schirra <ecsos(a)opensuse.org> writes: > >> Am 16. Januar 2024 16:39:39 MEZ schrieb "Dan Čermák via openSUSE Factory" <factory(a)lists.opensuse.org>: >>>Eric Schirra <ecsos(a)opensuse.org> writes: >>> >>>> Am 16. Januar 2024 09:30:25 MEZ schrieb Simon Lees <sflees(a)suse.de>: >>>>> >>>>> >>>>>On 1/16/24 14:43, Lew Wolfgang wrote: >>>>>> On 1/15/24 20:03, Lew Wolfgang wrote: >>>>>>> On 1/15/24 19:26, Simon Lees wrote: >>>>>>>>> Will the anticipated upgrade from 15 to 16 support these use cases? Or, >>>>>>>>> should we start looking for alternatives now? I really want to stay with >>>>>>>>> openSUSE if at all possible, but I have a responsibility to my users to >>>>>>>>> maintain continuity of operations going forward. Is it time for (shudder) >>>>>>>>> RHEL or a BSD? BTW, before 1998 we used Sun Solaris and SunOS >>>>>>>>> starting in 1986. >>>>>>>> >>>>>>>> >>>>>>>> ALP as it sits now is very different to ALP as it was first announced, alongside the read only transactional MicroOS style distro's that will be built from ALP, the successor to SLES 15 will also be built from ALP which is what Leap 16 will be built from. >>>>>>>> >>>>>>>> So containers won't be necessary, in many cases Upgrades from Leap 15 will be supported and you should expect an experience that's much closer to Leap 15 then that of MicroOS, although it won't be completely the same >>>>>>> >>>>>>> I know it's too soon to say, but are there guesses for how it will be different? >>>>>>> BTW, our users use KDE., Thunderbird, and SmartCards. >>>>>> >>>>>> I forgot to mention that we also use X11 display forwarding for remote displays. >>>>>> As I understand things, Wayland didn't support this, does it now? Will X11 be in 16? >>>>> >>>>>I have a version of X11 building on top of the ALP code base and my plan is to submit it to 16, I also still have several usecases for it. From my research I haven't found a reason why it would be any harder to put KDE on top of Leap 16 then it is for Leap 15 (some decisions around lifecycle might actually make it easier). But at the end of the day that will be up to the KDE team. >>>>> >>>>>Similarly Thunderbird will be up to its current maintainer, but as a worst case you'd need to move to the flatpack if the maintainer decided it was too much effort. This announcement is new and much of the codebase isn't even there on the SUSE ALP side yet so its still somewhat hard for maintainers to gauge the amount of effort they will need to put in. >>>> >>>> So it does. >>>> Even Suse people have use cases that don't work with Alp. First reason not to use Leap anymore. >>>> No more KDE under Leap. >>>> Second reason not to be able to use Leap anymore. >>>> No Thunderbird or Firefox under Leap. Only via flatpack? Third reason for no longer being able to use Leap. >>>> Has anyone ever thought about how to install different software (Thunderbird or Firefox etc.) if you are in an internal company network so that you cannot access the Internet? >>>> How can LeapAlp be used sensibly? >>> >>>This is all pure speculation. SLE 16 is still under development with >>>many cornerstones still not being fully defined. There will most >>>certainly be a Firefox in it (it is currently in the ALP codestream) and >>>there might be a KDE in it, if someone sends it there from Factory. This >>>is all not different from the way the current Leap works (or doesn't >>>work, depending on how you see it). >>> >>>Please, let's not freak out over rumors. Leap 16 will probably come and >>>it will probably be very similar to what you are used to. >>> >>>You might have to use a flatpak or two, but I have not yet given up hope >>>that we'll be able to build these on OBS. >> >> Why speculation? > >Because everything involving the Leap 15 successor is speculation at >this point. Nothing is clear and defined yet, except for a few very >basic things, like a non-immutable distro with next to no reliance on >containers or flatpaks. Or that it will be based on SLE 16. That's more >or less all that is known at the moment. > >> Isn't that how it is in aeon? Kalpa is still Alpha. And if I understand correctly, one person is working on it. >> Isn't it the case in aeon that it's only KDE? >> And in Aeon I have to install Firefox via flatpack? > >Aeon and Kalpa are based on Tumbleweed and are build specifically build >with flatpaks & immutable root in mind. Their existence has no >implication on Leap 16 or ALP. > >I see how you might come to this conclusion, as the official >communication around ALP has been spotty at best and confusing at >worst. But at the moment it looks like there will be a very traditional >distro based on ALP (with no flatpaks and no containers, unless you want >those), called SLE 16. And Leap 16 will be based on SLE 16. So kinda >like things are at the moment. That sounds better. Let's hope for the best. >> Every flatpack is one too many. >> How am I supposed to install or update it in an internal closed network without internet access? > >That is a problem I have indeed not considered. Thanks for bringing that >up! Gladly done. :-) >P.S.: you did not send your reply to the mailing list, hence mine wasn't > sent to the list either. However, feel free to reply to the full > list, this is not confidential or private information. Oh. That was an oversight. It's just nothing on a smartphone. :-) Regards Eric

1 0

Leap 16??? Why am I finding this out on Fosstodon??
by Fritz Hudnut 16 Jan '24

16 Jan '24

et al: Just saw on Fosstodon that there are plans for Leap 16 and/or an in between 15.7 to carry on the tradition of Leap?? But no apparent mention of it here?? I am glad to hear that, I do like Leap 15.6, even though it doesn't revive itself from suspend, it has fared better than my former Slow Roll system, which disappeared in a puff of cyber smoke . . . . I will be looking forward to the continuation of the Leap lineage . . . long live Leap for many iterations to come.

15 27

Slowroll cannot install wine
by Larry Len Rainey 16 Jan '24

16 Jan '24

2 2

Webcam no longer found
by Christian Boltz 15 Jan '24

15 Jan '24

Hello, I'm not sure if this is a regression in Tumbleweed or a hardware failure, therefore I'll ask before opening a bug: The webcam in my laptop no longer works, and also doesn't appear in the boot log anymore. The last time I used the camera was a week ago (2024-01-09), but in the log it appeared until 2024-01-11 [1]: Jan 11 19:35:10 tux kernel: usb 3-8: new high-speed USB device number 4 using xhci_hcd Jan 11 19:35:11 tux kernel: usb 3-8: New USB device found, idVendor=5986, idProduct=055c, bcdDevice= 6.05 Jan 11 19:35:11 tux kernel: usb 3-8: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Jan 11 19:35:11 tux kernel: usb 3-8: Product: BisonCam, NB Pro Jan 11 19:35:11 tux kernel: usb 3-8: Manufacturer: Generic Jan 11 19:35:11 tux kernel: usb 3-8: SerialNumber: 200901010001 [...] Jan 11 19:35:19 tux kernel: usb 3-8: Found UVC 1.00 device BisonCam, NB Pro (5986:055c) Am I the only one who "lost" the camera? Regards, Christian Boltz [1] Tumbleweed snapshot numbers related to these dates on request - I run zypper dup nearly daily. -- Security does only work as long as it does not get into the way of whatever fills the fridge. [Kristian Köhntopp in https://plus.google.com/+KristianKöhntopp/posts/PY9GZduTsrd]

6 9

New Tumbleweed snapshot 20240114 released!
by Dominique Leuenberger 15 Jan '24

15 Jan '24

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: MozillaFirefox (121.0 -> 121.0.1) kbd (2.6.3 -> 2.6.4) man-pages python-Jinja2 (3.1.2 -> 3.1.3) systemd (254.5 -> 254.8) xdg-desktop-portal === Details === ==== MozillaFirefox ==== Version update (121.0 -> 121.0.1) Subpackages: MozillaFirefox-translations-common - Mozilla Firefox 121.0.1 * Fixed unexpected line wrapping in some CJK contexts caused by changes in ideographic space handling. bmo#1870973) * Fixed a hang when loading sites containing column-based layouts under some circumstances. bmo#1867784) * Fixed missing rounded corners for videos playing over another video. bmo#1869994) * Fixed Firefox not closing properly and other applications being unable to use a USB security key after being previously used during a Firefox session. bmo#1863135) ==== kbd ==== Version update (2.6.3 -> 2.6.4) Subpackages: kbd-legacy - Update to version 2.6.4: - Use AX_ADD_FORTIFY_SOURCE to avoid redefining _FORTIFY_SOURCE - Do not look up include files in the current working directory ==== man-pages ==== - Do not remove bpf-helpers.7, as this is not provided by the bpftool package any more. ==== python-Jinja2 ==== Version update (3.1.2 -> 3.1.3) - update to 3.1.3 (bsc#1218722, CVE-2024-22195): * Fix compiler error when checking if required blocks in parent templates are xmlattr filter does not allow keys with spaces. * Make error messages stemming from invalid nesting of {% trans %} blocks more helpful. :pr:`1916` ==== systemd ==== Version update (254.5 -> 254.8) Subpackages: libsystemd0 libsystemd0-32bit libudev1 systemd-32bit systemd-boot systemd-container systemd-coredump systemd-lang udev - Add 5001-Revert-udev-update-devlink-with-the-newer-device-nod.patch 5002-Revert-udev-revert-workarounds-for-issues-caused-by-.patch It seems that systemd upstream has a dubious way to fix broken code these days... let's revert these hacks until a final decision is taken to solve https://github.com/systemd/systemd/issues/28141. See also https://github.com/systemd/systemd/pull/30075. - Import commit 67a5ac1043417d900bf417a884372ae14a96ef69 (merge of v254.8) For a complete list of changes, visit: https://github.com/openSUSE/systemd/compare/071ac409a0564863657d8f8a5a35e6a… - udev(-mini)?: ensure %_modulesloaddir exists and is owned properly. Allows other packages to install modules without worry of the parent directory. We do not ensure /etc/modules-load.d exists in the -mini flavor, as that directory is not meant to be used by packages. ==== xdg-desktop-portal ==== Subpackages: xdg-desktop-portal-lang - Also own the packaging directory used by portals themselves

1 0

Fwd: Re: Leap 16??? Why am I finding this out on Fosstodon??
by Martin Schlander 15 Jan '24

15 Jan '24

Accidentally responed off-list. Darn phone. I guess these Fosstodon guys are referencining newso.o.o. https://news.opensuse.org/2024/01/15/clear-course-is-set-for-os-leap/ That bit of news doesn't clearly state at all that Leap 16 will not be useful for the usecase of the vast majority of existing Leap users. Unless I have misunderstood a lot of things. So this kind of confusion and false hope is probably to be expected. (sorry for top posting) > > Den Mandag den 15. januar 2024 skrev Knurpht-openSUSE: > > On maandag 15 januari 2024 18:51:59 CET Fritz Hudnut wrote: > > > et al: > > > > > > Just saw on Fosstodon > > > > Like "I read on the Internet": without a link it does not exist. So I will not > > relate to that content. > > > that there are plans for Leap 16 and/or an in between > > > 15.7 to carry on the tradition of Leap?? But no apparent mention of it > > > here?? > > > > Sure there are: "openSUSE Release Engineering meeting 10.06.2024" is the > > recent one. > > > I am glad to hear that, I do like Leap 15.6, even though it doesn't > > > revive itself from suspend, it has fared better than my former Slow Roll > > > system, which disappeared in a puff of cyber smoke . . . . > > > > Leap 15.6 is still in it's development phase, and is definitely not released > > yet. Did fosstodon say as well that it was? > > > > > > I will be looking forward to the continuation of the Leap lineage . . . long > > > live Leap for many iterations to come. > > And your hope is based on fosstodon "news" ? > > > > -- > > Gertjan Lettink a.k.a. Knurpht > > openSUSE Board > > openSUSE Forums Team > > > > -- > Sendt fra min Sailfish enhe -- Sendt fra min Sailfish enhed

1 0

New Tumbleweed snapshot 20240112 released!
by Dominique Leuenberger 14 Jan '24

14 Jan '24

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: container-selinux (2.222.0 -> 2.228.0) gcc13 (13.2.1+git8109 -> 13.2.1+git8205) health-checker (1.10 -> 1.10+git20240111.cb84209) jasper (4.1.1 -> 4.1.2) kernel-source (6.6.10 -> 6.6.11) libgedit-amtk libjcat libstorage-ng (4.5.171 -> 4.5.172) linux-glibc-devel (6.6 -> 6.7) microos-tools (2.21+git5 -> 2.21+git9) pcr-oracle pipewire (1.0.0 -> 1.0.1) python-gevent python-greenlet (3.0.2 -> 3.0.3) python-tornado6 python-urllib3 samba (4.19.2+git.324.fa0b54b91b -> 4.19.4+git.339.acf1ccaa020) selinux-policy (20231124 -> 20240104) zstd === Details === ==== container-selinux ==== Version update (2.222.0 -> 2.228.0) - Update to version 2.228: * Allow container domains to watch fifo_files * container_engine_t: improve for podman in kubernetes case * Allow spc_t to transition to install_t domain * Default to allowing containers to use dri devices * Allow access to BPF Filesystems * Fix kubernetes transition rule * Label kubensenter as well as kubenswrapper * Allow container domains to execute container_runtime_tmpfs_t files * Allow container domains to ptrace themselves * Allow container domains to use container_runtime_tmpfs_t as an entrypoint * Add boolean to allow containers to use dri devices * Give containers access to pod resources endpoint * Label kubenswrapper kubelet_exec_t ==== gcc13 ==== Version update (13.2.1+git8109 -> 13.2.1+git8205) Subpackages: cpp13 gcc13-locale libasan8 libatomic1 libgcc_s1 libgcc_s1-32bit libgccjit0 libgfortran5 libgomp1 libhwasan0 libitm1 liblsan0 libobjc4 libquadmath0 libstdc++6 libstdc++6-32bit libstdc++6-locale libstdc++6-pp libstdc++6-pp-32bit libtsan2 libubsan1 - Update to gcc-13 branch head, 36ddb5230f56a30317630a928, git8205 ==== health-checker ==== Version update (1.10 -> 1.10+git20240111.cb84209) Subpackages: health-checker-plugins-MicroOS - Update to version 1.10+git20240111.cb84209: * Add missing rule for health-checker.service.8 * Don't generate html documentation * Fixing some typo's and improving the UX of the health-checker output * Fix a typo in README.md ==== jasper ==== Version update (4.1.1 -> 4.1.2) - Update to 4.1.2: * Fix invalid memory write bug (#367) (CVE-2023-51257). * Fix missing range check in the JPC encoder (#368). ==== kernel-source ==== Version update (6.6.10 -> 6.6.11) - keys, dns: Fix size check of V1 server-list header (git-fixes). - commit 05ae4ad - Linux 6.6.11 (bsc#1012628). - keys, dns: Fix missing size check of V1 server-list header (bsc#1012628). - ALSA: hda/tas2781: do not use regcache (bsc#1012628). - ALSA: hda/tas2781: move set_drv_data outside tasdevice_init (bsc#1012628). - ALSA: hda/tas2781: remove sound controls in unbind (bsc#1012628). - ALSA: hda/realtek: enable SND_PCI_QUIRK for hp pavilion 14-ec1xxx series (bsc#1012628). - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook (bsc#1012628). - ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6 (bsc#1012628). - drm/amd/display: pbn_div need be updated for hotplug event (bsc#1012628). - mptcp: prevent tcp diag from closing listener subflows (bsc#1012628). - Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()" (bsc#1012628). - drm/mgag200: Fix gamma lut not initialized for G200ER, G200EV, G200SE (bsc#1012628). - cifs: cifs_chan_is_iface_active should be called with chan_lock held (bsc#1012628). - cifs: do not depend on release_iface for maintaining iface_list (bsc#1012628). - KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL (bsc#1012628). - accel/qaic: Fix GEM import path code (bsc#1012628). - accel/qaic: Implement quirk for SOC_HW_VERSION (bsc#1012628). - wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ (bsc#1012628). - drm/bridge: parade-ps8640: Never store more than msg->size bytes in AUX xfer (bsc#1012628). - drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer (bsc#1012628). - drm/bridge: ps8640: Fix size mismatch warning w/ len (bsc#1012628). - netfilter: nf_tables: set transport offset from mac header for netdev/egress (bsc#1012628). - nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local (bsc#1012628). - octeontx2-af: Fix marking couple of structure as __packed (bsc#1012628). - drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern (bsc#1012628). - drm/i915/perf: Update handling of MMIO triggered reports (bsc#1012628). - ice: Fix link_down_on_close message (bsc#1012628). - ice: Shut down VSI with "link-down-on-close" enabled (bsc#1012628). - i40e: Fix filter input checks to prevent config with invalid values (bsc#1012628). - igc: Report VLAN EtherType matching back to user (bsc#1012628). - igc: Check VLAN TCI mask (bsc#1012628). - igc: Check VLAN EtherType mask (bsc#1012628). - ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable (bsc#1012628). - ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and offset (bsc#1012628). - mlxbf_gige: fix receive packet race condition (bsc#1012628). - net: sched: em_text: fix possible memory leak in em_text_destroy() (bsc#1012628). - r8169: Fix PCI error on system resume (bsc#1012628). - net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) (bsc#1012628). - selftests: bonding: do not set port down when adding to bond (bsc#1012628). - ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init (bsc#1012628). - sfc: fix a double-free bug in efx_probe_filters (bsc#1012628). - net: bcmgenet: Fix FCS generation for fragmented skbuffs (bsc#1012628). - netfilter: nf_nat: fix action not being set for all ct states (bsc#1012628). - netfilter: nft_immediate: drop chain reference counter on error (bsc#1012628). - net: Save and restore msg_namelen in sock_sendmsg (bsc#1012628). - i40e: fix use-after-free in i40e_aqc_add_filters() (bsc#1012628). - ASoC: meson: g12a-toacodec: Validate written enum values (bsc#1012628). - ASoC: meson: g12a-tohdmitx: Validate written enum values (bsc#1012628). - ASoC: meson: g12a-toacodec: Fix event generation (bsc#1012628). - ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux (bsc#1012628). - i40e: Restore VF MSI-X state during PCI reset (bsc#1012628). - igc: Fix hicredit calculation (bsc#1012628). - apparmor: Fix move_mount mediation by detecting if source is detached (bsc#1012628). - virtio_net: avoid data-races on dev->stats fields (bsc#1012628). - virtio_net: fix missing dma unmap for resize (bsc#1012628). - net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues (bsc#1012628). - net/smc: fix invalid link access in dumping SMC-R connections (bsc#1012628). ... changelog too long, skipping 110 lines ... - commit f421cf4 ==== libgedit-amtk ==== Subpackages: libgedit-amtk-5-0 libgedit-amtk-5-lang typelib-1_0-Amtk-5 - Update spec file to conclicts the legacy amtk-devel, which shipped the same file Amtk-%{api_ver}.gir as libgedit-amtk does. ==== libjcat ==== - Do not install test files: pass -Dtest=false to meson instead of Dtest=true (aids with reproducible build, boo#1218715). - Add check section and run meson test. ==== libstorage-ng ==== Version update (4.5.171 -> 4.5.172) Subpackages: libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 - merge gh#openSUSE/libstorage-ng#978 - added get_linux_partition_id() taking Arch parameter - make git ignore javascript in generated documentation - coding style - cleanup - 4.5.172 ==== linux-glibc-devel ==== Version update (6.6 -> 6.7) - Update to kernel headers 6.7 ==== microos-tools ==== Version update (2.21+git5 -> 2.21+git9) - Update to version 2.21+git9: * Add man-online command * Drop support for sle15 builds * Add OBS CI workflow ==== pcr-oracle ==== - Add fix_efi_measure.patch to fix the measurement of EFI binaries ==== pipewire ==== Version update (1.0.0 -> 1.0.1) Subpackages: gstreamer-plugin-pipewire libpipewire-0_3-0 pipewire-alsa pipewire-jack pipewire-lang pipewire-libjack-0_3 pipewire-modules-0_3 pipewire-pulseaudio pipewire-spa-plugins-0_2 pipewire-spa-tools pipewire-tools - Update to version 1.0.1: * Highlights - Work around the buggy ALSA backend in libcanberra by forcing the pulse backend in module-x11-bell. - Fix a race in the device info updates in pulse-server. - Fix timing and rate matching in ALSA sequencer. - Improve timing information in JACK and from the ALSA driver. - More small fixes and improvements. * PipeWire - Fix a build issue when examples where disabled. - Avoid some compiler warnings. - Avoid some bitfield data races. (#3706) * Modules - Bump the PTP driver priority. (#3217) - Support the previous "allowed" permission in the access module. - Fix filename leak in module-filter-chain. - Work around the buggy ALSA backend in libcanberra by forcing the pulse backend in module-x11-bell. (#3688) - Fix a race in the device info updates in pulse-server. - Fix compatibility in RAOP. (#3698) * SPA - Handle ALSA picth control errors correctly - Clamp buffer-frames correctly. (#3000) - Fix timing and rate matching in ALSA sequencer. (#3657) - Revert a commit that could result in current time in the future in the timing updates. - Improve adapter state checks. - Remove the timer from the ALSA pcm. - Fix timeout in freewheel driver. * Pulse-server - Also handle active ports for monitor sources. - Fix zeroconf-publish format properties. * JACK - Improve timing and transport calculations. - Handle -ENOENT from the core and don't error out. * GStreamer - Handle node port removal in the device provider. (#3708) - Improve error handling while connecting. - Fix dts_offset. ==== python-gevent ==== - Clean obsolete old python and old distribution directives * Only 15.5+ with the sle15 python module and Tumbleweed have the required Python 3.8+ * Drop fix-no-return-in-nonvoid-function.patch - Update test suite execution * Use -u-network flag to disable network tests * Add gevent-opensuse-nocolor-tests.patch -- Avoid colorization of test output in obs runners * Add gevent-fix-unittest-returncode-py312-c1.patch and gevent-fix-unittest-returncode-py312-c2.patch gh#gevent/gevent#2012 ==== python-greenlet ==== Version update (3.0.2 -> 3.0.3) - Update to 3.0.3 * Python 3.12: Restore the full ability to walk the stack of a suspended greenlet; previously only the innermost frame was exposed. See issue 388. Fix by Joshua Oreman in PR 393. - Disable building the docs: Now requires the furo theme, which is not available. ==== python-tornado6 ==== - Add patch openssl-3.2.patch gh#tornadoweb/tornado#3355 ==== python-urllib3 ==== - Add upstream patch openssl-3.2.patch, to fix tests with opennssl 3.2.0, gh#urllib3/urllib3#3271 ==== samba ==== Version update (4.19.2+git.324.fa0b54b91b -> 4.19.4+git.339.acf1ccaa020) Subpackages: libsamba-policy0-python3 samba-ad-dc-libs samba-client samba-client-32bit samba-client-libs samba-client-libs-32bit samba-gpupdate samba-ldb-ldap samba-libs samba-libs-python3 samba-python3 samba-winbind samba-winbind-libs samba-winbind-libs-32bit - Remove -x from bash shebang update-apparmor-samba-profile; (bsc#1218431). - Update to 4.19.4 * net changesecretpw cannot set the machine account password if secrets.tdb is empty; (bso#13577). * For generating doc, take, if defined, env XML_CATALOG_FILES; (bso#15540). * Trivial C typo in nsswitch/winbind_nss_netbsd.c; (bso#15541). * vfs_linux_xfs is incorrectly named; (bso#15542). * systemd stumbled over copyright-message at smbd startup; (bso#15377). * Following intermediate abolute share-local symlinks is broken; (bso#15505). * ctdb RELEASE_IP causes a crash in release_ip if a connection to a non-public address disconnects first; (bso#15523). * shadow_copy2 broken when current fileset's directories are removed; (bso#15544). * smbd does not detect ctdb public ipv6 addresses for multichannel exclusion; (bso#15534). * 'force user = localunixuser' doesn't work if 'allow trusted domains = no' is set; (bso#15469). * smbget debug logging doesn't work; (bso#15525). * smget: username in the smburl and interactive password entry doesn't work; (bso#15532). * smbget auth function doesn't set values for password prompt correctly; (bso#15538). * Unable to copy and write files from clients to Ceph cluster via SMB Linux gateway with Ceph VFS module; (bso#15440). * Multichannel refresh network information; (bso#15547). - Update to 4.19.3 * sid_strings test broken by unix epoch > 1700000000; (bso#15520). * smbd crashes if asked to return full information on close of a stream handle with delete on close disposition set; (bso#15487). * smbd: fix close order of base_fsp and stream_fsp in smb_fname_fsp_destructor(); (bso#15521). * Improve logging for failover scenarios; (bso#15499). * Files without "read attributes" NFS4 ACL permission are not listed in directories; (bso#15093). * CVE-2018-14628 [SECURITY] Deleted Object tombstones visible in AD LDAP to normal users; (bso#13595). * Kerberos TGS-REQ with User2User does not work for normal accounts; (bso#15492). * vfs_gpfs stat calls fail due to file system permissions; (bso#15507). * Samba doesn't build with Python 3.12; (bso#15513). ==== selinux-policy ==== Version update (20231124 -> 20240104) Subpackages: selinux-policy-targeted - Update to version 20240104: * Allow keepalived_t read+write kernel_t pipes (bsc#1216060) * allow rebootmgr to read the system state (bsc#1205931) ==== zstd ==== Subpackages: libzstd1 libzstd1-32bit libzstd1-x86-64-v3 - Disable build of gzip for Leap 15.x to fix build error.

1 0

New Tumbleweed snapshot 20240111 released!
by Dominique Leuenberger 12 Jan '24

12 Jan '24

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: grub2 (2.12~rc1 -> 2.12) gstreamer-plugins-rs libcap-ng (0.8.3 -> 0.8.4) libzypp (17.31.27 -> 17.31.28) mdadm mpg123 (1.32.3 -> 1.32.4) ncurses (6.4.20231202 -> 6.4.20240106) shadow yast2-core (5.0.1 -> 5.0.2) === Details === ==== grub2 ==== Version update (2.12~rc1 -> 2.12) Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - Version bump to 2.12 (PED-5589) * Added: - grub-2.12.tar.xz - fix_no_extra_deps_in_release_tarball.patch * Removed: - grub-2.12~rc1.tar.xz * Patch dropped as it merged into new version: - 0001-disk-cryptodisk-Fix-missing-change-when-updating-to-.patch - 0001-fs-btrfs-Zero-file-data-not-backed-by-extents.patch - 0001-fs-ntfs-Fix-an-OOB-write-when-parsing-the-ATTRIBUTE_.patch - 0002-fs-ntfs-Fix-an-OOB-read-when-reading-data-from-the-r.patch - 0003-fs-ntfs-Fix-an-OOB-read-when-parsing-directory-entri.patch - 0004-fs-ntfs-Fix-an-OOB-read-when-parsing-bitmaps-for-ind.patch - 0005-fs-ntfs-Fix-an-OOB-read-when-parsing-a-volume-label.patch - 0006-fs-ntfs-Make-code-more-readable.patch - 0001-kern-ieee1275-init-Restrict-high-memory-in-presence-.patch - 0001-fs-xfs-Incorrect-short-form-directory-data-boundary-.patch - 0002-fs-xfs-Fix-XFS-directory-extent-parsing.patch - 0003-fs-xfs-add-large-extent-counters-incompat-feature-su.patch - 0001-mkstandalone-ensure-stable-timestamps-for-generated-.patch - 0002-mkstandalone-ensure-deterministic-tar-file-creation-.patch * Patch adjusted for the updated base version: - use-grub2-as-a-package-name.patch - grub2-s390x-04-grub2-install.patch - grub2-btrfs-04-grub2-install.patch - grub2-ppc64le-disable-video.patch - 0002-AUDIT-0-http-boot-tracker-bug.patch - 0001-Unify-the-check-to-enable-btrfs-relative-path.patch - 0003-Handle-multi-arch-64-on-32-boot-in-linuxefi-loader.patch - 0004-Add-suport-for-signing-grub-with-an-appended-signatu.patch - 0016-grub-install-support-embedding-x509-certificates.patch - 0021-appended-signatures-documentation.patch - 0022-ieee1275-enter-lockdown-based-on-ibm-secure-boot.patch - safe_tpm_pcr_snapshot.patch ==== gstreamer-plugins-rs ==== - Increase memory for s390x builds in _constraints. - Update both vendor files and include jsonwebtoken 9.2 in them. - The ring crate only supports s390x since v0.17.0 and jsonwebtoken 8 uses an older version, so we now patch livekit-api to use jsonwebtoken 9(.2) which allows to build the package in s390x (bsc#1218563). ==== libcap-ng ==== Version update (0.8.3 -> 0.8.4) - Update to version 0.8.4 * In capng_change_id, clear PR_SET_KEEPCAPS if returning an error * pscap: add -p option for reporting a specified process * Annotate function prototypes to warn if results are unused * Drop python2 support ==== libzypp ==== Version update (17.31.27 -> 17.31.28) - Fix to build with libxml 2.12.x (fixes #505) - version 17.31.28 (22) ==== mdadm ==== - Update mdadm to latest upstream state upto commit 582945c2d3bb. (jsc#PED-7542) 1) The testing changes are not included here. 2) Code clean up, and more helper routines added for Manage.c, Monitor.c, mdadm.c, ReadMe.c, super-intel.c, super0.c, super1.c, Create.c, Incremental.c and so on. 3) Man page update for mdadm.8.in. 4) Several memory leak and double free fixes. 5) Check /etc/initrd-release for whether systemd running on an initrd. - Manage: Block unsafe member failing 0062-Manage-Block-unsafe-member-failing.patch - Mdmonitor: Split alert() into separate functions 0063-Mdmonitor-Split-alert-into-separate-functions.patch - Monitor: block if monitor modes are combined. 0064-Monitor-block-if-monitor-modes-are-combined.patch - Update mdadm Monitor manual. 0065-Update-mdadm-Monitor-manual.patch - mdadm: create ident_init() 0066-mdadm-create-ident_init.patch - mdadm: Add option validation for --update-subarray 0067-mdadm-Add-option-validation-for-update-subarray.patch - Fix --update-subarray on active volume 0068-Fix-update-subarray-on-active-volume.patch - Add code specific update options to enum. 0069-Add-code-specific-update-options-to-enum.patch - super-ddf: Remove update_super_ddf. 0070-super-ddf-Remove-update_super_ddf.patch - super0: refactor the code for enum 0071-super0-refactor-the-code-for-enum.patch - super1: refactor the code for enum 0072-super1-refactor-the-code-for-enum.patch - super-intel: refactor the code for enum 0073-super-intel-refactor-the-code-for-enum.patch - Change update to enum in update_super and update_subarray 0074-Change-update-to-enum-in-update_super-and-update_sub.patch - Manage&Incremental: code refactor, string to enum 0075-Manage-Incremental-code-refactor-string-to-enum.patch - Change char* to enum in context->update & refactor code 0076-Change-char-to-enum-in-context-update-refactor-code.patch - mdadm/udev: Don't handle change event on raw devices 0077-mdadm-udev-Don-t-handle-change-event-on-raw-devices.patch - Manage: do not check array state when drive is removed 0078-Manage-do-not-check-array-state-when-drive-is-remove.patch - incremental, manage: do not verify if remove is safe 0079-incremental-manage-do-not-verify-if-remove-is-safe.patch - super-intel: make freesize not required for chunk size 0080-super-intel-make-freesize-not-required-for-chunk-siz.patch - manage: move comment with function description 0081-manage-move-comment-with-function-description.patch - Fix NULL dereference in super_by_fd 0082-Fix-NULL-dereference-in-super_by_fd.patch - Mdmonitor: Make alert_info global 0083-Mdmonitor-Make-alert_info-global.patch - Mdmonitor: Pass events to alert() using enums instead of 0084-Mdmonitor-Pass-events-to-alert-using-enums-instead-o.patch - Mdmonitor: Add helper functions 0085-Mdmonitor-Add-helper-functions.patch - Add helpers to determine whether directories or files are 0086-Add-helpers-to-determine-whether-directories-or-file.patch - Mdmonitor: Refactor write_autorebuild_pid() 0087-Mdmonitor-Refactor-write_autorebuild_pid.patch - Mdmonitor: Refactor check_one_sharer() for better error 0088-Mdmonitor-Refactor-check_one_sharer-for-better-error.patch - util.c: reorder code lines in parse_layout_faulty() 0089-util.c-reorder-code-lines-in-parse_layout_faulty.patch - util.c: fix memleak in parse_layout_faulty() 0090-util.c-fix-memleak-in-parse_layout_faulty.patch - Detail.c: fix memleak in Detail() 0091-Detail.c-fix-memleak-in-Detail.patch - isuper-intel.c: fix double free in load_imsm_mpb() 0092-isuper-intel.c-fix-double-free-in-load_imsm_mpb.patch - super-intel.c: fix memleak in find_disk_attached_hba() 0093-super-intel.c-fix-memleak-in-find_disk_attached_hba.patch - super-ddf.c: fix memleak in get_vd_num_of_subarray() 0094-super-ddf.c-fix-memleak-in-get_vd_num_of_subarray.patch - Create: goto abort_locked instead of return 1 in error path 0095-Create-goto-abort_locked-instead-of-return-1-in-erro.patch - Create: remove safe_mode_delay local variable 0096-Create-remove-safe_mode_delay-local-variable.patch - Create: Factor out add_disks() helpers 0097-Create-Factor-out-add_disks-helpers.patch - mdadm: Introduce pr_info() 0098-mdadm-Introduce-pr_info.patch - mdadm: Add --write-zeros option for Create 0099-mdadm-Add-write-zeros-option-for-Create.patch - manpage: Add --write-zeroes option to manpage 0100-manpage-Add-write-zeroes-option-to-manpage.patch - Define alignof using _Alignof when using C11 or newer 0101-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch - Use existence of /etc/initrd-release to detect initrd. 0102-Use-existence-of-etc-initrd-release-to-detect-initrd.patch - Create: Fix checking for container in update_metadata 0103-Create-Fix-checking-for-container-in-update_metadata.patch ==== mpg123 ==== Version update (1.32.3 -> 1.32.4) Subpackages: libmpg123-0 mpg123-openal - Update to version 1.32.4 build: * Reorganize shared headers, API headers into src/include. * Use relative include paths, avoiding internal directories in CPPFLAGS except for config.h. * Group C99 feature checks and make several standard headers mandatory. * Get rid of SIZE_P, OFF_P and friends. * Only enforce dummy module together with libout123, to be able to build individual modules using --disable-components logic. out123: * added --libversion libmpg123: * Avoid indirect branches into the assembly routines by using C wrappers also for dct36, relieving us of the need to care for bti / endbr i nstructions for control flow integrity. ==== ncurses ==== Version update (6.4.20231202 -> 6.4.20240106) Subpackages: libncurses6 ncurses-utils terminfo terminfo-base terminfo-iterm terminfo-screen - Add foot to terminfo-base. It's the most compliant wayland terminal emulator according to https://github.com/dankamongmen/notcurses/blob/master/TERMINALS.md - Add ncurses patch 20240106 + use ansi+arrows, ansi+apparrows, ansi+csr, ansi+erase, ansi+idc, ansi+idc1, ansi+idl, ansi+idl1, ansi+inittabs to trim -TD + minor manpage formatting changes for consistency. + modify doc-html test package's install-directory, per lintian. + add attr_get.3x to man_db.renames.in (patch by Sven Joachim). - Add ncurses patch 20231230 + improve formatting/style of manpages (patches by Branden Robinson). + add ms-vt100-16color, winconsole -TD + add rio, rio-direct -TD + add mostlike -TD + add wezterm, contour -TD - Add ncurses patch 20231223 + improve formatting/style of manpages (patches by Branden Robinson). - Add ncurses patch 20231217 + improve formatting/style of manpages (patches by Branden Robinson). + correct an assignment in infocmp "-u" for detecting if a boolean is unset in a base entry and set in a use'd chunk, i.e., if it was cancelled. + modify infocmp "-u" option to not report cancels for strings which were already cancelled in a use'd chunk. + join two lines in infotocap.3x to eliminate a spurious "description" link in installed manpages (report by Sven Joachim). + fix typo in NEWS (report by Sven Joachim). - Port patches * ncurses-5.9-ibm327x.dif * ncurses-6.4.dif ==== shadow ==== Subpackages: libsubid4 login_defs - bsc#1199026 bsc#1203823: Remove pam_keyinit from PAM configuration. This was introduced for bsc#1144060. ==== yast2-core ==== Version update (5.0.1 -> 5.0.2) - Don't close file descriptors in .target.bash calls (bsc#1218064) avoiding "[ASYNC BUG] rb_thread_wakeup_timer_thread: write(3) EBADF" with Ruby 3.3 - 5.0.2

1 0

Tumbleweed - Review of the week 2024/02
by Dominique Leuenberger 12 Jan '24

12 Jan '24

Dear Tumbleweed users and hackers, Tumbleweed is back at full speed – with seven snapshots released in as many days. The release team could again not let their hands off the system even on the weekend and delivered all the changes as fast as possible. The most relevant changes in those seven snapshots were: * Bind 9.18.21 * GStreamer 1.22.8 * SELinux 3.6 * firewalls 2.1.0 * Linux kernel 6.6.10 * GNOME 45.3 * Node.js 21.5.0 * Grub 2.12 * Meson 1.3.1 While looking at the staging projects, there has been some progress, but the list of older requests is mostly unchanged. With the holiday period over, we can all expect changes there relatively soon. Currently, we have these changes staged: * Linux kernel 6.6.11 * systemd 254.8 * RPM 4.19: all fixes have arrived, and the final phase has started. We expect openQA runs over the weekend and will likely ship it soon. With RPM 4.19, we will have to promote cmake to ring0 * Ruby 3.3: yast failures are being debugged and worked on * libxml 2.12.x: slow progress * openSSL 3.2.0 * c-ares 1.21.0: nodejs build fails have been resolved, but a new cycle has formed: appstream-glib, c-ares, curl, googletest, nghttp2, python311 * dbus-broker: no progress: openQA fails to launch the network stack in the installer Cheers, Dominique

1 0

Re: systemd-vconsole-setup.service failure
by Tony Walker 10 Jan '24

10 Jan '24

Hit reply instead of reply all. See below. -- Tony On Tue, Jan 9, 2024, 3:10 PM Tony Walker <tony.walker.iu(a)gmail.com> wrote: > Thanks and good points, Martin! > > TL;DR I submitted a bug report > (https://bugzilla.opensuse.org/show_bug.cgi?id=1218623), but missed an > existing one (https://bugzilla.opensuse.org/show_bug.cgi?id=1218618). > Not surprisingly, the maintainers were ahead of me and my > understanding .I assumed that Plymouth was holding onto the tty and > preventing systemd-vconsole-setup from resetting the tty. A simple > view of my fix is that it kills Plymouth if it takes too long. > However, it appears that Plymouth may be leaving the tty in graphics > mode. > > Longer story... > > > However, I am not quite certain whether your solution is correct. > > At least we should try to understand why it works. > > I am not sure either. ;-) Systemd and the boot process are outside my > area of expertise. I started using Linux in the mid 90's and learned > all about rc scripts. When Debian moved to systemd, I just went along > for the ride and became a dinosaur who knew just enough to start and > stop daemons. This seemed like a good excuse to learn, so please > correct me. > > > plymouth gets special treatment from systemd. Rather than stopping > > "plymouth-start.service", systemd runs "plymouth-quit.service". The > > reason is AFAIR that the plymouth splash screen is supposed to keep > > being displayed while the system is switching root. For this reason, > > plymouthd uses "KillMode=none". I suppose if you replace this with > > "mixed", plymouthd will be stopped when the initramfs shuts down. Do > > you see any difference in the visual appearance of the boot screen > > after applying your changes? > > Yes, there is a brief (~1-2s) view of the console before and after > Plymouth. That is, this is a crude fix. My thinking was that there are > other ways to fix that. Part of my reasoning is that Fedora uses the > exact settings I proposed, so if I could find the time to dig into > Fedora, I might find some other changes elsewhere. Of course, because > Fedora sticks its head in a toilet, we don't have to. Still, I thought > the Fedora folks would probably have a good implementation given their > proximity to its developers and it might be good to see what they do. > > Crudely killing Plymouth when initramfs is done is exactly what I > intended. My understanding is that systemd-vconsole-setup is called by > systemd-localed.service, localectl, etc. My thinking was that Plymouth > was holding the tty while the next boot step was trying to configure > it. A classic race condition (I'm a programmer not an admin, so I > always go for synchronization first). > > > > 2) add "IgnoreOnIsolate=true" to the "[Unit]" section, and > > > > The effect of this directive is unclear to me for the case at hand. The > > man page says "If true, this unit will not be stopped when isolating > > another unit". But this unit hasn't been stopped before your changes, > > because it had "KillMode=none" set. Is this really needed to solve the > > issue? > > I honestly don't know. My testing says no. However, I saw this and > thought it might fix a corner case that I never saw but thought might > happen eventually. Basically, I am completely ignorant of what > Plymouth does. I thought Plymouth might fork some other processes and, > because I am ignorant, IgnoreOnIsolate=false might cause systemd to > kill Plymouth due to timing. That is, I wanted to kill Plymouth but > not too quickly. > > When I looked at the Fedora (rawhide) package, I saw that they do use > IgnoreOnIsolate=true. Again, I don't know and we don't need to do > what Fedora does. However, it did make me feel better. > > > On my system, systemd-vconsole-setup.service runs successfully very > > early during initramfs processing. It prints the "device or resource > > busy" error when it's started again later, after switching root, > > probably because the plymouthd instance from the initrd is still > > running ("KillMode=none"). It's probably unnecessary to start systemd- > > vconsole-setup again after switching root, because the first invocation > > from the initramfs should have already set the fonts, keymaps, etc. > > Good point. I saw that too and did not bother to look at the logs from > my last Debian system to see if the same thing happens there. However, > I suspect so. As I said above, my understanding is that > systemd-vconsole-setup is called by systemd-localed.service, > localectl, etc. As such, I would expect to see repeated service starts > during boot while the tty is reconfigured for different stages. Again, > this is outside of my expertise, so I may be wrong. > > > Actually, looking at my boot log, it is weird to see that systemd- > > vconsole.setup is started and stopped more than 10 times during a > > single boot, while it should really be sufficient to do this once and > > for all very early at system startup. > > As I said above, my assumption is it will be restarted several times. > I am very likely wrong. > > > This looks like a systemd issue to me. I suggest you open a bug so that > > it can be properly analyzed. > > I searched for the bug and opened one: > https://bugzilla.opensuse.org/show_bug.cgi?id=1218623. Unfortunately, > I missed an existing one: > https://bugzilla.opensuse.org/show_bug.cgi?id=1218618. Sorry! I did > find similar reports: > https://bugzilla.opensuse.org/show_bug.cgi?id=1215282 and > https://bugzilla.opensuse.org/show_bug.cgi?id=943312. In those bug > reports, it appears that Plymouth leaves the tty in graphics mode. My > thinking was that killing Plymouth would do some "garbage collection" > and reset the terminal if this is the root of my problem. Either way, > it seemed I had a partial solution. > > Feel free to teach me or ask me questions. > > -- > Tony Walker <tony.walker.iu(a)gmail.com> > PGP Key @ https://tonywalker1.github.io/ or https://keys.openpgp.org/ > 9F46 <https://keys.openpgp.org/9F46> D66D FF6C 182D A5AC 11E1 8559 98D1 > 7543 319C > > On Tue, Jan 9, 2024 at 4:46 AM Martin Wilck <mwilck(a)suse.com> wrote: > > > > On Sun, 2024-01-07 at 12:35 -0500, Tony Walker wrote: > > > I finally found some time to debug and find a solution... > > > > > > The problem seems to be a race-condition caused by plymouth not > > > terminating quickly enough. > > > > Thanks for debugging this and finding a workaround. It has been > > bothering me, too, but I never took the time to take deeper look. > > > > However, I am not quite certain whether your solution is correct. > > At least we should try to understand why it works. > > > > > To make the error with vconsole-setuo > > > stop, I modified /usr/lib/systemd/system/plymouth-start.service as > > > follows: > > > > > > 1) change "KillMode" from none to "mixed", > > > > plymouth gets special treatment from systemd. Rather than stopping > > "plymouth-start.service", systemd runs "plymouth-quit.service". The > > reason is AFAIR that the plymouth splash screen is supposed to keep > > being displayed while the system is switching root. For this reason, > > plymouthd uses "KillMode=none". I suppose if you replace this with > > "mixed", plymouthd will be stopped when the initramfs shuts down. Do > > you see any difference in the visual appearance of the boot screen > > after applying your changes? > > > > > 2) add "IgnoreOnIsolate=true" to the "[Unit]" section, and > > > > The effect of this directive is unclear to me for the case at hand. The > > man page says "If true, this unit will not be stopped when isolating > > another unit". But this unit hasn't been stopped before your changes, > > because it had "KillMode=none" set. Is this really needed to solve the > > issue? > > > > > 3) run "dracut -f". > > > > > > I rebooted a few times and the errors were not generated. > > > > > > Let me know if this works for you and I will submit a bug and patch. > > > > > > > On my system, systemd-vconsole-setup.service runs successfully very > > early during initramfs processing. It prints the "device or resource > > busy" error when it's started again later, after switching root, > > probably because the plymouthd instance from the initrd is still > > running ("KillMode=none"). It's probably unnecessary to start systemd- > > vconsole-setup again after switching root, because the first invocation > > from the initramfs should have already set the fonts, keymaps, etc. > > > > Actually, looking at my boot log, it is weird to see that systemd- > > vconsole.setup is started and stopped more than 10 times during a > > single boot, while it should really be sufficient to do this once and > > for all very early at system startup. > > > > This looks like a systemd issue to me. I suggest you open a bug so that > > it can be properly analyzed. > > > > Regards, > > Martin > > > > > > > > > > > -- > > > Tony Walker <tony.walker.iu(a)gmail.com> > > > PGP Key @ https://tonywalker1.github.io/ or https://keys.openpgp.org/ > > > 9F46 D66D FF6C 182D A5AC 11E1 8559 98D1 7543 319C > > > > > > On Fri, Jan 5, 2024 at 6:58 PM Tony Walker <tony.walker.iu(a)gmail.com> > > > wrote: > > > > > > > > I saw this too. I haven't had time to debug it, but my hunch is a > > > > missing dependency in it's unit file. That would cause a race > > > > condition where vconsole-setup tries to start before its > > > > dependencies are running. > > > > > > > > Hope this helps. > > > > > > > > -- Tony > > > > > > > > On Fri, Jan 5, 2024, 6:24 PM Joe Salmeri <jmscdba(a)gmail.com> wrote: > > > > > > > > > > Yesterday I updated several TW machines and also TW vms from > > > > > 20231120 to > > > > > 20231228. > > > > > > > > > > After rebooting I ran systemctl --failed which shows > > > > > > > > > > UNIT LOAD ACTIVE SUB > > > > > DESCRIPTION > > > > > ? systemd-vconsole-setup.service loaded failed > > > > > failed > > > > > Virtual Console Setup > > > > > > > > > > systemctl status systemd-vconsole-setup.service provides the > > > > > details > > > > > > > > > > × systemd-vconsole-setup.service - Virtual Console Setup > > > > > Loaded: loaded > > > > > (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) > > > > > Active: failed (Result: exit-code) since Thu 2024-01-04 > > > > > 17:10:27 > > > > > EST; 23h ago > > > > > Duration: 5h 2.219s > > > > > Docs: man:systemd-vconsole-setup.service(8) > > > > > man:vconsole.conf(5) > > > > > Main PID: 1105 (code=exited, status=1/FAILURE) > > > > > CPU: 5ms > > > > > > > > > > systemd[1]: Starting Virtual Console Setup... > > > > > systemd-vconsole-setup[1105]: No usable source console found: > > > > > Device or > > > > > resource busy > > > > > systemd[1]: systemd-vconsole-setup.service: Main process exited, > > > > > code=exited, status=1/FAILURE > > > > > systemd[1]: systemd-vconsole-setup.service: Failed with result > > > > > 'exit-code'. > > > > > systemd[1]: Failed to start Virtual Console Setup. > > > > > > > > > > Not sure what is causing the "No usable source console found: > > > > > Device or > > > > > resource busy" error but it happens on multiple TW machines and > > > > > also on > > > > > my TW vms. > > > > > > > > > > systemctl restart systemd-vconsole-setup.service > > > > > > > > > > Restarts the service with no errors or problems so wondering if > > > > > something timewise is not ready during the boot process ? > > > > > > > > > > Is this a known issue ? > > > > > > > > > > -- > > > > > Regards, > > > > > > > > > > Joe > > >

3 3