[Bug]: Can't create new bottles

[filson1]

Describe the bug

Tried creating bottles based on sys-wine-11.0 and soda-9.0-1. Both will stop with error message "Unable to Create Bottle" after "Template found, applying...".

When restarting Bottles, this is shown:

[Errno 2] No such file or directory: '/home/USER/.var/app/com.usebottles.bottles/data/bottles/templates/83b27b67-0df5-48af-946d-70cb590db4b3'  File "/app/share/bottles/bottles/backend/utils/threading.py", line 73, in __target
    result = self.task_func(*args, **kwargs)

  File "/app/share/bottles/bottles/backend/managers/manager.py", line 1758, in create_bottle
    TemplateManager.unpack_template(template, config)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^

  File "/app/share/bottles/bottles/backend/managers/template.py", line 191, in unpack_template
    shutil.copytree(
    ~~~~~~~~~~~~~~~^
        _path,
        ^^^^^^
    ...<4 lines>...
        ignore_dangling_symlinks=True,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^

  File "/usr/lib/python3.13/shutil.py", line 591, in copytree
    with os.scandir(src) as itr:
         ~~~~~~~~~~^^^^^

True enough, the system does not have a folder named 83b27b67-0df5-48af-946d-70cb590db4b3. It has 2 other folders with similar uuid names.

Running Bottles v.62.0.
Existing bottles works ok.

To Reproduce

Create a bottle with type Application and either Wine 11.0 or Soda 9.0-1 runner in the default dir.
Watch it fail to complete the creation.

Package

Flatpak from Flathub

Distribution

Pop_OS

Debugging Information

Official Package: true
Version: '62.0'
DE/WM: pop
Display:
    X.org: true
    X.org (port): :1
    Wayland: false
Graphics:
    vendors:
        amd:
            vendor: amd
            envs:
                DRI_PRIME: '1'
            icd: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/radeon_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/radeon_icd.i686.json
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.17.9-76061709-generic
Disk:
    Total: 32429117440
    Free: 32428953600
RAM:
    MemTotal: 60.4GiB
    MemAvailable: 48.9GiB
Bottles_envs: null

Troubleshooting Logs

Additional context

No response

[Graham--M]

Inside the directory for each template, there is a file called template.yml. The uuid: entry value at the bottom of it should match the name of the directory it was found in.

[filson1]

Correct. The folder with configuration for sys-wine-10.0 does not have a matching uuid.
Odd since my sys-wine is v.11 in the runner selector, with no v.10 listed.

template content:

config:
  Arch: win64
  CompatData: ''
  Creation_Date: ''
  Custom_Path: false
  DLL_Overrides: {}
  DXVK: dxvk-2.7.1-9-d6c19f9
  Environment: Application
  Environment_Variables: {}
  External_Programs: {}
  Inherited_Environment_Variables:
  - DBUS_SESSION_BUS_ADDRESS
  - DISPLAY
  - HOME
  - LANG
  - LC_ALL
  - LC_CTYPE
  - LC_MESSAGES
  - PATH
  - PULSE_SERVER
  - TERM
  - TZ
  - USER
  - WAYLAND_DISPLAY
  - XAUTHORITY
  - XDG_RUNTIME_DIR
  Installed_Dependencies:
  - arial32
  - times32
  - courie32
  - mono
  - gecko
  Language: sys
  LatencyFleX: latencyflex-v0.1.1
  Limit_System_Environment: true
  NVAPI: dxvk-nvapi-v0.9.0
  Name: ''
  Parameters:
    custom_dpi: 96
    decorated: true
    discrete_gpu: false
    dxvk: true
    dxvk_nvapi: false
    fixme_logs: false
    fsr: false
    fsr_quality_mode: none
    fsr_sharpening_strength: 2
    fullscreen_capture: false
    gamemode: false
    gamescope: false
    gamescope_borderless: false
    gamescope_fps: 0
    gamescope_fps_no_focus: 0
    gamescope_fullscreen: true
    gamescope_game_height: 0
    gamescope_game_width: 0
    gamescope_scaling: false
    gamescope_window_height: 0
    gamescope_window_width: 0
    latencyflex: false
    mangohud: false
    mangohud_display_on_game_start: true
    mouse_warp: true
    obsvkc: false
    pulseaudio_latency: false
    renderer: gl
    sandbox: false
    sync: wine
    take_focus: false
    use_be_runtime: true
    use_eac_runtime: true
    use_runtime: false
    use_steam_runtime: false
    versioning_automatic: false
    versioning_compression: false
    versioning_exclusion_patterns: false
    virtual_desktop: false
    virtual_desktop_res: 1280x720
    vkbasalt: false
    vkd3d: true
    vmtouch: false
    vmtouch_cache_cwd: false
    wayland: false
    winebridge: false
  Path: ''
  Registry_Rules: []
  Runner: sys-wine-10.0
  RunnerPath: ''
  Sandbox:
    share_net: false
    share_sound: false
  State: 0
  Uninstallers: {}
  Update_Date: ''
  VKD3D: vkd3d-proton-3.0
  Versioning: false
  Versioning_Exclusion_Patterns: []
  Windows: win10
  Winebridge: false
  WorkingDir: ''
  data: {}
  run_in_terminal: false
  session_arguments: ''
created: '2026-01-22 21:04:52'
env: application
uuid: 83b27b67-0df5-48af-946d-70cb590db4b3

I would take a screenshot of the runner list, but the widget blocks use of print screen and file upload is failing, so you'll have to take my word for it.

Do i understand it correctly when I assume the above template.yml will not work for sys-wine-11?
Or is it as easy as just copying the uuid from the template and overwriting the folder name?

[Graham--M]

Templates are just cached bottle prefixes so all the dependencies don't need to be setup from scratch each time.

I was puzzled as to how the UUIDs in the template.yml and the folder name could be different until I noticed that bottle prefixes which are setup from a template, contain a copy of template.yml.

It's possible during bottle prefix creation for a template to be used to create the prefix, the prefix then has additional updates, and then the template gets deleted and a new one made from the freshly created prefix.

The template creation is supposed to filter out the .yml files when copying the files from the bottle prefix to the new template but there's a typo that breaks that.

Basically this line is supposed to say:
ignored = ["dosdevices", "states", ".fvs", "*.yml", ".*"]
instead of:
ignored = ["dosdevices", "states", ".fvs", "*.yml.*"]

Normally the .yml files get overwritten anyway, but it looks like the new template.yml didn't get written (maybe due to a crash). If you check the creation date for that template's folder, it probably has a later timestamp than the created: '2026-01-22 21:04:52' from the template.yml you posted.

I think you would be better manually deleting that template's folder to fix your issue because of the old template.yml. It will just take a little longer to create the next new bottle prefix while it makes a new template.

[filson1]

You are correct in your assumption. I very likely did update the components of a bottle related to these 2 runners. At least I do whenever I see one come out.
And deleting the template for sys-wine 10, allowed me to make new bottles for both Wine 11 and Soda 9.

Will you do the nessesary things to register the bug? You seem like you know your way around the application.

[Graham--M]

I don't think there is a separate bug tracker. I'll see if I can submit a PR to try address this.

Just noting for my own reference some issues with the same problem:

• [Bug]: Can't create a bottle #4312
  They don't mention the cause. They try to fix it with mkdir but that just results in an empty bottle that has to be fully set up and the broken template is still there causing issues when it gets remade.
• [Bug]: #4266
  They seem to have had a separate issue with their GPU drivers, and messing with the runner configuration has then lead to a broken template. They don't explicitly mention if bottle creation is failing, but unpacking the template is failing in the log.

Not sure if these older issues are the same problem because they all have USER as the home directory path.

• [Bug]: Seemingly missing template for "Gaming" preset #4004
  They don't say what they did, but they likely fixed the issue by deleting the directory.
• [Bug]: Bottle creation fails when using Games template #3373
  Issue was automatically closed with no resolution.
• [Bug]: Unable to create bottle (no further explanation is given) #3202
  Issue was automatically closed with no resolution.
• [Bug]: Unable to create new application bottle. (crash report) #2798
  Issue was automatically closed with no resolution.