Still no solution, but I've at least (hopefully) eliminated some more variables.
As I know this problem doesn't currently exist on Vivid, I tried back-porting `network-manager` and `network-manager-applet` from Vivid, but no luck... same problem still exists.
And on the off chance that this is kernel-related, I also tried the 3.16 kernel on Trusty... but connecting to WiFi still works fine, so it doesn't seem to have anything to do with the kernel version.
However, I have noticed some differences in the Dbus processes running an a system with Nvidia hardware vs a system with an Intel GPU, so I'm further investigating that today...
Also, I'm not that familiar with network-manager, so if you have any advice for how I could get you better debugging information, please let me know!
Still no solution, but I've at least (hopefully) eliminated some more variables.
As I know this problem doesn't currently exist on Vivid, I tried back-porting `network-manager` and `network- manager- applet` from Vivid, but no luck... same problem still exists.
And on the off chance that this is kernel-related, I also tried the 3.16 kernel on Trusty... but connecting to WiFi still works fine, so it doesn't seem to have anything to do with the kernel version.
However, I have noticed some differences in the Dbus processes running an a system with Nvidia hardware vs a system with an Intel GPU, so I'm further investigating that today...
Also, I'm not that familiar with network-manager, so if you have any advice for how I could get you better debugging information, please let me know!