Error unable to create gui exiting kodi что это - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Error unable to create gui exiting kodi как исправить
Error unable to create gui exiting kodi как исправить
Quick Links
Sponsors
About Kodi
Error unable to create gui exiting kodi как исправить
Quick Links
Sponsors
About Kodi
Error unable to create gui exiting kodi как исправить
How To Fix Kodi 17 Unable To Create GUI Error On Windows 10

Error unable to create gui exiting kodi как исправить

kcarney
Member

So I just upgraded from 17.6 to 18.1 and the Error: Unable to create GUI. Exiting pops up when attempting to launch kodi via RDP. This is a VM running on ESXI 6.7 that I use solely for database maintenance and library updates to SQL.

If I connect to the VMConsole kodi will launch fine, any tweaks I can make to the VM hardware that might help?

u could try if next link has influence Enabling GPU rendering on Windows Server 2016 / Windows 10 RDP if u don’t like group objects, u could try next link Use hardware graphics adapters for all Remote Desktop Services sessions which shows the registry key for it.
Btw i checked my own pc’s registry for this key i don’t have it on my windows 10 machine (whom is acting as rdp server through rdp wrapper) so don’t really know if it will help.

Just reading up, cause your question gotten me interested. The next link points to information about udp ports How to improve Remote Desktop performance for remote users through an RDS Gateway Server .

Just found on a thread about acceleration:
«one thing you should keep in mind if your rdp settings are too low the acceleration is turned off.
in my experience if you want acceleration to work normally you need 32bit color (Depending on your app this could be lowered) and set the connection speed to LAN.». In my own setup i’ve it both on autodetect but effectivly it means i get highest display and bandwith settings, so it could matter.

Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2 might also contain some clues. As for example RemoteFX cannot be used and such.

Источник

Error unable to create gui exiting kodi как исправить

ashfallen0
Junior Member

(Previously fully-functioning system)
APT system update caused the following behavior:
system boots,
KODI splash,
Blank screen.
ssh into server, no running instance of kodi.bin
calling kodi from commandline produces:
ERROR: Unable to create GUI. Exiting

uname -a:
Linux ubuntu 3.13.0-87-generic #133-Ubuntu SMP Tue May 24 18:32:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

ashfallen0
Junior Member

I’m seeing the same error:

14:39:22 T:140537396340736 ERROR: GLX Error: No Display found
14:39:22 T:140537396340736 FATAL: CApplication::Create: Unable to init windowing system

This may be xorg related during update rather than kodi.

Theme by Mishar DESIGN, modded by Team Kodi

Quick Links

About Kodi

Kodi is a free and open source media player application developed by the XBMC Foundation, a non-profit technology consortium.

Kodi is available for multiple operating-systems and hardware platforms, featuring a 10-foot user interface for use with televisions and remote controls. It allows users to play and view most videos, music, podcasts, and other digital media files from local and network storage media and the internet.

Источник

Error unable to create gui exiting kodi как исправить

Rockeily
Member

(2017-11-19, 17:09) RENATOLORETO Wrote: When I try to obtain updated video drivers systems says thzat I have the lates version of drivers.

tom886
Junior Member

(2017-12-21, 08:46) nickr Wrote: Make sure you get the drivers from the video card/motherboard manufacturer, not microsoft.

Or much better, directly from the Graphic card vendor, e.g. Intel, AMD, NVDIA

Theme by Mishar DESIGN, modded by Team Kodi

Quick Links

About Kodi

Kodi is a free and open source media player application developed by the XBMC Foundation, a non-profit technology consortium.

Источник

Error unable to create gui exiting kodi как исправить

You did not get the advancedsettings.xml part right as debug mode was not enabled. You need to save the file here. C:UsersRONAppDataRoamingKodi

There is definitely a problem with either your hardware or your installed drivers as you can see by the errors at Line 185. I do note that your CPU and integrated graphics is 7+ years old, so most likely not fully compatible with Win 10. Did you locate the manufacturers drivers?

Dolphus70
Newbie

(2020-04-03, 07:22) Dolphus70 Wrote: I made a file called advancedsettings.xml as well, but nothing happened to that, still empty

And it will remain empty until you add something into it. Once you create the file, open it and paste into it the code that is in step 3 of that guide.

You cannot send me the log file. You need to paste the link into your post like you did for the first log.

Dolphus70
Newbie

(2020-04-03, 09:18) Dolphus70 Wrote: Im sorry Karellen, i’m not quiet sure of what your trying to tell me, «Once you create the file» (what file)

Did you read the instructions that I gave you?

Can you press the Start button in Windows and type dxdiag and run the app. Are there any errors? What is the DirectX Version in use? What DirectX Features are enabled?

But I am not sure what else we can do until those drivers are fixed. You might need to hop onto the AMD forums and ask why the drivers do not install.

Your onboard video card and/or its driver seems to be the culprit. It is getting a bit dated.
It worked well on Krypton but does not on Leia.
As a last resort, I would look at any potential DX error by doing:

WinKey and r
In the run box type in: dxdiag and press enter. Wait a bit, it will eventually do something.
Look for any error on any pane pertaining to video. Report back if any error.

Finally, on the shortcut with which you start Kodi,If started from the Win 10 menu :
1- Right click on Kodi icon then More then Open file location.
You will have in front of you a folder with the true shortcut to Kodi
2- Right click on that Kodi shortcut. Select Properties
On the top of the pane, select Compatibility, you can run the compatibility troubleshooter or modify the compatibility mode to Windows 7, 8 and others.
Try to launch Kodi after the changes.
Note if you start Kodi from a shortcut on the desktop, skip #1

I must warn you that I have little faith in this effort as the hardware used is simply not up to par.
But I hope to be wrong.

Dolphus70
Newbie

(2020-04-03, 09:18) Dolphus70 Wrote: Im sorry Karellen, i’m not quiet sure of what your trying to tell me, «Once you create the file» (what file)

Did you read the instructions that I gave you?

Can you press the Start button in Windows and type dxdiag and run the app. Are there any errors? What is the DirectX Version in use? What DirectX Features are enabled?

But I am not sure what else we can do until those drivers are fixed. You might need to hop onto the AMD forums and ask why the drivers do not install.

Dolphus70
Newbie

WinKey and r
In the run box type in: dxdiag and press enter. Wait a bit, it will eventually do something.
Look for any error on any pane pertaining to video. Report back if any error.

I must warn you that I have little faith in this effort as the hardware used is simply not up to par.
But I hope to be wrong.

Источник

How To Fix Kodi 17 Unable To Create GUI Error On Windows 10

Here’s a guide on how you can fix Kodi 17 / 17.3 Unable to create GUI error on your PC running Windows 10.

Kodi is one of the fastest growing platforms on the market at the moment with hundreds of thousands of users taking the opportunity to get onboard with the platform for their various device types. Downloading and installing Kodi 17 instantly gets access to all of the goodies and the features contained within, but it also brings a few bugs and known issues which produce error messages and cause confusion. The “ERROR: Unable to create GUI. Exiting” is one of those errors, and we are going to show you how to fix it.

Powerful platforms like Kodi are always extremely enjoyable until you run into problems. Unfortunately, most users are unable to actually effectively troubleshoot problems that they don’t understand, and information can sometimes be thin on the ground on the Internet. That is where we come in with a simple-to-follow walkthrough on how to resolve this particular problem.

Step 1: On the Windows PC, right-click on the This PC icon which represents the main machine and then select Properties.

Step 2: Select Device Manager from the list on the left-hand side and then select the Display adapters option to drop it down.

Step 3: Right-click on the listed graphics adapter and select the Properties option from the contextual menu that appears.

Step 4: From within that menu, select the Driver tab at the top of the window and then select Update Driver button.

Step 5: When the new window appears, make sure to select to search automatically for the driver updates. This will search for the best available software update. When the driver has been installed, exit out of the Device Manager.

Step 6: Load up the Kodi installation and you should have a more positive experience.

This resolution should hopefully get you up and running with Kodi 17 or 17.3 instantly without any further fuss or issue. It may be that additional problems occur down the line, but where this particular issue is concerned that should be sorted for the long haul. Enjoy the Kodi experience, and make sure to take full use of its power and functionality.

Kodi Unable to Create GUI Error SOLVED: How I Fixed It

I recently tried to launch Kodi 17.6 Krypton on my Windows 10 PC and received the “Kodi unable to create GUI” error. After trying several possible solutions, I found the fix! Well, I actually ended up using a “workaround” (which fixed the problem).

In this solution guide, I show you how I fixed my Kodi unable to create GUI error.

I also show you other things I tried (with no success – but they were worthy attempts anyway).

Here’s a run-down of what to do with a Kodi unable to create GUI error scenario.

Kodi Unable to Create GUI Solutions:

Try all 3 of the solutions below.

Google trackers are lurking on 75% of websites. Cover your tracks to protect yourself.

Use Kodi 18 instead of Kodi 17

This is the workaround that solved the problem for me.

Pros: On the upside, using Kodi 18 on my Windows 10 PC enables Kodi to utilize the 64-bit CPU my (newer) Windows laptop by which it is powered. Also, using this solution I could have skipped past the “update your GPU drivers” solution suggestions that other articles & Reddit threads suggest.
Cons: The only downside to this solution is that I now need to install one of several great Kodi 18 builds. The reason this is a downside is because many more Kodi builds exist for Kodi 17 in contrast with Kodi 18. Although in my case, this is the only solution that actually worked. So I am fine with installing a Kodi 18 build.
How to attempt this solution:
- To download Kodi 18, click here to go to the official Kodi 18 download options page. Or go to my Kodi 18 install page.
- Or click here or enter http://bit.ly/kodi18beta3x64 into your Windows 10 PC’s web browser to direct-download Kodi 18 (NOTE: This is the 64-bit version of Kodi, which is only usable by “newer” Windows PCs.
  
  Quickly solve the Kodi unable to create GUI error by using Kodi 18
- For Kodi 18 that works on “older” PCs, click here and then download the first file you see that ends in “.exe”).

Update graphics card drivers

Now this solution can take quite awhile to attempt – and if your PC is anything like mine, the solution didn’t actually solve the problem.

Pros: Your graphics card drivers may be out-of-date and/or broken anyway. So updating your graphics card drivers may or may not solve the “Kodi unable to create GUI” issue.
Cons: After updating my graphics card drivers, I still received the Kodi unable to create GUI error. But you can try this solution if you want! It’s up to you. I simply recommend using Kodi 18 instead of Kodi 17 because it was the quickest, easiest solution for me. To download my graphics card drivers took about 15 minutes (as the drivers were roughly a 200MB download).
How to attempt this solution:
- Click the Windows Start Menu, then type in “device manager” and click on the “Device Manager” item that appears in the auto-complete results.
- After the Device Manager launches, expand the “Display adapters” section.
  
  This is what the Display Adapters section of Device Manager looks like for my PC
- Then right-click on your display adapter, then click “Properties”.
- Now click on the “Driver” tab, then click “Update Driver”
- Finally, click “Search automatically for updated device driver software”.
- Then wait for Windows to search and install updated graphics card drivers (if they’re available). Sometimes you already have the latest drivers installed. In this case, you’re shit-out-of-luck in trying this solution and you should try another solution on this page.

Change Kodi launcher to run in Windowed mode

This solution didn’t work for me, but did work for some people on Reddit.

Pros: For some people, this fixes the problem! I know this same method fixed some Windows games that would not launch for me.
Cons: This solution attempt did not work for me. But it basically means you change the Options in the Kodi launcher so that Kodi launchces not-fullscreen (aka “windowed”).
How to attempt this solution:
- To do this, find Kodi in the Start Menu, then right-click the Kodi icon and then click properties.
- After that, find the area that says “Run” which has a dropdown menu next to it.
- The dropdown menu (by default) says “Normal window”.
- Change this to “Maximized”, then click “OK”.
  
  Screenshot of the part of the Properties window you need to change
- Now launch Kodi, cross your fingers, and see if you still get the Kodi unable to create GUI error.
- If it doesn’t fix the problem, scroll up to the “Kodi 18” section and download Kodi 18 on your Windows PC instead.

Good luck!

Источник

Solved Error: Unable to create GUI. Exiting. Windows Server 2016 via RDP

Posts: 88

Joined: Mar 2010

Reputation:
0

If I connect to the VMConsole kodi will launch fine, any tweaks I can make to the VM hardware that might help?

bufudocaxu.kodi

Posts: 50

Joined: Mar 2013

Reputation:
4

2019-02-20, 10:37
(This post was last modified: 2019-02-20, 14:29 by KillerSkunk.)

Remote Desktop Protocol (RDP) 8.0 update for Windows 7 and Windows Server 2008 R2 might also contain some clues. As for example RemoteFX cannot be used and such.

Posts: 88

Joined: Mar 2010

Reputation:
0

I’ll give this a try when I get home later. Thanks for all the info! I’ll let you know if anything helped

Posts: 50

Joined: Mar 2013

Reputation:
4

Good luck with it, if any worked (whether above or not) i’ll be happy to hear it (and others likely too)

Posts: 88

Joined: Mar 2010

Reputation:
0

This worked perfect! First link was all I needed. Thanks again

Quote:As of Windows 10 / Windows Server 2016, you can enable GPU usage remotely as both operating systems natively support DirectX 11 / OpenGL 3+ over RDP. It is as simple as setting a toggle in the group policy correctly on Windows 10 / Server 2016:

Open the Edit Group Policy tool from Control Panel or use the Windows Search dialog (Windows Key + R, then type in gpedit.msc)
Browse to: Local Computer PolicyComputer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostRemote Session Environment
Then enable “Use the hardware default graphics adapter for all Remote Desktop Services sessions”

PatK

Team-Kodi Member

Posts: 13,225

Joined: Mar 2010

Reputation:
460

PatK

Team-Kodi Member
Posts: 13,225

Posts: 1

Joined: May 2019

Reputation:
0

Hope you don’t mind I still bump this.
I’m also experimenting with ESXi and Kodi since I want to run my Kodi on my ESXi and just feed the image to my television.
I ran into the same problem, but since I don’t want to RDP all the time, the solution above wasn’t for me.

Instead I changed some settings on my VM and afterwards Kodi did launch. (This is without a GPU in passthrough).

Could perhaps be useful for someone.

Источник

Here’s a guide on how you can fix Kodi 17 / 17.3 Unable to create GUI error on your PC running Windows 10.

Step 1: On the Windows PC, right-click on the This PC icon which represents the main machine and then select Properties.

Step 2: Select Device Manager from the list on the left-hand side and then select the Display adapters option to drop it down.

Step 3: Right-click on the listed graphics adapter and select the Properties option from the contextual menu that appears.

Step 4: From within that menu, select the Driver tab at the top of the window and then select Update Driver button.

Step 6: Load up the Kodi installation and you should have a more positive experience.

Kodi unable to start GUI

RPi 3B+, freshly installed Raspbian Buster minimal/lite.

When I try to start kodi from console, I get error: «unable to start gui, exiting»

Googling, I found it’s probably the missing xserver. So, what is the minimal package needed for this?

Also, shouldn’t it be a dependency for kodi package?

Rascas: Posts: 761; Joined: Tue Mar 11, 2014 6:18 pm; Location: Porto, Portugal

Re: Kodi unable to start GUI

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

madjo1983: Posts: 10; Joined: Sat Jan 20, 2018 12:39 pm

Re: Kodi unable to start GUI

Fri Jul 05, 2019 2:41 pm

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Hi,

I have the same issue. Raspberry Pi 3 B+.
From console, the launching Kodi generates an error: ERROR: Unable to create GUI. Exiting
From X, it runs but taks almost 97%CPU and is very slow.

Could you explain more this topic about opensource video drivers VC4 FKMS or VC4 KMS ?
Will it allow a launch from console ?

Cheers,
Orlando

Rascas: Posts: 761; Joined: Tue Mar 11, 2014 6:18 pm; Location: Porto, Portugal

Re: Kodi unable to start GUI

Fri Jul 05, 2019 2:51 pm

In raspi-config. Search the forum s for more info, there is alot in here already.

madjo1983: Posts: 10; Joined: Sat Jan 20, 2018 12:39 pm

Re: Kodi unable to start GUI

Fri Jul 05, 2019 4:56 pm

I saw some posts.
I tried some stuff.
Is there a command line to know if VC4 FKMS or VC4 KMS are activated ?

Thanks.

madjo1983: Posts: 10; Joined: Sat Jan 20, 2018 12:39 pm

Re: Kodi unable to start GUI

Sat Jul 06, 2019 10:43 am

madjo1983 wrote: ↑

Fri Jul 05, 2019 4:56 pm

I saw some posts.
I tried some stuff.
Is there a command line to know if VC4 FKMS or VC4 KMS are activated ?

Thanks.

sudo nano /boot/config.txt

Should appear:
dtoverlay=vc4-kms-v3d

madjo1983: Posts: 10; Joined: Sat Jan 20, 2018 12:39 pm

Re: Kodi unable to start GUI

Sat Jul 06, 2019 10:44 am

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Is this a better idea to install stretch raspian version instead and use 18.2 Kodi version with usual parameters ?

Rascas: Posts: 761; Joined: Tue Mar 11, 2014 6:18 pm; Location: Porto, Portugal

Re: Kodi unable to start GUI

Sat Jul 06, 2019 12:30 pm

madjo1983 wrote: ↑

Sat Jul 06, 2019 10:44 am

Rascas wrote: ↑

Wed Jul 03, 2019 7:16 pm

Kodi available on Buster is still the Debian generic version, not optimized for the Pi. For it to work you have to select the opensource video drivers aka as VC4 FKMS or VC4 KMS. It will be slow and without HW video decoding. You will have to wait for a RPi optmized version.

Is this a better idea to install stretch raspian version instead and use 18.2 Kodi version with usual parameters ?

Yes.

Enigma776: Posts: 1; Joined: Sat Jun 24, 2017 2:52 pm

Re: Kodi unable to start GUI

Mon Sep 09, 2019 10:57 am

Just encountered this issue my self but can not find a way to install kodi 18.2 is there a known repository or command to install 18.2?

Pander: Posts: 25; Joined: Sun Nov 09, 2014 11:35 pm

Return to “Troubleshooting”

Источник

Raspberry PI 4 Kodi — Error: Unable to create gui. exiting

Hi,

Just got a new RPI4 ARMv8 unit and installed Arch Arm on it with the objective of replacing my old ARMv7 Kodi box with this one, yet I am unable to get Kodi started.
When I enable and start up kodi.service, the process exits with the message:

Code: Select all: ERROR: Unable to create GUI. Exiting

Interesting FATAL point in the kodi.log regarding the matter is:

Code: Select all: 2019-10-04 18:23:32.310 T:2977099792 FATAL: CApplication::Create: Unable to init windowing system

Full kodi.log:

https://pastebin.com/yFDekry8

I am using the kodi-rbp4 18.4-2 package. If I switch to kodi-rbp3 or kodi-rbp packages, then it seems that the GUI is somewhat started as the screen goes completely black like it is starting X, but nothing further — not even sounds when trying to navigate around.

The only logs from kodi.service from journal are:

Code: Select all: Oct 04 22:17:29 archpi-v2 systemd[1]: Started Kodi standalone (GBM). Oct 04 22:17:29 archpi-v2 systemd[312]: pam_unix(login:session): session opened for user kodi by (uid=0) Oct 04 22:17:34 archpi-v2 systemd[1]: kodi.service: Succeeded.

Full /boot/config.txt is:

Code: Select all: # See /boot/overlays/README for all available options gpu_mem=320 dtoverlay=vc4-fkms-v3d dtparam=audio=on initramfs initramfs-linux.img followkernel

The driver used is xf86-video-fbdev 0.5.0-1… I tried the alarm/xf86-video-fbturbo-git also but the results are the same.
Also checked that the kodi user’s home is set as /var/lib/kodi as I read that it could cause similar issues.

Code: Select all: kodi:x:975:975::/var/lib/kodi:/usr/bin/nologin

I am running out of ideas on what to check as my ARMv7 seems to be running on a similar setup without any issues. Anyone else managed to turn RPI4 ARMv8 into a simple Kodi box?
Any help and tips are very highly appreciated! (wiki links are welcome if relevant )

EDIT: changed the pastebin url for logs as they were from an incorrect service start attempt

Last edited by Kallestofeles on Fri Oct 04, 2019 8:30 pm, edited 1 time in total.

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by graysky » Fri Oct 04, 2019 8:04 pm

2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://envhome/

is mapped to: /root
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://home/

is mapped to: /root/.kodi
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://temp/

is mapped to: /root/.kodi/temp
2019-10-04 18:23:24.632 T:2977099792 NOTICE:

special://logpath/

is mapped to: /root/.kodi/temp

Bad bad bad. It seems you are trying to run as root. Using the kodi.service via systemctl will not do this so I don’t know how you’re starting it. Also, gbm does not require drivers so you can uninstall the xf86 stuff.

graysky

Posts: 1512

Joined: Sun Jun 26, 2011 6:56 am

Location: /run/user/1000

Website

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by Kallestofeles » Fri Oct 04, 2019 8:30 pm

Thank you for the quick reply!
It seems that I made a mistake with copying the logs from an attempt when I was indeed trying to start it up as root, my apologies. Here are the latest logs when systemd starts the application during a fresh reboot:

https://pastebin.com/yFDekry8

(ignore the time-jumping — seems that the system starts off with local time but then jumps to UTC — hence the strange jump in time in the beginning of logs)
Thanks for the xf86 tip, removed them.

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by graysky » Fri Oct 04, 2019 9:09 pm

I’m not sure what you have going on… it should just work. Did you attempt to migrate any old kodi profiles to this? Recommend you rename your /var/lib/kodi to /var/lib/kodi-old and then:

Code: Select all: # mkdir /var/lib/kodi # chown kodi:kodi /var/lib/kodi

Then start the systemd service… Are you using HDMI0 or HDMI1? I seems to recall needing to use HDMI0 which is right next to the power supply.

graysky

Posts: 1512

Joined: Sun Jun 26, 2011 6:56 am

Location: /run/user/1000

Website

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by Kallestofeles » Fri Oct 04, 2019 9:41 pm

Thanks for the help! Tried the folder replacement but no avail.
Did not try to migrate profiles, want a fresh start.
I am using HDMI-0 as I heard that sometimes HDMI-1 does not supply enough power and yeah, there is no image at all with the HDMI-1 connection, not even the console.

The strange thing is that with kodi-rbp package, all the extensions and resolutions load up normally:

https://pastebin.com/PkT5sTFZ

But the screen remains simply black.

EDIT:
Just for the completion’s sake, I did a fresh Arch arm install on the RPI4 unit and the only additional packets I installed (with their dependencies) were:

Code: Select all: linux-raspberrypi4-headers base-devel kodi-rbp4 wget omxplayer-git xorg-xrefresh xorg-xset

This is how the old RPI3 worked (with its respective rbp3 packages) with Kodi, but not the new RPI4.

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by graysky » Sat Oct 05, 2019 1:26 am

I am at a loss to explain what is going on for you… are you certain your hardware is RPi4? Recommend you post with your debug log to the kodi forum.

graysky

Posts: 1512

Joined: Sun Jun 26, 2011 6:56 am

Location: /run/user/1000

Website

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by Kallestofeles » Sat Oct 05, 2019 8:46 am

Yes, I am 100% sure that it is the RPI4 which I purchased just yesterday, says it also on the board itself + the new layout and connectors in comparison to the old RPI3 models. :lol:
Thanks, I shall post to Kodi forums then as well and if I get anywhere, I will update this topic also.

https://forum.kodi.tv/showthread.php?tid=348014

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by Kallestofeles » Sat Oct 05, 2019 11:01 am

I got the picture on! :lol:
After investigating a bit about the overlay options for config.txt, I had to add the cma-256 to vc4-fkms-v3d dtoverlay so that the whole line would read out like this:

Code: Select all: dtoverlay=vc4-fkms-v3d,cma-265

Have not yet tested out playback of any video files, but at least the interface is now operational and I can browse through Kodi’s menus. :lol:

EDIT:
Yep, playback is fine, all is working exactly as expected. Thank you so much graysky for helping out on this! Perhaps this cma thingy could also be added to the kodi-rbp4 package notes during installation that in case the normal method does not work, it is worth a shot to try it with this parameter?

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by graysky » Sat Oct 05, 2019 11:28 am

That’s fucked up… mine works without that at all… 2 and 4 G versions if that matters.

Code: Select all: # See /boot/overlays/README for all available options initramfs initramfs-linux.img followkernel # turn tv on # write out edid file with # sudo /opt/vc/bin/tvservice -d /boot/edid.dat # setting below will load it on boot gpu_mem=406 hdmi_edid_file=1 dtparam=audio=on dtoverlay=vc4-fkms-v3d hdmi_group=2 hdmi_mode=69

graysky

Posts: 1512

Joined: Sun Jun 26, 2011 6:56 am

Location: /run/user/1000

Website

Re: Raspberry PI 4 Kodi — Error: Unable to create gui. exiti

by Kallestofeles » Sun Oct 06, 2019 7:43 am

Thanks!
Maybe not a great idea to bump the thread with a simple continuation of a conversation, but I also noticed one additional strange thing — namely, I seem to have to keep one of the following installed:

Code: Select all: xf86-video-fbturbo-git xf86-video-fbdev

If neither of the two is installed, then Kodi simply boots to black screen and nothing further. Kodi service in systemd shows all good and the service is started. I do not use any X nor do I have xorg.conf set up. Go figure. :roll:

At least the box is now up — reaching the heat limit pretty frequently as well. Need to modify the case with a tiny fan probably.

Kallestofeles: Posts: 9; Joined: Sun Jul 21, 2019 11:24 am

Return to ARMv8

Who is online

Users browsing this forum: No registered users and 2 guests

Источник

Full /home/sander/kodi_crashlog-20190921_102252.log

############## Kodi CRASH LOG ###############

################ SYSTEM INFO ################
 Date: Sat Sep 21 10:22:52 CEST 2019
 Kodi Options: 
 Arch: x86_64
 Kernel: Linux 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019
 Release: Ubuntu 18.04.3 LTS (Bionic Beaver)
############## END SYSTEM INFO ##############

############### STACK TRACE #################
=====>  Core file: /home/sander/core (2019-09-21 10:22:52.225173121 +0200)
        =========================================
[New LWP 4640]
[New LWP 4707]
[New LWP 4641]
[New LWP 4643]
[New LWP 4708]
[New LWP 4740]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
[Current thread is 1 (Thread 0x7f93bfb74fc0 (LWP 4640))]

Thread 6 (Thread 0x7f93627fc700 (LWP 4740)):
#0  0x00007f93b63589d0 in __GI___nanosleep (requested_time=requested_time@entry=0x7f93627fb550, remaining=remaining@entry=0x0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  0x00007f93b638b877 in usleep (useconds=<optimized out>) at ../sysdeps/posix/usleep.c:32
#2  0x000055e7ac6c308f in CAESinkNULL::Process() ()
#3  0x000055e7acfaef3f in CThread::Action() ()
#4  0x000055e7acfaf1ff in CThread::staticThread(void*) ()
#5  0x00007f93be72e6db in start_thread (arg=0x7f93627fc700) at pthread_create.c:463
#6  0x00007f93b639588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f9362ffd700 (LWP 4708)):
#0  0x00007f93be734f85 in futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x7f9362ffc250, expected=0, futex_word=0x55e7ae5d14e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0x7f9362ffc250, mutex=0x55e7ae5d14f8, cond=0x55e7ae5d14b8) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0x55e7ae5d14b8, mutex=0x55e7ae5d14f8, abstime=0x7f9362ffc250) at pthread_cond_wait.c:667
#3  0x000055e7acfaee4d in CThread::Sleep(unsigned int) ()
#4  0x000055e7ac68e6fc in ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) ()
#5  0x000055e7ac68fd42 in ActiveAE::CActiveAESink::StateMachine(int, Actor::Protocol*, Actor::Message*) ()
#6  0x000055e7ac6908e7 in ActiveAE::CActiveAESink::Process() ()
#7  0x000055e7acfaef3f in CThread::Action() ()
#8  0x000055e7acfaf1ff in CThread::staticThread(void*) ()
#9  0x00007f93be72e6db in start_thread (arg=0x7f9362ffd700) at pthread_create.c:463
#10 0x00007f93b639588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f9394ea0700 (LWP 4643)):
#0  0x00007f93b6388bf9 in __GI___poll (fds=0x55e7ae5d7bf0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x000055e7acc95f91 in CFDEventMonitor::Process() ()
#2  0x000055e7acfaef3f in CThread::Action() ()
#3  0x000055e7acfaf1ff in CThread::staticThread(void*) ()
#4  0x00007f93be72e6db in start_thread (arg=0x7f9394ea0700) at pthread_create.c:463
#5  0x00007f93b639588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f93956a1700 (LWP 4641)):
#0  0x00007f93be7349f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55e7ae5c5d50) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55e7ae5c5d68, cond=0x55e7ae5c5d28) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55e7ae5c5d28, mutex=0x55e7ae5c5d68) at pthread_cond_wait.c:655
#3  0x000055e7ac85f229 in ANNOUNCEMENT::CAnnouncementManager::Process() ()
#4  0x000055e7acfaef3f in CThread::Action() ()
#5  0x000055e7acfaf1ff in CThread::staticThread(void*) ()
#6  0x00007f93be72e6db in start_thread (arg=0x7f93956a1700) at pthread_create.c:463
#7  0x00007f93b639588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f93637fe700 (LWP 4707)):
#0  0x00007f93be734f85 in futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x7f93637fd590, expected=0, futex_word=0x55e7ae5d10dc) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0x7f93637fd590, mutex=0x55e7ae5d10f0, cond=0x55e7ae5d10b0) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0x55e7ae5d10b0, mutex=0x55e7ae5d10f0, abstime=0x7f93637fd590) at pthread_cond_wait.c:667
#3  0x000055e7ac68bf17 in ActiveAE::CActiveAE::Process() ()
#4  0x000055e7acfaef3f in CThread::Action() ()
#5  0x000055e7acfaf1ff in CThread::staticThread(void*) ()
#6  0x00007f93be72e6db in start_thread (arg=0x7f93637fe700) at pthread_create.c:463
#7  0x00007f93b639588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f93bfb74fc0 (LWP 4640)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007f93b62b4801 in __GI_abort () at abort.c:79
#2  0x00007f93b62fd897 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f93b642ab9a "%sn") at ../sysdeps/posix/libc_fatal.c:181
#3  0x00007f93b630490a in malloc_printerr (str=str@entry=0x7f93b642c870 "double free or corruption (out)") at malloc.c:5350
#4  0x00007f93b630be75 in _int_free (have_lock=0, p=0x55e7ae8992c0, av=0x7f93b665fc40 <main_arena>) at malloc.c:4278
#5  __GI___libc_free (mem=0x55e7ae8992d0) at malloc.c:3124
#6  0x000055e7acd34b59 in std::_Rb_tree<int, std::pair<int const, RssSet>, std::_Select1st<std::pair<int const, RssSet> >, std::less<int>, std::allocator<std::pair<int const, RssSet> > >::_M_erase(std::_Rb_tree_node<std::pair<int const, RssSet> >*) ()
#7  0x000055e7acd33f89 in CRssManager::Clear() ()
#8  0x000055e7aca80d81 in CSettingsManager::OnSettingsUnloaded() ()
#9  0x000055e7aca81a53 in CSettingsManager::Unload() ()
#10 0x000055e7aca84bbe in CSettingsManager::Clear() ()
#11 0x000055e7ac3d5dc1 in CSettings::Uninitialize() ()
#12 0x000055e7ac3d680f in CSettings::~CSettings() ()
#13 0x00007f93b62b7041 in __run_exit_handlers (status=-1, listp=0x7f93b665f718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#14 0x00007f93b62b713a in __GI_exit (status=<optimized out>) at exit.c:139
#15 0x00007f93b6295b9e in __libc_start_main (main=0x55e7ac3521b0 <main>, argc=1, argv=0x7ffce25987f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffce25987e8) at ../csu/libc-start.c:344
#16 0x000055e7ac3b835a in _start ()
############# END STACK TRACE ###############

################# LOG FILE ##################

10:21:58.284 T:140272553381824  NOTICE: special://profile/ is mapped to: special://masterprofile/
10:21:58.284 T:140272553381824  NOTICE: -----------------------------------------------------------------------
10:21:58.284 T:140272553381824  NOTICE: Starting Kodi from Debian (17.6 Debian package version: 2:17.6+dfsg1-1ubuntu1). Platform: Linux x86 64-bit
10:21:58.284 T:140272553381824  NOTICE: Using Release Kodi from Debian x64 build
10:21:58.284 T:140272553381824  NOTICE: Kodi from Debian compiled from 2:17.6+dfsg1-1ubuntu1 by GCC 6.4.0 for Linux x86 64-bit version 4.15.15 (265999)
10:21:58.284 T:140272553381824  NOTICE: Running on Ubuntu 18.04.3 LTS, kernel: Linux x86 64-bit version 4.15.0-58-generic
10:21:58.284 T:140272553381824  NOTICE: FFmpeg version/source: 3.4.6-0ubuntu0.18.04.1
10:21:58.284 T:140272553381824  NOTICE: Host CPU: Intel(R) Celeron(R) J4105 CPU @ 1.50GHz, 4 cores available
10:21:58.284 T:140272553381824  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
10:21:58.284 T:140272553381824  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/x86_64-linux-gnu/kodi
10:21:58.284 T:140272553381824  NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/x86_64-linux-gnu/kodi/addons
10:21:58.284 T:140272553381824  NOTICE: special://masterprofile/ is mapped to: /home/sander/.kodi/userdata
10:21:58.284 T:140272553381824  NOTICE: special://envhome/ is mapped to: /home/sander
10:21:58.284 T:140272553381824  NOTICE: special://home/ is mapped to: /home/sander/.kodi
10:21:58.284 T:140272553381824  NOTICE: special://temp/ is mapped to: /home/sander/.kodi/temp
10:21:58.284 T:140272553381824  NOTICE: special://logpath/ is mapped to: /home/sander/.kodi/temp
10:21:58.284 T:140272553381824  NOTICE: The executable running is: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin
10:21:58.284 T:140272553381824  NOTICE: Local hostname: brixit
10:21:58.284 T:140272553381824  NOTICE: Log File is located: /home/sander/.kodi/temp//kodi.log
10:21:58.284 T:140272553381824  NOTICE: -----------------------------------------------------------------------
10:21:58.293 T:140272553381824   ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
10:21:58.333 T:140272553381824  NOTICE: load settings...
10:21:58.353 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:21:58.353 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:21:58.359 T:140272553381824  NOTICE: No Devices found - retry: 4
10:21:59.868 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:21:59.868 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:21:59.876 T:140272553381824  NOTICE: No Devices found - retry: 3
10:22:01.380 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:01.380 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:01.387 T:140272553381824  NOTICE: No Devices found - retry: 2
10:22:02.897 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:02.897 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:02.906 T:140272553381824  NOTICE: No Devices found - retry: 1
10:22:04.415 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:04.415 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:04.425 T:140272553381824  NOTICE: Found 0 Lists of Devices
10:22:04.429 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:04.429 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:04.434 T:140272553381824  NOTICE: No Devices found - retry: 4
10:22:05.941 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:05.941 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:05.949 T:140272553381824  NOTICE: No Devices found - retry: 3
10:22:07.459 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:07.459 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:07.467 T:140272553381824  NOTICE: No Devices found - retry: 2
10:22:08.976 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:08.976 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:08.986 T:140272553381824  NOTICE: No Devices found - retry: 1
10:22:10.496 T:140272553381824   ERROR: PulseAudio: Failed to connect context
10:22:10.496 T:140272553381824  NOTICE: PulseAudio might not be running. Context was not created.
10:22:10.504 T:140272553381824  NOTICE: Found 0 Lists of Devices
10:22:10.508 T:140272553381824  NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
10:22:10.508 T:140272553381824  NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
10:22:10.508 T:140272553381824  NOTICE: Default Video Player: VideoPlayer
10:22:10.508 T:140272553381824  NOTICE: Default Audio Player: paplayer
10:22:10.508 T:140272553381824  NOTICE: Disabled debug logging due to GUI setting. Level 0.
10:22:10.508 T:140272553381824  NOTICE: Log level changed to "LOG_LEVEL_NORMAL"
10:22:10.508 T:140272553381824  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
10:22:10.508 T:140272553381824  NOTICE: Loaded playercorefactory configuration
10:22:10.509 T:140272553381824  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
10:22:10.509 T:140272553381824  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
08:22:10.514 T:140272553381824  NOTICE: Running database version Addons27
08:22:10.560 T:140272553381824  NOTICE: ADDONS: Using repository repository.xbmc.org
08:22:10.568 T:140271006246656   ERROR: PulseAudio: Failed to connect context
08:22:10.568 T:140271006246656  NOTICE: PulseAudio might not be running. Context was not created.
08:22:10.575 T:140271006246656  NOTICE: No Devices found - retry: 4
08:22:12.086 T:140271006246656   ERROR: PulseAudio: Failed to connect context
08:22:12.086 T:140271006246656  NOTICE: PulseAudio might not be running. Context was not created.
08:22:12.094 T:140271006246656  NOTICE: No Devices found - retry: 3
08:22:13.604 T:140271006246656   ERROR: PulseAudio: Failed to connect context
08:22:13.604 T:140271006246656  NOTICE: PulseAudio might not be running. Context was not created.
08:22:13.613 T:140271006246656  NOTICE: No Devices found - retry: 2
08:22:15.122 T:140271006246656   ERROR: PulseAudio: Failed to connect context
08:22:15.122 T:140271006246656  NOTICE: PulseAudio might not be running. Context was not created.
08:22:15.131 T:140271006246656  NOTICE: No Devices found - retry: 1
08:22:16.641 T:140271006246656   ERROR: PulseAudio: Failed to connect context
08:22:16.641 T:140271006246656  NOTICE: PulseAudio might not be running. Context was not created.
08:22:16.651 T:140271006246656  NOTICE: Found 0 Lists of Devices
08:22:16.654 T:140271006246656 WARNING: ActiveAE::Configure - sink returned large buffer of 249 ms, reducing to 100 ms
08:22:16.666 T:140272553381824   ERROR: X11 Error: No Display found
08:22:16.666 T:140272553381824   FATAL: CApplication::Create: Unable to init windowing system


############### END LOG FILE ################

############ END Kodi CRASH LOG #############

Источник

Here’s a guide on how you can fix Kodi 18.5 Unable to create GUI error on your PC running Windows 10.

Kodi is one of the fastest growing platforms on the market at the moment with hundreds of thousands of users taking the opportunity to get onboard with the platform for their various device types. Downloading and installing Kodi 18.5 instantly gets access to all of the goodies and the features contained within, but it also brings a few bugs and known issues which produce error messages and cause confusion. The “ERROR: Unable to create GUI. Exiting” is one of those errors, and we are going to show you how to fix it.

Step 1: On the Windows PC, right-click on the This PC icon which represents the main machine and then select Properties.

Step 2: Select Device Manager from the list on the left-hand side and then select the Display adapters option to drop it down.

Step 3: Right-click on the listed graphics adapter and select the Properties option from the contextual menu that appears.

Step 4: From within that menu, select the Driver tab at the top of the window and then select Update Driver button.

Step 6: Load up the Kodi installation and you should have a more positive experience.

This resolution should hopefully get you up and running with Kodi 18.5 instantly without any further fuss or issue. It may be that additional problems occur down the line, but where this particular issue is concerned that should be sorted for the long haul. Enjoy the Kodi experience, and make sure to take full use of its power and functionality.

I hope this tutorial can help you troubleshoot your kodi problem. Have a nice day.

Источник