Bug 425389

Summary: Filesystem expose: raw:* and msd:* entries error out on Debian
Product: [Applications] kdeconnect Reporter: user456 <gwmeeqqhvjyhpandre>
Component: android-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: NEEDSINFO WAITINGFORINFO    
Severity: normal CC: aristsakas
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Unspecified   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description user456 2020-08-15 15:34:04 UTC
On my Samsung Galaxy A21S (stock Android 10, f-droid's KDE Connect 1.14.2),
the "filesystem expose" plugin directories include
- raw:/storage/emulated/0/Download/k
  - Debian fails when trying to create a file or directory in a raw:* dir:
    "File already exists".
  - strace mkdir abc
    mkdir("abc", 0777) = -1 EEXIST
- msd:19
  - How to create:
    Click to add a storage location, choose a dir in the file list that opens,
    click the blue button at the bottom to allow access.
  - Debian creates files and dirs in msd:* dirs, however it still prints
    an error: "No such file or directory".
  - strace mkdir ghi
    mkdir("ghi", 0777) = -1 ENOENT
- primary:Download
  - How to create:
    Click to add a storage location, click on the sandwich menu at the left,
    choose the internal memory ("Galaxy A21S"), navigate and choose the dir,
    click the blue button at the bottom to allow access.
  - Works flawlessly on Debian.

Debian is Debian 10 KDE with no third-party repos and kdeconnect 1.3.3-2.

Additional info:
- All permissions were granted to the app.
- "Share and receive" works, on the same network, between this phone and older
  phones that run older Android versions.
- "Filesystem expose" works, on the same network, between the PC and older
  phones that run older Android versions.
- Other phones with older Android and KDE Connect 1.14.2 only have primary:*
  entries, and they work on Debian.
Comment 1 aristsakas 2026-02-08 10:42:24 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with KDE Connect 25.12.2.