September 2023 - openSUSE Factory - openSUSE Mailing Lists

factory@ is now under moderation
by Neal Gompa 28 May '24

28 May '24

Hello all, Due to the recent continuous inappropriate behavior on the factory@ mailing list, we have taken the extraordinary action of moderating the entire mailing list. Each message being submitted will be actively reviewed for approval until the Board works through the necessary and appropriate behavior to resolve this incident. -- Neal Gompa (ID: Pharaoh_Atem)

3 2

[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

enabling reproducible builds in Factory and ALP
by Jan Zerebecki 15 Mar '24

15 Mar '24

Hi *, to support https://en.opensuse.org/openSUSE:Reproducible_Builds I plan to get the following project configuration for Factory and ALP enabled: Macros: %source_date_epoch_from_changelog Y %clamp_mtime_to_source_date_epoch Y %use_source_date_epoch_as_buildtime Y %_buildhost reproducible :Macros I'm still waiting to get https://github.com/openSUSE/product-builder/pull/26 merged to prevent a bug with mirrors that will otherwise happen. Afterwards a time of the build is still in the HTTP header Last-Modified when requesting the rpm file. HTTP mtime is a few seconds earlier than end time of the build (seen in OBS web UI only as start + duration). I didn't double check, but it should also be recorded in the Tumbleweed archive Bernhard keeps, which can with a bit of work be looked up by content hash or name including version of the rpm file if its not on the normal mirrors anymore. Both the build time and host can also still be seen in the build log. Comments welcome. -- Best regards, Jan Zerebecki

4 6

Proposal: amend the packaging guidelines for %fillup_only
by Dan Čermák 02 Mar '24

02 Mar '24

Hi list, our packaging guidelines for %fillup_only [1] currently do not suggest anything for the %files section for the files generated in `/etc/sysconfig/`. I would like to suggest that we start adding the newly generated file `/etc/sysconfig/$pkgname` as follows to the %files section: --8<---------------cut here---------------start------------->8--- %files %ghost %config(noreplace) %attr(0600,root,root) /etc/sysconfig/%{name} %dir /etc/sysconfig --8<---------------cut here---------------end--------------->8--- This ensures that rpm is aware of the files as configuration files. Thoughts, opinions? Cheers, Dan Footnotes: [1] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#%fillup_o… -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

3 3

wine and zlib
by Joe Salmeri 22 Feb '24

22 Feb '24

I did a fresh install of TW 20230222 on a new PC. My main desktop which was installed back in 2021 has also been updated ( zypper dup ) to 20230222. I found something odd when comparing packages between the 2 machines. Both PC's have wine installed, however... On my main desktop when the original install in 2021 of wine was done it installed libz1-32bit ( as per the zypper history logs ) and it still has that installed after it was updated to 20230222. On the new PC fresh install of 20230222 when wine was installed it installed libz-ng-compat1-32bit. The libz-ng-compat1-32bit version looks like it was forked in 2021, just after my main machine was originally built so that would explain why it has libz1-32bit but shouldn't it have been updated by zypper dup ??? Is this a bug that I should report? If so, which system is wrong / which version should be used? Thanks!

5 6

Recent e2fsprogs update flag changes
by Patrick Schaaf 22 Feb '24

22 Feb '24

Hi, as I haven't found discussion by searching, I thought I bring up a gotcha I ran into today, on a host recently updated to tumbleweed 20230801 level. With a somewhat recent update to e2fsprogs, now at 1.47.0 compared to May '23 at 1.46.5, the set of mkfs flags has changed: --- /root/mke2fs.conf.20230512 2023-08-09 12:00:14.379476597 +0200 +++ /etc/mke2fs.conf 2023-06-14 19:20:22.000000000 +0200 @@ -14 +14 @@ - features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize + features = has_journal,extent,huge_file,flex_bg,metadata_csum,metadata_csum_seed,64bit,dir_nlink,extra_isize,orphan_file For me, this resulted in an otherwise fine virtual machine with 20230512 userlevel, not booting after an "rsync copy migration" into a fresh root filesystem mkfs'ed with these new flags. Reason being that 3 months older fsck - the sytemd boot time rootfs service actually - goes "failed". I guess I'll need just use flag override options going forward, to cope with that, but thought I'd bring it to attention here at least. best regards Patrick

3 4

snapd applications not working on Tumbleweed (20230613)
by Jim Henderson 19 Jan '24

19 Jan '24

Wondering if anyone else is seeing this. I attempted to launch two apps (slack and spotify) installed with snapd, and the launch failed. Troubleshooting it, I removed all of the snaps from the system, uninstalled and reinstalled snapd, and I get the following output: --- $ snap install spotify error: cannot perform the following tasks: - Run configure hook of "spotify" snap if present (run hook "configure": ----- go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Matcha-dark-sea /snap/spotify/67/data-dir/themes/Matcha-dark-sea none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Matcha-sea /snap/spotify/67/data-dir/themes/Matcha-sea none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-compact /snap/spotify/67/data-dir/themes/Materia-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-dark-compact /snap/spotify/67/data-dir/themes/Materia-dark-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-dark /snap/spotify/67/data-dir/themes/Materia-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-light-compact /snap/spotify/67/data-dir/themes/Materia-light-compact none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia-light /snap/spotify/67/data-dir/themes/Materia-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Materia /snap/spotify/67/data-dir/themes/Materia none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Radiance /snap/spotify/67/data-dir/themes/Radiance none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Radiant-MATE /snap/spotify/67/data-dir/themes/Radiant-MATE none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-MATE-dark /snap/spotify/67/data-dir/themes/Yaru-MATE-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-MATE-light /snap/spotify/67/data-dir/themes/Yaru-MATE-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-bark-dark /snap/spotify/67/data-dir/themes/Yaru-bark-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-bark /snap/spotify/67/data-dir/themes/Yaru-bark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-blue-dark /snap/spotify/67/data-dir/themes/Yaru-blue-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-blue /snap/spotify/67/data-dir/themes/Yaru-blue none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-dark /snap/spotify/67/data-dir/themes/Yaru-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-light /snap/spotify/67/data-dir/themes/Yaru-light none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-magenta-dark /snap/spotify/67/data-dir/themes/Yaru-magenta-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-magenta /snap/spotify/67/data-dir/themes/Yaru-magenta none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-mate-dark /snap/spotify/67/data-dir/themes/Yaru-mate-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-mate /snap/spotify/67/data-dir/themes/Yaru-mate none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-olive-dark /snap/spotify/67/data-dir/themes/Yaru-olive-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-olive /snap/spotify/67/data-dir/themes/Yaru-olive none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-prussiangreen-dark /snap/spotify/67/data-dir/themes/Yaru-prussiangreen-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-prussiangreen /snap/spotify/67/data-dir/themes/Yaru-prussiangreen none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-purple-dark /snap/spotify/67/data-dir/themes/Yaru-purple-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-purple /snap/spotify/67/data-dir/themes/Yaru-purple none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-red-dark /snap/spotify/67/data-dir/themes/Yaru-red-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-red /snap/spotify/67/data-dir/themes/Yaru-red none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-sage-dark /snap/spotify/67/data-dir/themes/Yaru-sage-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-sage /snap/spotify/67/data-dir/themes/Yaru-sage none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-viridian-dark /snap/spotify/67/data-dir/themes/Yaru-viridian-dark none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru-viridian /snap/spotify/67/data-dir/themes/Yaru-viridian none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/Yaru /snap/spotify/67/data-dir/themes/Yaru none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied update.go:85: cannot change mount namespace according to change mount (/snap/gtk-common-themes/1535/share/themes/elementary /snap/spotify/67/data-dir/themes/elementary none bind,ro 0 0): cannot create writable mimic over "/snap/spotify/67/data-dir/themes": permission denied cannot update snap namespace: cannot create writable mimic over "/usr/lib/x86_64-linux-gnu": permission denied snap-update-ns failed with code 1 -----) --- The execution of both programs prior to the reinstallation did the same thing. I did note that /usr/lib/x86_64-linux-gnu does not exist on my system. Happy to report a bug on bugzilla, but wanted to see if anyone else had noticed this. -- Jim Henderson Please keep on-topic replies on the list so everyone benefits

5 10

Is it possible for Slowroll to officially support the integrity of NVidia and VMWare modules?
by Xu Zhao 19 Dec '23

19 Dec '23

Hello all, I am a 5-years Tumbleweed user. I am also the maintainer of many Tumbeweed packages such as telegram-desktop, chezscheme, amdvlk, and yacreader. I have both AMD and NVIDIA desktops with openSUSE Tumbleweed installed. NVidia closed-source GPU driver integration has always been a pain for rolling release like Tumbleweed because: 1) kernel's API keeps changing and it often takes NVidia 1~2 weeks to follow-up the latest kernel release in their new driver version (see http://rglinuxtech.com/ ); 2) people who don't care about NVidia do not want to slow down the rolling of kernel versions For example, even today the version of nvidia-open-driver-G06-signed-kmp-default(https://build.opensuse.org/packag…, 535.113.01) is not compatible with nvidia-video-G06 (https://download.nvidia.com/opensuse/tumbleweed/x86_64/, 535.104) on Tumbleweed. I am wondering if we can attract some users to Slowroll if it only releases snapshots whose kernel version is compatible with the NVidia GPU driver? At least I will be very interested to try it out on my Nvidia desktop. Similar case should apply for VMWare kernel modules, but if it takes too much additional efforts, I think we should priortize NVidia module integrity. Best, Xu -- Xu Zhao i(a)xuzhao.net

10 16

[TESTERS WANTED] Using git to maintain packages on OBS - test run
by Dan Čermák 08 Dec '23

08 Dec '23

Dear packagers for openSUSE Tumbleweed, we have been working on a prototype that allows you to maintain your packages in git (similarly to Fedora's dist git) on src.opensuse.org instead of on OBS. Contributions to the package are then handled via pull requests on src.opensuse.org which get automatically forwarded as submitrequests on OBS. This is currently just a prototype and we are looking for testers and general feedback. So if you want to participate as a maintainer, please check the full guide here: https://opensuse.github.io/scm-staging/user_guide.html tl;dr; you'll have to convert the develpackage to use `<scmsync>` from src.opensuse.org/pool and everything else should "just work". FAQ: - Where can I report issues or provide feedback? https://github.com/openSUSE/scm-staging/issues (for bugs) or https://github.com/openSUSE/scm-staging/discussions (for general feedback) - Is this how the future of packaging in openSUSE is going to look like? Maybe, maybe not. This is currently just a test drive and its outcome will influence the way forward. - Will submitrequests to my develpackage still work? Sadly no, branching a git maintained package on OBS does not work. Please indicate in the description of your package that users should contribute on src.opensuse.org instead. - Which tools do I need? Just git, git-lfs and osc (at least version 1.2.0 is recommended for service runs to work) Looking forward to your feedback! Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

23 66

Migrate from update-alternatives to libalternatives
by Martin Schreiner 05 Dec '23

05 Dec '23

Hello folks, As some of you may know, there are some limitations regarding update-alternatives that prevent it from working perfectly when using transactional updates. Basically, /var isn't part of the snapshot's data. This means that all files created/manipulated during package installation in /var/lib/alternatives won't be taken into consideration when snapshots are rolled back. More information is available here: https://kubic.opensuse.org/documentation/transactional-update-guide/tu-setu… This fact could lead to broken symlinks: Suppose I install "go1.20"(snapshot A) and "go1.21" (snapshot B). I then boot from snapshot A, but "/var/lib/alternatives/go" still tells "update-alternatives" that "go1.21" would be a valid choice, since this information lives outside of the snapshot's directories, in "/var". If "update-alternatives" were to accept that choice, then "/etc/alternatives/go" would become a broken link, our last line of defence here being how carefully maintained "update-alternatives" is. So that's not a system-level design solution, but rather very application-specific. What we're planning: Replace update-alternatives with libalternatives: https://github.com/openSUSE/libalternatives This change should be done gradually on Factory, and ideally it would require no manual intervention from the users. We plan on releasing this change in batches: i.e.: all Go versions we provide on Factory would be migrated to libalternatives in a single-pass. Then another set of closely-related packages, such as the OpenJDK. Then another, so on and so forth. What we need: The goal of this thread is to establish a line of discussion around this change, which should be a gradual one on Factory. All opinions, comments, ideas and criticism are valid, and will be taken into consideration. Status: There are currently 14909 spec files on openSUSE:Factory. 964 (6.46%) of these depend on update-alternatives. Currently 52 packages use libalternatives, such as vim and nodejs-common. Basically, the cores of both MicroOS and SLE Micro are already using libalternatives. Things that seem to be clear in this particular context: 1 - libalternatives should work really well with transactional updates: As the state of alternatives kept by libalternatives is maintained in /usr/share/libalternatives/<binary>/<pref>.conf, this means that packages only need to provide a single file to provide their alternative. This file will be part of the package's regular files (declared in %files), and no state is modified by any hooks (preun, postun, prerm, postrm) during the updates. Rolling back a snapshot will revert back to a state where that alternative didn't exist (as it wasn't installed). 2 - libalternatives does not manipulate symlinks: /usr/bin/alts (the main binary for libalternatives) executes binaries directly (by calling exec()). The actually binary (for example, /usr/bin/vi) is a symlink to /usr/bin/alts, which then reads its configuration files and determines which binary to execute, based on the highest priority. 3 - libalternatives supports user overrides: non-root users can override the alternatives by creating their own local preference file in $HOME/.config/libalternatives.conf. This may be done by invoking "alts" directly, as it serves both purposes. 4 - Even if it doesn't manipulate symlinks, groups and manpages are still supported: libalternatives has a "group" directive for manipulating groups of binaries together, and it has some verifications to ensure the binaries in these groups are indeed declared in tandem with one another, essentially managing them as a collection. It also has a "man" directive for man pages, so even if it's not doing symlink manipulation, look up man pages still works. In fact, our "man" package was patched to work with libalternatives support: https://build.opensuse.org/package/view_file/Base:System/man/man-db-2.9.4-a… 5 - No RPM macros are required: This is really cool. We're basically just adding a file to %files, to use libalternatives. So no RPM macros are even required here. But we could create an RPM macro that automatically writes the preference file, so we could easily manipulate its contents inside the RPM spec. 6 - How libalternatives can actually be used So there are actually at least TWO ways to use libalternatives: we either create a symlink to /usr/bin/alts, or use libalternatives as a shared object and write a tiny wrapper program, such as this one: https://build.opensuse.org/package/view_file/devel:languages:nodejs/nodejs-… The advantage of the first method is that we don't need a special – albeit short – C program to act as a dispatcher for libalternatives's magic sauce. The advantage of the second method is that we don't need packages to depend on the "alts" package (which contains /usr/bin/alts), but only on "libalternatives1" instead (which provides /usr/lib64/libalternatives.so.1). I appreciate if you can provide any insights here, they're more than welcome. Thank you.

16 45

SCSI device identification and SCSI symlink generation in sg3_utils 1.48
by Martin Wilck 09 Nov '23

09 Nov '23

With the forthcoming update of sg3_utils to v1.48 (currently in Base:System, to be submitted to Factory soon), SCSI device identification and SCSI symlink generation by udev will change. TL;DR: unreliable device identifiers will not be used by default any more, and /dev/disk/by-id symlinks for such identifiers will not be created by default, either. The policy can be changed by editing the udev rules in 00-scsi-sg3_config.rules. Please file bugs and / or notify me if you have trouble with this new identification scheme. Of course, while this is still in Base:System, we can also discuss the general approach for Factory, and the defaults to be applied. Long version: It is well known that referring to disk devices by their device node (like /dev/sda) is unreliable. In most situations, it is recommended to refer to devices by their content, i.e. using file system UUIDs or labels. Sometimes, however, the devices must be referred to by hardware properties. For this purpose, udev maintains various symlinks under /dev/disk/by-id. This post is specifically about SCSI symlinks, which have the format /dev/disk/by-id/scsi-XYZ. If you don't use dm-multipath, and don't use hardware IDs to refer to any disks or partitions anywhere, you can stop reading here. SCSI devices can be identified in different ways by the contents of SCSI VPD (Vital Product Data) pages. In PVD 83 (device identification), the following identifiers may occur (see SCSI spec SPC-6 §7.7.6 for details): a) NAA registered extended: 36... (+ 31 hex digits) b) NAA registered: 35... (+ 15 hex digits) c) NAA extended: 32... (+ 15 hex digits) d) EUI-64: 2... (+ 16 hex digits) e) SCSI name string: 8... (+ utf-8 string) f) NAA local ("L"): 33... (+ 15 hex digits) g) T10 vendor-ID ("T): 1... (+ string) h) vendor-specific ("V") 0... (+ string) Furthermore, we have i) serial number ("S"): S... (+ vendor/product/serial string) The list above is sorted roughly top-down by the reliability (uniqueness) of these identifiers. The udev rules select the most reliable available identifier from the above list to set the ID_SERIAL udev property, which is used e.g. by dm-multipath to identify SCSI devices which represent different paths to the same physical volume. Furthermore, the udev rules create /dev/disk/by-id/scsi-$ID symlinks for all identifiers from the above list that are defined for a given device. This makes sure that whatever identifier a user has chosen for referring to her disks will be available as symlink under /dev/disk/by-id. However, this has also severe disadvantages. The identifiers f)-i) are not reliable; IOW there can be multiple devices in the same system that use the same identifier, although they don't represent the same physical disk. This applies to i) in particular: Some large storage arrays use the same serial number for all LUNs they expose. Using such identifiers for multipath can cause fatal data corruption. Moreover, the creation of these symlinks during boot can slow down booting a lot, because thousands of devices may be contending for the same symlink. Lastly, not creating useless symlinks will tidy up /dev/disk/by-id and make it easier to read. Therefore sg3_utils 1.48 changes the policy for SCSI device identification. The policy can be customized in the udev rule "00-scsi- sg3_config.rules" (to change the policy, copy this file from /usr/lib/udev/rules.d to /etc/udev/rules.d first). For determining ID_SERIAL, only a)-e) above are tried. If users need to use additional identifiers from the list above, they can set the udev property .SCSI_ID_SERIAL_SRC (leading "." is intentional) to any combination of the capital letters in quotes in the list above. E.g. "ST" would mean to take g) and i) into account. To restore the previous behavior, set ENV{.SCSI_ID_SERIAL_SRC}="LTVS". The current upstream default is "T", so that g) above is still enabled. To disable all "unreliable" IDs, set it to the empty string. If udev encounters a device for which ID_SERIAL can't be assigned, it prints a warning to the journal. Symlink generation is controlled by the variable .SCSI_SYMLINK_SRC. It can also be set to any combination of "LTVS", with the same meaning of the letters as above, and controls which scsi-... symlinks udev will create under /dev/disk/by-id/, *in addition* to the symlink /dev/disk/by-id/scsi-$ID_SERIAL, which will always be created if ID_SERIAL could be determined. Again, to restore the previous behavior of the udev rules, set ENV{.SCSI_SYMLINK_SRC}="LTVS". The default is the empty string. Note 1: The symlink generation applies to both disks and partitions. Partition symlinks have a "-part$P" string appended to the name of the symlink of their parent disk. Note 2: Modern SCSI devices usually support one or more of the "reliable" identifiers a)-e) above. I expect that only very few old devices really need one of f)-i). Inform me if you find counter- examples. Note 3: ATA and USB devices have additional identifiers generated by the transport (/dev/disk/by-id/ata-* and /dev/disk/by-id/usb-*) which are unaffected by this change. These devices often don't expose proper SCSI IDs, but they actually don't need them because the ATA or USB identifiers are unique. Regards, Martin

7 27

Disk auto-unlocking with TPM 2.0
by Gary Lin 10 Oct '23

10 Oct '23

Hi, I'm pleased to introduce a new feature for openSUSE Tumbleweed: disk auto-unlocking with TPM 2.0. In short, it boots the encrypted root without asking for a passphrase. This feature is already integrated into Agama on ALP and we plan to merge it into yast-installation (*1). For now, if you're interested, just type a few commands to enable it. The hard requirements are LUKS2 partition(s), UEFI with Secure Boot enabled, and, of course, TPM 2.0. LUKS2 support in yast-installation is still experimental and needs a few extra steps. You could also choose to convert the existing LUKS1 partition to a LUKS2 one. The LUKS2 setup is addressed in the following link: https://en.opensuse.org/SDB:Encrypted_root_file_system#Setup_LUKS2_partitio… First of all, please update all packages, especially shim and grub2. The key package is fde-tools. Currently, there is a minor issue that the TCTI for native devices may not be installed, and the fix is on the way(*2). So, please install fde-tools along with libtss2-tcti-device0 for the time being. # zypper in fde-tools libtss2-tcti-device0 After installing fde-tools, you can test the TPM 2.0 support with # fdectl tpm-present If there is no error, it's time to seal a new random key for your root partition: # fdectl regenerate-key This command will request the passphrase of the root partition to enroll a new random key, seal the random key with TPM, and then update the grub configuration. Next, reboot your system. If everything is setup correctly, the system will boot without showing the passphrase prompt. One thing to be noted is that after a boot component upgrade, such as shim, grub2, or UEFI firmware, the signature in the sealed key may become invalid, and then you have to run the following command to update the signature. # fdectl tpm-authorize We are still working on a solution to update the signature automatically after shim and grub2 update to reduce such hassles. By default, 'fdectl' only manages the keyslots of the root partition. To extend the keyslot management to other partitions such as swap, please check https://en.opensuse.org/SDB:Encrypted_root_file_system#Additional_steps_for… A complete document is available here: https://en.opensuse.org/SDB:Encrypted_root_file_system#Unattended_boot_with… In case you encounter any issue, feel free to file a bug and assign it to bootloader-maintainers(a)suse.de Cheers, Gary Lin (*1) https://github.com/yast/yast-installation/issues/1088 (*2) https://build.opensuse.org/request/show/1100949

17 32

Leap not more useful for WebServer with php
by Walddys Emmanuel Dorrejo Céspedes 09 Oct '23

09 Oct '23

Leap is stuck with PHP 8.0 version, when most devs and project have move to php8.1/8.2, i was hoping that php8.1 at least this version reach leap 15.5, but didn't reached the main repo. sad.

6 6

Changes to dbus packaging (Some Attention maybe required).
by Simon Lees 04 Oct '23

04 Oct '23

Hi All, For Tumbleweed and ALP we plan to follow Red Hat / Fedora / Debian and move from dbus-daemon to dbus-broker as it has a number of advantages and is what upstream is now focusing on. While one of the goals here is to provide the same user experience there will be a couple of changes that will likely require adjustments in a few packages. 1. tools such as dbus-send and dbus-uuid will no longer be installed by default on all systems (we have many use cases that will simply no longer need them and this follows other distro's). Currently the package dbus-1-tools exists and is required by dbus-1 but that will change maybe to a recommends so if you know your package needs one of these tools you can add the Requires there now, otherwise I plan to go through and look at debian and fedora to try and find any packages that need this requires before it becomes optional for dbus. 2. The symlink from /etc/machine-id to /var/lib/dbus/machine-id will no longer be present on all machines and software should be adapted to use /etc/machine-id from systemd rather then the dbus copy. Again this has already happened for Debian and Fedora so hopefully many upstreams have already adapted to this. I'll outline the plan / timeline below. 1. Currently - dbus-broker has been in the distro for quite some time and the dbus-1 package has already been split up and we are at the point of asking people nicely to start testing (instructions below), myself and at least several other people have already been testing this without issues. 2. In 2-3 weeks if I don't hear of any issues we will update the systemd presets to enable dbus-broker rather then dbus-daemon. 3. Unless someone indicates they really want to keep maintaining dbus-daemon and have good reasons for doing so I will make dbus-daemon uninstallable. 4. Once we have done the work to ensure that as many packages that use dbus-send and other tools require the tools package we will drop the requires for dbus-tools from the dbus package. Instead it will probably move to being a Recommends in one of the patterns so it still ends up on most users machines. Switching to dbus-broker: Run the following as root zypper in dbus-broker systemctl disable dbus systemctl enable dbus-broker systemctl --global disable dbus systemctl --global enable dbus-broker https://www.mail-archive.com/debian-policy@lists.debian.org/msg35437.html https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementa… -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

4 6

Re: Trial to use a CDN for download.opensuse.org
by Jan Engelhardt 03 Oct '23

03 Oct '23

A slow mirror I could live with, but... an unreachable one ううん. This does not actually look like cdn is really used in this particular instance. # wget http://cdn.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmime-debugsour… -c --2023-09-30 17:19:37-- http://cdn.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmime-debugsour… Resolving cdn.opensuse.org (cdn.opensuse.org)... 151.101.109.91, 2a04:4e42:1a::347 Connecting to cdn.opensuse.org (cdn.opensuse.org)|151.101.109.91|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrorcache-jp.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmim… [following] --2023-09-30 17:19:37-- http://mirrorcache-jp.opensuse.org/debug/tumbleweed/repo/oss/x86_64/libvmim… Resolving mirrorcache-jp.opensuse.org (mirrorcache-jp.opensuse.org)... 139.162.108.149, 2400:8902::f03c:93ff:fec8:af18 Connecting to mirrorcache-jp.opensuse.org (mirrorcache-jp.opensuse.org)|139.162.108.149|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirror-jp.firstyear.id.au/debug/tumbleweed/repo/oss/x86_64/libvmime-… [following] --2023-09-30 17:19:38-- http://mirror-jp.firstyear.id.au/debug/tumbleweed/repo/oss/x86_64/libvmime-… Resolving mirror-jp.firstyear.id.au (mirror-jp.firstyear.id.au)... 139.162.108.7, 2400:8902::f03c:93ff:fec8:afa1 Connecting to mirror-jp.firstyear.id.au (mirror-jp.firstyear.id.au)|139.162.108.7|:80... ^C 17:20 f3:~ $ ping mirror-jp.firstyear.id.au PING mirror-jp.firstyear.id.au (139.162.108.7) 56(84) bytes of data. ^C --- mirror-jp.firstyear.id.au ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2027ms

2 3

Mesa 23.1.7 32-bit libraries missing in updates repo on Slowroll
by Kostadin Shishmanov 03 Oct '23

03 Oct '23

When I try to install steam on slowroll, for some reason Mesa-32bit-23.1.7 is missing from the "updates" repo and instead zypper asks me to downgrade Mesa to 23.1.5 in order to go through, which makes KDE use llvmpipe. Can someone figure out why the 32bit libraries of mesa 23.1.7 are missing from updates?

2 1

slowroll ignoring packages in updates repo
by Felix Miata 03 Oct '23

03 Oct '23

3 4

Puzzling rootless docker issue on TW
by Jim Henderson 01 Oct '23

01 Oct '23

I've been attempting to help a user in the forums[1] with an issue running Docker rootless - he's running into an issue with being able to pull images resulting in the following error: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: read udp 10.0.2.100:48971->10.0.2.3:53: i/o timeout He also opened a discussion in the Docker forums (who referred him to our forums), and I've been chatting with the guy (Ákos) who was helping him over there in that thread[2]. The puzzling thing for me is that I can't duplicate the issue. I've tried on GNOME and KDE both, and I just cannot reproduce the problem. In troubleshooting the issue together with Ákos, we seem to have isolated the issue to something in the slirp4netns network that's used in that configuration - but nobody involved has customized that setup at all - yet it fails for both of them and doesn't fail for me. The issue *seems* to be that the DNS server set up in that network (10.0.2.3) is not responsive for either of them - but it is for me. Wondering if anyone here has any ideas about what else to look at beyond what we already have in these two threads. I'm completely out of ideas. Jim [1] https://forums.opensuse.org/t/rootless-docker-i-o-timeout-with-docker- pull/169468/12 [2] https://forums.docker.com/t/rootless-docker-i-o-timeout-with-docker- pull/137848 -- Jim Henderson Please keep on-topic replies on the list so everyone benefits

4 11

openSUSE:Factory - Build fail notification
by DimStar / Dominique Leuenberger 30 Sep '23

30 Sep '23

Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - flux: Fails to build - gnuprumcu: Unresolvable - goverlay: Fails to build - python-Flask-Security-Too: Fails to build - python-pip-api: Fails to build Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>

1 0

New Tumbleweed snapshot 20230927 released!
by Dominique Leuenberger 30 Sep '23

30 Sep '23

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: Mesa (23.1.7 -> 23.1.8) Mesa-drivers (23.1.7 -> 23.1.8) autoyast2 (4.6.2 -> 5.0.1) gcc13 gnome-tweaks (42.beta+60 -> 45.0) gpg2 (2.3.8 -> 2.4.0) libsolv (0.7.24 -> 0.7.25) libstorage-ng (4.5.141 -> 4.5.143) mozjs115 (115.2.0 -> 115.2.1) open-vm-tools python-alembic (1.11.2 -> 1.12.0) tracker unar vsftpd yast2-schema (4.6.1 -> 5.0.1) yast2-storage-ng (4.6.12 -> 5.0.1) yast2-users (4.6.4 -> 5.0.1) === Details === ==== Mesa ==== Version update (23.1.7 -> 23.1.8) Subpackages: Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 libOSMesa8 libgbm1 - Backport upstream patches for compatibility with LLVM 17: * U_llvmpipe-only-include-old-Transform-includes-when-ne.patch removes unneeded includes of header files that no longer exist. * U_clover-llvm-move-to-modern-pass-manager.patch migrates Clover to the new pass manager, since the old PM has been removed. - disable nine on arm/aarch64 in the hope to fix build on this platform; there is no need for Direct3D/Wine for arm/aarch64 anyway ... - Update to bugfix release 23.1.8: - -> https://docs.mesa3d.org/relnotes/23.1.8.html ==== Mesa-drivers ==== Version update (23.1.7 -> 23.1.8) Subpackages: Mesa-dri Mesa-gallium Mesa-libva libxatracker2 - Backport upstream patches for compatibility with LLVM 17: * U_llvmpipe-only-include-old-Transform-includes-when-ne.patch removes unneeded includes of header files that no longer exist. * U_clover-llvm-move-to-modern-pass-manager.patch migrates Clover to the new pass manager, since the old PM has been removed. - disable nine on arm/aarch64 in the hope to fix build on this platform; there is no need for Direct3D/Wine for arm/aarch64 anyway ... - Update to bugfix release 23.1.8: - -> https://docs.mesa3d.org/relnotes/23.1.8.html ==== autoyast2 ==== Version update (4.6.2 -> 5.0.1) Subpackages: autoyast2-installation - Added several LUKS-related elements to the partitioning schema (jsc#PED-3878, jsc#PED-5518). - 5.0.1 - 5.0.0 (#bsc1185510) ==== gcc13 ==== Subpackages: cpp13 gcc13-locale libasan8 libatomic1 libgcc_s1 libgccjit0 libgfortran5 libgomp1 libhwasan0 libitm1 liblsan0 libobjc4 libquadmath0 libstdc++6 libstdc++6-locale libstdc++6-pp libtsan2 libubsan1 - add pr111411.patch (bsc#1215427) ==== gnome-tweaks ==== Version update (42.beta+60 -> 45.0) Subpackages: gnome-tweaks-lang - Update to version 45.0: + This release removes several features now found in GNOME Settings. There are also some small interface refreshments in preparation for the GTK4 upgrade. More significantly, the core interface has been refactored to use layout files. + Updated translations. - Switch compression to zst both in service and tarball produced. ==== gpg2 ==== Version update (2.3.8 -> 2.4.0) Subpackages: dirmngr gpg2-lang - Install the systemd user units in the _userunitdir [bsc#1201564] * Note that, there is no activation by default. * Rework excludes in the spec's files section. - Temporarily revert back to the pre-2.4 default for key generation. The new rfc4880bis has been set as the default in 2.4 version and might create incompatible keys. Note that, rfc4880bis can still be used with the option flag --rfc4880bis as in previous versions. * More info in the gnupg-devel ML: https://lists.gnupg.org/pipermail/gnupg-devel/2022-December/035183.html * Reverted commit https://dev.gnupg.org/rGcaf4b3fc16e9 * Add gnupg-revert-rfc4880bis.patch - Allow 8192 bit RSA keys in keygen UI when large_rsa is set * Add gnupg-allow-large-rsa.patch - Fix broken GPGME QT tests: Upstram dev task dev.gnupg.org/T6313 * The original patch has been modified to expand the changes also to the tests/gpgme/Makefile.in file. * Add gnupg-tests-Fix-tests-gpgme-for-in-source-tree-builds.patch - Updated to require libgpg-error-devel >= 1.46 - Rebased patches: * gnupg-allow-import-of-previously-known-keys-even-without-UIDs.patch * gnupg-add_legacy_FIPS_mode_option.patch - GnuPG 2.4.0: * common: Fix translations in --help for gpgrt < 1.47. * gpg: Do not continue the export after a cancel for the primary key. * gpg: Replace use of PRIu64 in log_debug. * Update NEWS for 2.4.0. * tests: Fix make check with GPGME. * agent: Allow arguments to "scd serialno" in restricted mode. * scd:p15: Skip deleted records. * build: Remove Windows CE support. * wkd: Do not send/install/mirror expired user ids. * gpgsm: Print the revocation time also with --verify. * gpgsm: Fix "problem re-searching certificate" case. * gpgsm: Print revocation date and reason in cert listings. * gpgsm: Silence the "non-critical certificate policy not allowed". * gpgsm: Always use the chain model if the root-CA requests this. * gpg: New export option "mode1003". * gpg: Remove a mostly duplicated function. * tests: Simplify fake-pinentry to use the option only. * tests: Fix fake-pinentry for Windows. * tests: Fix make check-all. * agent: Fix import of protected v5 keys. * gpgsm: Change default algo to AES-256. * tests: Put a workaround for semihosted environment. * tests: More fix for semihosted environment. * tests: Support semihosted environment. * tests: Fix tests under cms. * tests,w32: Fix for semihosted environment. * w32: Fix for tests on semihosted environment. * w32: Fix gnupg_unsetenv. * wkd: New option --add-revocs and some fixes. * wkd: Make use of --debug extprog. * gpg: New export-filter export-revocs. * gpg: Fix double-free in gpg --card-edit. * gpg: Make --require-compliance work with out --status-fd. * gpg: New option --list-filter. * dirmngr: Silence ocsp debug output. * tests: Fix to support --enable-all-tests and variants. * tests:w32: Fix for non-dot file name for Windows. * tests:gpgscm:w32: Fix for GetTempPath. * tests: Keep .log files in objdir. * tests: Use 233 for invalid value of FD. * w32: Fix gnupg_tmpfile for possible failure. * scd: Redact --debug cardio output of a VERIFY APDU. * common: Remove Windows CE support in common. * gpgsm: Fix colon outout of ECC encryption certificates. * scd:nks: Fix ECC signing if key not given by keygrip. * dirmngr: Fix verification of ECDSA signed CRLs. * agent: Allow trustlist on Windows in Unicode homedirs. * gpg: Fix verification of cleartext signatures with overlong lines. * gpg: Move w32_system function. * gpg: New option --quick-update-pref. * gpg: New list-options show-pref and show-pref-verbose. * tests: Add tests to check that OCB is only used for capable keys. * gpg: Make --list-packets work w/o --no-armor for plain OCB packets. * tests: Add symmetric decryption tests. * tests: Add tr:assert-same function. * agent: Avoid blanks in the ssh key's comment. * build: Update m4 files. * gpg: Merge --rfc4880bis features into --gnupg. * gpg: Allow only OCB for AEAD encryption. * gpg: New option --compatibility-flags. * gpgsm: Also announce AES256-CBC in signatures. * gpg: Fix trusted introducer for user-ids with only the mbox. * gpg: Import stray revocation certificates. * agent: Automatically convert to extended key format by KEYATTR. * card: New commands "gpg" and "gpgsm". * card: Also show fingerprints of known X.509 certificates. * scd:nks: Support non-ESIGN signing with the Signature Card v2. * gpgsm: Allow ECC encryption keys with just keyAgreement specified. * gpgsm: Use macro constants for cert_usage_p. * build: Update gpg-error.m4. * agent,common,dirmngr,tests,tools: Remove spawn PREEXEC argument. * gpg: Move NETLIBS after GPG_ERROR_LIBS. * gpg: Use GCRY_KDF_ONESTEP_KDF with newer libgcrypt in future. * common,w32: Fix struct stat on Windows. * agent,w32: Support Win32-OpenSSH emulation by gpg-agent. * common: Don't use FD2INT for POSIX-only code. * dirmngr: Fix build with no LDAP support. ==== libsolv ==== Version update (0.7.24 -> 0.7.25) Subpackages: libsolv-tools python3-solv ruby-solv - support complex deps in SOLVABLE_PREREQ_IGNOREINST - fix minimization not prefering installed packages in some cases - reduce memory usage in repo_updateinfoxml - fix lock-step interfering with architecture selection - fix choice rule handing for package downgrades - fix complex dependencies with an "else" part sometimes leading to unsolved dependencies - bump version to 0.7.25 ==== libstorage-ng ==== Version update (4.5.141 -> 4.5.143) Subpackages: libstorage-ng-lang libstorage-ng-ruby libstorage-ng1 - merge gh#openSUSE/libstorage-ng#949 - reduce manual memory handing - 4.5.143 - merge gh#openSUSE/libstorage-ng#948 - fixed memory leak - more consistent function naming - 4.5.142 ==== mozjs115 ==== Version update (115.2.0 -> 115.2.1) - Update to version 115.2.1: + Security fix: CVE-2023-4863: Heap buffer overflow in libwebp. ==== open-vm-tools ==== Subpackages: libvmtools0 open-vm-tools-desktop - open-vm-tools is built with containerinfo plugin from 15 sp3 onwards ==== python-alembic ==== Version update (1.11.2 -> 1.12.0) - Clean up the SPEC file - update to 1.12.0 * Added new feature to the "code formatter" function which allows standalone executable tools to be run against code, without going through the Python interpreter. Known as the `exec` runner, it complements the existing `console_scripts` runner by allowing non-Python tools such as `ruff` to be used. * Change the default value of `.EnvironmentContext.configure.compare_type` to `True`. As Alembic's autogenerate for types was dramatically improved in version 1.4 released in 2020, the type comparison feature is now much more reliable so is now enabled by default. * Fixed issue where the `ForeignKeyConstraint.match` parameter would not be rendered in autogenerated migrations. * Fixed issue where the `revision_environment` directive in `alembic.ini` was ignored by the `alembic merge` command, leading to issues when other configurational elements depend upon `env.py` being invoked within the command. * Added support for `op.drop_constraint()` to support PostgreSQL `ExcludeConstraint` objects, as well as other constraint-like objects that may be present in third party dialects, by resolving the `type_` parameter to be `None` for this case. Autogenerate has also been enhanced to exclude the `type_` parameter from rendering within this command when `type_` is `None`. ==== tracker ==== Subpackages: libtracker-sparql-3_0-0 tracker-data-files tracker-lang typelib-1_0-Tracker-3_0 - use pkgconfig(icu-i18n) to use the current libicu. (jsc#PED-6193) ==== unar ==== - use pkgconfig(icu-uc) to use the current libicu. (jsc#PED-6193) ==== vsftpd ==== - Enable crypto-policies support: [bsc#1211301] * Add vsftpd-use-system-wide-crypto-policy.patch ==== yast2-schema ==== Version update (4.6.1 -> 5.0.1) - Added several LUKS-related elements to the partitioning schema (jsc#PED-3878, jsc#PED-5518). - 5.0.1 - 5.0.0 (#bsc1185510) ==== yast2-storage-ng ==== Version update (4.6.12 -> 5.0.1) - AutoYaST: official support for LUKS2 (jsc#PED-3878, jsc#PED-5518) - 5.0.1 - 5.0.0 (#bsc1185510) ==== yast2-users ==== Version update (4.6.4 -> 5.0.1) - Don't use obsolete method Dir.exists? (bsc#1215637) - 5.0.1 - 5.0.0 (#bsc1185510)

1 0

udisks2 2.10.x are crashing for SSP
by xtex 29 Sep '23

29 Sep '23

I found that the stack canary protector (stack smashing detector) is aborting udisksd from time to time. And plasmashell could not start udisks2 because of this, so the desktop could not start up. I ran `snapper undochange` to revert the last dist-update, then ran `zypper al udisks2` to lock udisks2. After another dist-update, I logged into plasma desktop successfully. Now the version is `cpe:/o:opensuse:tumbleweed:20230926`. There are two issues may be useful: - <https://github.com/storaged-project/udisks/issues/1152> - <https://github.com/storaged-project/udisks/issues/1193> It seems that libblockdev-3.0.3 will fix this problem? This is actually a reply to <Login issues after recent Tumbleweed update> but idk why my mail server is not delivering mails correctly, sry. Sep 29 09:41:54 xtex dbus-daemon[1007]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms) Sep 29 09:41:29 xtex systemd[1]: udisks2.service: Failed with result 'core- dump'. Sep 29 09:41:29 xtex systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Sep 29 09:41:29 xtex systemd-coredump[31217]: [🡕] Process 31210 (udisksd) of user 0 dumped core. Stack trace of thread 31210: #0 0x00007efe1ea91e0c __pthread_kill_implementation (libc.so.6 + 0x91e0c) #1 0x00007efe1ea3f0e6 __GI_raise (libc.so.6 + 0x3f0e6) #2 0x00007efe1ea268d7 __GI_abort (libc.so.6 + 0x268d7) #3 0x00007efe1ea277a3 __libc_message (libc.so.6 + 0x277a3) #4 0x00007efe1eb2785b __GI___fortify_fail (libc.so.6 + 0x12785b) #5 0x00007efe1eb28d36 __stack_chk_fail (libc.so.6 + 0x128d36) #6 0x00007efe1c00961c bd_nvme_get_sanitize_log (libbd_nvme.so.3 + 0x561c) .......................... Sep 29 09:41:29 xtex udisksd[15730]: *** stack smashing detected ***: terminated -- -- xtex

1 0

Login issues after recent Tumbleweed update
by Adrian Glaubitz 29 Sep '23

29 Sep '23

Hello! I have run into an issue where logging in or out on KDE can take quite long after one of the recent Tumbleweed updates. Also, during the last dist-upgrade, I've been getting dbus timeouts: Failed to activate service 'org.freedesktop.systemd1' Has anyone experienced similar issues? Thanks, Adrian

3 2

New Tumbleweed snapshot 20230926 released!
by Dominique Leuenberger 28 Sep '23

28 Sep '23

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: ImageMagick (7.1.1.15 -> 7.1.1.17) apache2-mod_php8 apparmor branding-openSUSE cairo (1.17.8 -> 1.18.0) distribution-logos-openSUSE (20220322 -> 20230921) drbd flashrom (1.2 -> 1.3.0) git gnome-control-center gnome-mahjongg (3.40.0 -> 3.40.0+35) gnustep-base graphite2 imlib2 (1.12.0 -> 1.12.1) libapparmor libdrm libguestfs libreoffice (7.6.1.1 -> 7.6.1.2) libsecret (0.21.0 -> 0.21.1) ovmf (202305 -> 202308) p11-kit (0.24.1 -> 0.25.0) php8 python-constantly python-tornado6 (6.3.2 -> 6.3.3) stoken (0.92 -> 0.93) swtpm (0.8.0 -> 0.8.1) systemd transactional-update (4.3.0 -> 4.4.0) tuned (2.20.0.18+git.7b1a20b -> 2.21.0.0+git.670541d) xdg-utils (1.1.3+20230830 -> 1.1.3+20230831) yast2-bootloader (4.6.2 -> 5.0.2) yast2-installation (4.6.7 -> 5.0.1) yast2-trans (84.87.20230913.43f962446c -> 84.87.20230922.91d997adab) === Details === ==== ImageMagick ==== Version update (7.1.1.15 -> 7.1.1.17) Subpackages: ImageMagick-config-7-SUSE ImageMagick-extra libMagickCore-7_Q16HDRI10 libMagickWand-7_Q16HDRI10 - version update to 7.1.1.17 * upstream changelog: https://github.com/ImageMagick/Website/blob/main/ChangeLog.md#711-17---2023… - modified patches % ImageMagick-library-installable-in-parallel.patch (refreshed) - follow upstream, create open, limited, secure and websafe alternative configuration packages with different policy.xml - removing p7zip redundant dependency ==== apache2-mod_php8 ==== - add missing references to rpm changelog - 15sp4 only: [bsc#1200772], [jsc#SLE-24723] add pecl, pear [jsc#SLE-23639] version update ==== apparmor ==== Subpackages: apparmor-abstractions apparmor-docs apparmor-parser apparmor-parser-lang apparmor-profiles apparmor-utils apparmor-utils-lang python3-apparmor - Fix pam_apparmor %post and %postun scripts to handle pam-config errors (bsc#1215596) ==== branding-openSUSE ==== Subpackages: grub2-branding-openSUSE libreoffice-branding-openSUSE plymouth-branding-openSUSE wallpaper-branding-openSUSE yast2-qt-branding-openSUSE - Enable grub2-branding on ppc64le. patterns-microos-base has Requires (grub2-branding-openSUSE if grub2). So we need the branding. ==== cairo ==== Version update (1.17.8 -> 1.18.0) Subpackages: libcairo-gobject2 libcairo-script-interpreter2 libcairo2 - Update to version 1.18.0: + The first stable cairo release in five years should be cause for celebration. + All the API added in the 1.17 development cycle is now considered stable, and will not change. + Many thanks to all the contributors for this release. + The cairo-sphinx tool has been removed; we could not find any instruction on how to use it, and no user answered our call for help. If you were using cairo-sphinx, please reach out to the cairo maintainers. + Cairo now implements Type 3 color fonts for PDF. + Multiple documentation fixes, to ensure that the cairo API reference is up to date. Also fixed multiple compiler warnings generated when building cairo. + The XML surface has been removed; it was disabled by default when building cairo, and we could not find any downstream distributor that would enable it. + The Tee surface is now automatically enabled. Downstream distributors of cairo have been enabling for years it in order to build Firefox. + Fixed multiple issues with the DWrite font backend. + Improved the Quartz surface; mainly, Quartz surfaces now use the main display ColorSpace, speeding up rendering operations. + Cairo now hides all private symbols by default on every platform; the old "slim" symbols hack to alias internally used symbols has been dropped, in favor of using `-Bsymbolic-functions` with toolchains that support it. + Fixed multiple memory leaks in the code base and test suite, and general maintenance. + Added new API to expose the Pixman dithering filter to cairo patterns; this is currently implemented only for image surfaces. - Drop patches fixed upstream: + cairo-1.17.8-fix-tee-compilation.patch + cairo-1.17.8-ft-font-missing-glyph.patch - Rebase patches with quilt. - Stop passing xml=disabled to meson setup, xml backend is dropped. ==== distribution-logos-openSUSE ==== Version update (20220322 -> 20230921) Subpackages: distribution-logos-openSUSE-Tumbleweed distribution-logos-openSUSE-icons - Add Aeon branding ==== drbd ==== - drbd: fix build error against kernel v6.5.4 (boo#1215699) * add upstream patch + 0001-drbd-allow-transports-to-take-additional-krefs-on-a-.patch + 0002-drbd-improve-decision-about-marking-a-failed-disk-Ou.patch + 0003-drbd-fix-error-path-in-drbd_get_listener.patch + 0004-drbd-build-fix-spurious-re-build-attempt-of-compat.p.patch + 0005-drbd-log-error-code-when-thread-fails-to-start.patch + 0006-drbd-log-numeric-value-of-drbd_state_rv-as-well-as-s.patch + 0007-drbd-stop-defining-__KERNEL_SYSCALLS__.patch + 0008-compat-block-introduce-holder-ops.patch + 0009-drbd-reduce-net_ee-not-empty-info-to-a-dynamic-debug.patch + 0010-drbd-do-not-send-P_CURRENT_UUID-to-DRBD-8-peer-when-.patch + 0011-compat-block-pass-a-gendisk-to-open.patch + 0012-drbd-Restore-DATA_CORKED-and-CONTROL_CORKED-bits.patch + 0013-drbd-remove-unused-extern-for-conn_try_outdate_peer.patch + 0014-drbd-include-source-of-state-change-in-log.patch + 0015-compat-block-use-the-holder-as-indication-for-exclus.patch + 0016-drbd-Fix-net-options-set-defaults-to-not-clear-the-t.patch + 0017-drbd-propagate-exposed-UUIDs-only-into-established-c.patch + 0018-drbd-rework-autopromote.patch + 0019-compat-block-remove-the-unused-mode-argument-to-rele.patch + 0020-drbd-do-not-allow-auto-demote-to-be-interrupted-by-s.patch * add suse special patch + bsc-1215699_fix-build-error-against-kernel-v6.5.4.patch ==== flashrom ==== Version update (1.2 -> 1.3.0) - Update to 1.3.0 - See changelog at https://www.flashrom.org/Flashrom/1.3 - Removed patches (merged upstream): - flashrom-install-man-file.patch - flashrom-j-link-spi.patch ==== git ==== Subpackages: git-core git-email git-svn git-web perl-Git - Downgrade openssh dependency to recommends (bsc#1215533) ==== gnome-control-center ==== Subpackages: gnome-control-center-color gnome-control-center-goa gnome-control-center-lang gnome-control-center-user-faces - Add gnome-control-center-add-user-button.patch: Show add user button when user is a normal user (bsc#1215556 glgo#GNOME/Settings!1927). ==== gnome-mahjongg ==== Version update (3.40.0 -> 3.40.0+35) Subpackages: gnome-mahjongg-lang - Update to version 3.40.0+35: + window: always show number of moves left + gnome-mahjongg: update 'moves left' on tile match and restart + game: Only create a single timer + User help: Correct dead IRC link + Updated translations. - Switch to service, git checkout of current head. ==== gnustep-base ==== - use pkgconfig(icu-uc) to use the current libicu. (jsc#PED-6193) ==== graphite2 ==== - fixed license string [bsc#1207676]: LGPL-2.1-or-later OR MPL-2.0 OR GPL-2.0-or-later ==== imlib2 ==== Version update (1.12.0 -> 1.12.1) Subpackages: imlib2-loaders libImlib2-1 - update to 1.12.1: * Fix some clang complaints * scaling: MMX asm scaling causes segv, disable for now * loading: Call module exit function also when not dlclosing module on unload * loaders: Fix build with -m32 --enable-debug * test_load_2: Add forgotten xeyes.png * test_save: Fix for jxl loader on ix86 * test_scale: MMX scaling is disabled * RAW loader: Don't unload loader * loaders: Fix CPPFLAGS order * imlib2_grab, imlib2_view: Unset context colormap * x11_grab: Use correct depth when grabbing ==== libapparmor ==== - Fix pam_apparmor %post and %postun scripts to handle pam-config errors (bsc#1215596) ==== libdrm ==== Subpackages: libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1 - provide/obsolete dropped packages libkms1/libkms-devel (bsc#1215526) - adjusted n_libdrm-drop-valgrind-dep-generic.patch, n_libdrm-drop-valgrind-dep-intel.patch to generated 2.4.116 pkgconfig files in order to fix build against sle15/Leap 15.x ==== libguestfs ==== Subpackages: libguestfs-appliance libguestfs-xfs libguestfs0 - bsc#1215543 - guestfs regression: file: Use -S option with -z Omit-file--S-option-on-older-distros-that-lack-support.patch See also bsc#1215461 - bsc#1215586 - guestfs regression: non functional network due to missing sysconfig-netconfig libguestfs.spec ==== libreoffice ==== Version update (7.6.1.1 -> 7.6.1.2) Subpackages: libreoffice-base libreoffice-calc libreoffice-draw libreoffice-filters-optional libreoffice-gnome libreoffice-gtk3 libreoffice-icon-themes libreoffice-impress libreoffice-l10n-cs libreoffice-l10n-da libreoffice-l10n-de libreoffice-l10n-el libreoffice-l10n-en libreoffice-l10n-en_GB libreoffice-l10n-es libreoffice-l10n-fr libreoffice-l10n-hu libreoffice-l10n-it libreoffice-l10n-ja libreoffice-l10n-pl libreoffice-l10n-pt_BR libreoffice-l10n-ru libreoffice-l10n-zh_CN libreoffice-l10n-zh_TW libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-qt5 libreoffice-writer libreofficekit - libreoffice-draw requires libreoffice-impress from 7.5 onwards, bsc#1215595 - Update to 7.6.1.2: https://wiki.documentfoundation.org/Releases/7.6.1/RC2 ==== libsecret ==== Version update (0.21.0 -> 0.21.1) Subpackages: libsecret-1-0 libsecret-lang typelib-1_0-Secret-1 - Update to version 0.21.1: + Fix updating credentials by another process in the same Flatpak sandbox. + Migrate to g_memdup2. + Updated translations. ==== ovmf ==== Version update (202305 -> 202308) Subpackages: qemu-ovmf-x86_64 - Update to edk2-stable202308 - Features (https://github.com/tianocore/edk2/releases): CryptoPkg: consume OpenSSL 3.0 Replace the OVMF-specific SataControllerDxe with the generic one in MdeModulePkg Remove the duplicated definitions from BaseTools Arm GIC Library and Driver improvements Use restricted memory mappings in PEI Add SmmCpuFeaturesLib implementation for AMD Processor family Add USB Network RNDIS Drivers Support Standalone MM based variable services in PEI on ARM systems Add RISC-V MMU support Add RISC-V support to CLANGDWARF toolchain - Patches (git log --oneline --date-order edk2-stable202305..edk2-stable202308): 819cfc6b42 OvmfPkg/RiscVVirt: Fix issues in VarStore Blockmap config 00b51e0d78 MdeModulePkg: HeapGuard: Don't Assume Pool Head Allocated In First Page 48089f3a7c OvmfPkg/Bhyve: build platform info HOB eaffa1d7ff UefiCpuPkg:Wake up APs after power-up or RESET through SIPI. 1d76560146 OvmfPkg: Disable PcdFirstTimeWakeUpAPsBySipi. 98e9d29e06 UefiCpuPkg: Add PcdFirstTimeWakeUpAPsBySipi 055c7bd1a7 UefiCpuPkg: Add SendStartupIpiAllExcludingSelf 991515a058 CryptoPkg: remove BN and EC accel for size optimization e91bfffd4f CryptoPkg/openssl: update CI config for openssl 3.0 46226fb5d3 CryptoPkg: remove strcmp to syscall c0aeb92663 CryptoPkg: run configure.py to update all generated files dfa6147a79 CryptoPkg: add more dummy implement of openssl for size optimization 2bead79cfc CryptoPkg: add implemention of _ftol2_sse() to avoid build error b2ff8e45db CryptoPkg: add define of maximum unsigned size_t 4b5faa5775 CryptoPkg: add missing gcc instructions 43e0ede26b CryptoPkg: Enable memcpy sys call in RISCV64 build f0d3e59754 CryptoPkg: Align with 4096 when build with OpensslFullAccel bdf3142eb7 CryptoPkg/TlsLib: use unsigned long for ErrorCode 20193b20b5 CryptoPkg: disable C4133 warning in openssl libraries bf1ff73c8c CryptoPkg: Add instrinsics to support building openssl3 on IA32 windows cea8e3b513 CryptoPkg: adapt 3.0 change in SslNull.c ea7a37d352 CryptoPkg: use UEFI provider as default 9b9b331e0f CryptoPkg: Move all UEFI implement of openssl to OpensslStub 5e1900f266 CryptoPkg/openssl: adapt EcSm2Null.c for openssl 3.0 174a306ccd CryptoPkg/openssl: store dummy update for openssl 3.0 3af00aec7f CryptoPkg/openssl: move compiler_flags to buildinf.c c638d1f672 CryptoPkg/openssl: adapt rand_pool.c to openssl 3.0 changes eac38f74c4 CryptoPkg/TlsLib: ERR_GET_FUNC is gone 2a6dc1211f CryptoPkg/BaseCryptLib: drop BIO_* dummy functions 63c8d160ae CryptoPkg/BaseCryptLib: adapt CryptSm3.c to openssl 3.0 changes. 84158d0ebe CryptoPkg/BaseCryptLib: no openssl deprecation warnings please ac492c3ead CryptoPkg/openssl: UefiAsm.conf update for openssl 3.0 81f5aa0700 CryptoPkg/openssl: add openssl3 configure scripts 7cede6d5f4 CryptoPkg/openssl: update Openssl*.inf files for openssl 3.0 49a113a7a4 CryptoPkg/openssl: cleanup all openssl1.1.1 generated files and code 9d6d237c3c CryptoPkg/openssl: update submodule to openssl-3.0.9 136931c4db MedPkg/Include: Add PCI_EXPRESS_EXTENDED_CAPABILITY_DVSEC_ID 3c274c0d83 MdePkg: Add new status codes to PrintLib 107ddf1de9 MdePkg: Add missing status codes 2d8c17a9b6 OvmfPkg/PlatformCI: Boot OVMF in SMP mode. bae848ee25 OvmfPkg/PlatformCI VS2019: Disable workaround for cpuhp bugfix 744c42bfd8 OvmfPkg/PlatformCI: Use recent Qemu on Windows 01ad4134c3 MdeModulePkg: Solve boot hang Xhci driver when use USB DVD with empty disk ef05145136 ArmPkg: DefaultExceptionHandlerLib: Do Not Allocate Memory 7672d1cca5 MdeModulePkg/SetupBrowser: Load storage via GetVariable for EfiVarStore fa789cc68a BaseTools: scan Edk2ToolsBuild.py make output 5cadb8ce21 BaseTools: BinToPcd: Resolve xdrlib deprecation d11968fcc5 MdeModulePkg/Bus/Ata/AtaAtapiPassThru: Fix UNUSED_VALUE Coverity issue c7c1170a45 MdeModulePkg/Bus/Ata/AtaAtapiPassThru: Fix SIGN_EXTENSION Coverity issue 677f2c6f15 OvmfPkg/RiscVVirt: Update README for CLANGDWARF support 3f49462558 BaseTools/tools_def: Add CLANGDWARF support for RISC-V 0f9fd06919 OvmfPkg/RiscVVirt: SecEntry: Remove unnecessary assembly directives 8543840cfd OvmfPkg/RiscVVirt: use 'auto' alignment and FIXED for XIP modules 70f3e62dc7 OvmfPkg/BhyvePkg: enable bus enumeration f284981506 Revert "OvmfPkg/Bhyve: remove IncompatiblePciDeviceSupport DXE driver" 1c923b9f25 Revert "OvmfPkg/Bhyve: consume PciHostBridgeLibScan" c7a7f09c1d UefiCpuPkg: Decouple the SEV-ES functionality. 25a6745fe8 RedfishPkg/RedfishDiscoverDxe: fix netmask check issue dcf05f958e MdePkg/Include/IndustryStandard: Remove VS20xx workaround 5309ddc83b EmulatorPkg/Win/Host: Fix RUNTIME_FUNCTION redefinition error 925c445fd3 OvmfPkg/RiscVVirt: Avoid printing hard coded timeout value 7427dd3fc0 OvmfPkg/RiscVVirt: Check "no-map" and mark EfiReservedMemoryType c6b512962e UnitTestFrameworkPkg: UnitTestPersistenceLib: Save Unit Test Cache Option b2de9ec5a7 CryptoPkg/OpensslLib: Upgrade OpenSSL to 1.1.1u 6510dcf6f7 NetworkPkg/HttpDxe: fix driver binding start issue. a52044a9e6 OvmfPkg/IoMmuDxe: add locking to IoMmuAllocateBounceBuffer 08aacbf056 OvmfPkg/CloudHv: update Maintainers.txt entry 4d1014093f UefiCpuPkg: Uses gMmst in MmSaveStateLib 39ded59c09 OvmfPkg/PeilessStartupLib: Updated with PcdSecureBootSupported 3399f64588 RedfishPkg/RedfishRestExDxe: reset session when TCP timeout happens dd49d448b0 MdeModulePkg/Bus/Pci/EhciDxe: Fix FORWARD_NULL Coverity issues f220dcbba8 UefiCpuPkg: RISC-V: Support MMU with SV39/48/57 mode cc13dcc576 OvmfPkg: RiscVVirt: Remove satp bare mode setting 33d0a3cc92 OvmfPkg/RiscVVirt: Add VirtNorFlashDxe to APRIORI list a8a72fc1ff OvmfPkg/RiscVVirt: SEC: Add IO memory resource hob for platform devices a9fc9bb466 OvmfPkg/RiscVVirt: VirtNorFlashPlatformLib: Fix wrong flash size fbec9aec00 MdePkg/Register: RISC-V: Add satp mode bits shift definition 7178047402 MdePkg/BaseLib: RISC-V: Support getting satp register value e674096acc OvmfPkg/ResetVector: Fix assembler bit test flag check ff3382a51c MdeModulePkg/Bus/Usb/UsbNetwork/UsbCdcNcm: Add USB Cdc NCM devices support 5e400d22a0 MdeModulePkg/Bus/Usb/UsbNetwork/UsbCdcEcm: Add USB Cdc ECM devices support fc0d5922f1 MdeModulePkg/Bus/Usb/UsbNetwork/UsbRndis: Add USB RNDIS devices support 8dab4eebe4 UefiPayloadPkg: Integrate UiApp and BootManagerMenuApp into MultiFv 964a4f032d UefiCpuPkg: Eliminate the second INIT-SIPI-SIPI sequence. 629c1dacc9 UefiCpuPkg: ApWakeupFunction directly use CpuMpData. 8bb018afaf UefiCpuPkg: Create MpHandOff. ... changelog too long, skipping 204 lines ... qemu-uefi-riscv64.bin ==== p11-kit ==== Version update (0.24.1 -> 0.25.0) Subpackages: libp11-kit0 libp11-kit0-32bit p11-kit-tools - Add d1d4b0ac316a27c739ff91e6c4153f1154e96e5a.patch: Fix probing of C_GetInterface. - Update to 0.25.0: * add PKCS#11 3.0 support * add support for profile objects * add ability to adjust module and config paths at run-time via system environmental exports * make terminal output nicer * p11-kit: add command to print merged configuration * p11-kit: add commands to list, add and delete profiles of a token * trust: add command to check format of .p11-kit files * virtual: fix libffi type signatures for PKCS#11 3.0 functions * server: fix umask setting when --group is specified * server: check SHELL only when neither --sh nor --csh is specified * rpc: use space string in C_InitToken * rpc: fix two off-by-one errors identified by asan * modules: make logging message more translatable * pkcs11.h: support CRYPTOKI_GNU for IBM vendor mechanisms * pkcs11.h: add IBM specific mechanism and attributes * pkcs11.h: add ChaCha20/Salsa20 and Poly1305 mechanisms * pkcs11.h: add AES-GCM mechanism parameters for message-based encryption * po: update translations from Transifex - Update upstream p11-kit.keyring file - Add missing lang files - Switch to using Meson as the build system ==== php8 ==== Subpackages: php8-cli php8-ctype php8-dom php8-gd php8-gettext php8-iconv php8-mbstring php8-mysql php8-openssl php8-pdo php8-sqlite php8-tokenizer php8-xmlreader php8-xmlwriter - add missing references to rpm changelog - 15sp4 only: [bsc#1200772], [jsc#SLE-24723] add pecl, pear [jsc#SLE-23639] version update ==== python-constantly ==== - Clean up the SPEC file - use unbundled versioneer to build package ==== python-tornado6 ==== Version update (6.3.2 -> 6.3.3) - Update to 6.3.3 * The Content-Length header and chunked Transfer-Encoding sizes are now parsed more strictly (according to the relevant RFCs) to avoid potential request-smuggling vulnerabilities when deployed behind certain proxies. - Add py312-datetime.patch to fix build with Python 3.12 ==== stoken ==== Version update (0.92 -> 0.93) - Version update to 0.93: * upstream moved to github * Drop support for versions of nettle older than 2014 * Further v4 token work * fixes in README * Add --both option to print current and next token * Support for v4 token decode * Remove bashisms (Alon Bar-Lev) ==== swtpm ==== Version update (0.8.0 -> 0.8.1) Subpackages: swtpm-selinux - Update to version 0.8.1: - swtpm: - Restore logging to stderr on log open failure - swtpm_setup: - Exit with '0' upon --version rather than '1'. - Initialized @argv in get_swtpm_capabilities() - swtpm_localca: - Add missing NULL option to end of array - SELinux: - Add rules for user_tpm_t:sockfile to allow unlink - Add rules for sock_file on user_tmp_t ==== systemd ==== Subpackages: libsystemd0 libsystemd0-32bit libudev1 systemd-32bit systemd-container systemd-coredump systemd-lang udev - systemd.spec: during package updates, restart localed, timedated and hostnamed if they're running. - systemd.spec: when enabling units prefer enabling service units over socket ones for socket activable services. The services shipped by systemd automatically redirect the enablement request to the socket unit. ==== transactional-update ==== Version update (4.3.0 -> 4.4.0) Subpackages: dracut-transactional-update libtukit4 transactional-update-zypp-config tukit tukitd - Version 4.4.0 - t-u: Introduce setup-fips command [jsc#SMO-194] - libtukit: Always set a cleanup algorithm for snapshots - when using API, D-Bus interface or tukit the snapshots will be automatically cleaned up by snapper after some time now; in the past only snapshots created by the transactional-update shell script would be cleanup after, and only after a `t-u cleanup` run. - tukit: enable kexec's syscall detection feature - tukit: Don't throw exceptions from the child process after fork - tukitd: Rename service file to org.opensuse.tukit.service - tukitd: Allow querying DBus Properties [boo#1214707] - t-u: Add support for fully written-out update commands - t-u: Improve detection of existing kernel parameters ==== tuned ==== Version update (2.20.0.18+git.7b1a20b -> 2.21.0.0+git.670541d) - Update to version 2.21.0.0+git.670541d: * new release (2.21.0) * api: fixed stop method not to require any parameter * new release (2.21.0-rc.1) * gui: multiple fixes and warnings removal * gui: fixed inconsistent tabs and spaces, introduced by #516 * Serialize SIGHUP processing * No errors when physical_package_id file does not exist * Update tests: disable systemd rate limiting. * network-latency: enable rcu_normal_after_boot=1 kernel parameter * remove ktimer_lockless_check sysfs setting from realtime-virtual profiles * move rtentsk to network-latency profile * move "tsc=reliable" setting from realtime to network-latency tuned configuration * unify common sysctl settings between realtime and cpu-partitioning profiles * Rename rollback-related constants and variables * Add rollback option to tuned-main.conf * Recast README into MarkDown with various minor corrections and improvements * Remove setting ip forwarding via openshift profile * Fix logging in [scheduler] plug-in * fixed sap-hana docu regarding processor power settings * Added sap-hana-kvm-guest profile * tests/beakerlib: Add new test which covers socket API. * plugin_net: expand variables properly * fix typo * add error dialog when no active profile set ==== xdg-utils ==== Version update (1.1.3+20230830 -> 1.1.3+20230831) - Update to version 1.1.3+20230831: * Revert putting process in background from !55 - revert _service to the original state - revert drop of xdg-terminal-don-t-run-kreadconfig-if-KDE_SESSION_VE.patch (bsc#1215384) ==== yast2-bootloader ==== Version update (4.6.2 -> 5.0.2) - Fixed testsuite for architectures other than x86_64. - 5.0.2 - Supporting systemd-boot for architecture x86_64. This feature can be enabled/disabled by the "enable_systemd_boot" flag in the product description file for each product (default is disabled). - 5.0.1 - 5.0.0 (#bsc1185510) - support 32 bit UEFI firmware on x86_64/i386 architecture (bsc#1208003, jsc#PED-2569) - 4.6.3 ==== yast2-installation ==== Version update (4.6.7 -> 5.0.1) - Adapt code for changes in yast2-bootloader done for systemd-boot experimental support (jsc#PED-1906) - 5.0.1 - 5.0.0 (#bsc1185510) ==== yast2-trans ==== Version update (84.87.20230913.43f962446c -> 84.87.20230922.91d997adab) Subpackages: yast2-trans-af yast2-trans-ar yast2-trans-bg yast2-trans-bn yast2-trans-bs yast2-trans-ca yast2-trans-cs yast2-trans-cy yast2-trans-da yast2-trans-de yast2-trans-el yast2-trans-en_GB yast2-trans-es yast2-trans-et yast2-trans-fa yast2-trans-fi yast2-trans-fr yast2-trans-gl yast2-trans-gu yast2-trans-hi yast2-trans-hr yast2-trans-hu yast2-trans-id yast2-trans-it yast2-trans-ja yast2-trans-jv yast2-trans-ka yast2-trans-km yast2-trans-ko yast2-trans-lo yast2-trans-lt yast2-trans-mk yast2-trans-mr yast2-trans-nb yast2-trans-nl yast2-trans-pa yast2-trans-pl yast2-trans-pt yast2-trans-pt_BR yast2-trans-ro yast2-trans-ru yast2-trans-si yast2-trans-sk yast2-trans-sr yast2-trans-sv yast2-trans-tr yast2-trans-uk yast2-trans-vi yast2-trans-wa yast2-trans-xh yast2-trans-zh_CN yast2-trans-zh_TW yast2-trans-zu - Update to version 84.87.20230922.91d997adab: * New POT for text domain 'packager'. * New POT for text domain 'iscsi-client'.

1 0

User session closed after screen blank+locked (TW 20230925)
by Andreas Herrmann 28 Sep '23

28 Sep '23

Hi, I've observed an odd problem today (at least thrice) so far. When after a while my screen is locked, and I try to log back in, my entire session is lost. Restarting stuff is complicated due to weired networking/socket(?) issues. E.g. mutt complains with a "not seen before message" and won't start. Thus I have to reboot and start over again. This is "openSUSE Tumbleweed 20230925". Did others observe similar issues? Thanks. -- Regards, Andreas SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nürnberg, Germany GF: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

3 3