-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome OS support #37
Comments
Disabling individual features does not seem to be possible as of now: There is two Options:
cargo build --release --no-default-features --features wayland,x11,xdg_desktop_portal
|
If you could tell me what Distro you're using, I may be able to help you with getting libadwaita installed. |
Sorry I overlooked chrome os. |
Do you have an update on this? |
I tried running in a Crostini container (with libadwaita-1-0 installed) and got this:
|
You are on a Chromebook as well? |
Yeah (don't think Crostini exists anywhere else). I compiled the binary on a more powerful linux host and copied over the binary - I assume that doesn't matter. |
Could you run For input capture either the I would not get my hopes up too much that any of this works in Chrome OS unfortunately. |
I don't really have my hopes up for ChromeOS. But I am interested in the rest of the operating systems, especially Linux+MacOS. If I can help debug integration any there let me know. |
gtk_shell1 might be a valid fallback for layer_shell but at least zwp_keyboard_shortcuts_inhibit_manager_v1 would still be required to do anything useful.
Will do :) Still in pretty early development. |
sorry i dropped out a bit, i layed off trying to control my chromebooks for a bit, but i'm still interested and will get back to testing. |
Cheers! At least rudimentary input capture should always be possible through an application window. I feel Iike input emulation might be the bigger problem |
Is this what you were asking about, @feschber ?
I thought that the remote desktop portal was something to be installed. Surprisingly I do have xdg-desktop-portal-gtk and xdg-desktop-portal installed. Wondering if switching to the KDE version would be helpful, though when I set the current desktop to gnome I get the exact same output. @bpstrngr I thought crosh was restricted to executing Chrome management utilities. You're saying there's a way to run scripts/binaries in that environment? |
It must be capital KDE, what you want is the xdg-desktop-portal backend |
|
Can you rerun this with LAN_MOUSE_LOG_LEVEL=debug? |
CLI run
|
Okay, seems like I need to add some more debug information first. |
@jpeeler you can try the latest main now. I added a fallback interface so it does not crash before we know whats going on. |
(Using a6ab109).
|
Okay seems like the remote desktop portal is not available. XTest likely wont work either. |
This Gtk-CRITICAL error is because I had used widgets from libadwaita-1.4 (accidentally). If you try the latest main, you may be able to get the gui to launch. |
Yep, I was compiling against libadwaita-rs 0.5.2. The GUI does indeed launch, which is nice. |
Something I just wondered - do you know of any necessary portal versions that are required to get things to work? This linux container I'm testing with is running Debian 12. The KDE portal is 5.27.5, which seems to be around 7 months old. But maybe everything that is required has been implemented for a while and the problem is more so on the ChromeOS wayland side. |
For input emulation only the remote desktop portal is required. (org.freedesktop.portal.RemoteDesktop). Do I understand correctly that you are running KDE on a Linux container in ChromeOS? Can you check the output of |
The xdg-desktop-portal package is 1.16.0, which is about 12 months old. And I realized that I only had the -gtk portal installed earlier. However, it doesn't change the result all that much. I am not running KDE as a desktop environment on ChromeOS if that's what you're asking. But am using their packages to run various apps (such as VLC).
I don't understand why the KDE portal is not listed though. |
found the time to test this too, starting from the point where you taught me how to opt out of libadwaita, i compiled with
The thing i can add, for what it's worth, is what happens outside crostini, on the host chromeos shell:
or, when built with "x11,xdg_desktop_portal" features included:
(been down the rabbit hole of building/copying such libs individually, in this case i assume the list would be long, so i just didn't include these features, X11 will certainly be ever foreign to the native chromeos shell). |
Oh, and mind you, i had to checkout the v0.3.3 tag, because on the latest main, and several commits back,
|
ChromeOS would need to support either
And either
Neither of which is very likely to happen anytime soon. The error you are seeing is because xdg-output That would lead to the next error though, which is that wlr-layer-shell is not supported. So in short the options to get input capture working are:
For input emulation I have less hope other than chromeos supporting either xdg remote desktop or Libei at some point. The other error you are seeing is very peculiar and seems to be an issue with cargo on chromeos. With that the GUI should now launch as well. |
trying to test this in a graphically rather limited wayland environment (chrome os), and i worked through a few errors to satisfy the gui dependencies, but libadwaita being a more complicated one, I'm just wishing for a way to opt out of building the gui and rely on the cli only:
![image](https://private-user-images.githubusercontent.com/26650418/285683898-4d7c3b56-f554-41dd-8d85-4a1597852bea.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk4MTgwNDYsIm5iZiI6MTcxOTgxNzc0NiwicGF0aCI6Ii8yNjY1MDQxOC8yODU2ODM4OTgtNGQ3YzNiNTYtZjU1NC00MWRkLThkODUtNGExNTk3ODUyYmVhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAxVDA3MDkwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJhMDM1NzhkMGNmODg1MjFjMjdjNWJlZWU2YmE3OWYwMTBlOGVjZWQ1ODQ0N2ZlYTc0NGI1MTM4YjRmNjlmMzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.3e4EryAUscU5zPs8rIRhpw1WJNG3waFdtQ15oLdcaQs)
is it already available just not mentioned in the readme?
Sorry if it could be determined with more familiarity with cargo toolchains.
Thanks!
The text was updated successfully, but these errors were encountered: