[Bug]: navigating out and back into the bottle config page in main screen kills running wine processes in bottle

[owopeachy]

Describe the bug

Hello.
This piece of code called when the config updates causes the running wine processes to terminate (wineboot.kill line)

bottles/backend/managers/manager.py

I gather from the code this has to do with updating the sync method but I am not touching the sync method at all, this happens when navigate out from bottle A to main window, open another bottle B in the main window, then return to the bottle A. If i comment out the wineserver kill calls it does not terminate.

I have the sync set to System but it does this regardless what sync method I use. I suspect it could be something to do with NTsync as that is enabled on my system

To Reproduce

open program in bottle A
navigate out from bottle A to main window
open another bottle B in the main window
return to the bottle A.

Package

Flatpak from Flathub

Distribution

Arch linux

Debugging Information

Official Package: true
Version: '51.17'
DE/WM: plasma
Display:
    X.org: true
    X.org (port): :1
    Wayland: true
Graphics:
    vendors:
        nvidia:
            vendor: nvidia
            envs:
                __NV_PRIME_RENDER_OFFLOAD: '1'
                __GLX_VENDOR_LIBRARY_NAME: nvidia
                __VK_LAYER_NV_optimus: NVIDIA_only
            icd: /usr/share/vulkan/icd.d/nvidia_icd.json
            nvngx_path: /usr/lib/nvidia/wine
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.13.1-zen1-1-zen
Disk:
    Total: 502612451328
    Free: 85747646464
RAM:
    MemTotal: 31.3GiB
    MemAvailable: 18.4GiB
Bottles_envs: null
Tools and Libraries:
    cabextract: true
    p7zip: true
    patool: true
    glibc_min: '2.41'
    icoextract: true
    pefile: true
    orjson: true
    markdown: true
    ImageMagick: true
    FVS: true
    xdpyinfo: true

Troubleshooting Logs

Additional context

I have fixed it by editing my .py files manually, just noting here as i did not see any issues for this issue.
Thanks for your hard work!

[github-actions]

This issue has been automatically closed as part of a cleanup process to help the team manage issues more effectively.

If the problem still persists, feel free to comment and we will gladly reopen it.