You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a workaround of issue #29 , I tried to use Chrome OS's Linux container and run Localsend's AppImage version, to see if port mapping can make Localsend correctly discover local devices. Yet it seems when I launch it, nothing happens. htop shows the process has been started, but there is no UI, no messages, no stdout printing. It would be great if you can let me know how can I diagnose this problem or enable some verbose options to see what's going on.
The text was updated successfully, but these errors were encountered:
That's interesting. I tried to run this AppImage with strace to get some insight on what's happening. It seems a lot of openat calls failed with ENOENT, so perhaps that's some dependency missing? I am not very experienced in Linux app development, so this is just a guess. You can try to diff my log to a log generated when the AppImage version is running as expected. Hope this helps.
I just performed a restart and it's working now. I suppose there might be some temporary problem or incorrect state that got resolved by the restart. Though since the Linux container in Chrome OS is just another container with its seperate network stack and subnet, discovering local devices is still not working. But nonetheless it's indeed working now, so I am closing this issue. Thanks again for your great creation!
As a workaround of issue #29 , I tried to use Chrome OS's Linux container and run Localsend's AppImage version, to see if port mapping can make Localsend correctly discover local devices. Yet it seems when I launch it, nothing happens.
htop
shows the process has been started, but there is no UI, no messages, no stdout printing. It would be great if you can let me know how can I diagnose this problem or enable some verbose options to see what's going on.The text was updated successfully, but these errors were encountered: