Skip to content
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

"Can't query network for available connections, network not selected" on chromeos flex #74

Open
Wallby opened this issue Aug 4, 2024 · 9 comments
Labels
enhancement New feature or request unlikely to do Unlikely to be implemented waiting for more votes

Comments

@Wallby
Copy link

Wallby commented Aug 4, 2024

Description

The message between quotation marks in the title is shown on chromeos flex version 127.0.6478.222 when pressing this button.. image

image

Cursr version 1.7.2 installed from .deb.

@Wallby
Copy link
Author

Wallby commented Aug 4, 2024

Also on opening cursr I got this warning and error..

image

@ragauskl ragauskl added enhancement New feature or request unlikely to do Unlikely to be implemented waiting for more votes labels Aug 4, 2024
@ragauskl
Copy link
Contributor

ragauskl commented Aug 4, 2024

That will likely be because it's chromeos and that's not supported. Only Windows, macOS and Linux (X11, and work in progress on wayland).

The errors you're seeing:

  • "...network not selected" - This is because no supported LAN network ranges have been detected, you can try using ZeroTier to create a LAN if it's simply issue with network range, however another possibility that underlaying module simply can't retrieve network information on chromeos in which case it's OS support issue.
  • "Unsupported Platform" - If it's not Windows, macOS or supported Linux it defaults to 'Linux' behaviour (also therefore the unexpected error below it) and error message, error message should not say 'Linux desktop environment' but that's a minor issue not worth fixing as chromeos is not supported anyways. Looks like chromeos is returning 'linux' for platform and the X-Generic is ORIGINAL_XDG_CURRENT_DESKTOP environment variable therefore the message.

When downloading Cursr you should have seen that there's no build/download for chromeos. As this is not in demand right now I don't have plans to add support or it, but I'll leave this issue open so people can upvote it and if there will be enough interest/thumbs up on this issue I'll consider adding it, but I don't think there will be many requiring support for chromeos so it's unlikely to happen.

@Wallby
Copy link
Author

Wallby commented Aug 9, 2024

When downloading Cursr you should have seen that there's no build/download for chromeos. As this is not in demand right now I don't have plans to add support or it, but I'll leave this issue open so people can upvote it and if there will be enough interest/thumbs up on this issue I'll consider adding it, but I don't think there will be many requiring support for chromeos so it's unlikely to happen.

There shouldn't have to be any support for ChromeOS Flex, because it installs .deb files in a vm, thus it is a matter of linux support, not specifically ChromeOS Flex support.

@ragauskl
Copy link
Contributor

ragauskl commented Aug 9, 2024

Could be but it's still a support issue as Linux environments vary much more than Windows and macOS do. I did look into why ChromeOS Flex was being detected as Linux I did notice that it's Linux based, so what you say does make sense, however it is 'X-Generic' which still is not officially supported. Note that it was not on my radar/I'm lacking the knowledge of ChromeOS because I or anyone I know never used one (except for very short time long ago I had very limited chromebook) indicating a too low demand. Currently Linux is <5% of users, those using ChromeOS Linux will probably be way less than even 1%

I have a pending update to website which indicates that only X11 and Gnome desktop combinations are officially supported for now. Wayland and KDE support is work in progress. 'X-Generic' from what I understand is just a generic term probably indicating that it's using X window system meaning:

  1. This is good meaning that there's no issue with input control/monitoring (unlike Wayland making adding support for it much more complex).
  2. The error 'org.freedesktop.secrets' indicates that system does not have Gnome secrets storage and Cursr can't store license and user session for longer than single session. KDE has similar issue which I'll be fixing in near future/before Wayland, so it may get fixed for 'X-Generic' chromeos as well.
  3. The issue with network still persists, Cursr currently only supports LAN ranges 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 so you either need to have that available on your device or use ZeroTier to put both devices on one of these network ranges. If this will solve the issue then it's just a network setup issue, however if this still does not work means that underlaying node.js library can't query/retrieve network information which could be a support issue in a 3rd party package and I would need to add a custom implementation.

@Wallby
Copy link
Author

Wallby commented Sep 11, 2024

Turns out ChromeOS has a port forwarding settings menu for enabling ports for the linux virtual environment.

image

Does Cursr require any specific ports?

@ragauskl
Copy link
Contributor

ragauskl commented Sep 11, 2024

Yeap, by default UDP 61650 for discovery of other peer instances and 4440 for TCP and UDP communications between devices - can change both in Virtual Switch setting section. However this won't resolve the 'network not selected' issue as Cursr doesn't see on which network it should bind to those ports.

If you or anyone else by any chance can test node.js os package function 'os.networkInterfaces()' on chromeos flex and let me know what it returns, that could help identify if it's node.js issue or is it issue with Cursr code - sooner than I may be able to start looking into this issue.

But first check if any of the supported networks from my previous message are available on your device. If they are not than that will be the issue as Cursr doesn't support other network types for now (but can be worked around with ZeroTier or other similar solution).

@Wallby
Copy link
Author

Wallby commented Sep 17, 2024

The ports alone did not work. I noticed this in the settings (pressing "Reload Network" did nothing)..

clipboard_2024-09-17_15-33

@ragauskl
Copy link
Contributor

That's because there are no networks that Cursr can find. The Reload Network only works/is needed if you detected new network/connected to new wifi or ethernet and don't see the network on the dropdown list.

@ragauskl
Copy link
Contributor

As mentioned above:

If you or anyone else by any chance can test node.js os package function 'os.networkInterfaces()' on chromeos flex and let me know what it returns, that could help identify if it's node.js issue or is it issue with Cursr code - sooner than I may be able to start looking into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request unlikely to do Unlikely to be implemented waiting for more votes
Projects
None yet
Development

No branches or pull requests

2 participants