users November 2024

users@lists.fedoraproject.org

82 participants
96 discussions

Fedora 41 - Postgresql Problem
by Max Pyziur 01 Nov '24

01 Nov '24

Greetings, I have three machines running Fedora, one just completed the update. Generally, no problems updating. But I noticed there was deprecation of postgresql, and when I went to review/work on one of my databases via cli I received the following message: pyz@pegasus ~> psql commodities WARNING: database "commodities" has a collation version mismatch DETAIL: The database was created using collation version 2.39, but the operating system provides version 2.40. HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE commodities REFRESH COLLATION VERSION, or build PostgreSQL with the right library version. psql (16.3) Type "help" for help. commodities=# Generally in the past when there has been a major upgrade, then the procedure was to rebuild databases from backup. In this case, the issue seems to be a bit more nuanced. Any and all suggestions on how to proceed are welcome. Thank you, Max pyz(a)brama.com mailto:pyz@brama.com

2 3

Strange DNF5 Functionality
by Stephen Morris 01 Nov '24

01 Nov '24

Hi, With the upgrade to DNF5, when I issue sudo dnf upgrade, for all package upgrades it lists the package that is being replaced and lists the repository as being <unknown>, why is it specifying anything for the repository of the installed package? regards, Steve

3 2

Post Fedora 41 upgrade - sshd problem
by Max Pyziur 01 Nov '24

01 Nov '24

Greetings again, Post-upgrade and using ssh to access other machines via ssh I get the following error: pyz@Gryphon ~> ssh brill -v OpenSSH_9.8p1, OpenSSL 3.2.2 4 Jun 2024 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf debug1: Reading configuration data /etc/ssh/ssh_config.d/50-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config /etc/ssh/ssh_config line 57: Bad key types 'ssh-rsa,ssh-dss,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519'. /etc/ssh/ssh_config line 58: Bad key types 'ssh-rsa,ssh-dss,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519'. /etc/ssh/ssh_config: terminating, 2 bad configuration options I know that this is an occasional occurrence post upgrade. Thank you for any and all advice. Max pyz(a)brama.com

5 6

Podman 5.3 Test Day 2024-11-01 through 2024-11-08
by Sumantro Mukherjee 01 Nov '24

01 Nov '24

Hey Folks! We will be testing Fedora 41 with the new update in Podman 5.3. To ensure a smooth transition, the Podman team and the Quality team of Fedora have decided to host a test day[1]. The idea is for users to test Podman 5.3 on a Fedora 41 machine and submit results in the Test Day App[2]. If you have spare cycles or use Podman as a daily driver, it will be great to have some folks try out and report bugs right away. We will want more Karmas on[3] and any following builds for Podman 5.3 [1] http://fedoraproject.org/wiki/Test_Day:2024-11-01_Podman_5.3 [2] https://testdays.fedoraproject.org/events/203 [3] https://bodhi.fedoraproject.org/updates/FEDORA-2024-50c8b12d3c -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

systemd-sysusers problem
by ToddAndMargo 01 Nov '24

01 Nov '24

Hi All, Fedora 39 Which should I have? systemd-standalone-sysusers or systemd? # dnf install systemd-standalone-sysusers --allowerasing Last metadata expiration check: 0:14:46 ago on Tue 29 Oct 2024 01:43:41 PM PDT. Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: systemd-standalone-sysusers x86_64 254.19-1.fc39 updates 139 k Downgrading: systemd x86_64 254.5-2.fc39 fedora 4.7 M systemd-container x86_64 254.5-2.fc39 fedora 568 k systemd-libs i686 254.5-2.fc39 fedora 729 k systemd-libs x86_64 254.5-2.fc39 fedora 689 k systemd-networkd x86_64 254.5-2.fc39 fedora 649 k systemd-pam x86_64 254.5-2.fc39 fedora 363 k systemd-resolved x86_64 254.5-2.fc39 fedora 295 k systemd-rpm-macros noarch 254.5-2.fc39 fedora 31 k systemd-udev x86_64 254.5-2.fc39 fedora 2.1 M Transaction Summary ================================================================================ Install 1 Package Downgrade 9 Packages Total download size: 10 M Is this ok [y/N]: y Downloading Packages: (1/10): systemd-container-254.5-2.fc39.x86_64.r 245 kB/s | 568 kB 00:02 (2/10): systemd-libs-254.5-2.fc39.i686.rpm 271 kB/s | 729 kB 00:02 (3/10): systemd-libs-254.5-2.fc39.x86_64.rpm 268 kB/s | 689 kB 00:02 (4/10): systemd-networkd-254.5-2.fc39.x86_64.rp 248 kB/s | 649 kB 00:02 (5/10): systemd-pam-254.5-2.fc39.x86_64.rpm 262 kB/s | 363 kB 00:01 (6/10): systemd-rpm-macros-254.5-2.fc39.noarch. 117 kB/s | 31 kB 00:00 (7/10): systemd-resolved-254.5-2.fc39.x86_64.rp 238 kB/s | 295 kB 00:01 (8/10): systemd-254.5-2.fc39.x86_64.rpm 512 kB/s | 4.7 MB 00:09 (9/10): systemd-udev-254.5-2.fc39.x86_64.rpm 517 kB/s | 2.1 MB 00:04 (10/10): systemd-standalone-sysusers-254.19-1.f 28 kB/s | 139 kB 00:05 -------------------------------------------------------------------------------- Total 836 kB/s | 10 MB 00:12 Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction test error: file /usr/bin/systemd-sysusers conflicts between attempted installs of systemd-standalone-sysusers-254.19-1.fc39.x86_64 and systemd-254.5-2.fc39.x86_64

1 2

systemd-sysusers start fails
by ToddAndMargo 01 Nov '24

01 Nov '24

Hi All, Fedora 39 systemd-254.19-1.fc39.x86_64 (provides systemd-sysusers) I can not get lightdm to start Xfc or MATE. After entering my password into the greeter, I get a black screen with a mouse pointer, then back to the greeter. When I start lighdm, it see Failed to start systemd-sysuses.service So I need to fix that before going further with lightdm troubleshooting. From my working FC41 virtual machine (Xfce, MATE, lightdm), as a base line in troubleshooting, this is what it is support to look like: $ systemctl status systemd-sysusers ○ systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) since Tue 2024-10-29 15:16:01 PDT; 18min ago Duration: 1.152s Invocation: ca24eb4ee687400ca481db82053345c2 Condition: start condition unmet at Tue 2024-10-29 15:16:03 PDT; 18min ago ├─ ConditionNeedsUpdate=|/etc was not met └─ ConditionCredential=|sysusers.extra was not met Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) Main PID: 285 (code=exited, status=0/SUCCESS) $ systemctl list-dependencies systemd-sysusers systemd-sysusers.service ● └─system.slice This is what I get with FC39: # systemctl start systemd-sysusers <nothing> # systemctl status systemd-sysusers × systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: failed (Result: exit-code) since Tue 2024-10-29 13:44:43 PDT; 3h 16min> Condition: start condition unmet at Tue 2024-10-29 13:55:45 PDT; 3h 5min ago ├─ ConditionNeedsUpdate=|/etc was not met └─ ConditionCredential=|sysusers.extra was not met Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) Main PID: 292 (code=exited, status=1/FAILURE) CPU: 7ms Oct 29 13:45:00 rn6.foobar.local systemd[1]: systemd-sysusers.service - Create> Oct 29 13:45:01 rn6.foobar.local systemd[1]: systemd-sysusers.service - Create> Oct 29 13:55:45 rn6.foobar.local systemd[1]: systemd-sysusers.service - Create> Notice: journal has been rotated since unit was started, output may be incomplete. $ systemctl list-dependencies systemd-sysusers systemd-sysusers.service ● └─system.slice # systemctl status system.slice ● system.slice - System Slice Loaded: loaded Active: active since Tue 2024-10-29 13:44:43 PDT; 3h 32min ago A tail on starting the service: # journalctl -efx -t systemd Oct 29 17:20:19 rn6.foobar.local systemd[1]: systemd-sysusers.service - Create System Users was skipped because no trigger condition checks were met. Subject: A start job for unit systemd-sysusers.service has finished successfully Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit systemd-sysusers.service has finished successfully. The job identifier is 9388. Oct 29 17:20:20 rn6.foobar.local systemd[2843]: Started dbus-:1.2-org.xfce.Xfconf@5.service. Subject: A start job for unit UNIT has finished successfully Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit UNIT has finished successfully. Hmmm successful. Ha! Main PID: 292 (code=exited, status=1/FAILURE) How do I fix this? -T

1 1