https://bugs.kde.org/show_bug.cgi?id=360257
--- Comment #3 from Jan Grulich <jgrul...@redhat.com> --- (In reply to Elvis Angelaccio from comment #2) > (In reply to Jan Grulich from comment #1) > > I don't think we should be checking this. We display the error message from > > NetworkManager once it fails to activate the connection and if NM is missing > > something, it should report it then in the error message which we display to > > the user. > This makes sense indeed, so this report probably belongs upstream? Yes, if you want NM to report this error then report it to NM bugzilla. > > I also think that this is a packaging issue, if NM requires > > something then it should be as a dependency (we have that in Fedora). > > I was wondering the same, because the plasma-nm Arch package does not > require dnsmasq as optional dependency. However I discovered later that the > networkmanager package does. So the Arch packaging is probably correct. It shouldn't be as a dependency for plasma-nm package, but for NetworkManager. Looking at NM package in Archlinux I see that dnsmasq is optional dependency. -- You are receiving this mail because: You are watching all bug changes.
