XDG Settings Portal did not return response in time

[donnol]

wsl -v WSL version: 1.2.5.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.3031

$ rustc -V rustc 1.70.0 (90c541806 2023-05-31)

$ cargo -V cargo 1.70.0 (ec8a8a0ca 2023-04-25)

$ cd ../egui/examples/confirm_exit/

$ cargo run Finished dev [unoptimized + debuginfo] target(s) in 0.68s Running /home/jd/Project/jd/egui/target/debug/confirm_exit [2023-06-07T06:22:35Z ERROR sctk_adwaita::config] XDG Settings Portal did not return response in time: timeout: 100ms, key: color-scheme [2023-06-07T06:23:28Z ERROR sctk_adwaita::pointer] Failed to set cursor [2023-06-07T06:23:29Z ERROR sctk_adwaita::pointer] Failed to set cursor

[henryksloan]

WINIT_UNIX_BACKEND="x11" seems to mitigate this, along with the Failed to set cursor messages:

WINIT_UNIX_BACKEND="x11" cargo run

[donnol]

@henryksloan Thanks, it work with your option.

$ WINIT_UNIX_BACKEND="x11" cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.14s
     Running `/home/jd/Project/jd/egui/target/debug/confirm_exit`
段错误

But a segment fault error message displays after close the windows.

[AbhinavGarg90]

WSL version: 2.1.4.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22621.3155

I am getting the same problem.

abhinavgarg@Abhinav-ASUS:~/personal-work/egui/examples/serial_windows$ WINIT_UNIX_BACKEND="x11" cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.16s
     Running `/home/abhinavgarg/personal-work/egui/target/debug/serial_windows`
Starting first window…
[2024-03-17T01:21:39Z ERROR sctk_adwaita::config] XDG Settings Portal did not return response in time: timeout: 100ms, key: color-scheme
^C

This runs, spawns a window with a small black screen, and if i try to close the window I get a segmentation fault. Can't get any of the examples from the repository to run, they all behave as mentioned above.

If I had to guess, it's something to do with missing Linux dependencies. Are they outlined anywhere?

[soucosmo]

Tente adicionar no topo do seu main.rs

![windows_subsystem = "windows"]

[emilk]

If I had to guess, it's something to do with missing Linux dependencies. Are they outlined anywhere?

Yes, here for instance: https://github.com/emilk/egui?tab=readme-ov-file#demo

[shadowInvert]

WSL version: 2.1.5.0 cargo 1.77.1 (e52e36006 2024-03-26) rustc 1.77.1 (7cf61ebde 2024-03-27)

I have satisfied the dependencies written there Are these errors only for people using wsl?

If we focus on examples/hello_world_simple, cargo run -p hello_world_simple

[2024-04-03T09:06:07Z ERROR sctk_adwaita::config] XDG Settings Portal did not return response in time: timeout: 100ms, key: color-scheme
Segmentation fault

in other examples/ cargo run -p custom_keypad

[2024-04-03T09:27:52Z ERROR sctk_adwaita::config] XDG Settings Portal did not return response in time: timeout: 100ms, key: color-scheme
Io error: Broken pipe (os error 32)
Io error: Broken pipe (os error 32)
[2024-04-03T09:27:52Z ERROR arboard::platform::linux::x11] Worker thread errored with: Unknown error while interacting with the clipboard: Connection reset by peer (os error 104)
[2024-04-03T09:27:52Z ERROR arboard::platform::linux::x11] Could not hand the clipboard data over to the clipboard manager: Unknown error while interacting with the clipboard: The X11 server closed the connection
[2024-04-03T09:27:52Z ERROR arboard::platform::linux::x11] Failed to flush the clipboard window. Error: Broken pipe (os error 32)
Io error: Broken pipe (os error 32)
Error: WinitEventLoop(ExitFailure(1))
Segmentation fault

In egui_demo_app, no Error occurs, but WARN keeps appearing many times, and finally Segmentation fault cargo run --release -p egui_demo_app

[2024-04-03T09:46:14Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Default
[2024-04-03T09:46:14Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to EwResize
[2024-04-03T09:46:14Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to EwResize
[2024-04-03T09:46:14Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Default
[2024-04-03T09:46:15Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Default
[2024-04-03T09:46:15Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Pointer
[2024-04-03T09:46:15Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Pointer
[2024-04-03T09:46:15Z WARN  winit::platform_impl::platform::wayland::window::state] Failed to set cursor to Text
loop

[geo-ant]

![windows_subsystem = "windows"]

I'm running into the same problem. Came here to report that neither this nor WINIT_UNIX_BACKEND="x11" helped. My system:

WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.4291 rustc: 1.76.0 cargo: 1.76.0 egui: 0.26

EDIT: same applies for egui 0.27.2, I just updated... UPDATE: same still applies for egui 0.28 and rustc: 1.79.0

[frabul]

I have this issue too in WSL. I workaround is to force winit to use x11 runtime instead of wayland. That can be done by unsetting the environment variable WAYLAND_DISPLAY In code can be done like this. std::env::set_var("WAYLAND_DISPLAY", ""); // Force X11 on Linux