Error unable to create gui exiting kodi что это
Error unable to create gui exiting kodi что это
Derek
Posting Freak
Marco275
Member
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
k4sh1n
Posting Freak
AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
jmh2002
Posting Freak
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too 
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
Marco275
Member
If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
(2016-03-16, 09:57) Marco275 Wrote: If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
k4sh1n
Posting Freak
Can you remove profiles.xml from KODI userdata folder and re-start KODI
Win key + R key
Paste: %appdata%\Kodi\userdata\
Press OK
manny_203
Newbie
(2016-03-15, 05:38) PatK Wrote: From V15.2 to 16.1, Kodi went from DX9 to DX11 and a lot of graphic cards are having issues over this move. Try different rendering methods.
There’s a possibility that the notebook gfx system is insufficient for Kodi DX11 and the safe move to Isengard 15.2 might be warranted on this equipment.
(2016-03-15, 05:52) Derek Wrote: Intel GPU by any chance?
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
DX11 is supported on Vista, try updating the DX11, manually to ensure all necessary files were installed.
Failing that pastebin a link to your debug log of when KODI fails. This can be manually set via advancedsettings.xml.
(2016-03-15, 14:56) k4sh1n Wrote: AFAIK v.16 Jarvis DX11 has the retained backwards compatibility with DX9.C, so users don’t need new GPU H/W for new KODI releases.
Yeah I saw this backwards compatibility mentioned too but the forum appears to be full of issues since Jarvis v16 was released.
My Kodi runs on my older windows machine but I have the green colour issue mentioned in other threads even though I’ve been using DX11 for a long time and don’t have issues playing videos in other media players.
So, kodi is getting the finger pointed at it. But Ill try some of the fixes you mentioned too
It looks like there is different flavours of direct X some issues in various windows are reporting and no doubt it’s linked to the graphic card routines and if you haven’t the latest drivers; or the gfx company isn’t supporting patches for your card there’s going to be trouble., If you do have issues then a manual install of dx11 might be advisable, dx11.1 for win8 users and dx 11.2 for win10 users, although according to all information this should be backward compatible. At this point in my mind, the gfx hardware has the pointer of being the culprit.
(2016-03-16, 09:57) Marco275 Wrote: If you run the installer, you can (de)select PVR add-ons, skin add-ons, screensaver etc..
Since I don’t have a touchscreen I always deselected the Skin add-ons/estouchy option resulting in Kodi resulting in Kodi giving an error message during startup.
I run older hardware too and with estouchy selected Kodi runs fine now, so at least in my case, it has little to do with the Direct X version.
(2016-03-15, 09:45) Marco275 Wrote: Did you select Estouchy install?
Derek I think my pc shoud have it
marco275 this estouchy install you speak of is a skin for kodi, I cannot not even open up kodi, so I would be able to deal with skins.
absolutely nothing has worked at all. but i appreciate the help
(2016-03-17, 05:13) k4sh1n Wrote: Can you remove profiles.xml from KODI userdata folder and re-start KODI
Win key + R key
Paste: %appdata%\Kodi\userdata\
Press OK
Error unable to create gui exiting kodi что это
mikeyguk
Newbie
Hi I’ve just done a clean install of Windows 7 ultimate (6.1 build 7601) using the following spec:
Asus A8R32 deluxe bios version 8.00.12
AMD Athlon 64 X2 Dual Core 4400+ 2.2ghz
4096GB RAM
NVIDIA GeForce GT 520 with 332.21 driver
Realtek ALC882 R2.73
XBMC Frodo
When clicking on the XBMC icon from the start menu it doesn’t load art as and returns the error message «ERROR:Unable to create GUI. Exiting».
I have tried updating the graphics card and sound audio drivers to no avail.
Any suggestions I’d really appreciate!
Are you using a funky desktop resolution?
mikeyguk
Newbie
I’ve never actually set the resolution on it and have only ever been connecting to the pc using a remote desktop connection.
Is this beyond what xbmc can render?
MatteN
Senior Member
Kodi Error: Unable To Create Application Exiting (3 Fixes)
Kodi is an amazing application that users can use to stream different shows and movies for them. The application is extremely easy to set up and only requires a few things. One of this is having a stable internet connection so that your videos don’t buffer while you are watching them. Secondly, users have to first make their accounts and subscribe to packages
If they want additional features. You can go through all of these from the official website of this company. While this might be a great streaming platform, some users have reported getting the error ‘Unable to create application exiting’ while using Kodi. If this happens then this article should help you out in troubleshooting this problem.
Kodi Error: Unable To Create Application. Exiting
Mostly this problem happens if there are corrupt files in your directory. This usually happens when there might be an interruption while downloading the software. You might be using a Wi-Fi connection which can often fluctuate causing this problem. Whatever the case might be, we recommend that you re-install the application.
This should delete all the previous files and then replace them, fixing the issue. Start by uninstalling the application from your device and then install the latest version. The update should also fix any issues that the streaming software had. After the re-installation ends, you can then reboot your system. This will help in replacing all the old files, you should now be able to use Kodi without any problems.
If the error persists then your application might be having problems trying to replace all these files automatically. In this case, you should manually replace all the logs and directory files for your Kodi software. It is important that you first rename the folder Kodi from your directory before you start this process.
You can then move these files slowly onto your new folder and test which one had the issue. Most users have reported that the ‘userdata’ files were causing this problem. This is why you should first take out these and check your application.
If it is now working fine then you can start using the software. However, if it does not then you can proceed with the process. You should keep in mind that some of your addons might get deleted and you will have to add them again on your own.
Lastly, there can be several reasons for getting this error message aside from the user files. To check this, you can open up the log files for Kodi. These contain all the error messages and going through them can help you identify the problem.
If there is any problem with your account then try to remove it and then add it back. Aside from this, some people might find it hard to read through these log files. In this case, you can send a copy of these to the customer support team so that they can help you out.
Запуск Kodi на Raspberry Pi V4
Здравствуйте! Прошу помочь с запуском kodi на Raspberry Pi V4 (ос Raspbian) При попытке запуска из терминала выпадает ошибка «open /dev/fb0: No such file or directory». Поиск в гугле результатов не дал (с Linux первое знакомство). Я так понимаю, проблема с видеодрайвером, но как ее решить, не пойму.
Cудя по /dev/fb0 он пытается запуститься во фреймбуфере вместо иксов. А не из теминала он запускается? Из простого решения есть специалтный дистрибутив libreELEC как раз для запуска kodi.
Нет, не из терминала тоже не запускается (никаких ошибок, просто ничего не происходит). Если я правильно понимаю, иксы запускаются командой startx? При этой команде в терминале такие ошибки:
(EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at «/home/pi/.local/share/xorg/Xorg.0.log» for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Не удалось получить файловый дескриптор, указывающий на консоль
извиняюсь, ввёл в заблуждение. стоит актуальная версия Raspberry Pi OS
Please also check the log file at «/home/pi/.local/share/xorg/Xorg.0.log» for additional information.
у меня иксы не стартуют если в конфиге disable_fw_kms_setup=1 т.е. выпилен edid, даже если режим hdmi прописан руками
сижу жду третий кабель 🙂
жаль жаль, с тройками вообще проблем не было, куда только их не отправлял вообще не думая что они могут начать выпендриваться на столь ровном месте
Ну ты смешной. Зачем на таком мощном железе огрызок, где не ставятся пакеты? Установить retropie со всеми эмулями, потом через менюшку поставить kodi и выбрать автовход в него. Провозится долго, да, но зато возьмёт от системы всё. Придётся ещё пару джойстиков (лучше беспроводных) докупать.
Может, посоветуете, как решить существующую проблему (отсутствие /dev/fb0)? хотелось бы установить kodi на голую ОС, эмулятор не интересует. Или совет, в какую сторону двигаться/гуглить
Вывали kodi.log полный на pastebin
Из голого сеанса из командной строки
А где его взять? в /var/log нет такого файла
Может, посоветуете, как решить существующую проблему
Сегодня нет коди под рукой у себя проверить, завтра посмотрю. Попробуй перед запуском попереключать видеодрайвер все 3 варианта в raspi-config и попробовать с каждым.
не сочти за наглость, можешь объяснить, как переключать видеодрайвер в raspi-config?
только у 4ки не три а два варианта (Full KMS на последней ОС нема, только Fake KMS и Legacy)
G1 Legacy не включается: The GL driver is disabled.
Legacy это программный рендер без GL
Изменил файл config.txt: разкомментировал строки hdmi_force_hotplug=1 и hdmi_safe=1. В итоге файл /dev/fb0 создался. Теперь при попытке запуска kodi в терминале «ERROR: Unable to create GUI. Exiting /usr/bin/kodi –standalone has exited in an unclean state 3 times in the last 20 seconds. Something is probably wrong»
эта ошибка ещё хуже гуглится 🙁 прошу поделиться мыслями, в какую сторону копать
DietPi
DietPi Community Forum
Post by Milemar » Mon May 17, 2021 11:31 pm
I have installed DietPi x64 on rPi4. All good, no problem at all.
I have configured network access, passwords, hostname, etc. and finished the minimal install without any additional software.
After that, I ran dietpi-software and selected Kodi.
That went all OK apart of one message:
I assume this is nothing important as this points to some Kodi icon.
I have chosen not to boot to Kodi and left the default setting (manual login).
As root user I ran «kodi» command and was returned a message «Unable to create GUI. Exiting», and the path to the log.
The «No display found» suggest there is no display connected to the rPi4 but it is connected via HDMI to AV and then to the TV. The whole installation was done like this.
I have tried to reinstall Kodi and X.Org. The result is the same.
I know that Kodi wasn’t supported on the x64 build but that note disappeared from the download page so I am assuming it is supported now.
Am I correct?
Thanks for any help.
M.
Post by Joulinar » Tue May 18, 2021 10:45 am
what version of DietPi you are running?
Basically the error message regarding the missing desktop item can be ignored, it’s know but will not have any impact on your system. We will change this behaviour on next release https://github.com/MichaIng/DietPi/pull/4362
pls try to use startkodi if you like to launch kodi from CLI. See as well our online docs https://dietpi.com/docs/software/media/#kodi
Regarding Kodi in general. DietPi is using Raspberry OS as base image. Means we don’t install an own Kodi version, we use the official one provided via Raspberrypi apt package.
Post by Milemar » Wed May 19, 2021 9:04 am
Post by Joulinar » Wed May 19, 2021 11:30 pm
Post by Milemar » Thu May 20, 2021 9:53 am
The output is the same.
Here is the kodi crash log:
For the testing purpose, I have installed XFCE and I was able to start it with no problem.
I have tried to run Kodi after XFCE installation and still the same.
TBH I am a little bit fed up already and I am close to installing the 32-bit version of DietPi.
Post by Milemar » Thu May 20, 2021 11:50 am
Post by Joulinar » Thu May 20, 2021 10:30 pm
Basically you changed from Raspberry OS 64bit to Raspberry OS 32bit. Kodi package is pulled from global apt package source. This is not really DietPi is providing. We simply pull the package and do some configs.
But there is one huge difference between 64bit and 32bit.
On 32bit Kodi is installed from archive.raspberrypi.org with version 18.7
While 64bit is pulling the package from deb.debian.org in an old version 17.6
Post by Milemar » Tue May 25, 2021 6:40 pm
Thanks for that info.
I used to run Kodi on DietPi before and it was the x86 version. But there was an info on the downloading site that Kodi is unsupported on x64 build. Now that info is gone and I thought that something has changed in that matter.
Maybe is worth to put that info back next to the x64 image download link.
Post by Joulinar » Tue May 25, 2021 10:50 pm
Post by MichaIng » Sat May 29, 2021 12:25 pm