the only 0 byte profile.xml is in \\192.168.1.16\Kodi-Failed\userdata delete this?
Posts by sparkplug
-
-
I recently rebooted my libeelec on slice that has been crashing a lot
with difficulty I updated to 9.2
How even I can not leave safe mode
profiles are in \\192.168.1.16\Userdata\profiles as well as the failed dir
the error part of the log is as follows
"
############## kodi CRASH LOG ###############
################ SYSTEM INFO ################
Date: Wed Dec 4 10:58:37 EST 2019
kodi Options: --standalone -fs
Arch: armv7l
Kernel: Linux 4.19.66 #1 SMP Mon Sep 2 20:03:15 EDT 2019
Release: LibreELEC 9.1.501
############## END SYSTEM INFO ##############
############### STACK TRACE #################
=====> Core file: /storage/.cache/cores/core.!usr!lib!kodi!kodi.bin.1575475117.953
=========================================
[New LWP 953]
[New LWP 954]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x03070200 in ?? ()
[Current thread is 1 (Thread 0x737b0010 (LWP 953))]
Thread 2 (Thread 0x737af380 (LWP 954)):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x2440968) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x24470bc, cond=0x2440940) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x2440940, mutex=0x24470bc) at pthread_cond_wait.c:655
#3 0x74d0b22c in std::condition_variable::wait(std::unique_lock<std::mutex>&) () from /usr/lib/libstdc++.so.6
#4 0x006b9ff0 in ?? ()
#5 0x006ba07c in ?? ()
#6 0x00384dd8 in ANNOUNCEMENT::CAnnouncementManager::Process() ()
#7 0x00695864 in CThread::Action() ()
#8 0x006b9a54 in CThread::staticThread(void*) ()
#9 0x76f4a39c in start_thread (arg=0x737af380) at pthread_create.c:486
#10 0x74e88518 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /usr/lib/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Thread 1 (Thread 0x737b0010 (LWP 953)):
#0 0x03070200 in ?? ()
#1 0x00505070 in CSettingsManager::OnSettingsCleared() ()
#2 0x0051c8e0 in CSettingsManager::Clear() ()
#3 0x004d6284 in CSettingsBase::Uninitialize() ()
#4 0x004e1ff0 in CSettingsComponent::Deinit() ()
#5 0x004e8508 in CSettingsComponent::~CSettingsComponent() ()
#6 0x004e8538 in CSettingsComponent::~CSettingsComponent() ()
#7 0x0057db58 in CApplication::~CApplication() ()
#8 0x0057dbc8 in CApplication::~CApplication() ()
#9 0x008d70b4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
############# END STACK TRACE ###############
################# LOG FILE ##################
2019-12-04 10:58:37.860 T:1937440784 NOTICE: -----------------------------------------------------------------------
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Starting Kodi (18.4 Git:newclock5_18.4-Leia). Platform: Linux ARM 32-bit
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Using Release Kodi x32 build (version for Raspberry Pi)
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Kodi compiled 2019-09-03 by GCC 8.3.0 for Linux ARM 32-bit version 4.19.66 (267074)
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Running on LibreELEC (official): 9.1.501, kernel: Linux ARM 32-bit version 4.19.66
2019-12-04 10:58:37.861 T:1937440784 NOTICE: FFmpeg version/source: 4.0.4-Kodi
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Host CPU: ARMv7 Processor rev 4 (v7l), 4 cores available
2019-12-04 10:58:37.861 T:1937440784 NOTICE: ARM Features: Neon enabled
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi/
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/kodi/addons
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://masterprofile/ is mapped to: /storage/.kodi/userdata
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://envhome/ is mapped to: /storage
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://home/ is mapped to: /storage/.kodi
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://temp/ is mapped to: /storage/.kodi/temp
2019-12-04 10:58:37.861 T:1937440784 NOTICE: special://logpath/ is mapped to: /storage/.kodi/temp
2019-12-04 10:58:37.861 T:1937440784 NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Local hostname: Kodi
2019-12-04 10:58:37.861 T:1937440784 NOTICE: Log File is located: /storage/.kodi/temp/kodi.log
2019-12-04 10:58:37.862 T:1937440784 NOTICE: -----------------------------------------------------------------------
2019-12-04 10:58:37.864 T:1937440784 INFO: loading settings
2019-12-04 10:58:37.864 T:1937440784 ERROR: CProfileManager: error loading special://masterprofile/profiles.xml, Line 0
Failed to open file
2019-12-04 10:58:37.864 T:1937440784 NOTICE: special://profile/ is mapped to: special://masterprofile/
2019-12-04 10:58:37.864 T:1937440784 FATAL: unable to load profile
############### END LOG FILE ################
############ END kodi CRASH LOG #############
"
Thank you
-
Thank you for keeping us supported
-
now there is raspberry Pi 4 will there be a build? I know we have to wait for the right form factor
-
Thanks for your reply
What i'm looking for a HDMI out
very Hi quality Analog out
Internal Hard drive
Ethernet via wifi and RJ45
A remote control
hopefully 3 or more USB ports
Self contained case
software such as libelec
Optional
sharable tcp stack
addressable via a web page and mapped drive.
Mullticasting? (like sonos)
Im not a programmer.
any idea?
-
I love my slice but there aren't any more
As the slice is getting slightly long in the tooth DOes anyone have any idea what I might use to replace it or get a second unit? 
-
Thanks for the help Chewitt I found that the log files had filled up the available memory. deleted them and all is happy!
Using the latest pre-release fork
-
My lovely slice has started to get wonkey
I am lookng for the latest development builds
Chewitt?
Its seems to reboot lately and get stuck on updating the database with new music recordings
help?.
-
Thanks Chewitt... Glad to see you still with us1! love my Slice
-
Did the update via libele menu in slice I had to change to manual update to get it. Will report back
-
So just to be clear the tar can not be copied to the update directory on the slice cm3?
-
ordered a cm3 today on my side of the pond!
-
If you have a Slice, then just buy the CM3, and swap it with the orignal
Cant find one for sale
-
How do I become a cm3 tester on this side of the pond?
-
Excited thank you
-
-
can we overclock a bit?
-
Up and running nicely