[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-05-14 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=405501 Jan Grulich changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla |

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-04-30 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=405501 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-17 Thread Bruce Anderson
https://bugs.kde.org/show_bug.cgi?id=405501 Bruce Anderson changed: What|Removed |Added Assignee|jgrul...@redhat.com |banderson19...@san.rr.com -- You are

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-16 Thread K900
https://bugs.kde.org/show_bug.cgi?id=405501 --- Comment #2 from K900 --- Yeah, that's what I've been doing. Also, it turns out the autoconnect setting is actually enabled by nmcli by default for some reason, so that one isn't plasma-nm's fault. Anyway, I might just start hacking on it when I get

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-16 Thread Bruce Anderson
https://bugs.kde.org/show_bug.cgi?id=405501 Bruce Anderson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-15 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=405501 Jan Grulich changed: What|Removed |Added CC||banderson19...@san.rr.com, |

[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support

2019-03-15 Thread K900
https://bugs.kde.org/show_bug.cgi?id=405501 K900 changed: What|Removed |Added Platform|Other |Archlinux Packages CC|