Permission Denied - Ubuntu 22.04.3 latest

[JayCroghan]

thread 'main' panicked at 'Can't open test file: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', src/utils.rs:94:45
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[sassman]

Thanks for reporting.

How do you execute the program? Via snap or anything?
What is your current working directory?
What permissions does your current working directory have?

[JayCroghan]

Installed via snap, executed at bash with ssd-benchmark command.
Tried in ~ and \media\ssd which is a full read/write NTFS file system.
Full read/write.

[sassman]

Can you pls try it on a native FS? Like on linux an ext4 or something?

[JayCroghan]

My home drive is ext4, when i run it in /~ it also gives the same error.

[RushJet1]

For me it works on my main ext4 SSD, but when I try on the NTFS one it has the same error as JayCroghan reported.

[sassman]

I suspect the problem on the mounted fs.
What does mount say? What are your users permissions?

Also snaps create a own layer of permissions on top of your current user.

[ekuznetsov139]

Snap architecture severely restricts the ability of its snaps to access the file system. Pretty much the only places where it is allowed to write are /tmp and its own user storage area. It can't even see the inside of your $HOME. As such, ssd-benchmark has very limited usefulness if installed as a snap.
At best, you can install it as a snap, but then run the internal executable directly. On my system, the command is:
/snap/ssd-benchmark/118/bin/ssd-benchmark
This bypasses snap's confinement and gives the process the same privileges as the shell where it is executed.

[sassman]

This permission problem should be addressed by the --directory argument (see issue #32)
Then it should be possible to measure any other directory where the snap installed version might have write access.

[Sch-LikA]

Hello ! First a huge thanks for the simple tool ! I have the same issue, also installed from snap. when using the --directory argument I get 'The provided directory is not valid' error ...

When using the binary directly from the snap folder it works fine. So definitively a snap issue ...