librepods-org / librepods-org/librepods

[Linux] Config folder not being created

Open Beginner friendly
#633 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug linux
Dominant language
Kotlin
Stars
29.9k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

App version

linux-rust commit 672e65a

Variant

Rust rewrite (linux-rust branch)

Distro and version

Arch Linux

Desktop environment / compositor

KDE 6 (Wayland)

Install method (only official sources)

Built from source (nix or otherwise)

AirPods model

AirPods Pro 3

What happened

Config folder is not being created and thus no app_settings.json is written when updating settings in the app.

Logs and stderr

When run as std::fs::write(app_settings_path,settings.to_string()).unwrap()

[2026-06-14T20:11:47Z DEBUG librepods::ui::window] Writing settings to /home/eron/.config/librepods/app_settings.json: {"stem_control":true,"theme":"Dark","tray_text_mode":false}

thread 'main' (163117) panicked at src/ui/window.rs:656:73:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/ui/window.rs at line 656, where settings are written to /home/eron/.config/librepods/app_settings.json and the missing-directory error occurs. Reproduce by changing a setting in the Linux Rust build, then verify that the config folder and app_settings.json are created and settings save without a panic.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.