| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Simon pointed out that there's no reason to have the mesh device
icon active when the mesh is not being used.
Adapt it to behave more like the wired network device icon in this
respect.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
When the mesh is not active, grey out the mesh device icon and update
the palette text.
Also remove the "Create new network" option from the mesh device
palette.
|
|
|
|
|
| |
The mesh support tried to connect to a mesh network automatically,
even though there was a connection set in the configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Three or more mesh icons were being added after every suspend/resume.
There was already code present to detect when the device goes away and
remove the icons, but it was not working. NetworkManagerObserver was
attempting to look at the properties of the gone-away device in order to
see if it is a mesh device, but this was failing because the device has
already been destroyed at this point.
Solve this by recording the device path of the mesh device when it is
detected, so that we can later determine if the gone-away device is the
mesh device.
Signed-off-by: Martin Abente <mabente@paraguayeduca.org>
|
|
|
|
|
|
| |
from Home favorite view
[dsd: backport to 0.84]
|