Dropbox support

That is another view of the symptom. The reality is that there is nothing to move!

But the code inside of the flatpak:

  • doesn’t understand the metadata it is getting from the composefs fs type
  • is not expecting /home to be a symlink and so is not doing the equiv of performing a stat command the follows the symlink.

For example, look at the difference of this output:

$ stat /home
  File: /home -> var/home
  Size: 8         	Blocks: 8          IO Block: 4096   symbolic link
Device: 0,39	Inode: 563         Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:home_root_t:s0
Access: 1970-01-01 00:00:00.000000000 +0000
Modify: 1970-01-01 00:00:00.000000000 +0000
Change: 1970-01-01 00:00:00.000000000 +0000
 Birth: -

vs dereferencing the symlink like this:

$ stat -L /home
  File: /home
  Size: 28        	Blocks: 0          IO Block: 4096   directory
Device: 0,50	Inode: 256         Links: 1
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:home_root_t:s0
Access: 2025-08-25 20:30:54.504715317 +0000
Modify: 2024-12-28 13:11:12.910724872 +0000
Change: 2025-08-24 18:42:06.380999950 +0000
 Birth: 2024-12-28 12:57:19.448791400 +0000

I suspect they are not recognizing that `/home` is a symlink so they are querying the wrong filesystem and failing.

Thanks for the kind words.