Thanks, but you realize that’s not in development, right? That it’s a final release?
“Edit Connections” seems like the obvious solution. Is there some reason why this doesn’t seem so obvious?
I never noticed any problems here. What do you see as problematic?
Yes and one I find, as was mentioned elsewhere, can yield an inaccurate display. If you maximize the terminal window, everything works fine. It’s just a little clunky.
As mentioned in this bug there is no native connection editor in
nm-tray. While that is problematic, it is beneficial because it is otherwise simple and functional and based on Qt, so we’d like to keep it. Because of this, we added “Advanced Network Confguration,” i.e.
nm-connection-editor. “Edit Connections” doesn’t go directly to it because of a problem we had but I think I may have a solution to that for 20.04 (and maybe we’ll SRU this to 19.10).
I did not have this problem (and I’ve got that annoying Broadcom BCM4313 14e4:4727 rev 01 wireless card that is just problematic all the way around, at least on the test machine). Also I know of nowhere that
nm-tray (yes, the nm does stand for Network Manager) intends to usurp what Network Manager does.
That’s strange and I cannot say I’ve ever experienced that before. I would remove the connection and add it again. It should default to having it connect automatically.
This is most likely a default setting on your kernel module. That’s not something Lubuntu would set by default but it may be something that Ubuntu or Debian or perhaps even the kernel itself set by default. Either way, though your generality that it could be bad might be true, it might not be for your particular module.
You can do something like
lspci -nnk | grep -A3 Network to see which kernel module you’re using. Then you can see the parameters available with the module with
modinfo -p module.
On the machine I’m on right now I find:
power_save:enable WiFi power management (default: disable) (bool)
And there’s nothing in
/etc/modprobe.d to suggest anything different, so it’s disabled for me.
If this is truly not the case for you, I’d investigate a little farther and if it does indeed seem like it’s problematic, I would report a bug against the kernel itself in Ubuntu and let the Kernel Team sort out whether or not it’s something that should be fixed upstream or not.