bug(startup): 1.0.3 core dump in Xorg session

[yochananmarqos]

Describe the bug

AUR package maintainer here. 1.0.3 fails to start while 1.0.2 launches fine. Log is attached.

EDIT: This only happens on my NVIDIA machine running a GNOME Xorg session . I cannot reproduce on my AMD machine running a GNOME Wayland session.

Expected behavior

N/A

You have a solution?

No response

Provide logs

UAD_20240326.log

Acknowledgements

• This issue is not a duplicate of an existing bug report.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[edgy-b]

Describe the bug

AUR package maintainer here. 1.0.3 fails to start while 1.0.2 launches fine. Log is attached.

EDIT: This only happens on my NVIDIA machine running a GNOME Xorg session . I cannot reproduce on my AMD machine running a GNOME Wayland session.

Expected behavior

N/A

You have a solution?

No response

Provide logs

UAD_20240326.log

Acknowledgements

• This issue is not a duplicate of an existing bug report.
• I have chosen an appropriate title.
• All requested information has been provided properly.

This seems to be related to rust-windowing/winit#2018

[yochananmarqos]

@edgy-b I honestly have no idea how a two year old issue is related. In this case, the GUI never opens.

Also, please don't quote the issue in your reply.

[edgy-b]

@edgy-b I honestly have no idea how a two year old issue is related. In this case, the GUI never opens.

Also, please don't quote the issue in your reply.

Seesh didnt noticed that its so old.
Write issue in winit github, so they can check

[phoropter]

Also using the AUR package, won't launch on Plasma 6 wayland with amd gpu. Errors on launching from CLI:

wl_drm@53: error 0: wl_drm.create_prime_buffer is not implemented
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
warning: queue 0x5de7b5cc3a20 destroyed while proxies still attached:
  wl_registry@56 still attached
Protocol error 0 on object 2024-03-27 08:51:52 ERROR [/home/user/.cache/pikaur/build/universal-android-debloater/src/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/wgpu-hal-0.19.3/src/vulkan/adapter.rs:1790] get_physical_device_surface_capabilities: An unknown error has occurred, due to an implementation or application bug
wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
thread 'Protocol error main0' panicked at  on object /home/user/.cache/pikaur/build/universal-android-debloater/src/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.19.3/src/backend/wgpu_core.rswl_drm:@72453:: 18
:
Error in Surface::configure: Validation Error

Caused by:
    Surface does not support the adapter's queue family
Protocol error 
0note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53: 
Protocol error 0 on object wl_drm@53:

[Frigyes06]

@phoropter Please open a separate issue

@yochananmarqos could you try updating the lockfile to latest and build to see if it got fixed in the meantime?

I opened an issue at winit because they were modifying a lot, but iced could also be at fault.

[yochananmarqos]

@Frigyes06 The Cargo.lock hasn't been touched since the 1.0.3 tag.

[Frigyes06]

@yochananmarqos Can you run uad with xtrace and upload the logs?

[yochananmarqos]

I'm guessing you mean xtrace as in the Debian package? All I have is /usr/bin/xtrace as a part of glibc.

[Frigyes06]

I love it when people name things the exact same. I think it'd be best if you talked directly to the winit guys over at rust-windowing/winit#3616

[AnonymousWP]

Closing this as it's stale. Try v1.1.0.