[Ruud14]

I am getting the "ERROR: Unable to create GUI. Exiting" Error when trying to run Kodi 18 and 19.
I also tried Kodi 17 but that kept crashing after a few seconds in.
The only version I got to work is "Kodi 16.0ALPHA4 Git:20151026-05c25be".
I simply don't want to use this version anymore because it is way too old and many addons just don't work.
I've tried many solutions from other people but so far none of them worked.
My setup is kind of unique:
I am running Kodi on windows 8 which is in a virtualbox running on a dell r710 server running Ubuntu server.
I am accessing this windows 8 virtualbox using Remote Desktop (mstsc).
I've looked at the error logs and most of the errors are about sound devices not found.
And since it is a virtualbox that is not strange at all.

This is the log file: https://paste.kodi.tv/utipulitod.kodi
*EDITED BY MODERATOR*

[Klojum]

This is the log file

Please adhere to the instructions just above the Post Reply button.

"Do not post logs in the forum. Use https : //paste.kodi.tv/ instead."

[lillymin]

I am getting the "ERROR: Unable to create GUI. Exiting" Error when trying to run Kodi 18 and 19.
I also tried Kodi 17 but that kept crashing after a few seconds in.
The only version I got to work is "Kodi 16.0ALPHA4 Git:20151026-05c25be".
I simply don't want to use this version anymore because it is way too old and many addons just don't work.
I've tried many solutions from other people but so far none of them worked.
My setup is kind of unique:
I am running Kodi on windows 8 which is in a virtualbox running on a dell r710 server running Ubuntu server.
I am accessing this windows 8 virtualbox using Remote Desktop (mstsc).
I've looked at the error logs and most of the errors are about sound devices not found.
And since it is a virtualbox that is not strange at all.

This is the log file: https://paste.kodi.tv/utipulitod.kodi
*EDITED BY MODERATOR*

Good day. I have the same problem. I have tried running Kodi new versions on VmWare Player guest and Hyper-V guest. It does not work. Old XBMC versions do work.
It is odd that I can run new Kodi on low Atom processor tablet but not in virtual guest environment.
From what I understand is that Kodi introduced new graphics handling that left out numerous users. There are many threads on here with the same problem but no solution.
Without solution I need to find another media server like Plex or something. Did not yet test if that works though.

[PatK]

in a virtualbox

Kodi hits some of the hardware directly to be as efficient as possible and utilize gfx routines. @lillymin is correct in this assumption. If you can get into the Kodi interface at all, then there might be the possibility of using an external player. Side note: although it will not likely make any difference to sandboxing or VM machines, the debug logging wasn't turned on.

[lillymin]

Kodi hits some of the hardware directly to be as efficient as possible and utilize gfx routines.

But I think that was a wrong decision from the developers. Virtual machines are getting more and more widespread even for home users. Windows 10 comes with Hyper-V and also in professional environment the move goes into virtual machine direction not the opposite.

[PatK]

that was a wrong decision from the developers

It was an expeditious way to approach the ever changing landscape and complexities that new gfx engines and displays bring to the environment.  You're looking at VM as more of a o/s jack of all trades tool, while HTPC users are entertaining dedicated equipment for optimal performace of their media interests.  Suggestion:-  boot LibreElec off a USB stick?

[Ruud14]

After trying lots of things I finally got rid of the error.
I asked a few questions on the virtualbox forum and posted how I solved it:
https://forums.virtualbox.org/viewtopic.php?f=7&t=94285

Sadly I am now having the same issue I had with kodi v17 which was that it kept crashing a few seconds after opening it saying: "Kodi has stopped working"
Does anyone know a solution for this?

[PatK]

I am now having the same issue I had with kodi v17

 Am I to understand that your issue with Leia (via post 7 linjk) has been worked-out, but now you have an issue with Krypton?

[Ruud14]

I am now having the same issue I had with kodi v17

 Am I to understand that your issue with Leia (via post 7 linjk) has been worked-out, but now you have an issue with Krypton? 

No, I am now having the same error I had with Krypton but now on Leia

[Ruud14]

So my problem now is that a few seconds after starting up kodi it says: "Kodi stopped working".
I read the error logs and there seemed to be a lot of audio related errors, but since this is all running in a vm I didn't have any audio devices.
My solution to this was to create a fake audio device using this https://www.vb-audio.com/Cable/index.htm Software.
It basically mimics a real audio ouput device for me.

Now that those errors were out of the way, I decided to completely reinstall Kodi (With deleting profile folder as well).
After doing that Kodi ran fine for a minute or so and then again: "KodI stOpPeD WorKINg"

So I looked at the error logs again and this is what it said:
https://pastebin.com/WWubPi0N

After saving the log and deleting it from the profile folder I started kodi again and this time kodi crashed immediately with the same "KodI stOpPeD WorKINg" message.
The log is different though and strange enough has no errors in it:
https://pastebin.com/tX5FzMeP

So what should I look for when the log has no errors in it?

[PatK]

Usually the last sequence of entries will give you an idea at what process it's failing. Keep in mind that failures can be triggered much earlier, and only when those routines are put into use, the failure occurs. In your case the first log ERROR: DX:eviceResources::FinishCommandList: failed to finish command queue. indicate a direct X problem. A lot more information will be imparted when you turn on logging and in this case it would be instigated with an advancedsettings.xml file as per https://forum.kodi.tv/showthread.php?tid=323719 Log file/Advanced (wiki)

[Ruud14]

Usually the last sequence of entries will give you an idea at what process it's failing. Keep in mind that failures can be triggered much earlier, and only when those routines are put into use, the failure occurs. In your case the first log ERROR: DX:eviceResources::FinishCommandList: failed to finish command queue. indicate a direct X problem. A lot more information will be imparted when you turn on logging and in this case it would be instigated with an advancedsettings.xml file as per https://forum.kodi.tv/showthread.php?tid=323719 Log file/Advanced (wiki)

First of all, Thank you for doing all this

I enabled the logging, this is the new log file. (I didn't re-install kodi, I just deleted the previous log files)
https://pastebin.com/SMxCbkev

[PatK]

It appears you have a compromised set-up with banned software {repository.exodusredux v0.0.8 installed} forum rules are strick, no support for banned add-ons & repositories. Official:Forum rules/Banned add-ons (wiki) never-the-less your log is not from the portable installation and still displays a virtual set-up.

[Ruud14]

It appears you have a compromised set-up with banned software {repository.exodusredux v0.0.8 installed} forum rules are strick, no support for banned add-ons & repositories. Official:Forum rules/Banned add-ons (wiki) never-the-less your log is not from the portable installation and still displays a virtual set-up.

Oh I'm sorry, I didn't know that was banned, I uninstalled.
What exactly do you mean with portable and virtual set-up?