https://bugs.kde.org/show_bug.cgi?id=421867
Bug ID: 421867
Summary: Bridge w/ a slave hangs at "connecting"
Product: plasma-nm
Version: 5.18.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: esj...@hyunmu.am
Target Milestone: ---
SUMMARY
Starting a bridge connection with a slave through the nm applet (or
"Connections" in system settings) makes the connection stuck at "connecting".
STEPS TO REPRODUCE
1. Create a bridge connection using the applet, and add an ethernet device as a
slave. Using default settings will create a slave w/ DHCP. You may want to
disable IPv6 and STP here, because, in some setups, they make the bridge
connection hang for a while.
2. "Connect" to the bridge using the applet.
OBSERVED RESULT
The status of the bridge connection in the applet is stuck at "Connecting"
indefinitely without any errors nor warnings.
EXPECTED RESULT
The bridge becomes successfully "Connected".
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70
Qt Version: 5.14.2
ADDITIONAL INFORMATION
The problem here is that the applet does NOT start the slave along with the
bridge. Starting the slave manually (i.e. `nmcli connection start
<name-of-the-slave>`) does fix the issue. The applet isn't malfunctioning, but
is merely misaligned with the underlying service.
Maybe the solution for this is to simply include slaves in the connection list,
just like nmcli. It doesn't matter if clicking on them only shows a stub
message (instead of configuration form), because what's important is that all
connections are visible to users.
--
You are receiving this mail because:
You are watching all bug changes.
