Open kattsukii opened 2 months ago
I recently compiled it on my system, and it works perfectly, as you can see in this picture. I'm running it on Plasma 6 Wayland [Arch Linux]. I think Vulkan drivers are missing from your system. Check it first!
Thanks for the explanation and try-out, theskpaul. 🙂
I had same problem in Windows 11, with an "INVALID PARAMETER", only .000040 sec execution time
It does need remote SSL inquires validation to checksum? because i got problem with openssl SSL validation
I have the exact same issue
OS: Fedora 40 Silverblue
❯ rpm-ostree status -b
State: idle
BootedDeployment:
● fedora:fedora/40/x86_64/silverblue
Version: 40.20240902.0 (2024-09-02T00:42:54Z)
BaseCommit: 14a2faa512f11119ddbf672b4014c55a2658498be14d44812a47fcb663c4b7e8
GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
RemovedBasePackages: firefox firefox-langpacks 129.0.2-1.fc40
LayeredPackages: akmod-nvidia android-tools distrobox gnome-tweaks gparted kernel-tools kitty printer-driver-brlaser rpmfusion-free-release rpmfusion-nonfree-release starship steam-devices tailscale
xboxdrv xorg-x11-drv-nvidia xorg-x11-drv-nvidia-cuda
this is from $HOME/.cache/uad/UAD_20240904.log
2024-09-04 18:38:13 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:38:13 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:38:13 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
2024-09-04 18:40:56 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:40:56 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:40:56 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
2024-09-04 18:43:12 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/egl.rs:268] No config found!
2024-09-04 18:43:12 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/egl.rs:257] EGL says it can present to the window but not natively
2024-09-04 18:43:12 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:43:12 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:43:12 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:20 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/egl.rs:268] No config found!
2024-09-04 18:44:20 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/egl.rs:257] EGL says it can present to the window but not natively
2024-09-04 18:44:20 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:44:20 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:20 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:37 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:44:37 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:37 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:56 DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-09-04 18:44:56 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
2024-09-04 18:44:56 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
I ran it using the iGPU and then dGPU (just in case)
(edit) forgot to add vulkaninfo, Silverblue comes with vulkan by default
here's vulkaninfo
@rscm I collapsed vulkaninfo
because it was extremely long!
Thank you for the debug info, but it was hard to scroll this page 😅
Could this be related to the back-end that iced
uses? Could you try compiling it with a new version of iced
?
@rscm I collapsed
vulkaninfo
because it was extremely long!Thank you for the debug info, but it was hard to scroll this page 😅
sorry I didn't knew that markdown syntax. I will use it from now on. Sorry again.
It seems it's a GH MD "flavor" non-standard HTML extension (such as <img>
)
Uuum.. I'm having this problem as well.
`2024-09-13 22:50:37 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/adapter.rs:774] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears. 2024-09-13 22:50:37 WARN [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/gles/adapter.rs:774] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears. wp_linux_drm_syncobj_manager_v1#71: error 0: surface already exists Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71: Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71: Protocol error 0 on object wp_linux_drm_syncobj_manager_v12024-09-13 22:50:37 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR @71: Protocol error 0 on object wp_linux_drm_syncobj_manager_v12024-09-13 22:50:37 ERROR [/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR @71: thread 'mainProtocol error ' panicked at 0/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.19.3/src/device/global.rs on object :wp_linux_drm_syncobj_manager_v11859@:7121: :
internal error: entered unreachable code: Fallback system failed to choose present mode. This is a bug. Mode: AutoVsync, Options: []Protocol error
0note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@71:`
I'm on:
Operating System: Solus 4.5 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.8-301.current (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10300H CPU @ 2.50GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: GF65 Thin 10SDR System Version: REV:1.0
related to the back-end that
iced
uses?
Maybe:
Hmm, I see that users say that it works with wgpu
removed: https://github.com/iced-rs/iced/issues/2562#issuecomment-2322787586. Should we offer builds with and without wgpu
if that's possible?
related #556
builds with and without
wgpu
if that's possible?
We should try:
wgpu
I have the same issue on arch linux. This is the log:
2024-10-10 21:12:45 WARN [/home/benia/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.4/src/gles/adapter.rs:774] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
2024-10-10 21:12:45 WARN [/home/benia/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.4/src/gles/adapter.rs:774] Detected skylake derivative running on mesa i915. Clears to srgb textures will use manual shader clears.
wp_linux_drm_syncobj_manager_v1#61: error 0: Surface already has a syncobj attached
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 2024-10-10 21:12:46 ERROR [/home/benia/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.4/src/vulkan/adapter.rs:1824] get_physical_device_surface_present_modes: ERROR_SURFACE_LOST_KHR
0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
2024-10-10 21:12:46 ERROR [/home/benia/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.4/src/vulkan/adapter.rs:1839] get_physical_device_surface_formats: ERROR_SURFACE_LOST_KHR
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@thread '61main: ' panicked at
/home/benia/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.19.4/src/device/global.rsProtocol error :01859 on object :wp_linux_drm_syncobj_manager_v121@:
61internal error: entered unreachable code: Fallback system failed to choose present mode. This is a bug. Mode: AutoVsync, Options: []:
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Protocol error 0 on object wp_linux_drm_syncobj_manager_v1@61:
Describe the bug
Download the latest version, then run it.
the message i get after i run it
Expected behavior
to run
You have a solution?
No response
Operating System
Linux
Window Manager
Wayland
Desktop Environment
GNOME 46.4, fedora 40, rustc: 1.81.0 (eeb90cda1 2024-09-04), cargo: 1.81.0 (2dbb1af80 2024-08-20), rust-analyzer: 2024-09-09
Provide logs
Acknowledgements