You can run 'ps -ef | grep wpa_ | grep -v grep' to get the command line used by NM to start wpa_supplicant.
But the point is that while you may not care where the messages come from, which I understand perfectly, but *we* care for clarity's sake. Open a new report, because if your problem is still here, it's because another bug about bad message priority setting. Why is that a problem for you to separate reports? You know, reports are divided not based on visible problems for users, but about root causes for programmers: this is the best way to provide patches that apply to a precise software. Now, what I'd like to know is whether this latter bug comes from NM or wpa_supplicant. Alexander, do you have an idea? -- Executes wpa_supplicant in too verbose mode https://bugs.launchpad.net/bugs/51784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
