Fedora Account System
Red Hat Associate
Red Hat Customer
Package NetworkManager-openvpn-1.12.5-1.fc43 installs two conflicting files in /usr/lib/sysusers.d/, namely networkmanager-openvpn.conf contents: u nm-openvpn - 'Default user for running openvpn spawned by NetworkManager' - - and nm-openvpn-sysusers.conf contents: u! nm-openvpn - "NetworkManager OpenVPN" /var/lib/openvpn/chroot The first one (networkmanager-openvpn.conf) comes from NetworkManager-openvpn-1.12.3-1.fc43. The second was added because it was created upstream (see https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/blob/main/nm-openvpn-sysusers.conf.in?ref_type=heads). This is evidenced by the update process, where you get the output >>> Running %triggerin scriptlet: systemd-0:258.3-2.fc43.x86_64 >>> Finished %triggerin scriptlet: systemd-0:258.3-2.fc43.x86_64 >>> Scriptlet output: >>> /usr/lib/sysusers.d/nm-openvpn-sysusers.conf:1: Conflict with earlier configuration for user 'nm-openvpn' in /usr/lib/sysusers.d/networkmanager-openvpn.conf:1, ignoring line. Reproducible: Always Steps to Reproduce: 1. Install NetworkManager-openvpn-1.12.5-1.fc43 2. Observe the warning message Actual Results: Warning message Expected Results: No warning messages Additional Information: One of the files should be removed from the installation package. Possibly a 'u!' (locked user) should be used instead of the plain 'u' user.
Same issue here when doing dnf update. So, just use upstream's sysusers conf. here's the patch. ``` diff --git a/NetworkManager-openvpn.spec b/NetworkManager-openvpn.spec index 56c3b13..17528a2 100644 --- a/NetworkManager-openvpn.spec +++ b/NetworkManager-openvpn.spec @@ -8,7 +8,7 @@ Summary: NetworkManager VPN plugin for OpenVPN Name: NetworkManager-openvpn Epoch: 1 Version: 1.12.5 -Release: 1%{?dist} +Release: 2%{?dist} License: GPL-2.0-or-later URL: http://www.gnome.org/projects/NetworkManager/ @@ -58,12 +58,6 @@ the OpenVPN server with NetworkManager (GNOME files). %prep %autosetup -p1 -# Create a sysusers.d config file -cat >networkmanager-openvpn.sysusers.conf <<EOF -u nm-openvpn - 'Default user for running openvpn spawned by NetworkManager' - - -EOF - - %build if [ ! -f configure ]; then ./autogen.sh @@ -84,7 +78,6 @@ make check %install make install DESTDIR=%{buildroot} INSTALL="%{__install} -p" -install -m0644 -D networkmanager-openvpn.sysusers.conf %{buildroot}%{_sysusersdir}/networkmanager-openvpn.conf rm -f %{buildroot}%{_libdir}/NetworkManager/lib*.la @@ -94,13 +87,12 @@ rm -f %{buildroot}%{_libdir}/NetworkManager/lib*.la %{_libdir}/NetworkManager/libnm-vpn-plugin-openvpn.so %{_datadir}/dbus-1/system.d/nm-openvpn-service.conf %{_prefix}/lib/NetworkManager/VPN/nm-openvpn-service.name -%{_prefix}/lib/sysusers.d/nm-openvpn-sysusers.conf -%{_prefix}/lib/tmpfiles.d/nm-openvpn-tmpfiles.conf +%{_sysusersdir}/nm-openvpn-sysusers.conf +%{_tmpfilesdir}/nm-openvpn-tmpfiles.conf %{_libexecdir}/nm-openvpn-service %{_libexecdir}/nm-openvpn-service-openvpn-helper %doc AUTHORS README %license COPYING -%{_sysusersdir}/networkmanager-openvpn.conf %files -n NetworkManager-openvpn-gnome ``` It seems packit doesn't work well with previous manual steps. :(
After the NetworkManager-openvpn package is installed. This conf file conflict is announced for other packages. I did a `dnf upgrade` this morning, and I received this same conflict announcement when upgrading to setroubleshoot-server-0:3.3.36-2.fc43.x86_64 and tcpdump-14:4.99.6-1.fc43.x86_64. Here's a snippet from my latest dnf log: 2026-01-07T17:27:37+0000 [4471] INFO RPM callback open file "/var/cache/libdnf5/updates-431245df5652aba0/packages/setroubleshoot-server-3.3.36-2.fc43.x86_64.rpm" 2026-01-07T17:27:37+0000 [4471] INFO RPM callback start sysusers scriptlet "setroubleshoot-server-0:3.3.36-2.fc43.x86_64" 2026-01-07T17:27:38+0000 [4471] INFO [scriptlet] /usr/lib/sysusers.d/nm-openvpn-sysusers.conf:1: Conflict with earlier configuration for user 'nm-openvpn' in /usr/lib/sysusers.d/networkmanager-openvpn.conf:1, ignoring line. 2026-01-07T17:27:38+0000 [4471] INFO RPM callback stop sysusers scriptlet "setroubleshoot-server-0:3.3.36-2.fc43.x86_64" return code 0 2026-01-07T17:27:38+0000 [4471] INFO RPM callback install start "setroubleshoot-server-0:3.3.36-2.fc43.x86_64" total 1543376 2026-01-07T17:27:38+0000 [4471] INFO RPM callback install stop "setroubleshoot-server-0:3.3.36-2.fc43.x86_64" amount 1543376 total 1543376
*** Bug 2426921 has been marked as a duplicate of this bug. ***
When downgraded to 1:1.12.3-1.fc43 further reinstalls don't generate scriptlet output, therefore I assume this was introduced with 1:1.12.5-1.fc43.
This happens directly after installation from live 1.6 and running dnf up
*** Bug 2428543 has been marked as a duplicate of this bug. ***
With version 1.2.25 upstream has its own sysusers file. The problem is with the following commit: https://src.fedoraproject.org/rpms/NetworkManager-openvpn/c/14848a3693eaa15dcf2b04fe84d7ecf54e8b6cc8?branch=rawhide (Update to 1.12.5 upstream release) Which also adds the following line: %{_prefix}/lib/sysusers.d/nm-openvpn-sysusers.conf and this without removing the pre-existing generation and installation of another sysusers file from the following commit: https://src.fedoraproject.org/rpms/NetworkManager-openvpn/c/bd1f1f439bb842aa92390f784f5772a2cb4491f3?branch=rawhide (Add sysusers.d config file to allow rpm to create users/groups automatically) Stop generate and install that file (networkmanager-openvpn.sysusers.conf), and this bug will be solved.
I can reproduce this on Fedora Rawhide (fc44). During `dnf upgrade --refresh` I consistently get: /usr/lib/sysusers.d/nm-openvpn-sysusers.conf:1: Conflict with earlier configuration for user 'nm-openvpn' in /usr/lib/sysusers.d/networkmanager-openvpn.conf:1, ignoring line. Versions: NetworkManager-openvpn-1.12.5-1.fc44.x86_64 systemd-259-1.fc44.x86_64 rpm-6.0.1-1.fc44.x86_64 libdnf5-5.3.0.0-4.fc44.x86_64 dnf5-5.3.0.0-4.fc44.x86_64 Both sysusers files are owned by the same package: $ rpm -qf /usr/lib/sysusers.d/networkmanager-openvpn.conf /usr/lib/sysusers.d/nm-openvpn-sysusers.conf NetworkManager-openvpn-1.12.5-1.fc44.x86_64 NetworkManager-openvpn-1.12.5-1.fc44.x86_64 File contents: $ sed -n '1,80p' /usr/lib/sysusers.d/networkmanager-openvpn.conf u nm-openvpn - 'Default user for running openvpn spawned by NetworkManager' - - $ sed -n '1,80p' /usr/lib/sysusers.d/nm-openvpn-sysusers.conf u! nm-openvpn - "NetworkManager OpenVPN" /var/lib/openvpn/chroot It looks like the package ships two sysusers definitions for the same user; dropping one of them (preferably keep the upstream one) would avoid the warning.
FEDORA-2026-3dbe33d912 (NetworkManager-openvpn-1.12.5-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-3dbe33d912
FEDORA-2026-2e8747340c (NetworkManager-openvpn-1.12.5-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-2e8747340c
FEDORA-2026-3dbe33d912 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3dbe33d912` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3dbe33d912 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-2e8747340c has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2e8747340c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2e8747340c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-2e8747340c (NetworkManager-openvpn-1.12.5-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-3dbe33d912 (NetworkManager-openvpn-1.12.5-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.