https://bugs.kde.org/show_bug.cgi?id=517317
Bug ID: 517317
Summary: Editing bridge autoconnect in KDE resets
NetworkManager connection.autoconnect-ports
Classification: Plasma
Product: plasmashell
Version First 6.6.2
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Networking in general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
SUMMARY
When editing a NetworkManager bridge connection in the KDE network settings UI,
disabling normal "Automatically connect" also resets the bridge-specific
NetworkManager setting `connection.autoconnect-ports` (and
`connection.autoconnect-slaves`) back to the default value `-1`.
This breaks manual activation of the bridge in my setup. The bridge profile can
still be brought up manually with `nmcli`, but only if
`connection.autoconnect-ports` remains set to `1`.
STEPS TO REPRODUCE
1. Create a NetworkManager bridge profile and set
`connection.autoconnect-ports` to `1`.
2. Verify in CLI that the bridge profile shows:
- `connection.autoconnect: yes`
- `connection.autoconnect-ports: 1`
3. Open the KDE network settings UI for that bridge connection.
4. Disable normal "Automatically connect" in the UI and save the profile.
5. Check the profile again with `nmcli connection show <bridge-name>`.
OBSERVED RESULT
The KDE UI changes not only `connection.autoconnect`, but also resets:
- `connection.autoconnect-ports` from `1` to `-1 (default)`
- `connection.autoconnect-slaves` from `1` to `-1 (default)`
As a result, manual activation of the bridge no longer behaves correctly (the
bridged interface stays down, no DHCP/no connection to the uplink network)
until I restore the setting manually with:
`nmcli connection modify <bridge-name> connection.autoconnect-ports 1`
EXPECTED RESULT
Changing the normal bridge autoconnect setting in the KDE UI should not
silently reset bridge-port autoconnect behavior.
If the UI does not expose `connection.autoconnect-ports`, it should at least
preserve the existing value instead of overwriting it with the default.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: CachyOS (Arch-based)
KDE Plasma Version: 6.6.2
KDE Frameworks Version: unknown
Qt Version: 6.10.2
plasma-nm Version: 6.6.2-1.1
plasma-workspace Version: 6.6.2-1.1
ADDITIONAL INFORMATION
Relevant CLI output before disabling autoconnect in the KDE UI:
`nmcli connection show lan-bridge | grep autoconnect`
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.autoconnect-slaves: 1 (yes)
connection.autoconnect-ports: 1 (true)
Relevant CLI output after disabling autoconnect in the KDE UI:
connection.autoconnect: no
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.autoconnect-slaves: -1 (default)
connection.autoconnect-ports: -1 (default)
If I manually restore only this setting:
`nmcli connection modify lan-bridge connection.autoconnect-ports 1`
then manual activation works again, even with `connection.autoconnect: no`.
This suggests the KDE UI is not preserving bridge-specific NetworkManager
settings when saving the profile.
--
You are receiving this mail because:
You are watching all bug changes.
