[BUG]: program can't handle bad write permissions #27

New Issue

2026-09-02T14:02:29+04:00

max commented

2026-09-02 14:02:29 +04:00

📋 Description

Program failed to detect the absence of the write permissions and tried to write there and expectedly FFmpeg failed

🔁 Steps to Reproduce

mkdir -p /tmp/noaccess
chmod 000 /tmp/noaccess
./venv/bin/python -m audio_splitter.main test_data/png_test.opus test_data/png_test.txt -o /tmp/noaccess
chmod 755 /tmp/noaccess
rm -rf /tmp/noaccess

✅ Expected Behavior

Program exits with 'no write permissions' error

❌ Actual Behavior

Program passes this path to FFmpeg which fails

📄 Logs / Screenshots

No response

📦 Audio Splitter Version

commit 25e8c0293e

💻 Operating System

Debian 13

🌍 Browser (if applicable)

No response

📎 Additional Context

No response

✅ Submission Checklist

I have searched for existing issues (open and closed) that report the same problem
I am using the latest stable release of Audio Splitter
I have provided clear steps to reproduce the issue
I have included relevant logs or error messages (with sensitive info removed)

### 📋 Description Program failed to detect the absence of the write permissions and tried to write there and expectedly FFmpeg failed ### 🔁 Steps to Reproduce 1. mkdir -p /tmp/noaccess 2. chmod 000 /tmp/noaccess 3. ./venv/bin/python -m audio_splitter.main test_data/png_test.opus test_data/png_test.txt -o /tmp/noaccess 4. chmod 755 /tmp/noaccess 5. rm -rf /tmp/noaccess ### ✅ Expected Behavior Program exits with 'no write permissions' error ### ❌ Actual Behavior Program passes this path to FFmpeg which fails ### 📄 Logs / Screenshots _No response_ ### 📦 Audio Splitter Version commit 25e8c0293e4b8bc52984c6c6a1711f98594603d9 ### 💻 Operating System Debian 13 ### 🌍 Browser (if applicable) _No response_ ### 📎 Additional Context _No response_ ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that report the same problem - [x] I am using the latest stable release of Audio Splitter - [x] I have provided clear steps to reproduce the issue - [ ] I have included relevant logs or error messages (with sensitive info removed)

max added the bug label 2026-09-02 14:02:29 +04:00

max added the core label 2026-09-02 15:50:38 +04:00

max referenced this issue from a commit

2026-09-02 18:35:31 +04:00

fix #27 (core): no write permissions fail

max referenced a pull request that will close this issue

2026-09-02 18:37:43 +04:00

fix #27 (core): no write permissions fail #35

max referenced a pull request that will close this issue

2026-09-02 18:38:19 +04:00

fix #27 (core): no write permissions fail #35

max closed this issue