Latency issues on Linux #17
Comments
|
Do you have an XDG Desktop Portal implementation installed? |
|
Yes, I have XDG Desktop Portal installed. |
|
xdg-desktop-portal doesn't do anything by itself; you need one of the backend implementations (xdg-desktop-portal-gtk or xdg-desktop-portal-kde). |
|
I also have xdg-desktop-portal-gtk installed. I also installed xdg-desktop-portal-kde and this did not change the latency. If it helps, I start i3 using xinit. |
That's likely the problem. Normally when logging in with a display manager, systemd starts the xdg-desktop-portal service. |
|
Is it possible to support graceful failure in the event of xdg-desktop-portal not being started? I'm not familiar enough with d-bus to know whether this is possible. |
|
zbus doesn't have a convenient API to set a maximum timeout, but it looks like that is possible. |
|
There is already a zbus issue for that. |
|
This could be alleviated by switching to an async API: #10 (review) |
|
zbus author here. 👋
Correct. Runtimes provide timeout API already and since the async API is the recommended one, the priority for adding this feature got lowered with 2.0 when we switched to async being the primary API in 2.0. |
|
My vote would be for adding an async API. I briefly looked over the PR - is there a way I can contribute to it? |
dark-light has a nasty problem on Linux: frewsxcv/rust-dark-light#17 So we made dark-light opt-in in #1437 This PR makes dark-light a default dependency again, but only use it on Max and Windows. This is controlled with the new NativeOptions::follow_system_theme. If this isn't enabled, then NativeOptions::default_theme is used.
* Use dark-light on Mac and Windows dark-light has a nasty problem on Linux: frewsxcv/rust-dark-light#17 So we made dark-light opt-in in #1437 This PR makes dark-light a default dependency again, but only use it on Max and Windows. This is controlled with the new NativeOptions::follow_system_theme. If this isn't enabled, then NativeOptions::default_theme is used. * Add eframe::WebOptions
There are significant latency issues when calling
detecton Arch Linux using i3. D-bus times out waiting for freedesktop to respond, which results in a 25 second latency.The text was updated successfully, but these errors were encountered: