https://bugs.winehq.org/show_bug.cgi?id=57752
Bug ID: 57752 Summary: Reason (DAW) fails to start when wine's user "music" subdirectory is a symbolic link Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: schroedingerscat@disroot.org CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 77956 --> https://bugs.winehq.org/attachment.cgi?id=77956 Log from when the error dialog "Internal Error" is shown
ReasonStudio's DAW Reason v13 and v12 (and possibly earlier versions, too) behave wrong when having to access a directory that is a symbolic link on the user's ext4/btrfs drive.
This problem only affects staging builds (tested with v9.21, v9.22 and v10.0). Builds from the same version via mainline do not exhibit this behavior.
The problems are: 1. Reason fails to start with an "Internal Error" when $WINEPREFIX/drive_c/users/username/Music is a symbolic link (which is the default for a new wineprefix) 2. Reason's Browser shows an empty directory if you browse to a directory that contains a symbolic link
How to reproduce problem 1: 1. Use a staging build of a recent wine version, like 10.0 2. In the following step, ignore the command "winetricks isolate_home" from the installation instructions as that will replace the user directory's symbolic links with real directories 3. Follow download and installation instructions from the "Additional Comments" section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=42495 4. Running from the instructions will fail with an error dialog showing "Internal Error"
How to reproduce problem 2: 1. Use a staging build of a recent wine version, like 10.0 2. In the following step, do execute the command "winetricks isolate_home" from the installation instructions so the app starts 3. Follow download and installation instructions from the "Additional Comments" section here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=42495 4. (if not authorized) click on "run in demo mode" (dialog might open without focus behind Reason's splash screen) 5. Finish initial configuration wizard 6. In a path your current Wineprefix can access, create a symbolic link to a directory 7. Open Reason's Browser (F9) 8. Navigate to the directory containing your newly created symbolic link via the browser's side pane "Computer" -> the directory containing the symbolic link will be shown as empty
Both problems do not happen in a mainline build indicating that this only happens in staging builds. I've attached a log from when the "Internal Error" dialog is shown.