mirror of
https://github.com/afkarxyz/SpotiFLAC.git
synced 2026-04-26 07:35:52 +03:00
[GH-ISSUE #150] Regression in v6.7: "mkdir unknown: read-only file system" error after update #1422
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SpotiFLAC#1422
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @kaspy003 on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/afkarxyz/SpotiFLAC/issues/150
After updating to the latest version, I am unable to download any tracks. The application fails with a mkdir unknown: read-only file system error for every track. The previous version worked perfectly with the exact same configuration.
It appears the application is trying to create a directory literally named "unknown" at the root level (or an invalid relative path) instead of using the configured output path.
Environment:
OS: macOS Sequoia (Apple Silicon / M1 Max)
App Version: v6.7
Previous Working Version: 6.6
Steps to Reproduce:
Launch the application on macOS.
Load a playlist for download.
Start the download process.
Observed Behavior: The download fails immediately for all tracks. The logs show: error: [Track Name] - failed to create output directory: mkdir unknown: read-only file system
Expected Behavior: The application should use the configured output path and download files successfully, as it did in the previous version.
Troubleshooting Attempted:
Checked Full Disk Access permissions for the terminal/app (enabled).
Verified the output directory exists and is writable (chmod 777 verified).
Tried changing the output path to a simple absolute path (e.g., /Users/username/Music).
Result: The error persists regardless of the config settings, suggesting the app is ignoring the config path or parsing it incorrectly, defaulting to unknown.
@kryptalivian commented on GitHub (Dec 9, 2025):
Same here - M4 processor on latest Mac OS
@cookie-drummer commented on GitHub (Dec 9, 2025):
I confirm the issue. v6.7 is useless on macOS.
@jacksonstewart commented on GitHub (Dec 9, 2025):
I can confirm the issue as well.
@enriqueqs commented on GitHub (Dec 11, 2025):
same as in
#156
PR #157 should fix it
@k-popfilters commented on GitHub (Dec 12, 2025):
same here on M2 running Tahoe, a workaround for this is to revert back to the 6.6 update it should work! This is only temporary for now until 6.8 comes out
@afkarxyz commented on GitHub (Dec 14, 2025):
fixed