Hi! I write here after several times I tried to make Kodi works on my iMac, before on High Sierra and now on Mojave. I installed the last version of Kodi 17 and tried the beta 18 too, there's no way to make it work. I tried to disable gatekeeper and it doesn't work. I don't really know what the problem is and how to resolve it. I can copy here the Log of the error when I try to open it and it crashes. Hope somebody could help me to finally resolve the problem and use Kodi on my Mac
THANK YOU!!
https://paste.kodi.tv/eqetunacir
That’s a strange crash - never seen this one before - I need a
debug log (wiki) in addition please.
(2018-11-05, 20:43)Memphiz Wrote: [ -> ]That’s a strange crash - never seen this one before - I need a debug log (wiki) in addition please.
I guess I didn't understood how to create this debug log. I found a Kodi.log file on a folder and a guisettings.xml. I have to send one of those files?
Do you have anything inside the dvd Drive? If yes - take it out - if not - put a DVD in for a test.
Is this a real Mac or a hackintosh?
(2018-11-07, 17:55)Memphiz Wrote: [ -> ]Do you have anything inside the dvd Drive? If yes - take it out - if not - put a DVD in for a test.
Is this a real Mac or a hackintosh?
It's a real late 2013 iMac, it doesn't have the Dvd drive on it....
Help!!! I have the same issue...I just update to Mojave. I tried looking for the Kodi.log to find the problem, but it does not appear anywhere.
(2018-11-08, 18:42)mcnacchia Wrote: [ -> ]Help!!! I have the same issue...I just update to Mojave. I tried looking for the Kodi.log to find the problem, but it does not appear anywhere.
It's on a hidden folder, you need to make it visible to see it. I use an app called InvisibliX to make visibile the hidden files. Then you can find it on /Users/<username>/Library/Logs/kodi.log
daniele2506: i have built a test build that should not crash in the same way (but mit still crash). It has more debug output in addition.
The test build will appear in maybe 1 hour from now here:
http://mirrors.kodi.tv/test-builds/osx/x86_64/
And it will have something like "cdio_debug" in the filename.
Please test this build and post a new
debug log (wiki) and crash report (in case it crashes)
No Kodi.log exists anywhere...I still do not understand why it does not open. I guess you can tell, I am very new at this.
(2018-11-08, 23:18)Memphiz Wrote: [ -> ]daniele2506: i have built a test build that should not crash in the same way (but mit still crash). It has more debug output in addition.
The test build will appear in maybe 1 hour from now here:
http://mirrors.kodi.tv/test-builds/osx/x86_64/
And it will have something like "cdio_debug" in the filename.
Please test this build and post a new debug log (wiki) and crash report (in case it crashes)
Oh thank you very much!!! I'll test it and I'll let you know
(2018-11-08, 23:22)mcnacchia Wrote: [ -> ]No Kodi.log exists anywhere...I still do not understand why it does not open. I guess you can tell, I am very new at this.
you should make as I did thanks to the help in this post. I am still trying to resolve. You should post your crash log too and try to ding this Kodi.log in the invisibile folders
(2018-11-08, 23:43)daniele2506 Wrote: [ -> ] (2018-11-08, 23:18)Memphiz Wrote: [ -> ]daniele2506: i have built a test build that should not crash in the same way (but mit still crash). It has more debug output in addition.
The test build will appear in maybe 1 hour from now here:
http://mirrors.kodi.tv/test-builds/osx/x86_64/
And it will have something like "cdio_debug" in the filename.
Please test this build and post a new debug log (wiki) and crash report (in case it crashes)
Oh thank you very much!!! I'll test it and I'll let you know
Wow! It opened! It seems that something worked, don't know why
this is the debug log:
https://paste.kodi.tv/puzapemaba.kodi
Can you explain to me what the problem is eventually and what should I do now? Thank you!
You have debug disabled - please enable debug and post a new debug log. Then I can tell whats going wrong.
It is sort of expected that it works now - but I need the full debug log to invent the proper fix.