Fixed in commit ab56054a: federation.remove-node now also purges the synthetic mesh peer, shared secret, messages, presence, and persisted contact entry (mesh::purge_federation_peer). Combined with the #42 name refresh, removing the stale 'Arch HP'/'HP Pro Desk' entry via the UI now fully clears it from the mesh chat list too. Pending deploy+test.
Fixed in commit ab56054a: federation.remove-node now also purges the synthetic mesh peer, shared secret, messages, presence, and persisted contact entry (mesh::purge_federation_peer). Combined with the #42 name refresh, removing the stale 'Arch HP'/'HP Pro Desk' entry via the UI now fully clears it from the mesh chat list too. Pending deploy+test.
Correction: an earlier comment referencing commit ab56054a (federation remove-node mesh purge) was mis-filed on this issue by mistake — it belongs to #42, not this USB-flashing issue. Please disregard it here. This issue (USB flashing from kiosk) is unchanged.
Correction: an earlier comment referencing commit ab56054a (federation remove-node mesh purge) was mis-filed on this issue by mistake — it belongs to #42, not this USB-flashing issue. Please disregard it here. This issue (USB flashing from kiosk) is unchanged.
Fixed (root cause matched your attachment): the image's archipelago user was created with only -G sudo, missing dialout, so it couldn't open the USB serial device to flash. image-recipe/build/auto-installer/Dockerfile.rootfs now creates it with -G sudo,dialout, so new images can flash out of the box. EXISTING nodes need the one-liner from your note once: sudo usermod -aG dialout archipelago (then re-login). Closing.
Fixed (root cause matched your attachment): the image's `archipelago` user was created with only `-G sudo`, missing `dialout`, so it couldn't open the USB serial device to flash. `image-recipe/build/auto-installer/Dockerfile.rootfs` now creates it with `-G sudo,dialout`, so new images can flash out of the box. EXISTING nodes need the one-liner from your note once: `sudo usermod -aG dialout archipelago` (then re-login). Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Can't flash USB device - fix attached
Steps to Reproduce
Try to flash meshcore from archy kiosk
Expected Behavior
Should flash device
Actual Behavior
Can't connect, try again
Archipelago Version
1.7.56
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
[Bug]:to [Bug]: Fix flashing USB from kioskFixed in commit ab56054a: federation.remove-node now also purges the synthetic mesh peer, shared secret, messages, presence, and persisted contact entry (mesh::purge_federation_peer). Combined with the #42 name refresh, removing the stale 'Arch HP'/'HP Pro Desk' entry via the UI now fully clears it from the mesh chat list too. Pending deploy+test.
Correction: an earlier comment referencing commit ab56054a (federation remove-node mesh purge) was mis-filed on this issue by mistake — it belongs to #42, not this USB-flashing issue. Please disregard it here. This issue (USB flashing from kiosk) is unchanged.
Fixed (root cause matched your attachment): the image's
archipelagouser was created with only-G sudo, missingdialout, so it couldn't open the USB serial device to flash.image-recipe/build/auto-installer/Dockerfile.rootfsnow creates it with-G sudo,dialout, so new images can flash out of the box. EXISTING nodes need the one-liner from your note once:sudo usermod -aG dialout archipelago(then re-login). Closing.