lfg2025/archy
1
0
Fork 0
Code Issues 20 Pull Requests Actions Packages Projects Releases 61 Wiki Activity

[Bug]: Name change kills kiosk #98

New Issue
Closed
opened 2026-07-17 10:58:59 +00:00 by ssmithx · 1 comment
ssmithx commented 2026-07-17 10:58:59 +00:00
Collaborator
Copy Link

Description

This is an old bug where if the hostname changes, kiosk doesn't work. Now that name change changes the hostname, it's been brought to the foreground as a serious issue

Steps to Reproduce

Go to setting and rename archipelago to the new name.
Reboot

Expected Behavior

Kiosk should come up

Actual Behavior

Black screen

Archipelago Version

1.7.101-alpha

Hardware

x86_64 (Intel/AMD)

Relevant Logs

No response

Screenshots

No response

### Description This is an old bug where if the hostname changes, kiosk doesn't work. Now that name change changes the hostname, it's been brought to the foreground as a serious issue ### Steps to Reproduce Go to setting and rename archipelago to the new name. Reboot ### Expected Behavior Kiosk should come up ### Actual Behavior Black screen ### Archipelago Version 1.7.101-alpha ### Hardware x86_64 (Intel/AMD) ### Relevant Logs _No response_ ### Screenshots _No response_
lfg2025 commented 2026-07-17 15:33:22 +00:00
Owner
Copy Link

Root cause: Chromium's profile lock (SingletonLock) encodes hostname+pid; after a rename the stale lock reads as another computer holding the profile, Chromium silently refuses to start (--noerrdialogs) and the kiosk black-screens. Fix on main: a177ef3b — the kiosk launcher now clears Singleton{Lock,Cookie,Socket} before every Chromium start, and the rename handler clears them immediately as a hostname side-effect (covers nodes still on the old launcher). Ships via next OTA/RC; leaving open until verified with a rename+reboot on hardware.

Root cause: Chromium's profile lock (SingletonLock) encodes hostname+pid; after a rename the stale lock reads as another computer holding the profile, Chromium silently refuses to start (--noerrdialogs) and the kiosk black-screens. Fix on main: `a177ef3b` — the kiosk launcher now clears Singleton{Lock,Cookie,Socket} before every Chromium start, and the rename handler clears them immediately as a hostname side-effect (covers nodes still on the old launcher). Ships via next OTA/RC; leaving open until verified with a rename+reboot on hardware.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai ssmithx lfg2025
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfg2025/archy#98
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?