ok, one more update. Now the actual release.

The release candidates fared well, so this will probably not cause problems.

there is a new release candidate.

Abort the testing of the 1.38-rc2 and start again with 1.38-rc3. Sorry about that.

This one brings an intentional change in behavior, w.r.t. the order in which IPv6 addresses are configured. That can affect source address selection for IPv6, but the new behavior is deemed preferable.

This update has been unpushed.

I worry, there is a bug in this release:

A revert of the patch currently fails to build: . Will investigate tomorrow.

Sorry for any inconvenience.

@jakub, it seams, this breaks build with LTO. Here:


checking if gcc supports flag -fno-strict-aliasing in envvar CFLAGS... yes
checking if gcc supports flag -flto -flto-partition=none in envvar CFLAGS... no
configure: error: Link Time Optimization -flto is not supported.
error: Bad exit status from /var/tmp/rpm-tmp.Uwjyx0 (%build)
    Bad exit status from /var/tmp/rpm-tmp.Uwjyx0 (%build)

Adam apparently changed the used domain (from domain.local), which avoids the test failure. While I don't understand what the problem is, I'd like to re-open this update and hopefully get it through.

This update has been unpushed.

That is still under investigation, sorry. But clearly, this update should be retired...

@adamwill it is probably related to the changes how NetworkManager configures systemd-resolved. Is it possible to add some printf debugging statements before the failure? In particular resolvectl ; nmcli device ; ip addr ; ip route.

Btw, yesterday we also released 1.28.0 which is now in rawhide (package "1.28.0-1"). That might have exactly the same problem. Does it?

Thank you for having extensive CI tests! That is awesome!!

@decathorpe I think this is fine as a zero-day update, or even later. Since this is an unusually large change, I would give it plenty time in testing. No rush.

@andilinux, thank you for the feedback!! It is however not clear to me what's wrong here. It would be great, if you could provide more information by opening a bugzilla or an email to the upstream mailing list (

@pbrobinson: that would be a surprise, because the difference between (previous) 1.10.8 and new 1.10.10 is very small. Also, there is not enough information to identify the issue. Consider opening a bug. Thank you!!

@bluepencil, there is not enough information to figure out why it crashes for you. Consider opening a bug and providing a backtrace. Also, install NetworkManager-debuginfo package.

This update has been unpushed.

It's unclear what exactly means "Cannot save password and private key. Show passwords is not working.". Does 1.8.0-2 fix the issue?