March 2024 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Leap 42.3 Build 0312 released!
by Ludwig Nussel 25 Apr '24

25 Apr '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&version=42.3&bui… https://bugzilla.opensuse.org/buglist.cgi?product=openSUSE%20Distribution&q… When you reply to discuss some issues, make sure to change the subject. Please use the test plan at https://docs.google.com/spreadsheets/d/1AGKijKpKiJCB616-bHVoNQuhWHpQLHPWCb3… to record your testing efforts and use bugzilla to report bugs. Packages changed: biosdevname btrfsmaintenance conduit gconf2-branding-openSUSE (42.1 -> 42.3) ibus kactivitymanagerd kde-user-manager kernel-source (4.4.73 -> 4.4.74) libxml2 libzypp (16.12.0 -> 16.13.0) lightdm marble mc plasma5-integration plasma5-openSUSE postgresql (9.4 -> 9.6) python-coverage (3.7.1 -> 4.3.4) ucode-intel (20160714 -> 20170511) yast2-bootloader (3.2.22 -> 3.2.23) yast2-ntp-client (3.2.9 -> 3.2.12) === Details === ==== biosdevname ==== - Duplicate naming of SRIOV VFs by biosdevname when VPD_DCM Strings are present in VFs (bsc#1042185) * Add: biosdevname_avoid_duplicates.patch ==== btrfsmaintenance ==== - Require btrfsprogs (bsc#1047226) - update to 0.2 - updated documentation - no hardcoded paths to external utilities - fixed logger name typos for 'journal' target - defrag fixes (sysconfig, find arguments) - Removed patch: balance-typo.patch - Added patch: sysconfig-override-trim.diff - Add balance-typo.patch (bnc#986543) - version 0.1.1 - fix typo and make journal logging target work - cron refresh: remove bashism - Removed patches: * 0003-Add-COPYING-file.patch * 0011-cron-refresh-remove-debuggiong-output.patch - cron script symlinks are not created on first installation (bsc#907343) - add COPYING to package - refresh script: remove extra messages - add uninstall targets - fix refresh service - adjust sysconfig defaults - Add more package dependencies (cron, zypp-plugin) - minor bugfixes - Add supplements(btrfsprogs) - initial version 0.1 ==== conduit ==== Subpackages: conduit-lang - Use python-vobject instead of vobject per python-vobject change in 42.3. ==== gconf2-branding-openSUSE ==== Version update (42.1 -> 42.3) - do not build novell-sound-theme in the gconf2-branding-SLED build to prevent duplicated binaries in openSUSE Leap. The novell-sound-theme is taken from gconf2-branding-SLES sources on both the SLED product and the SLES WE module. bsc#1046099 - bump versions ==== ibus ==== Subpackages: ibus-branding-openSUSE-KDE ibus-gtk ibus-gtk-32bit ibus-gtk3 ibus-lang libibus-1_0-5 libibus-1_0-5-32bit python-ibus typelib-1_0-IBus-1_0 - Update ibus.spec: copy auto-start files to SOURCE directory to enable modifications before compile. - Add ibus-disable-engines-preload-in-GNOME.patch: Disable load preload-engines actions in SLE, which is unnecessary for mono IMF in SLE and may cause CJK user login failed (bsc#1036729). ==== kactivitymanagerd ==== - Recommend -lang package ==== kde-user-manager ==== - Recommend -lang package ==== kernel-source ==== Version update (4.4.73 -> 4.4.74) Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms - Delete patches.kabi/kabi-fix-for-kvm-x86-fix-singlestepping-over-syscall. No need for kABI fix yet for Leap 42.3. - commit f0a86d9 - Fix kABI breakage by KVM CVE fix (bsc#1045922). - commit c0308f6 - powerpc/perf: Fix branch event code for power9 (fate#321438, Pending SUSE Kernel Fixes). - commit e954af6 - powerpc: Fix /proc/cpuinfo revision for POWER9 DD2 (bsc#1046789). - commit 444247f - Refresh metadata patches.drivers/ibmvnic-a2-Fix-assignment-of-RX-TX-IRQ-s.patch. - commit be32be9 - drm/i915: Serialize GTT/Aperture accesses on BXT (bsc#1046821). - commit b263fef - Bluetooth: hidp: fix possible might sleep error in hidp_session_thread (bsc#1031784). - Refresh patches.suse/kgr-0008-mark-task_safe-in-some-kthreads.patch. - commit 18c6f3e - KVM: x86: fix singlestepping over syscall (CVE-2017-7518 bsc#1045922). - commit d989643 - nvme/pci: Fix stuck nvme reset (bsc#1043805). - commit 7afe4f0 - Refresh fadump patches to upstream and add metadata patches.arch/powerpc-fadump-add-reschedule-point-while-releasing-memory.patch. patches.arch/powerpc-fadump-avoid-duplicates-in-crash-memory-ranges.patch patches.arch/powerpc-fadump-avoid-holes-in-boot-memory-area-when-fadump-is-registered.patch patches.arch/powerpc-fadump-provide-a-helpful-error-message.patch - commit f0fb5c3 - blacklist.conf: Remove duplicated entries - commit cb960d2 - Remove duplicated blacklist entries and put git-commit tag to patches - commit 12a0cb2 - blacklist.conf: Remove duplicated entry. - commit 561ddb1 - ibmvnic: Fix assignment of RX/TX IRQ's (bsc#1046589). - commit 5fa38bf - blacklist.conf: blacklist 570d8e939801 we do not care about the code in Documentation all that much, do we? - commit 69d5811 - blacklist.conf: blaclist 5380e5644afb it is just not worth backporting without any explicit report where a silently truncated success would lead to a real bug. - commit fc28626 - blacklist.conf: unnecessary patch The bug triggers only upon a malformed descriptor and the comparison is so that our buffer would be too large not too small so no overflow. The device would not work, but it won't anyway. - commit 99f8a16 - Rearrange the previous patches for hpsa and smartpqi to the right position. - commit a1f1f27 - Update patches.fixes/xfs-split-default-quota-limits-by-quota-type.patch (bsc#1040941). Fix the bug nr used. - commit 115ba75 - printk: Correctly handle preemption in console_unlock() (bsc#1046434). - commit 0a3c2a4 - printk/xen: Force printk sync mode when migrating Xen guest (bsc#1043347). - commit e13596b - btrfs: disable possible cause of premature ENOSPC (bsc#1040182) - commit 8bf31da - rbd: make sure pages are freed by libceph (bsc#1045596). - rbd: drop extra rbd_img_request_get (bsc#1045596). - commit c8719f2 - dm-raid: Do not call BUG() in __rdev_sectors() (bsc#1046264). - commit 0b1aab0 - btrfs: Round down values which are written for total_bytes_size (bsc#1043912). - btrfs: Manually implement device_total_bytes getter/setter (bsc#1043912). - commit c4d2eb7 - pipe: cap initial pipe capacity according to pipe-max-size limit (bsc#1045330). - commit 4ee3ec2 - Blacklist drivers/net/ethernet/ibm/emac We do not build the driver. - commit d432b2b - blacklist.conf: this patch breaks the API It disallows some operations that are now allowed - commit 98325c2 - arm64: Update config files. (bsc#1036737) Disable XGENE_PMU. - commit 7bb0115 - Disable Xilinx network drivers (bsc#1046170). - commit 656fc83 - hwpoison, memcg: forcibly uncharge LRU pages (bnc#1046105). - commit 2b252e1 - blacklist.conf: blacklist 570d8e939801 the issue is visible only when 80df554275c2 is applied (4.7+ and not backported to our trees) - commit 47b83ce - config/x86_64: make CONFIG_SERIAL_8250_DW and *_MID built-in (bsc#1024449) - commit 2e3ca7e - Refresh patches.drivers/0477-nvme-add-hostid-token-to-fabric-options.patch. Update mainline references. - commit eee1109 - fs/exec.c: account for argv/envp pointers (bnc#1039354, CVE-2017-1000365). - commit 7418d0f - Refresh ibmvnic patch metadata patches.drivers/ibmvnic-98-ibmvnic-Correct-return-code-checking-for-ibmvnic_init-during-probe.patch. patches.drivers/ibmvnic-a0-ibmvnic-Fix-incorrectly-defined-ibmvnic_request_map_rsp-structure.patch. patches.drivers/ibmvnic-a1-ibmvnic-Fix-error-handling-when-registering-long-term-mapped-buffers.patch. - commit babc17a - Refresh metadata patches.fixes/powerpc-tm-Fix-stack-pointer-corruption-in-__tm_recheckpoint. - commit 0b5bdc6 - powerpc/ftrace: Pass the correct stack pointer for DYNAMIC_FTRACE_WITH_REGS (FATE#322421). - commit 936e653 - nvme: add hostid token to fabric options (bsc#1045293). - commit 52dffb9 - iw_cxgb4: Fix error return code in c4iw_rdev_open() (bsc#1026570). - RDMA/iw_cxgb4: Always wake up waiter in c4iw_peer_abort_intr() (bsc#1026570). - commit 2ce43b1 - clocksource/drivers/arm_arch_timer: Fix read and iounmap of incorrect variable (bsc#1045937). - commit 594f037 - Linux 4.4.74 (CVE-2017-1000364 bnc#1012382 bnc#1039348 bnc#1045340 bsc#1031717 bsc#1043231). - Delete patches.drivers/media-pvrusb2-reduce-stack-usage-pvr2_eeprom_analyze. - Delete patches.drivers/media-vb2-Fix-an-off-by-one-error-in-vb2_plane_vaddr. - Delete patches.drivers/staging-rtl8188eu-prevent-an-underflow-in-rtw_check_. - Delete patches.fixes/mm-fix-new-crash-in-unmapped_area_topdown.patch. - Delete patches.fixes/mm-larger-stack-guard-gap-between-vmas.patch. - commit 5e41880 - tty: Fix ldisc crash on reopened tty (bnc#1043488). - commit 04cca20 - tty: Destroy ldisc instance on hangup (bnc#1043488). - tty: Refactor tty_ldisc_reinit() for reuse (bnc#1043488). - tty: Use 'disc' for line discipline index name (bnc#1043488). - tty: Move tty_ldisc_kill() (bnc#1043488). - tty: Handle NULL tty->ldisc (bnc#1043488). - tty: Prepare for destroying line discipline on hangup (bnc#1043488). - tty: Reset c_line from driver's init_termios (bnc#1043488). - tty: Simplify tty_set_ldisc() exit handling (bnc#1043488). - commit c016cca - kabi: ignore fs_info parameter for tracepoints that didn't have it (bsc#1044912). - commit 24869ea ==== libxml2 ==== Subpackages: libxml2-2 libxml2-2-32bit libxml2-devel libxml2-tools - Security fix: * libxml2-CVE-2017-7376.patch [bsc#1044887, CVE-2017-7376] * Increase buffer space for port in HTTP redirect support - Security fix: * libxml2-CVE-2017-7375.patch [bsc#1044894, CVE-2017-7375] * Prevent unwanted external entity reference - Upstream patches updated and with tests: * libxml2-CVE-2017-9047.patch and libxml2-CVE-2017-9048.patch merged into libxml2-CVE-2017-9047.patch [bsc#1039066, bsc#1039661] * libxml2-CVE-2017-9049.patch and libxml2-CVE-2017-9050.patch merged into libxml2-CVE-2017-9049.patch [bsc#1039063, bsc#1039064] ==== libzypp ==== Version update (16.12.0 -> 16.13.0) - Adapt loop mounting of iso images (bsc#1038132, bsc#1033236) - Adjust zypp.conf for openSUSE Tumbleweed (bsc#1031756) - Change arch variable names conflicting with compiler macros (fixes #70) - Fix potential crash if repo has no baseurl (bnc#1043218) - version 16.13.0 (0) ==== lightdm ==== Subpackages: liblightdm-gobject-1-0 lightdm-lang - Augment patch to also resolve the target of symlink sessions for detemining the preselected option: * ignore-known-symlink-sessions.patch ==== marble ==== Subpackages: libastro1 libmarblewidget-qt5-27 marble-data marble-devel marble-doc marble-kde marble-lang - Add Fix-utm-enum-value.patch and reverse-apply it, this upstream commit causes a crash when adding bookmarks if switched to UTM view angles because the necessary handler functions for the dialog are not implemented yet (boo#1044747, kde#381872) - Add Fix-plain-map-and-political-map-showing-no-content.patch to fix the plain map and the political map being not displayed at all (kde#379297) ==== mc ==== Subpackages: mc-lang - sftp.patch: Backport upstream fixes for SFTP (boo#1004280, boo#1042797) ==== plasma5-integration ==== - Move the Recommends: %{name}-plugin-lang to the plasma5-integration-plugin sub package, otherwise the translations won't get installed as there is no main package (boo#1027925) - Actually apply the aforementioned patch (shouldn't the source validator have warned?) ==== plasma5-openSUSE ==== Subpackages: plasma5-defaults-openSUSE plasma5-theme-openSUSE plasma5-workspace-branding-openSUSE sddm-theme-openSUSE - Fix installation of the sddm theme files (boo#1047254) ==== postgresql ==== Version update (9.4 -> 9.6) Subpackages: postgresql-contrib postgresql-devel postgresql-docs postgresql-server - Bump version and defaultpackage to 9.6. - Move ~postgres/.bash_profile to postgresql-server to avoid a file conflict between the versioned server packages. - Bump version and defaultpackage to 9.4. - Bump version and defaultpackage to 9.3. - Change license string to PostgreSQL. - Make all dummy packages noarch. - Make PostgreSQL 9.2 the default. - Reduce the postgresql packages with unversioned names to dummy packages that require the respective versioned package names. ==== python-coverage ==== Version update (3.7.1 -> 4.3.4) - uninstall alternatives in %postun - update for singlespec - update to 4.3.4: - Using the --skip-covered option on an HTML report with 100% coverage would cause a ?No data to report? error, as reported in issue 549. This is now fixed; thanks, Lo�c Dachary. - If-statements can be optimized away during compilation, for example, if 0: or if __debug__:. Coverage.py had problems properly understanding these statements which existed in the source, but not in the compiled bytecode. This problem, reported in issue 522, is now fixed. - If you specified --source as a directory, then coverage.py would look for importable Python files in that directory, and could identify ones that had never been executed at all. But if you specified it as a package name, that detection wasn?t performed. Now it is, closing issue 426. Thanks to Lo�c Dachary for the fix. - If you started and stopped coverage measurement thousands of times in your process, you could crash Python with a ?Fatal Python error: deallocating None? error. This is now fixed. Thanks to Alex Groce for the bug report. - On PyPy, measuring coverage in subprocesses could produce a warning: ?Trace function changed, measurement is likely wrong: None?. This was spurious, and has been suppressed. - Previously, coverage.py couldn?t start on Jython, due to that implementation missing the multiprocessing module (issue 551). This problem has now been fixed. Also, issue 322 about not being able to invoke coverage conveniently, seems much better: jython -m coverage run myprog.py works properly. - Let?s say you ran the HTML report over and over again in the same output directory, with --skip-covered. And imagine due to your heroic test-writing efforts, a file just acheived the goal of 100% coverage. With coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. - update to Version 4.3.1 ? 2016-12-28: - Some environments couldn?t install 4.3, as described in issue 540. This is now fixed. - The check for conflicting --source and --include was too simple in a few different ways, breaking a few perfectly reasonable use cases, described in issue 541. The check has been reverted while we re-think the fix for issue 265. - update to Version 4.3 ? 2016-12-27: Special thanks to Lo�c Dachary, who took an extraordinary interest in coverage.py and contributed a number of improvements in this release. - The HTML report now supports a --skip-covered option like the other reporting commands. Thanks, Lo�c Dachary for the implementation, closing issue 433. - Subprocesses that are measured with automatic subprocess measurement used to read in any pre-existing data file. This meant data would be incorrectly carried forward from run to run. Now those files are not read, so each subprocess only writes its own data. Fixes issue 510. - Coverage.py wouldn?t execute sys.excepthook when an exception happened in your program. Now it does, thanks to Andrew Hoos. Closes issue 535. - The coverage combine command will now fail if there are no data files to combine. The combine changes in 4.2 meant that multiple combines could lose data, leaving you with an empty .coverage data file. Fixes issues issue 525, issue 412, issue 516, and probably issue 511. - The branch coverage issues described in issue 493, issue 496, and issue 502 are now fixed, thanks to Lo�c Dachary. - Options can now be read from a tox.ini file, if any. Like setup.cfg, sections are prefixed with ?coverage:?, so [run] options will be read from the [coverage:run] section of tox.ini. Implements part of issue 519. Thanks, Stephen Finucane. - Specifying both --source and --include no longer silently ignores the include setting, instead it fails with a message. Thanks, Nathan Land and Lo�c Dachary. Closes issue 265. - Coverage.py can now search .pex files for source, just as it can .zip and .egg. Thanks, Peter Ebden. - update to 4.2: - Since ``concurrency=multiprocessing`` uses subprocesses, options specified on the coverage.py command line will not be communicated down to them. Only options in the configuration file will apply to the subprocesses. Previously, the options didn't apply to the subprocesses, but there was no indication. Now it is an error to use ``--concurrency=multiprocessing`` and other run-affecting options on the command line. This prevents failures like those reported in `issue 495`_. - Filtering the HTML report is now faster, thanks to Ville Skytt�. - update to 4.0.3: - Fixed a mysterious problem that manifested in different ways: sometimes hanging the process (`issue 420`_), sometimes making database connections fail (`issue 445`_). - The XML report now has correct ``<source>`` elements when using a ``--source=`` option somewhere besides the current directory. This fixes `issue 439`_. Thanks, Arcady Ivanov. - Fixed an unusual edge case of detecting source encodings, described in `issue 443`_. - Help messages that mention the command to use now properly use the actual command name, which might be different than "coverage". Thanks to Ben Finney, this closes `issue 438`_. - add LICENSE.txt - Pre require coreutils. This package is needed for the rm call in the pre section. Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.gONanE: line 3: rm: command not found - specfile: * updated license * updated update-alternatives * README.txt -> README.rst - update to version 4.0: (long list, see http://coverage.readthedocs.org/en/latest/changes.html) - fix rhel deps by depending on /usr/sbin/update-alternatives ==== ucode-intel ==== Version update (20160714 -> 20170511) - Update to version 20170511 - Update to version 20161104. ==== yast2-bootloader ==== Version update (3.2.22 -> 3.2.23) - AuotYaST configuration: Set StorageDevices flag disks_valid to true. So libstorage can scan valid disks and "/" partition can be found. (bnc#1043132) - 3.2.23 ==== yast2-ntp-client ==== Version update (3.2.9 -> 3.2.12) - Resrict records are written at the end but the default file and most profiles use them at the beginning, which mangles the file completely (bsc#983486). To fix it we have just changed the order of writing. - 3.2.12 - AutoYaST: Fix crash when trying to sanitize not string values, for example initial_sync. - AutoYaST: Sanitize comments by only removing blank spaces at the beginning and adding line break. This avoids augeas parse errors (bsc#1045777). - 3.2.11 - AutoYaST: Fix crash in CFA when creating a command record with some key value option is given (bsc#1045968) - 3.2.10 - AutoYaST: Comments from autoyast profile should not be sanitized to avoid entries without space between value and comment (e.g trustedkey 1# coment). This is caused by a bug in augeas adding new entries. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

FDE in MicroOS and Tumbleweed: pcrlock update
by aplanas 18 Apr '24

18 Apr '24

Hi, after the announcement of sdbootutil[1] and the support of full disk encryption (FDE)[2] using systemd-cryptenroll via pcr-oracle, we are releasing images for MicroOS and Tumbleweed that support the new systemd-pcrlock mechanism! In December we described[3] how we implemented in MicroOS (and later in Tumbleweed) a solution for FDE that uses the TPM2 or the FIDO2 key to unlock the LUKS2 root device, using only the systemd user space tools. To generate the predictions of the PCRs values, we used the in-house pcr-oracle application, that we extended to support the generation of signed policies in JSON format, that systemd-cryptenroll and systemd-cryptsetup use to seal and unseal the key that will open the encrypted LUK2 device in our system. Two weekends ago something changed: openSUSE released systemd v255, that now support the generation of policies using the new experimental tool systemd-pcrlock[4]. pcrlock proposes a different approach to the generation of TPM2 policies. Instead of signed policies (which requires the generation of a RSA key pair that is used to sign the PCR policy to make it independent of the sealed key), pcrlock uses NVIndex policies. Those are basically policies that are stored inside the non-volatile RAM that the TPM2 provides. The policy is now stored inside the TPM2, and the index can only be changed if the policy itself is meet. The new pcrlock tool is also quite handy. It can generate the predictions (some small .pcrlock files stored in /var) of each component (firmware, bootloader, kernel, raw files, etc), and also present all the extensions of the PCR registered in the event log in a very nice way! The architecture is sound, but there is a systemd-pcrlock bug[5] that fails when measuring large initrd files. This has an implication only on the first boot, as the initial initrd is for now ignored, discarding initially PCR9. This is automatically fixed in the next update, but can also be manually fixed if the user reboot using the new smaller initrd, and later call `sdbootutil update-predictions`. Anyway, we extended the tools to support the pcrlock mechanism now. For new installations, if pcrlock is supported it will be preferred instead of the signed policies. The team is still working on more interesting stuff for later: we are making good progress in turning the distribution independent of the boot loader. We can use exactly this same FDE mechanism (signed policies or NVIndex policies) using systemd-boot or GRUB2 (with BLS patches). More on that in the next announcement! [1] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… [2] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… [3] https://news.opensuse.org/2023/12/20/systemd-fde [4] https://www.freedesktop.org/software/systemd/man/latest/systemd-pcrlock.html [5] https://github.com/systemd/systemd/issues/31883

5 27

xz security alert and CVE-2024-3094
by Ana Guerrero Lopez 05 Apr '24

05 Apr '24

Hi, If you're using an up-to-date Tumbleweed, please make sure to update as soon as possible your system. The latest versions of "xz" (5.6.0 and 5.6.1) contained malicious code ( refer to CVE-2024-3094 ) and the package in Tumbleweed has been reverted back to version 5.4. After reading this mail, please update your system and ensure you're downgrading xz to the version *5.6.1.revertto5.4. *This version despite**itsname is version 5.4. Last step is reboot your system. Hopefully we'll have soon more detailed information about this CVE. Have a nice weekend! Ana from the openSUSE release team.

22 42

KDE Megarelease 6 in TW snapshot 20240311
by Charlie Chan 04 Apr '24

04 Apr '24

Zypper doesn’t fetch all the lang packs in Plasma 6. I have to detect which lang pack is missing, try to guess by file names, and install them one by one… Not an usual openSUSE experience :( Charlie

3 3

KDE Megarelease 6 in TW snapshot 20240311
by Fabian Vogt 04 Apr '24

04 Apr '24

Hi, the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/ Plasma 5 will be replaced, it is no longer part of the repository. There are a few minor issues in this snapshot found by openQA but not considered severe enough to actually block the snapshot from getting published. They'll all be fixed with Plasma 6.0.2 in one of the next snapshots, also for those installing or upgrading now. 1. For fresh installs, the GTK theme is not set correctly: https://bugs.kde.org/show_bug.cgi?id=482763 Workaround is to either set it manually in systemsettings or run "kded5" once in a terminal or krunner. 2. For upgrades (any version), the launcher icon switches to the Plasma one: https://github.com/openSUSE/plasma-opensuse/pull/25 Workaround is to change the icon manually to "start-here-branding" for now. 3. Upgrades from very old systems fail due to "libksysguard5-helper": https://bugzilla.opensuse.org/show_bug.cgi?id=1221350 When upgrading from Leap <= 15.3, you might encounter Problem: libksysguard5-plugins-5.27.10-2.2.x86_64 requires libprocesscore.so.9()(64bit), but this requirement cannot be provided As workaround, select the "deinstallation of libksysguard5-helper" option. 4. Plasmashell takes 25s during start if bluetooth not available: https://bugs.kde.org/show_bug.cgi?id=481870 If kdeconnect-kde is installed on a system without bluetooth HW, it delays Plasma start by 25s. Workaround is to disable the KDE Connect systray icon. 5. The etesync resource is broken in kdepim-runtime 24.02.0. It will be back in one of the next snapshots. The Wayland session isn't default yet, that will have to be switched in a separate step later. This also makes it possible to differentiate whether bugs are more likely caused by Plasma 6 itself or the Wayland session. Have a lot of fun, the openSUSE KDE packaging team

27 65

zypper dup wants to update all packages ?
by Michael Pujos 01 Apr '24

01 Apr '24

A zypper dup on my install wants to update all packages (4900). Is that normal ? From what I can tell there is no glibc update with a full distro rebuild...

10 9

[opensuse-factory] reproducible builds status 2024-03
by Bernhard M. Wiedemann 31 Mar '24

31 Mar '24

Hi, This month, we enabled macros to allow for bit-reproducible verification of rpms. Thanks Jan Zerebecki + mls. Finally I was able to bit-reproduce OBS-made rpms when workarounding https://github.com/rpm-software-management/rpm/issues/2965 So we finally have a number above zero in the "verified-bit-identical" value. It will rise further when running more tests next month. Also got one step closer to reproducible java-21 packages. And I started to test with --nocheck which found packages that misused the %check section to change %install results. Here are the autogenerated bits: last month's status: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… Last months' reproducible builds project updates (including my work): https://reproducible-builds.org/reports/2024-02/ I uploaded https://rb.zq1.de/compare.factory-20240331/ today https://rb.zq1.de/spec/glossar.txt explains the meaning of below values: total-packages: 15400 (+144) build-tried: 15344 (+145) build-failed: 39 (+5) build-n-a: 212 (-21) build-succeeded: 15093 (+161) build-official-failed+na: 133 (-65) build-compare-failed: 161 (-18) build-compare-succeeded: 14932 (+179) verify-failed: 318 (-181) verified-semi-reproducible: 11474 (+372) verified-bit-identical: 1012 (+1007) bit-by-bit-identical: 14342 (+75) not-bit-by-bit-identical: 745 (+79) not-bit-by-bit-identicalcheck: 751 (+86) https://rb.zq1.de/compare.factory-20240331/graph.png shows the change over time https://rb.zq1.de/compare.factory-20240331/unreproduciblerings.txt lists very unreproducible core packages (bootstrap+DVD) Of the badly unreproducible packages, 4 were in ring0 31 were in ring1 That makes it 35/4043 => 0.87 % which is below the overall average of 161/15093 => 1.07 % 745/15093 => 4.94 % of packages are not perfectly reproducible package notes: ==> ./FlightGear/.rb.notes <== FTBFS-j1 make[2]: *** No rule to make target 'src/EmbeddedResources/FlightGear-resources.cxx', needed by 'src/Main/CMakeFiles/fgfs_autogen_timestamp_deps'. Stop. ==> ./arpack-ng/.rb.notes <== FTBFS-j1 ==> ./bmap-tools/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1221108 FTBFS-2024-06-12 = https://github.com/intel/bmap-tools/issues/116 FTBFS-2024-06-12 ==> ./ca-certificates-mozilla/.rb.notes <== TODO /usr/share/factory/var/lib/ca-certificates/java-cacerts differs at offset '30' (Java KeyStore) ==> ./caddy/.rb.notes <== => SR 1163784 FTBFS-nocheck ==> ./eww/.rb.notes <== rust1.76/llvm ==> ./glfw/.rb.notes <== => https://github.com/geany/geany/pull/3785 toolchain ==> ./helm/.rb.notes <== = helm https://github.com/helm/helm/issues/12880 SSL FTBFS-2024-06-07 FTBFS-2032 ==> ./himmelblau/.rb.notes <== rust/llvm ==> ./igrep/.rb.notes <== rust/llvm low-entropy ==> ./jackson-core/.rb.notes <== javadoc filesys + minor java maven jar strip-nd +++ new//usr/share/java/META-INF/maven/com.fasterxml.jackson.core/jackson-core/pom.properties 2019-11-01 00:36:26.518271564 +0000 ==> ./java-21-openj9/.rb.notes <== date+time+username ; mailed to fstrba --- old /usr/lib64/jvm/java-21-openj9-21/lib/default/libj9jit29.so (objdump) ==> ./java-21-openjdk/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1221224 java-21-openjdk parallelism +?ASLR? ==> ./kf6-qqc2-desktop-style/.rb.notes <== qt6-declarative toolchain issue? parallelism? +++ /var/tmp/build-root.2b/.mount/home/abuild/rpmbuild/BUILD/qqc2-desktop-style-6.0.0/build/.rcc/qmlcache/org_kde_desktop_private_org.kde.desktop/private/CheckIndicator_qml.cpp 2040-04-14 03:00:38.066666668 +0000 ==> ./kubefirst/.rb.notes <== = https://bugzilla.opensuse.org/show_bug.cgi?id=1221680 kubefirst bug ==> ./latex2html/.rb.notes <== => SR 1150775 drop latex log => SR 733232 drop date in latex log ==> ./libressl/.rb.notes <== = https://github.com/libressl/portable/issues/1018 SSL FTBFS-2024-04-01 found range 1711981509 -> 1711983313 ==> ./med-tools/.rb.notes <== => SR 1156899 %check fdupes issue --- old-PROVIDES ==> ./mhvtl/.rb.notes <== => https://github.com/markh794/mhvtl/pull/128 tar/gz /usr/lib/firmware/mhvtl/mhvtl_kernel.tgz ==> ./musique/.rb.notes <== => SR 1163266 date -DEFINES = -DAPP_VERSION=1.12 -DAPP_NAME=Musique -DAPP_UNIX_NAME=musique -DBUILD_YEAR=2024 ... ==> ./nautilus/.rb.notes <== date from data/org.gnome.Nautilus.metainfo.xml.in.in: <release version="@release-version@" date="@build-date@"/> ==> ./nfdump/.rb.notes <== => SR 1163778 ==> ./ollama/.rb.notes <== => https://github.com/ollama/ollama/pull/2836 gzip mtime - 76ed00 1f8b0808 a18be065 02036c69 62657874 .......e..libext ==> ./openssl-3/.rb.notes <== FTBFS

1 0

New Tumbleweed snapshot 20240329 released!
by Dominique Leuenberger 30 Mar '24

30 Mar '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: gnome-control-center (46.0 -> 46.0.1) myspell-dictionaries (20221012 -> 20240321) open-vm-tools openSUSE-release (20240328 -> 20240329) publicsuffix (20240306 -> 20240326) python-pyasn1-modules (0.3.0 -> 0.4.0) systemd-default-settings (0.8 -> 0.9) tracker (3.7.0 -> 3.7.1) tracker-miners (3.7.0 -> 3.7.1) virtualbox virtualbox-kmp === Details === ==== gnome-control-center ==== Version update (46.0 -> 46.0.1) Subpackages: gnome-control-center-color gnome-control-center-goa gnome-control-center-lang gnome-control-center-user-faces gnome-control-center-users - Update to version 46.0.1: + Handle legacy panel arguments + Accessibility: Allow launching subpages directly. + Privacy: Fix Thunderbolt panel not launching. + System: - Avoid setting auto time sync when it isn't needed. - Improve startup time by loading subpages on demand. + Updated translations. ==== myspell-dictionaries ==== Version update (20221012 -> 20240321) Subpackages: myspell-cs_CZ myspell-da_DK myspell-de myspell-de_DE myspell-el_GR myspell-en myspell-en_GB myspell-en_US myspell-es myspell-es_ES myspell-fr_FR myspell-hu_HU myspell-it_IT myspell-lightproof-en myspell-lightproof-hu_HU myspell-lightproof-pt_BR myspell-lightproof-ru_RU myspell-pl_PL myspell-pt_BR myspell-ru_RU - version update to 20240321 * use general label for Turkish dictionary * Updated Afrikaans dictionary * tdf#159164 Update the English dictionaries: GB+ZA+AU+CA+US * update hunspell dictionaries for Turkish language * Updated Slovenian thesaurus * tdf#156723 False positives in pt-BR lightproof * Belarusian hunspell dictionary update * Update the Korean Dictionaries: ko-KR * Updated the English dictionaries: GB * Update Danish dictionaries (v2.8.001) * Fix path of logo for Spanish dictionary * Fixes issue #156669: Updates Catalan dictionaries (spelling, hyphenation, and thesaurus) with latest releases. * Add Indonesian hyphenation library to dictionary package * Updating RLA-ES Spanish spellcheker to v2.8. * Updated Slovak dictionaries (v2.4.7 2023-08-29) * Update of Occitan spellchecker (more words and up-to-date licence * tdf#156723 Remove false pleonasms for pt-BR * tdf#156101 add en-IL alongside the other English locales * On Linux dictionaries are packaged separately * Update Hungarian dictionary * Updated the English dictionaries: GB+ZA * tdf#154459 Improve grammar for hlp_ellipsis * Add .gitreview used by git-review tool * id: sync dictionaries to version v2.3.0 (2022.09.21) * Updated Slovenian thesaurus * tdf#148876 Adding Thai hyphenation patterns * Update Italian hyphenation and dictionary * Update Mongolian dictionary * Fix typos in Thesaurus - modified sources % update.sh - deleted patches - es-remove-duplicate-locales.diff (upstreamed) ==== open-vm-tools ==== Subpackages: libvmtools0 open-vm-tools-desktop - Remove protobuf < 22 dependency from spec file (bsc#1217478) Required linking with additional absl libraries for sle_version > 150400. - Use (boo#1222089) for updating open-vm-tools to version 12.4.0. ==== openSUSE-release ==== Version update (20240328 -> 20240329) Subpackages: openSUSE-release-appliance-custom openSUSE-release-dvd - automatically generated by openSUSE-release-tools/pkglistgen ==== publicsuffix ==== Version update (20240306 -> 20240326) - Update to version 20240326: * Add `*.ir.md` (#1625) * Update name for info.cx (#1616) * add `nftstorage.link` (#1548) * GD - graphic.design (#1940) * Removing wildcard for cloudapp.azure.com (#1944) ==== python-pyasn1-modules ==== Version update (0.3.0 -> 0.4.0) - update to 0.4.0: * Added support for Python 3.11, 3.12 * Removed support for EOL Pythons 2.7, 3.6, 3.7 ==== systemd-default-settings ==== Version update (0.8 -> 0.9) Subpackages: systemd-default-settings-branding-SLE systemd-default-settings-branding-openSUSE - Import 0.9 bb859bf user@.service: Disable controllers by default (jsc#PED-2276) ==== tracker ==== Version update (3.7.0 -> 3.7.1) Subpackages: libtracker-sparql-3_0-0 tracker-data-files tracker-lang typelib-1_0-Tracker-3_0 - Update to version 3.7.1: + Fix possible stalls in D-Bus endpoint batch updates. + Better API documentation around handling of corrupted databases. + Test improvements. ==== tracker-miners ==== Version update (3.7.0 -> 3.7.1) Subpackages: tracker-miner-files tracker-miners-lang - Update to version 3.7.1: + Improvements to the handling of corrupted databases. + Further syscall rules in the seccomp sandbox. + Fix some possible warnings during tracker-extract-3 startup. + Fixes to extraction of dc:source fields from XMP data. + Avoid SIGABRT on missing Landlock. ==== virtualbox ==== - The location of vboxconfig is wrong. Add file fixes_for_vboxconfig.patch to fix. Some errors in vboxdrv.sh are fixed. - Further fixes for builds on Leap 15.6. Fixes boo#1221496. Adds file fixes_for_leap15.6.patch ==== virtualbox-kmp ==== - The location of vboxconfig is wrong. Add file fixes_for_vboxconfig.patch to fix. Some errors in vboxdrv.sh are fixed. - Further fixes for builds on Leap 15.6. Fixes boo#1221496. Adds file fixes_for_leap15.6.patch

1 0

Tumbleweed - Review of the week 2024/13
by Dominique Leuenberger 30 Mar '24

30 Mar '24

Dear Tumbleweed users and hackers, What a week! We all were looking forward to a short week just before the Easter weekend and a long break. Things just never are, as they are expected to be, right? You have “only” received 4 snapshots this week (0325, 0326, 0327, and 0328) – and, as happens very rarely, some updates in the update channel (this should indicate to you it is important enough for us to side-track the already fast release process). The most relevant changes this week were: * Mesa 24.0.3 * KDE Gear 24.02.1 * emacs 20.3 * Shadow 4.15.1 * Mozilla Firefox 124.0.1 * KDE Plasma 6.0.3 * LibreOffice 24.2.2 * TeXLive 2024 * Qt 6.6.3 * cURL 8.7.1 !!! xz 5.6.1.revertto5.4 (version 5.4, but with a version tag > 5.6.1 for users that wrongly would not use zypper dup – we wanted to be sure). Please see https://news.opensuse.org/2024/03/29/xz-backdoor/ and upgrade SOON (at least liblzma5, then reboot) For some regions, there is a long weekend ahead – so expect no / few snapshots until early next week. For snapshot 0328, Ring0 has been completely bootstrapped (as the attack vectors for xz were not fully known, we went the safest route) and for 0329 all of Tumbleweed rebuilt against that new base; Ezpect that snapshot to appear ‘large’ (even though many packages will not be different). The relevant changes to come to you during the next days/week include: * Python 3.9 module removal (the bootstrap rebuild was a good excuse, as that removal would have required OBS internal rebuild strategy anyway – so instead of doing it twice, we pulled that change forward into 0329 – I mentioned that removed for a few weeks already) * Linux kernel 6.8.2 * Linux LTS Kernel 6.6.23 * dbus-broker: no progress this week * libxml 2.12.x: slow/no progress * GCC 14: phase 2: use gcc14 as the default compiler Cheers, Dominique

2 1