New Issue Checklist
Issue:
When the user's home directory resides on a non-boot volume (e.g. a secondary internal or external drive mounted at /Volumes/), enabling Homebrew auto-update scheduling fails with "Failed to register LaunchAgent: Bootstrap failed: 5: Input/output error".
Root cause: macOS launchd refuses to load plists from non-boot volumes for security reasons. Since Pearcleaner writes the plist to ~/Library/LaunchAgents/, and that path resolves to /Volumes/<DriveName>/Users/<username>/Library/LaunchAgents/, launchd rejects it. The actual error from log show:
Caller specified a plist with bad ownership/permissions: path = /Volumes/<DriveName>/Users/<username>/Library/LaunchAgents/com.alienator88.Pearcleaner.homebrew-autoupdate.plist
Suggested fix: Detect that $HOME is on a non-boot volume and write the plist to /Library/LaunchAgents/ (system-level) instead, with root:wheel / 644 permissions.
Steps:
- Have home directory on a non-boot volume (e.g.
/Volumes/<n>/Users/<username>/)
- Enable Homebrew auto-update scheduling in Pearcleaner
- Observe "Failed to register LaunchAgent: Bootstrap failed: 5: Input/output error"
Screenshots:
N/A
Debug Console
N/A
Console Logs
N/A
New Issue Checklist
Issue:
When the user's home directory resides on a non-boot volume (e.g. a secondary internal or external drive mounted at
/Volumes/), enabling Homebrew auto-update scheduling fails with "Failed to register LaunchAgent: Bootstrap failed: 5: Input/output error".Root cause: macOS launchd refuses to load plists from non-boot volumes for security reasons. Since Pearcleaner writes the plist to
~/Library/LaunchAgents/, and that path resolves to/Volumes/<DriveName>/Users/<username>/Library/LaunchAgents/, launchd rejects it. The actual error fromlog show:Suggested fix: Detect that
$HOMEis on a non-boot volume and write the plist to/Library/LaunchAgents/(system-level) instead, withroot:wheel/644permissions.Steps:
/Volumes/<n>/Users/<username>/)Screenshots:
N/A
Debug Console
Console Logs