bootandy/archived-dust
1
0
Fork 0
mirror of https://github.com/bootandy/dust.git synced 2026-06-08 11:29:05 +03:00
Code Issues 21 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #424] "Did not have permissions for all directories" in mount point and its subdirectories #185

New Issue
Closed
opened 2026-06-08 11:26:02 +03:00 by zhus · 13 comments
zhus commented 2026-06-08 11:26:02 +03:00
Owner
Copy Link
Copy Source

Originally created by @ggambetta on GitHub (Aug 4, 2024).
Original GitHub issue: https://github.com/bootandy/dust/issues/424

dust works fine on my main SSD. However it doesn't seem to work at all on a secondary SSD I have mounted somewhere:

/dev/sda1 on /media/gabriel/Extra type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)

$ pwd
/media/gabriel/Extra

$ dust
Did not have permissions for all directories (add --print-errors to see errors)
4.0K ┌── .│█████████████[...]███████████████████ │ 100%

$ ls
drwxrwxr-x   4 gabriel gabriel 4.0K Aug  4 12:17 SomeSubdirectory

$ dust --print-errors SomeSubdirectory
Did not have permissions for directories: SomeSubdirectory
4.0K ┌── SomeSubdirectory│█████████████[...]███████████████████ │ 100%

It doesn't seem to be a permissions issue, because the same happens with sudo. This is on Ubuntu 22, with dust 1.1.1.

Originally created by @ggambetta on GitHub (Aug 4, 2024). Original GitHub issue: https://github.com/bootandy/dust/issues/424 `dust` works fine on my main SSD. However it doesn't seem to work at all on a secondary SSD I have mounted somewhere: `/dev/sda1 on /media/gabriel/Extra type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)` ``` $ pwd /media/gabriel/Extra $ dust Did not have permissions for all directories (add --print-errors to see errors) 4.0K ┌── .│█████████████[...]███████████████████ │ 100% $ ls drwxrwxr-x 4 gabriel gabriel 4.0K Aug 4 12:17 SomeSubdirectory $ dust --print-errors SomeSubdirectory Did not have permissions for directories: SomeSubdirectory 4.0K ┌── SomeSubdirectory│█████████████[...]███████████████████ │ 100% ``` It doesn't seem to be a permissions issue, because the same happens with sudo. This is on Ubuntu 22, with dust 1.1.1.
zhus closed this issue 2026-06-08 11:26:02 +03:00
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@wugeer commented on GitHub (Aug 6, 2024):

hello，I also have two SSDs on my laptop. The results of executing dust on these two SSDs are normal, so I need more information to locate this problem.
Are there any special permissions set in this directory? For example, for lsattr operations, you can execute lsattr <you_directory_or_file> to see the execution result?
Also, could you provide the results of running the dust command in the SomeSubdirectory directory?

<!-- gh-comment-id:2270386582 --> @wugeer commented on GitHub (Aug 6, 2024): hello，I also have two SSDs on my laptop. The results of executing dust on these two SSDs are normal, so I need more information to locate this problem. Are there any special permissions set in this directory? For example, for lsattr operations, you can execute `lsattr <you_directory_or_file>` to see the execution result? Also, could you provide the results of running the dust command in the SomeSubdirectory directory?
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 6, 2024):

Thank you for looking into this!

There's no special attributes that I know of; I haven't set any, and the output of lsattr is the same as in the other filesystem where dust works fine.

Running dust in SomeSubdirectory gives the same error message.

$ pwd
/media/gabriel/Extra

$ lsattr .
--------------e------- ./SomeSubdirectory

$ lsattr SomeSubdirectory
--------------e------- SomeSubdirectory/registry.csv

$ cd SomeSubdirectory

$ lsattr .
--------------e------- ./registry.csv

$ dust --print-errors
Did not have permissions for directories: .
4.0K ┌── SomeSubdirectory│█████████████[...]███████████████████ │ 100%

$ cd /media/gabriel

$ lsattr .
--------------e------- ./Extra

Anything else I can take a look at?

<!-- gh-comment-id:2270444633 --> @ggambetta commented on GitHub (Aug 6, 2024): Thank you for looking into this! There's no special attributes that I know of; I haven't set any, and the output of `lsattr` is the same as in the other filesystem where `dust` works fine. Running `dust` in `SomeSubdirectory` gives the same error message. ``` $ pwd /media/gabriel/Extra $ lsattr . --------------e------- ./SomeSubdirectory $ lsattr SomeSubdirectory --------------e------- SomeSubdirectory/registry.csv $ cd SomeSubdirectory $ lsattr . --------------e------- ./registry.csv $ dust --print-errors Did not have permissions for directories: . 4.0K ┌── SomeSubdirectory│█████████████[...]███████████████████ │ 100% $ cd /media/gabriel $ lsattr . --------------e------- ./Extra ``` Anything else I can take a look at?
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 6, 2024):

Tried chmod a+rwx /media/gabriel/Extra and I still get the same error. So, still unclear what permissions dust is missing.

<!-- gh-comment-id:2270446956 --> @ggambetta commented on GitHub (Aug 6, 2024): Tried `chmod a+rwx /media/gabriel/Extra` and I still get the same error. So, still unclear what permissions `dust` is missing.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 6, 2024):

Oooh, this is interesting! Compiled from source, and that works on /media/gabriel/Extra perfectly fine!

<!-- gh-comment-id:2270451082 --> @ggambetta commented on GitHub (Aug 6, 2024): Oooh, this is interesting! Compiled from source, and that works on `/media/gabriel/Extra` perfectly fine!
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 6, 2024):

For sanity checking, I built from source at the 1.1.1 commit (dbd18f90e7) and it still works. Not what I expected. So what's the difference between the 1.1.1 I'm building and the 1.1.1 I have installed? Must be a dependency?

<!-- gh-comment-id:2270454103 --> @ggambetta commented on GitHub (Aug 6, 2024): For sanity checking, I built from source at the 1.1.1 commit (dbd18f90e7b184d12f14533e76e5915dbe4a2051) and it still works. Not what I expected. So what's the difference between the 1.1.1 I'm building and the 1.1.1 I have installed? Must be a dependency?
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 6, 2024):

The release build also works. There goes another theory.

<!-- gh-comment-id:2270456884 --> @ggambetta commented on GitHub (Aug 6, 2024): The release build also works. There goes another theory.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@wugeer commented on GitHub (Aug 6, 2024):

I'm glad that your issue could be resolved. From my computer(arch linux), it appears that dust depends on very basic packages. Perhaps you can check the build script of the installed dust 1.1.1 program on ubuntu to find the differences between it and the local build.
image
image
Also， you can contact Danie de Jager (danie.dejager) who is the publisher of 'dust' on Ubuntu Snap, to seek help.
image

<!-- gh-comment-id:2270525513 --> @wugeer commented on GitHub (Aug 6, 2024): I'm glad that your issue could be resolved. From my computer(arch linux), it appears that dust depends on very basic packages. Perhaps you can check the build script of the installed dust 1.1.1 program on ubuntu to find the differences between it and the local build. ![image](https://github.com/user-attachments/assets/746b12cc-6f1f-491e-837e-e11bcb66a2d2) ![image](https://github.com/user-attachments/assets/fb16c558-b59b-4598-9ac7-185d00ad2388) Also， you can contact Danie de Jager (danie.dejager) who is the publisher of 'dust' on Ubuntu Snap, to seek help. ![image](https://github.com/user-attachments/assets/260c1faa-e3a4-4978-98ff-4ae3f132947b)
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 7, 2024):

For sanity checking, I built from source at the 1.1.1 commit (https://github.com/bootandy/dust/commit/dbd18f90e7b184d12f14533e76e5915dbe4a2051) and it still works. Not what I expected. So what's the difference between the 1.1.1 I'm building and the 1.1.1 I have installed? Must be a dependency?

That is very strange, not sure how that could happen.

<!-- gh-comment-id:2274041647 --> @bootandy commented on GitHub (Aug 7, 2024): >For sanity checking, I built from source at the 1.1.1 commit (https://github.com/bootandy/dust/commit/dbd18f90e7b184d12f14533e76e5915dbe4a2051) and it still works. Not what I expected. So what's the difference between the 1.1.1 I'm building and the 1.1.1 I have installed? Must be a dependency? That is very strange, not sure how that could happen.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@ggambetta commented on GitHub (Aug 7, 2024):

Happy to help debug this, please let me know if you want the output of some commands or to poke the system in some other way.

<!-- gh-comment-id:2274252044 --> @ggambetta commented on GitHub (Aug 7, 2024): Happy to help debug this, please let me know if you want the output of some commands or to poke the system in some other way.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Aug 9, 2024):

I'm honestly not sure what to do. If you can think of some debugging by all means go for it.

I'm happy to write this off as a one off oddity though.

<!-- gh-comment-id:2276739889 --> @bootandy commented on GitHub (Aug 9, 2024): I'm honestly not sure what to do. If you can think of some debugging by all means go for it. I'm happy to write this off as a one off oddity though.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@wugeer commented on GitHub (Aug 16, 2024):

I've already opened an issue with the package maintainer seeking help, and I hope there will be some progress. :)
https://github.com/daniejstriata/dust-snap/issues/2

<!-- gh-comment-id:2293026217 --> @wugeer commented on GitHub (Aug 16, 2024): I've already opened an issue with the package maintainer seeking help, and I hope there will be some progress. :) https://github.com/daniejstriata/dust-snap/issues/2
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@clouedoc commented on GitHub (Oct 6, 2024):

Hello, I encountered this issue as well.
I think the fix is to add information to the README.md that specifies that dust installed through snap can only access the /home folder.
I will open a PR.

<!-- gh-comment-id:2395412647 --> @clouedoc commented on GitHub (Oct 6, 2024): Hello, I encountered this issue as well. I think the fix is to add information to the README.md that specifies that `dust` installed through `snap` can only access the `/home` folder. I will open a PR.
zhus commented 2026-06-08 11:26:03 +03:00
Author
Owner
Copy Link
Copy Source

@bootandy commented on GitHub (Oct 18, 2024):

Good idea, @clouedoc - thanks.

<!-- gh-comment-id:2420680508 --> @bootandy commented on GitHub (Oct 18, 2024): Good idea, @clouedoc - thanks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 windows help wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus (Sergey Zhukov)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#185
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?