New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osmio 4k kodi not start branch 4.4 #543
Comments
permissions ? |
oh yes funny i have test other 4.4 box and np |
weird :-) |
strange kodi create new files and cant read any more next issue |
/media/hdd is flash or usb device? |
usb hdd root have 777 rights but kodi create new files and rights lost |
but strange test today sf8008 and kodi have works |
something must modify them but how to find what... other hdd? |
6.3 create kodi files with 750 |
kodi is starting when i use a 6.3 userhome 20:39:35.828 T:547981541264 ERROR: GetConverter: iconv_open() for "UTF-8" -> "UTF-32LE" failed, errno = 22 (Invalid argument) and some gui png not show correct |
there is gconv in rrecommends but maybe its job for iconv |
And kodi not start on my gi et 11000 4k. 21:36:14.334 T:3019590416 NOTICE: Starting Kodi (17.6 Git:2019-10-29-7e52c-stb). Platform: Linux ARM 32-bit |
have nothing todo with 4.4 build see build with 4.3 -> GCC 8.2.0 |
Sorry: |
have nothing todo with oe-a .> Running on openpli develop, kernel: |
i am rollback opkg to old version no change issue was wrong file and folder permissions ipk show all correct but after install permissions corrupt root@osmio4kplus:~# ls -l /usr/lib64/kodi/ root@osmio4kplus:~# ls -l /usr/bin/ko* after remove the kodi and install again file permission looks ok |
hmm, cannot this be issue with busybox nice command not being suid? what can change permissions after install ? |
with oe- 4.3 all ok root@osmio4kplus:~# ls -l /usr/bin/ko* root@osmio4kplus:~# ls -l /usr/lib64/kodi/ |
they all have sticky bit set? this is weird ... so in 4.3 flags are 1xxx and in 4.4 0xxx something with pseudo? |
ipk looks ok for me next issue was when i fix the permission kodi start and the profile was create and the permission was not ok too 12:15:08.316 T:547748835216 ERROR: CSettings: unable to load settings from special://masterprofile/guisettings.xml, creating new default settings the file have only x bit no rw kodi cant start, i fix this and kodi works |
arent partitions doublemounted or so ? cannot this be issue with mounts? |
no i use the internel emmc flash box box 1,3gb free, very strange, and why permission are different after remove and install again other box like hd51 all ok |
driver issue ? |
or opkg have issue when to many ipks installed to same time |
what about trying to change permissions in do_install_append ? like chmod -r 0750 ${D}${libdir}/ ... |
The file permission problem goes away if you exclude libopen.so from the preload list in enigma2.sh. #check for sundtek tuner helper lib the problem is not limited to kodi but appears in every file installed by the e2 plugin browser. I think this is related to the glibc version and libopen.so. We must check to remove it if possible. It doesn’t seem necessary now. possible other crash like uianimation we can fix it too |
LIBC_SO = /lib/libc.so.6 ? if yes, then: |
kodi it works now |
Please do not swear, I have no one to ask. A very strange error kodi worked yesterday.But now it does not start-terminal unable to connect to ipc server*** Unable to join nxclient_ipc_thread_regular |
out of system resources,maybe? |
Clean installation only kodi.I uninstalled and installed on a new one that does not work. |
And this should not be for kodi? |
newflash older image and try again? |
when it worked and now dont,but nothing significant changed? |
Nothing has changed. |
does kodi start from e2 plugins screen? |
I think I found why the kodi does not work, but I still need to check.It seems to be related to the file defconfig. |
fixed with last updates |
kodi not start log show this
19:20:53.647 T:547600736144 NOTICE: special://profile/ is mapped to: special://masterprofile/
19:20:53.647 T:547600736144 NOTICE: -----------------------------------------------------------------------
19:20:53.647 T:547600736144 NOTICE: Starting Kodi (17.6 Git:2019-10-05-7e52c-stb). Platform: Linux ARM 64-bit
19:20:53.647 T:547600736144 NOTICE: Using Release Kodi x64 build
19:20:53.647 T:547600736144 NOTICE: Kodi compiled Oct 5 2019 by GCC 9.2.0 for Linux ARM 64-bit version 5.2.0 (328192)
19:20:53.661 T:547600736144 NOTICE: Running on Unknown Linux Distribution 0.0, kernel: Linux ARM 64-bit version 5.3.0
19:20:53.661 T:547600736144 NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
19:20:53.661 T:547600736144 NOTICE: Host CPU: ARMv8 Processor rev 0 (v8l), 2 cores available
19:20:53.661 T:547600736144 NOTICE: ARM Features: Neon disabled
19:20:53.661 T:547600736144 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
19:20:53.661 T:547600736144 NOTICE: special://xbmcbin/ is mapped to: /usr/lib64/kodi
19:20:53.661 T:547600736144 NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib64/kodi/addons
19:20:53.661 T:547600736144 NOTICE: special://masterprofile/ is mapped to: /media/hdd/.kodi/userdata
19:20:53.661 T:547600736144 NOTICE: special://envhome/ is mapped to: /media/hdd
19:20:53.661 T:547600736144 NOTICE: special://home/ is mapped to: /media/hdd/.kodi
19:20:53.661 T:547600736144 NOTICE: special://temp/ is mapped to: /tmp/kodi
19:20:53.661 T:547600736144 NOTICE: special://logpath/ is mapped to: /tmp/kodi
19:20:53.661 T:547600736144 NOTICE: The executable running is: /usr/lib64/kodi/kodi.bin
19:20:53.661 T:547600736144 NOTICE: Local hostname: osmio4kplus
19:20:53.661 T:547600736144 NOTICE: Log File is located: /tmp/kodi//kodi.log
19:20:53.661 T:547600736144 NOTICE: -----------------------------------------------------------------------
19:20:53.662 T:547600736144 NOTICE: load settings...
19:20:53.663 T:547600736144 ERROR: CSettings: error loading settings definition from special://xbmc/system/settings/settings.xml, Line 0
Failed to open file
19:20:53.663 T:547600736144 FATAL: Unable to load settings definitions
all files exist with branch 4.3 all working no idea why
The text was updated successfully, but these errors were encountered: