Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] In my file selector, when I add the /run folder in the exclude list, it displays as "/run/user/1000/doc/61a606e8/run" #564

Open
MarArMar opened this issue Jul 16, 2024 · 5 comments
Labels

Comments

@MarArMar
Copy link

MarArMar commented Jul 16, 2024

Describe the bug
I clicked the "+" to add an exclude path,

In my file selector, when I add the /run folder in the exclude list, it displays as "/run/user/1000/doc/61a606e8/run"

To Reproduce
Steps to reproduce the behavior:

  1. Go to Preference > database
  2. Click on The plus, it opens the "Select Folder - Portal" window
  3. Select the "/run" folder
  4. See error

Expected behavior
Path added is /run

Screenshots
If applicable, add screenshots to help explain your problem.

image

Desktop (please complete the following information):

  • OS: [e.g. Ubuntu 20.04] Linux 6.5.0-10043-tuxedo x86_64 x86_64 Tuxedo OS 2.0
  • How you installed FSearch : flatpak
  • Version [output of fsearch --version] : command not found: fsearch => Installed by flatpak => 0.2.3 flathub-stable

Additional context
Add any other context about the problem here.

@MarArMar
Copy link
Author

Operating System: TUXEDO OS 2
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12
Kernel Version: 6.5.0-10043-tuxedo (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 62,0 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT
Manufacturer: ASUS

@MarArMar
Copy link
Author

Currently I end up indexing / because of this..

It does it only for specific folders, generally under root, /lib is another example

@porridgewithraisins
Copy link
Contributor

As I understand it, Flatpaks each see their own /run filesystem, so the flatpak fsearch sees /run as /run/user/1000/whatever. Not sure how to fix this as I don't use flatpaks.

@MarArMar
Copy link
Author

Ok interesting, I will try uninstalling fsearch & installing in in another way then

@yllekz
Copy link

yllekz commented Feb 15, 2025

I have other flatpak apps that don't exhibit the problem that fsearch is demonstrating here. IT seems fsearch is erroneously translating the proper /run/user/xxxx/gvfs/networkpathgoeshere to some weird immutable path that gets reset every time the connection is lost. Other apps such as OnlyOffice, OBS, etc do not do this, they just remember the actual path. I checked permissions in Flatseal and fsearch as all what it needs, identical to the aforementioned apps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants