Open
Description
System Information
- OS: Pop!_OS Cosmic (latest alpha as of March 2025)
- DE: Cosmic DE (Wayland)
- File manager: cosmic-files
- pCloud client: Official AppImage from https://www.pcloud.com/
Summary
After logging in and launching the cosmic-files file manager, there's a noticeable delay (approx. 10–15 seconds) before the home directory is displayed — this only happens when the official pCloud AppImage has mounted the ~/pCloudDrive
FUSE-based directory.
Context
- The pCloud AppImage creates a virtual mount at
~/pCloudDrive
using FUSE - In my case, this cloud drive contains ~300GB of existing folders and files
- The delay occurs even when not opening
pCloudDrive
directly in the file manager — the folder just being present in$HOME
seems to trigger it - Once loaded, everything behaves normally
Steps to Reproduce
- Run the official pCloud AppImage and mount your account (must contain files)
- Wait for
~/pCloudDrive
to appear - Launch cosmic-files
- Observe slow initial load of home directory (blank window for 10–15s)
What I Expected
The file manager should open the home folder without delay, regardless of whether a mounted FUSE folder is present — even with many files inside.
Notes
- This is a real-world backup workflow (syncing documents/projects to pCloud)
- I haven’t yet tested whether this occurs in other file managers (like Nautilus or Dolphin)
- I also haven't checked journalctl for specific entries, but I can do that if needed
Suggestion
Perhaps defer scanning of FUSE-mounts until opened, or handle delayed I/O more gracefully if the user isn't actively opening that folder.
Thanks for building this desktop — Cosmic has been a joy to work with so far. Let me know if I can help test anything further.