Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tools/include/branding/postinst/mate.sh`:
- Around line 65-101: The preset currently replaces the whole panel layout
(object-id-list and single toplevel 'top'), removing the
bottom/workspace/window-list panel; instead keep an explicit bottom toplevel and
only remove the broken applets: update object-id-list to include the window-list
and workspace-switcher IDs, add a [org/mate/panel/toplevels/bottom] stanza
(orientation/bottom, size) and corresponding
[org/mate/panel/objects/window-list] and
[org/mate/panel/objects/workspace-switcher] entries (locked,
toplevel-id='bottom', positions) so fresh MATE profiles retain the bottom panel
while you still omit the broken applet object sections (e.g.,
NotificationAreaApplet/Clock/ShowDesktop) rather than dropping the entire second
panel.
- Around line 108-111: The loop that deletes each user's ~/.config/dconf/user
must not be used because it wipes all GSettings for existing accounts; remove
the for ... rm -f "$home/.config/dconf/user" code and instead implement one of
two safe approaches: (A) set MATE/Caja-specific defaults via system dconf
profiles and keyfiles (create/update entries under /etc/dconf/db/* and run dconf
update) so new-user defaults apply without touching existing user files, or (B)
if you must modify existing accounts, iterate users and run dconf write/reset
only for the specific MATE/Caja keys needed using the dconf CLI (e.g., dconf
reset -f /org/mate/... or dconf write /org/mate/... for targeted keys) rather
than deleting the entire $home/.config/dconf/user file; replace references to
the removed rm line with the chosen safe method.
- Around line 136-144: The script currently unconditionally writes an NM
override which can disable NetworkManager-managed ethernet; instead source the
runtime variables (e.g. run set_runtime_variables.sh) and check the
NETWORK_RENDERER variable, and only create
/etc/NetworkManager/conf.d/10-armbian-unmanaged.conf and restart NetworkManager
when NETWORK_RENDERER indicates systemd-networkd is the active renderer (match
the exact value provided by set_runtime_variables.sh, e.g. "systemd-networkd");
leave the existing NetworkManager logic (command -v NetworkManager) intact but
gate the unmanaged-devices write behind that NETWORK_RENDERER check.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@tools/include/branding/postinst/mate.sh`:
- Around line 154-162: The script currently unconditionally writes an
unmanaged-devices override when NetworkManager exists, which can break wired
networking if NetworkManager is the active renderer; modify the block that
creates /etc/NetworkManager/conf.d/10-armbian-unmanaged.conf so it first sources
or checks the runtime NETWORK_RENDERER variable (as set by
set_runtime_variables.sh) and only applies the override when NETWORK_RENDERER ==
"systemd-networkd"; locate the conditional that uses command -v NetworkManager
and add a guard testing NETWORK_RENDERER for equality to "systemd-networkd"
before creating the conf file and restarting NetworkManager.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tests/MATE01.conf`:
- Around line 5-9: The test currently uses set -e so a failing
./bin/armbian-config --api module_desktop install de=mate will prevent the
subsequent remove call; add an EXIT trap inside the testcase() subshell (after
set -e and before the install command) that always runs ./bin/armbian-config
--api module_desktop remove de=mate to guarantee cleanup even on failure. Use
the trap with the EXIT signal inside the subshell so the remove runs when the
subshell exits, and keep the trap target exactly the remove invocation shown in
the diff.

In `@tools/modules/system/module_appimage.sh`:
- Around line 78-81: The script currently may resolve fusermount to an empty
path (variable fmount) and later re-run a lookup that can embed an empty
FUSERMOUNT_PROG into the generated Exec, breaking AppImage startup; fix by
resolving fusermount once into the local variable fmount, validate that fmount
is non-empty before writing to /etc/environment or embedding into any Exec
lines, and reuse that same fmount value later instead of performing a second
lookup (ensure any code that references FUSERMOUNT_PROG reads from the resolved
variable fmount and, if empty, either skip writing/embedding or fail with a
clear message).
- Around line 71-73: The pkg_install call that ensures FUSE support
("pkg_install libfuse2 fuse3") must be checked and the script should fail fast
if installation fails; update the AppImage FUSE block to capture the exit status
of pkg_install (the invocation in the "ensure FUSE support for AppImages"
block), log an error describing the failure, and exit with a non‑zero status (or
return non‑zero) instead of continuing to create the launcher when
libfuse2/fuse3 installation fails.

---

Outside diff comments:
In `@tools/include/branding/postinst/cinnamon.sh`:
- Around line 135-143: The NetworkManager block in cinnamon.sh leaves a stale
/etc/NetworkManager/conf.d/10-armbian-unmanaged.conf when systemd-networkd
becomes inactive, so update the logic around the command -v NetworkManager /
systemctl is-active --quiet systemd-networkd check to remove the file when
systemd-networkd is not active (mirror the existing stale-config cleanup
elsewhere); specifically, ensure the script either deletes
/etc/NetworkManager/conf.d/10-armbian-unmanaged.conf when systemd-networkd is
inactive or conditionally creates it only when active, and restart
NetworkManager via systemctl restart NetworkManager || true after making that
change (reference the 10-armbian-unmanaged.conf path, the NetworkManager check,
and the systemctl is-active --quiet systemd-networkd call).

In `@tools/include/branding/postinst/gnome.sh`:
- Around line 42-50: The current guard only creates
/etc/NetworkManager/conf.d/10-armbian-unmanaged.conf when systemd-networkd is
active but never removes it when networkd becomes inactive, leaving Ethernet
permanently unmanaged; update the logic in gnome.sh around the systemctl
is-active check so that if systemd-networkd is inactive and the file
/etc/NetworkManager/conf.d/10-armbian-unmanaged.conf exists you remove that file
(and then restart NetworkManager), otherwise keep the existing creation path
when systemd-networkd is active; ensure removals ignore errors (e.g., rm -f) and
always attempt to restart NetworkManager after creating or removing the file.