[sparky3387]

It was running in VirtualBox (Just for testing), with a 7600K powering

I have also tried Docker, and as it does not have a sound card it gets more errors, until I added pulseaudio and a null audio device, no errors then but it still would not boot.

Debug log

[wsnipex]

09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event0 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event1 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event3 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event6 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event5 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event2 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event4 (Permission denied)

also, make sure /dev/dri/card0 exists and your user has permissions for it

[sparky3387]

09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event0 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event1 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event3 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event6 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event5 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event2 (Permission denied)
09:46:32.280 T:139926123454592   ERROR: open_restricted - failed to open /dev/input/event4 (Permission denied)

Correct I needed to :
1. Add my user to the input group
2. Install upower,consolekit and udisks2

And that got rid of pretty much all errors (except two niggling ones about upower states). Unfortunately, even with only this error, it still refuses to start.....
Debug log

Edit: Nvm after touching and chowning that dri/card0 it works! Thanks!
Second Edit: Nope, it just took longer to crash.......
Third edit: I did apt-get install --reinstall xserver-xorg-video-intel xserver-xorg xserver-xorg-core && dpkg-reconfigure xserver-xorg-core and now the card0 exists on its own, I have added my user to the video group, but it still does not start

[a1rwulf]

Nope, it just took longer to crash...

can you post another Debug Log then.
First log indicated a permission problem, but if it takes longer to crash it could be a different issue now.

[sparky3387]

Nope, it just took longer to crash...

can you post another Debug Log then.
First log indicated a permission problem, but if it takes longer to crash it could be a different issue now.  

Thanks a1rwulf

Debug log

[a1rwulf]

Unfortunately it's still the same.
Now that I read your last post, you created the file /dev/dri/card0 using touch?
That can't work at all.
This is the device file of the graphics card.
Can you give me the output of

Code:

ls -l /dev/dri

[sparky3387]

Unfortunately it's still the same.
Now that I read your last post, you created the file /dev/dri/card0 using touch?
That can't work at all.
This is the device file of the graphics card.
Can you give me the output of

Code:

ls -l /dev/dri

I originally attempted to touch the file, then I researched a bit more and realised that the file was created by xserver (not included with Ubuntu Server), I ran the following command:
apt-get install --reinstall xserver-xorg-video-intel xserver-xorg xserver-xorg-core && dpkg-reconfigure xserver-xorg-core

I then added the user to the video group, but still no luck, here  is my dev/dri
drwxr-xr-x  3 root root      80 Sep  8 08:06 .
drwxr-xr-x 18 root root    3.8K Sep  8 08:06 ..
drwxr-xr-x  2 root root      60 Sep  8 08:06 by-path
crw-rw----  1 root video 226, 0 Sep  8 08:06 card0
I have even tried installing a full blown ubuntu desktop killing the desktop and then starting kodi and still get the exact same error log, its definitely to do with the graphics detection, as if I leave the windows manager (and desktop) running it runs fine.

[a1rwulf]

All that sounds a little bit odd to me.
As I'm not really familiar with Virtualbox, I'll share how it works for me with a native ubuntu installation.

It would really surprise me if card0 is installed by X11, afaik this is thr device tree exposed by the kernel and the purpose of gbm is not to need X11 at all.

Hence I'm confused by

its definitely to do with the graphics detection, as if I leave the windows manager (and desktop) running it runs fine.

I always just run:

Code:

sudo systemctl isolate multi-user.target

prior to starting kodi-gbm

[marantz]

Thanks guys, it works very well

edit:
what i did was
addgroup user audio
addgroup user video
addgroup user input

and then it worked.

second edit:
everything works fine but kodi takes alot more cpu with kodi-gbm then with kodi17 and the homemade patch

[matthuisman]

Looks like a headless patch for KODI 18 maybe a bit trickier with all the win system stuff.

Maybe the best approach is to add a new platform / window system (like GBM did) that simply implements the WinSystem interface (but just does nothing).
https://github.com/xbmc/xbmc/tree/master/xbmc/windowing
https://github.com/xbmc/xbmc/blob/master...System.cpp

Then compile with
-DCORE_PLATFORM_NAME=headless

It would then stop the need for patching in everywhere the functions are called.
Also for compiling, you wouldn't need all the GLES / GL / X11 dependencies.

Something like that may also have a chance of being merged?

[a1rwulf]

everything works fine but kodi takes alot more cpu with kodi-gbm then with kodi17 and the homemade patch

Yes that's because we actually render.
But the usecase I designed it for, was not exactly to run it on a sever with minimal hw utilization.
Still people can use it for this scenario if they don't mind the higher load.

[a1rwulf]

Looks like a headless patch for KODI 18 maybe a bit trickier with all the win system stuff.

Maybe the best approach is to add a new platform / window system (like GBM did) that simply implements the WinSystem interface (but just does nothing).
https://github.com/xbmc/xbmc/tree/master/xbmc/windowing
https://github.com/xbmc/xbmc/blob/master...System.cpp

Then compile with
-DCORE_PLATFORM_NAME=headless

It would then stop the need for patching in everywhere the functions are called.
Also for compiling, you wouldn't need all the GLES / GL / X11 dependencies.

Something like that may also have a chance of being merged?

 While I wouldn't deny per se, it would be much nicer if interested people help improving the architecture, so that this is not needed.

[Damien67]

All,

I need a bit of help...I have had kodi/media/MariaDB running in a Win7 now 10 machine for years.
When a torrent ends, a curl command simply performs a database update.

I got more and more familiar with Linux and Docker thanks to Home Assistant, and decided to explore what I could do with Kodi and Maria DB.

So I deployed a second Debian VM, installed Maria DB, connected one of my Kodi, all good.
Installed Docker, OK.
Installed kodi-headless, connected it to MariaDB, all good.
Can open the WebUI, see the media etc.

But...all my sources are still in my Windows10 shares, I just can't get the Docker container to connect SMB, so obviously I can't update the library.

The Kodi log shows:

json:
13:42:07.932 T:140160872175360   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.1.8/Media/Movies'

                                            unix_err:'1' error : 'Operation not permitted'

13:42:07.932 T:140160872175360   ERROR: GetDirectory - Error getting smb://192.168.1.8/Media/Movies/

13:43:38.688 T:140162106067072  NOTICE: Samba is idle. Closing the remaining connections

I tried Hostname, IP address, password on the share, no password...can't browse SMB from Docker container.

How do you guys go about this? Are there some instructions you can point me to? I have spent a couple days trying to make this work...
Thanks in Advance!!

[MrTarantula]

This does not belong in development, and it's more of a Docker question anyway. You're better off trying the support forum. But my first instinct would be to check the Windows firewall. Try completely disabling it (only temporarily) to see if that fixes the issue. Then figure out what ports you need.

[Damien67]

I figured someone would have been in the same situation and could have provided easy help...

But you did got me somewhere. I never questioned those Win10 shares because all other devices access them fine, ShieldTV, Android TV, PCs...no problem.
I also have a NAS (older Readynas, not very fast, good for backups and low read/write speed applications), and the WebUI can browse it just fine in SMB. So the problem isn't Kodi-headless!

More networking troubleshooting to come!
Thanks