Open SuperSamus opened 1 year ago
The problem comes from Wine-TKG, which Soda is based on, from this code: https://github.com/Frogging-Family/wine-tkg-git/blob/bcb3ba72a3c98eac7d04990590deaf101f3bc58e/wine-tkg-git/wine-tkg-patches/hotfixes/valve/de-steamify.mypatch#LL625C15-L625C15
I'm not exactly sure what it does, but this is the culprit. I don't think there's much we can do about it
@Kinsteen I think this also breaks duplicating bottles: I just noticed that duplicating a certain bottle takes ages and copies and excessive amount of data (I cancelled when the new bottle reached ca. 20GB in size, as compared to 4.4 GB in the original bottle). It looks as if the duplication process copies these symlinks literally, i.e. effectively attempts to copy my entire home directory (something similar to #743 perhaps?).
@swsnr This is fixed upstream, it's somewhat related to this
The Same here Once my ssd ran out of space because bottles duplicated my entire home or something like that... because of this bug I avoid duplicating or creating snapshots.
Searching nautilus, these are the only symbolic links that exist inside (C:)
⭐ Edit: Looks like bottle duplication is working correctly now, the symlinks remain as symlinks in the duplicated bottle, no files within the links were duplicated.
Describe the bug
During the creation of a Bottle, some symlinks are created in
$HOME/Documents
: they are namedDownloads
,Music
,Pictures
,Templates
andVideos
. They all point towards$HOME/Documents
, making them affectively useless. I checked the source code, but I have no idea what's creating them (it's not this, I reproduced it with this code deleted).This only happens during bottle creation, not when changing runner. If you are wondering, "Unlinked home directory" doesn't fix the issue. I'm not using Flatpak, nor sandbox. Didn't test whether changing system language has a different behavior.
To Reproduce
$HOME/Documents
with your file managerPackage
Package from nixpkgs (which I have looked at)
Distribution
NixOS 23.05 Unstable
Troubleshooting Logs
Additional context
No response