I installed RDM Enterprise on a new ChromeOS device with an i3 CPU. The splash logo pops up but then closes. Nothing else happens.
Are you able to run RDM from a terminal using the remotedesktopmanager command?
That should print some debug ouput hinting us at was is wrong.
Keep in mind, we officially only support Ubuntu for now.
Regards
Jonathan Lafontaine
Here is the output,
xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Mod3, ignoring Lock Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.DllNotFoundException: lib/libWebView.so assembly:<unknown assembly> type:<unknown type> member:(null) at (wrapper managed-to-native) Client.Controls.WebView.NewWebView() at Client.Views.Dashboard.BaseDashboardView..ctor (System.IntPtr handle) [0x00007] in <07af1acce5f745dfba5c26585148f32a>:0 at Client.Views.Dashboard.DashboardRootView..ctor (Gtk.Builder builder) [0x00011] in <07af1acce5f745dfba5c26585148f32a>:0 at Client.Views.Dashboard.DashboardRootView..ctor () [0x0000b] in <07af1acce5f745dfba5c26585148f32a>:0 at Client.Views.Embedded.EmbeddedDashboardView..ctor () [0x00000] in <07af1acce5f745dfba5c26585148f32a>:0 at Devolutions.RemoteDesktopManager.Managers.EmbeddedViewManager.OpenDashboard () [0x00000] in <07af1acce5f745dfba5c26585148f32a>:0 at Client.Windows.MainWindow..ctor (Gtk.Builder builder) [0x0004d] in <07af1acce5f745dfba5c26585148f32a>:0 at Client.Windows.MainWindow..ctor () [0x0000b] in <07af1acce5f745dfba5c26585148f32a>:0 at Devolutions.RemoteDesktopManager.App+<>c.<OnStartup>b__1_0 () [0x00005] in <36b90ddc36d54df4aa1326764d6674cf>:0 at Client.Windows.SplashScreenWindow.DoWork () [0x0000a] in <07af1acce5f745dfba5c26585148f32a>:0 at GLib.Timeout+TimeoutProxy.Handler () [0x00000] in <5a34df7d261240358d61453b6bc52857>:0 at GLib.ExceptionManager.RaiseUnhandledException (System.Exception e, System.Boolean is_terminal) [0x00000] in <5a34df7d261240358d61453b6bc52857>:0 at GLib.Timeout+TimeoutProxy.Handler () [0x00000] in <5a34df7d261240358d61453b6bc52857>:0 at System.Object.wrapper_native_0x792025b48aa0 () [0x00000] in <a17fa1457c5d44f2885ac746c1764ea5>:0 at Gtk.Application.Run () [0x00000] in <c2feb1c5d39a4660b3f5c10dab7825eb>:0 at Devolutions.RemoteDesktopManager.Program.Main (System.String[] args) [0x00000] in <36b90ddc36d54df4aa1326764d6674cf>:0
The most likely reason for this error is ChromeOS is lacking the libwebkit2gtk-4.0 shared lib and related dependencies.
Installing that package will probably fix your issue.
Jonathan Lafontaine
That worked! However when I try to enter our company's enterprise serial number it states the serial number is not valid.
Anything in the terminal output that might be useful concerning that problem?
On my Linux system, your key is passing validation without any issue.
Jonathan Lafontaine
The 3rd time I tried activating it actually worked. The process took about 90 seconds and then showed a message that it activated. Checked the about section and it does show my correct license information. It closes and starts normally. Now to try adding our data source.
This is the output from terminal, this happens every time I start RDM.
xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Mod3, ignoring Lock (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.536: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.565: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.573: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.580: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.585: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): GLib-GObject-CRITICAL **: 10:39:46.592: g_signal_connect_data: assertion 'c_handler != NULL' failed (RemoteDesktopManager:10634): Gtk-CRITICAL **: 10:39:46.648: gtk_entry_set_text: assertion 'text != NULL' failed (RemoteDesktopManager:10634): Gtk-CRITICAL **: 10:39:46.701: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkNotebook xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Mod3, ignoring Lock
Reporting back that our MariaDB data source added successfully. We use a PSK and it asks every time RDM is started. Curious if there is an easier way to keep the data source encrypted while not having to ask for the PSK on every start (this doesn't happen on Windows).
Glad to know RDM is able to run on your chrombook.
Regarding the PSK, there is probably a way, we just haven't got around to it yet.
I'll try to sneak this for the next build.
Jonathan Lafontaine
After some investigative work, we already are saving the PSK in a secure keychain.
RDM uses libsecret to securely save information on disk.
ChromeOS is probably not shipping with libsecret-1-0 installed by default.
Could you try installing that?
Jonathan Lafontaine
libsecret-1-0 along with libsecret-1-dev, libsecret-1-common, and libsecret-1-tools are already installed.
After some investigative work, we already are saving the PSK in a secure keychain.
RDM uses libsecret to securely save information on disk.
ChromeOS is probably not shipping with libsecret-1-0 installed by default.
Could you try installing that?
Could you try this command in a terminal
secret-tool search SourcePassword 'Remote Desktop Manager'
Jonathan Lafontaine
Could you try this command in a terminal
secret-tool search SourcePassword 'Remote Desktop Manager'
Command not found for secret-tool
Weird, secret-tool is part of libsecret-tools and should be available.
Jonathan Lafontaine
I think I know why.
Could you try installing gnome-keyring?
sudo apt-get install gnome-keyring
Jonathan Lafontaine
I think I know why.
Could you try installing gnome-keyring?
sudo apt-get install gnome-keyring
BOOM! That was it. RDM asked to enter in a password to create a key ring. After that I shut it down and started again, didn't ask for a PSK.
These steps should be pinned on the forum.
I am running Chrome OS V 84.0.4147.136 (Official Build) (64-bit) for reference. One step closer for moving away from W10.
Good, glad that is working for you now.
Even if we are still in preview, let us know what features are missing/incomplete/broken so we can focus our efforts on stuff our users use.
Jonathan Lafontaine