https://bugs.kde.org/show_bug.cgi?id=413211
Jan Grulich <jgrul...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jgrul...@redhat.com
--- Comment #3 from Jan Grulich <jgrul...@redhat.com> ---
(In reply to Dmitry from comment #2)
> Proposed fix does not fix the issue itself, just mitigates the most extreme
> case.
> Behaviour is still broken due to:
>
> 1. Configuration is still changes implicitly:
> * before editing: NetworkManager does not set ethernet mode
> * after editing: NetworkManager sets 100 Mb/s FullDuples
> 2. In some cases (1) leads to UX regression
> * it makes connection over gigabit link slower
> * it makes connection over 100 HD link no longer working
> 3. In some rare cases it leads to faulty condition
> * in case of (https://bugzilla.kernel.org/show_bug.cgi?id=205067) it's
> impossible to configure/preserve via GUI a persistently working gigabit
> connection.
>
> The only fix I hae ideas about is implementing this as a separate mode of a
> connection like it works in XFCE, where not only "Manual" and "Auto" modes
> are present, but also "Ignored", which essentially is the described above
> mode.
>
> Implementing this fix may require adding come code into networkmanager-qt as
> plasma-nm uses it to interact with NetworkManager.
I just checked nm-connection-editor and they indeed have additional option,
which is "Ignore", but in the code it doesn't make any difference. If the link
negotiation is set to "Ignore" or "Automatic", it sets speed to 0 and duplex to
unknown type, which is the same what we do in plasma-nm.
--
You are receiving this mail because:
You are watching all bug changes.
