2015-01-25, 01:42
VIA NOT VID 
Kodi not xbmc
Just tried to launch xbmc in a window (for upnp use only) via rdp and it states it can't create the gui. So I decided this was due to rdp being shit, and therefore added a delay to xbmc via the -d x command.
I added a 120second delay to xbmc launch. Clicked the short cut, exited the rdp session, and to my amazement, xbmc will wait 120seconds and still fail with the same error? Is this because it was "launched" within an RDP session, even though the session was subsequently disconnected and closed?
Can I launch xbmc from a RDP session at all?
I don't actually want to use it or navigate it, or change settings etc. I just want it to start it lol
Its already set to share via upnp... Problem is I can't start it up without actually physically being in front of it? It works fine if I go over to it and launch it normally.
But launching it in an RDP with a 2 minute delay and exiting the RDP sessions and closing all RDP sessions/connections it still fails with the same error, until I go over and click it manually?
Is there a way to just launch it remotely or are we physically tethered to it?
Kodi not xbmc
Just tried to launch xbmc in a window (for upnp use only) via rdp and it states it can't create the gui. So I decided this was due to rdp being shit, and therefore added a delay to xbmc via the -d x command.
I added a 120second delay to xbmc launch. Clicked the short cut, exited the rdp session, and to my amazement, xbmc will wait 120seconds and still fail with the same error? Is this because it was "launched" within an RDP session, even though the session was subsequently disconnected and closed?
Can I launch xbmc from a RDP session at all?
I don't actually want to use it or navigate it, or change settings etc. I just want it to start it lol
Its already set to share via upnp... Problem is I can't start it up without actually physically being in front of it? It works fine if I go over to it and launch it normally.
But launching it in an RDP with a 2 minute delay and exiting the RDP sessions and closing all RDP sessions/connections it still fails with the same error, until I go over and click it manually?
Is there a way to just launch it remotely or are we physically tethered to it?
