https://bugs.kde.org/show_bug.cgi?id=366708
--- Comment #2 from Simone Gaiarin <simg...@gmail.com> --- Hi Lamarque, your answer made me read the NM specifications and I've found that the value autoconnect-priority is int32 which can possibly be negative (other parameters require specifically uint32). Executing the command: nmcli connection modify MYCONNECTION connection.autoconnect-priority -10 doesn't rise any error and running nmcli connection show MYCONNECTION shows that the value has been set. I cannot test if this priority works in this moment, but if it's the case it would be enough to let the priority value be negative in the UI spinbox and the problem would be solved. -- You are receiving this mail because: You are watching all bug changes.
