Íñigo Huguet 3355ba9380 core: rename NM_STATE_ASLEEP to NM_STATE_DISABLED ... When we do `nmcli networking off` it's shown as state "sleeping". This is confusing, and the only reason is that we share internally code to handle both situations in a similar way. Rename the state to the more generic name "disabled", situation that can happen either because of sleeping or networking off. Clients cannot differentiate the exact reason only with the NMState value, but better that they show "network off" as this is the most common reason that they will be able to display. If the system is suspending, there will be only a short period of time that they can show the state, and showing "network off" is not wrong because that's what NM has done as a response to suspend. In the logs, let's make explicit the exact reason why state is changing to DISABLED: sleeping or networking off. Logs before: manager: disable requested (sleeping: no enabled: yes) manager: NetworkManager state is now ASLEEP Logs after: manager: disable requested (sleeping: no enabled: yes) manager: NetworkManager state is now DISABLED (NEWORKING OFF) State before: $ nmcli general STATE ... asleep ... State after: $ nmcli general STATE ... network off ...		2025-09-23 09:17:03 +02:00
..
glib	core: rename NM_STATE_ASLEEP to NM_STATE_DISABLED	2025-09-23 09:17:03 +02:00
qt	meson: replace deprecated dep.get_pkgconfig_variable	2024-04-04 08:13:38 +00:00