search

Cathwyler / MagicRemoteService

Use your LG Magic Remote as a Windows mouse and control your PC with the LG Magic Remote from your LG WebOS TV
GNU General Public License v3.0
48 stars 2 forks source link

Error when opening the interface (VPN problem?) #5

Closed Spottyfriend closed 9 months ago

Spottyfriend commented 10 months ago

Everything works fine I think (ie the remote works as a mouse as intended and all the buttons seem to work as I configured them), except that occasionally when trying to open MagicRemoteService's settings, I get this error. I have to reboot my PC, open MagicRemoteService, then click to install it on my TV again. Occasionally I get an error again and have to repeat.

(FYI I am using a VPN, but have enabled passthrough for MagicRemoteService. Maybe I need passthrough on something else?)

image

** Exception Text ** System.IndexOutOfRangeException: Index was outside the bounds of the array. at MagicRemoteService.MacAddressBox.set_Value(PhysicalAddress value) at MagicRemoteService.Setting.TVDataRefresh() at MagicRemoteService.Setting..ctor(Service mrs) at MagicRemoteService.Application.Setting(Object sender, EventArgs e) at System.Windows.Forms.NotifyIcon.OnDoubleClick(EventArgs e) at System.Windows.Forms.NotifyIcon.WmMouseDown(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.NotifyIcon.WndProc(Message& msg) at System.Windows.Forms.NotifyIcon.NotifyIconNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

** Loaded Assemblies ** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

MagicRemoteService Assembly Version: 1.2.0.0 Win32 Version: 1.2.0.0 CodeBase: file:///D:/MagicRemoteService_1.2.0.0/MagicRemoteService.exe

System Assembly Version: 4.0.0.0 Win32 Version: 4.8.9172.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.ServiceProcess Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll

System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.9037.0 built by: NET481REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Cathwyler commented 10 months ago

In some case (VPN connected or something else) the app is not able to get a proper MAC address and ended up with an exception. This error should be corrected in the latest release (1.2.0.1). This is probably linked with your other Wake-on-LAN issue.

Let me know if the new version works fine.

Regards,

Cathwyler

Spottyfriend commented 9 months ago

This version seems to work well regarding this. I don't get the bug and the WoL (on my other issue post) consistently works. Different problem now is that the auto-launch on startup no longer seems to work... I could probably make this work manually through Windows but the checkbox in the interface itself doesn't seem to work anymore

Cathwyler commented 9 months ago

The "Automatically launch at startup" option work through a Windows service. This issue is probably because the Windows service is stopped at start or encountering an error. You can confirme it by checking the MagicRemoteService status in the Windows services list (Win+R and type services.msc).

The option is marked as activated if a Windows service named MagicRemoteService exists regardless of the service status. For a better understanding i will probably make the option uncheked if the Windows service is not running.

When you have these kind of issue the best way is to save again the PC tab in MagicRemoteService settings. When saving the app reconfigure the MagicRemoteService Windows service and the firewall rule.

If you want to change the path of the executable file you need to stop the Windows service in the services list or uncheck "Automatically launch at startup" option and save it. You will be able to move (or delete) the executable file. Once you did it you need to check the option (if not) and save again the PC tab. The Windows service will be reconfigured with the new path.

Please let me know if the auto launch is working again.