October 2023 - openSUSE Factory - openSUSE Mailing Lists

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

Glibc Dynamic Loader Hit By A Nasty Local Privilege Escalation Vulnerability
by Adam Mizerski 04 Oct '23

04 Oct '23

Quoting from https://www.phoronix.com/news/Glibc-LD-Nasty-Root-Bug > A nasty vulnerability has been made public today concerning Glibc's > dynamic loader that can lead to full root privileges being obtained by > local users. This affects Linux distributions of the past two years > with the likes of Ubuntu 22.04 LTS, 23.04, Fedora 38, and others > vulnerable to this local privilege escalation issue.

2 1

Re: TW snapshot 20230901: grub2-2.12 not really ready?
by Patrick Schaaf 04 Oct '23

04 Oct '23

Hi folks, following up on previous thread, just want to share a personal observation. On one of my private little servers, I updated to snapshot 20231001 today (been a while that I updated before). That brought in grub 2.12~rc1, and the update resulted in an unbootable system, as reported before by others, dropping me to the grub rescue prompt. I could fix the situation by (network) rescue booting + re-running grub2-install on /dev/sda + /dev/sdb. Most likely cause (guessing), is my peculiar drive setup - just sharing for information, I'm not complaining that it didn't work magically! * two SSDs /dev/sda + /dev/sdb * gpt partitioning * the usual grub BIOS partition on both drives * rest of the drive a second partition * these large partitions, run as software RAID1 * and on top of that, LVM with a logical root volume and no separate boot Again, not complaining, just want to share info + maybe help someone who runs into something similar. best regards Patrick

1 0

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 kocelfc＠tutanota.com 03 Oct '23

03 Oct '23

Is there an issue somewhere which can be tracked?

2 1

why does zypper marks a package "obsolete" even with higher version number ...
by André Verwijs 03 Oct '23

03 Oct '23

at the bottom, why does zypper marks a package "obsolete" even with higher version number ... true: "epson-inkjet-printer-escpr-1.8.0-1.x86_64¨ is installed manually (downloaded package) how does zypper deal with package version numbers?? verwijs-leap:~ # zypper dup Repository 'Insync Fedora 27' is up to date. Retrieving repository '.NET/Mono based Software (openSUSE_Tumbleweed)' metadata ...................................[done] Building repository '.NET/Mono based Software (openSUSE_Tumbleweed)' cache ........................................[done] Repository 'MySQL 8.0 Community Server' is up to date. Repository 'MySQL 8.0 Community Server Debug' is up to date. Repository 'MySQL Connectors Community' is up to date. Repository 'MySQL Connectors Community Debug' is up to date. Repository 'MySQL Tools Community' is up to date. Repository 'MySQL Tools Community Debug' is up to date. Repository 'MySQL Tools Community preview' is up to date. Retrieving repository 'The Mono Project (openSUSE_Factory)' metadata ..............................................[done] Building repository 'The Mono Project (openSUSE_Factory)' cache ...................................................[done] Repository 'nVidia Graphics Drivers Tumbleweed' is up to date. Repository 'MariaDB 11.2 (sles 12)' is up to date. Repository 'MariaDB 11.2 (sles 15)' is up to date. Repository 'openSUSE-Leap-15.6-1' is up to date. Repository 'repo-non-oss (15.6)' is up to date. Repository 'repo-openh264 (15.6)' is up to date. Repository 'repo-oss (15.6)' is up to date. Repository 'update-backports (15.6)' is up to date. Repository 'update-backports-debug (15.6)' is up to date. Repository 'update-non-oss (15.6)' is up to date. Repository 'update-oss (15.6)' is up to date. Repository 'update-sle (15.6)' is up to date. Repository 'update-sle-debug (15.6)' is up to date. Repository 'packages-microsoft-com-prod' is up to date. Repository 'Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports' is up to date. Repository 'Update repository of openSUSE Backports' is up to date. Repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' is up to date. Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up to date. All repositories have been refreshed. Refreshing service 'openSUSE'. Loading repository data... Warning: Repository 'update-backports (15.6)' metadata expired since 2023-09-29 11:08:32 CEST. Warning: Repository 'update-backports-debug (15.6)' metadata expired since 2023-09-29 11:08:33 CEST. Warning: Repository 'update-non-oss (15.6)' metadata expired since 2023-09-21 14:47:58 CEST. Warning: Repository 'Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports' metadata expired since 2023-09-29 11:08:33 CEST. Warning: Repository 'Update repository of openSUSE Backports' metadata expired since 2023-09-29 11:08:32 CEST. Warning:Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manualy refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Problem: problem with the installed epson-inkjet-printer-escpr-1.8.0-1.x86_64 Solution 1: install epson-inkjet-printer-escpr-1.7.22-bp156.2.2.x86_64 from vendor openSUSE replacing epson-inkjet-printer-escpr-1.8.0-1.x86_64 from vendor Seiko Epson Corporation Solution 2: keep obsolete epson-inkjet-printer-escpr-1.8.0-1.x86_64 Choose from above solutions by number or cancel [1/2/c/d/?] (c):

4 3

RE: why does zypper marks a package "obsolete" even with higher version number ...
by André Verwijs 03 Oct '23

03 Oct '23

oops..!! forgot to share system information: Operating System: openSUSE Leap 15.6 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.19-default (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Core™2 CPU 6700 @ 2.66GHz Memory: 5.7 GiB of RAM Graphics Processor: GeForce GT 610/PCIe/SSE2

1 0

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

[opensuse-factory] Slowroll version bump 20231001
by Bernhard M. Wiedemann 03 Oct '23

03 Oct '23

Hi, the last (and first) Slowroll base snapshot from Tumbleweed was 20230822 The next one should be 20231001 if it passes openQA. Why? We need to catch up with major version bumps to not diverge too much from Tumbleweed. E.g. there are no kernel updates anymore in the 6.4.x series and we do not even have the latest 6.4.16 from upstream but .12 there. https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed… illustrates the concept of these bumps So far we have 1156 pkg updates not released 1423 pkg updates released So we did not stand still either and usually got the most important (security) fixes 1-2 days after Tumbleweed. I guess, with more elaborate event-based coding and smaller staging projects, we could get that down to a few hours. Ciao Bernhard M.

2 3