[Bug]: Creating a bottle hangs on wine config is being updated when permissions are missing

[bowlofeggs]

Describe the bug

I am unable to create a bottle with a new install from flathub. It hangs with the GUI saying "The Wine config is being updated…":

The console logs don't seem to indicate what it might be doing.

I don't see a lot of cpu/network activity with htop/btm. I'm not sure what it's waiting on.

I later discovered that this seemed to be a permissions issue. I added the user who was running bottles to more groups, and then they were able to get past this step.

It would be better if permission errors were logged instead of hanging.

To Reproduce

1. On a new install, create a bottle in an account that is in only the Linux "users" group. I tried a few variations, like using a different engine, or using the application-style vs. gaming style, but it seems to hang either way.

Package

Flatpak from Flathub

Distribution

Gentoo

Debugging Information

Official Package: true
Version: '51.18'
DE/WM: gnome
Display:
    X.org: true
    X.org (port): :2
    Wayland: true
Graphics:
    vendors:
        intel:
            vendor: intel
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/intel_icd.x86_64.json:/usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/intel_hasvk_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/intel_icd.i686.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/intel_hasvk_icd.i686.json
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.12.15-gentoo-dist
Disk:
    Total: 33447133184
    Free: 33446961152
RAM:
    MemTotal: 62.3GiB
    MemAvailable: 55.3GiB
Bottles_envs: null

Troubleshooting Logs

$ flatpak run com.usebottles.bottles

(process:2): GLib-GIO-WARNING **: 22:14:06.121: Can't find module 'dconf' specified in GSETTINGS_BACKEND
22:14:06 (INFO) Launching with URI: None 
22:14:06 (INFO) [Activate] request received. 
22:14:06 (INFO) Bottles Started! 
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:782: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:814: FINISHME: support more multi-planar formats with DRM modifiers
22:14:08 (ERROR) Data file not found. Creating new one. 
22:14:12 (INFO) Performing Bottles checks… 
22:14:12 (INFO) Runners path doesn't exist, creating now. 
22:14:12 (INFO) Runtimes path doesn't exist, creating now. 
22:14:12 (INFO) WineBridge path doesn't exist, creating now. 
22:14:12 (INFO) Bottles path doesn't exist, creating now. 
22:14:12 (INFO) Dxvk path doesn't exist, creating now. 
22:14:12 (INFO) Vkd3d path doesn't exist, creating now. 
22:14:12 (INFO) Nvapi path doesn't exist, creating now. 
22:14:12 (INFO) Templates path doesn't exist, creating now. 
22:14:12 (INFO) Temp path doesn't exist, creating now. 
22:14:12 (INFO) LatencyFleX path doesn't exist, creating now. 
22:14:12 (INFO) Runners found:
	 - sys-wine-9.0
 
22:14:12 (WARNING) Library file not found, creating new one 
22:14:12 (INFO) Library saved 
22:14:13 (INFO) Catalog dependencies loaded 
22:14:13 (INFO) Catalog installers loaded 
22:14:15 (INFO) Catalog components loaded 
22:14:17 (INFO) Performing Bottles checks… 
22:14:17 (WARNING) No dxvk found. 
22:14:21 (INFO) Installing component: [dxvk-2.5.3]. 
dxvk-2.5.3.tar.gz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (9.4MiB/9.4MiB - 9.0MiB)

22:14:22 (INFO) Renaming [dxvk-2.5.3.tar.gz] to [dxvk-2.5.3.tar.gz]. 
22:14:22 (INFO) Dxvks found:
	 - dxvk-2.5.3
 
22:14:22 (INFO) Component installed: dxvk dxvk-2.5.3 
22:14:22 (WARNING) No vkd3d found. 
22:14:27 (INFO) Installing component: [vkd3d-proton-2.14.1]. 
vkd3d-proton-2.14.1.tar.gz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (2.8MiB/2.8MiB - 7.5MiB)

22:14:28 (INFO) Renaming [vkd3d-proton-2.14.1.tar.gz] to [vkd3d-proton-2.14.1.tar.gz]. 
22:14:28 (INFO) Vkd3ds found:
	 - vkd3d-proton-2.14.1
 
22:14:28 (INFO) Component installed: vkd3d vkd3d-proton-2.14.1 
22:14:28 (WARNING) No nvapi found. 
22:14:30 (INFO) Installing component: [dxvk-nvapi-v0.8.0]. 
dxvk-nvapi-v0.8.0.tar.gz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (3.3MiB/3.3MiB - 8.7MiB)

22:14:32 (INFO) Renaming [dxvk-nvapi-v0.8.0.tar.gz] to [dxvk-nvapi-v0.8.0.tar.gz]. 
22:14:32 (INFO) Nvapis found:
	 - dxvk-nvapi-v0.8.0
 
22:14:32 (INFO) Component installed: nvapi dxvk-nvapi-v0.8.0 
22:14:32 (WARNING) No latencyflex found. 
22:14:37 (INFO) Installing component: [latencyflex-v0.1.1]. 
latencyflex-v0.1.1.tar.xz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (372.0KiB/372.0KiB - 2.7MiB)

22:14:37 (INFO) Renaming [latencyflex-v0.1.1.tar.xz] to [latencyflex-v0.1.1.tar.xz]. 
22:14:37 (INFO) Component installed: latencyflex latencyflex-v0.1.1 
22:14:38 (WARNING) No WineBridge found. 
22:14:38 (INFO) Installing component: [winebridge-1.1.0]. 
WineBridge-eb78a75.tar.xz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (3.3MiB/3.3MiB - 8.2MiB)

22:14:39 (INFO) Renaming [WineBridge-eb78a75.tar.xz] to [WineBridge-eb78a75.tar.xz]. 
22:14:39 (INFO) Component installed: winebridge winebridge-1.1.0 
22:14:39 (INFO) Runners found:
	 - sys-wine-9.0
 
22:14:39 (WARNING) No managed runners found. 
22:14:43 (INFO) Installing component: [soda-9.0-1]. 
soda-9.0-1-x86_64.tar.xz (100%) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (59.1MiB/59.1MiB - 8.0MiB)

22:14:51 (INFO) Renaming [soda-9.0-1-x86_64.tar.xz] to [soda-9.0-1-x86_64.tar.xz]. 
22:14:55 (INFO) Runners found:
	 - soda-9.0-1
	 - sys-wine-9.0
 
22:14:55 (INFO) Component installed: runner soda-9.0-1 
22:15:07 (INFO) Generating bottle configuration… 
22:15:07 (INFO) Using Wine Runtime tool -- send_status(-i) 
22:15:07 (WARNING) Bottles runtime was requested but not found 
wineserver: using server-side synchronization.
wine: configuration in L"/home/games/.var/app/com.usebottles.bottles/data/bottles/bottles/Epic" has been updated.

Additional context

No response

[bowlofeggs]

I discovered that adding the user who was running bottles to more system groups allowed the bottle creation to succeed.

I do think there is still a bug and/or improvement to be made here, however, as the program should log a permission error rather than hanging indefinitely. That would have made the group membership issue easier to discover.