Results 1 to 7 of 7

Thread: Kodi Crash -- Something different

  1. #1
    Join Date
    Nov 2016
    Beans
    6

    Kodi Crash -- Something different

    Hi there everyone,
    Before I explain what I can about my issue with Kodi I'd like to make something very clear:

    I have used linux for about 7 years now as my preferred operating system. I worked on Shell/Bash coding, and even made a very nice tutorial about using xrandr with cvt for newcomers who aren't familiar with Ubuntu.
    Since I couldn't find the login for my original account (rhss6-2011) I made this account.
    HOWEVER for the last 3 years I haven't really used computers at all, so I did something new...

    I'm running a Raspberry Pi 3 Model B with Ubuntu Mate 16.04 LTS. While I am NOT new to Linux (regardless whether any version of *buntu, Debian, Kali, BackTrack, or even TinyCore) Raspberry Pi is something I have *NEVER* dealt with before. I'm posting this into the UbuntuForums because (due to familiarity) I've done some weird things that worked such as using Debian methods to solve Ubuntu issues, or even using Kali to fix Debian by adding to the sources.list and whatnot.

    Anyways, I have my Raspberry Pi up and running (obviously), and installed Kodi (via using the Ubuntu Software Manager, seeing how allegedly there's no need to compile it or anything). Installation went fine. "Launching" of the application went just fine. For approximately 1.3 seconds. Kodi crashed before even coming to the main menu. No black screen, and the system didn't freeze either. Conveniently while mucking with my system a bit here and there, making some tweaks etc. I noticed a crash-log in my home folder.

    So, I'm hoping that by giving y'all the crashlog, someone will at least be able to point me in the right direction.
    If anyone can help me figure this one out, or of course explain exactly what's going on that would be greatly appreciated!

    Sincerely,
    TORDarthRevan


    Code:
    ############## Kodi CRASH LOG ###############
    
    ################ SYSTEM INFO ################
     Date: Sat May 20 22:07:33 EDT 2017
     Kodi Options: 
     Arch: armv7l
     Kernel: Linux 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016
     Release: Ubuntu 16.04.2 LTS (Xenial Xerus)
    ############## END SYSTEM INFO ##############
    
    ############### STACK TRACE #################
    =====>  Core file: /home/darthrevan/core (2017-05-20 22:07:22.928861301 -0400)
            =========================================
    [New LWP 8759]
    [New LWP 8779]
    [New LWP 8763]
    [New LWP 8786]
    [New LWP 8787]
    [New LWP 8788]
    [New LWP 8789]
    [New LWP 8762]
    [New LWP 8775]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
    Core was generated by `/usr/lib/arm-linux-gnueabihf/kodi/kodi.bin'.
    Program terminated with signal SIGSEGV, Segmentation fault.
    #0  0x74c59964 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
    [Current thread is 1 (Thread 0x6f9a3000 (LWP 8759))]
    
    Thread 9 (Thread 0x6efff2e0 (LWP 8775)):
    #0  0x74c90a50 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
    #1  0x00000000 in ?? ()
    Backtrace stopped: previous frame identical to this frame (corrupt stack?) -- What???
    
    Thread 8 (Thread 0x6b99f2e0 (LWP 8762)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7f03a in pthread_cond_timedwait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x004247fc in ActiveAE::CActiveAE::Process() ()
    #3  0x0091d568 in CThread::Action() ()
    #4  0x0091d74c in CThread::staticThread(void*) ()
    #5  0x76a7a5b4 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #6  0x74c96aac in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 7 (Thread 0x613bc2e0 (LWP 8789)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7edba in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x6da9229a in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 6 (Thread 0x6c52a2e0 (LWP 8788)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7edba in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x6da9229a in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 5 (Thread 0x6cd2a2e0 (LWP 8787)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7edba in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x6da9229a in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 4 (Thread 0x6d52a2e0 (LWP 8786)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7edba in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x6da9229a in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 3 (Thread 0x6f9a02e0 (LWP 8763)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7eeb2 in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x761de7d2 in pa_threaded_mainloop_wait () from /usr/lib/arm-linux-gnueabihf/libpulse.so.0
    #3  0x00437546 in CAESinkPULSE::AddPackets(unsigned char**, unsigned int, unsigned int) ()
    #4  0x00425bfa in ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) ()
    #5  0x00426820 in ActiveAE::CActiveAESink::StateMachine(int, Actor::Protocol*, Actor::Message*) ()
    #6  0x00426e8c in ActiveAE::CActiveAESink::Process() ()
    #7  0x0091d568 in CThread::Action() ()
    #8  0x0091d74c in CThread::staticThread(void*) ()
    #9  0x76a7a5b4 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #10 0x74c96aac in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    Thread 2 (Thread 0x6e5ff2e0 (LWP 8779)):
    #0  0x76a83454 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #1  0x76a7f03a in pthread_cond_timedwait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #2  0x0091c1be in XbmcThreads::CEventGroup::wait(unsigned int) ()
    #3  0x00748e9a in CRemoteControl::Process() ()
    #4  0x0091d568 in CThread::Action() ()
    #5  0x0091d74c in CThread::staticThread(void*) ()
    #6  0x76a7a5b4 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
    #7  0x74c96aac in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    
    Thread 1 (Thread 0x6f9a3000 (LWP 8759)):
    #0  0x74c59964 in strlen () from /lib/arm-linux-gnueabihf/libc.so.6
    #1  0x006dbf94 in CRenderSystemGLES::InitRenderSystem() ()
    #2  0x3fb00074 in ?? ()
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    ############# END STACK TRACE ###############
    
    ################# LOG FILE ##################
    
    22:06:54 T:1872375808  NOTICE: special://profile/ is mapped to: special://masterprofile/
    22:06:54 T:1872375808  NOTICE: -----------------------------------------------------------------------
    22:06:54 T:1872375808  NOTICE: Starting Kodi from Debian (15.2 Git: (unknown)). Platform: Linux ARM (Thumb) 32-bit
    22:06:54 T:1872375808  NOTICE: Using Release Kodi from Debian x32 build
    22:06:54 T:1872375808  NOTICE: Kodi from Debian compiled from 15.2+dfsg1-3ubuntu1 by GCC 5.3.1 for Linux ARM (Thumb) 32-bit version 4.4.6 (263174)
    22:06:54 T:1872375808  NOTICE: Running on Ubuntu 16.04.2 LTS, kernel: Linux ARM 32-bit version 4.4.38-v7+
    22:06:54 T:1872375808  NOTICE: FFmpeg version: 2.8.6-1ubuntu2
    22:06:54 T:1872375808  NOTICE: Host CPU: ARMv7 Processor rev 4 (v7l), 4 cores available
    22:06:54 T:1872375808  NOTICE: ARM Features: Neon disabled
    22:06:54 T:1872375808  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
    22:06:54 T:1872375808  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/arm-linux-gnueabihf/kodi
    22:06:54 T:1872375808  NOTICE: special://masterprofile/ is mapped to: /home/darthrevan/.kodi/userdata
    22:06:54 T:1872375808  NOTICE: special://home/ is mapped to: /home/darthrevan/.kodi
    22:06:54 T:1872375808  NOTICE: special://temp/ is mapped to: /home/darthrevan/.kodi/temp
    22:06:54 T:1872375808  NOTICE: The executable running is: /usr/lib/arm-linux-gnueabihf/kodi/kodi.bin
    22:06:54 T:1872375808  NOTICE: Local hostname: Korriban
    22:06:54 T:1872375808  NOTICE: Log File is located: /home/darthrevan/.kodi/temp/kodi.log
    22:06:54 T:1872375808  NOTICE: -----------------------------------------------------------------------
    22:06:54 T:1872375808   ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property 'OnLowBattery'
    22:06:54 T:1872375808   ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property 'CanSuspend'
    22:06:55 T:1872375808   ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property 'CanHibernate'
    22:06:55 T:1872375808  NOTICE: load settings...
    22:06:55 T:1872375808  NOTICE: Found 1 Lists of Devices
    22:06:55 T:1872375808  NOTICE: Enumerated PULSE devices:
    22:06:55 T:1872375808  NOTICE:     Device 1
    22:06:55 T:1872375808  NOTICE:         m_deviceName      : Default
    22:06:55 T:1872375808  NOTICE:         m_displayName     : Default
    22:06:55 T:1872375808  NOTICE:         m_displayNameExtra: Default Output Device (PULSEAUDIO)
    22:06:55 T:1872375808  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
    22:06:55 T:1872375808  NOTICE:         m_channels        : FL,FR
    22:06:55 T:1872375808  NOTICE:         m_sampleRates     : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
    22:06:55 T:1872375808  NOTICE:         m_dataFormats     : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
    22:06:55 T:1872375808  NOTICE:     Device 2
    22:06:55 T:1872375808  NOTICE:         m_deviceName      : alsa_output.0.analog-stereo
    22:06:55 T:1872375808  NOTICE:         m_displayName     : bcm2835 ALSA Analog Stereo
    22:06:55 T:1872375808  NOTICE:         m_displayNameExtra: Analog Output (PULSEAUDIO)
    22:06:55 T:1872375808  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
    22:06:55 T:1872375808  NOTICE:         m_channels        : FL,FR
    22:06:55 T:1872375808  NOTICE:         m_sampleRates     : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
    22:06:55 T:1872375808  NOTICE:         m_dataFormats     : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
    22:06:55 T:1872375808   ERROR: CSettings: unable to load settings from special://masterprofile/guisettings.xml, creating new default settings
    22:06:55 T:1872375808  NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
    22:06:55 T:1872375808  NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)
    22:06:55 T:1872375808  NOTICE: Default DVD Player: dvdplayer
    22:06:55 T:1872375808  NOTICE: Default Video Player: dvdplayer
    22:06:55 T:1872375808  NOTICE: Default Audio Player: paplayer
    22:06:55 T:1872375808  NOTICE: Disabled debug logging due to GUI setting. Level 0.
    22:06:55 T:1872375808  NOTICE: Log level changed to "LOG_LEVEL_NORMAL"
    22:06:55 T:1872375808  NOTICE: Loading player core factory settings from special://xbmc/system/playercorefactory.xml.
    22:06:55 T:1872375808  NOTICE: Loaded playercorefactory configuration
    22:06:55 T:1872375808  NOTICE: Loading player core factory settings from special://masterprofile/playercorefactory.xml.
    22:06:55 T:1872375808  NOTICE: special://masterprofile/playercorefactory.xml does not exist. Skipping.
    22:06:55 T:1805251296  NOTICE: Thread ActiveAE start, auto delete: false
    22:06:55 T:1872364256  NOTICE: Thread AESink start, auto delete: false
    22:07:00 T:1805251296   ERROR: ActiveAE::InitSink - failed to init
    22:07:09 T:1872364256   ERROR: Previous line repeats 1 times.
    22:07:09 T:1872364256  NOTICE: PulseAudio: Opened device Default in pcm mode with Buffersize 150 ms
    22:07:15 T:1872375808  NOTICE: Previous line repeats 2 times.
    22:07:15 T:1872375808  NOTICE: ADDONS: Using repository repository.xbmc.org
    22:07:15 T:1851781856  NOTICE: Thread RemoteControl start, auto delete: false
    22:07:16 T:1872375808  NOTICE: Checking resolution 16
    22:07:21 T:1872375808   ERROR: CWinSystemX11::XErrorHandler: BadAtom (invalid Atom parameter), type:0, serial:33, error_code:5, request_code:18 minor_code:0
    22:07:21 T:1872375808 WARNING: Visual 0x21 of the SDL window is not suitable, looking for another one...
    22:07:21 T:1872375808   ERROR: Failed to determine egl config for visual info
    22:07:21 T:1872375808   ERROR: Previous line repeats 236 times.
    22:07:21 T:1872375808   ERROR: EGL/GLX Error: vInfo is NULL!
    
    
    ############### END LOG FILE ################
    
    ############ END Kodi CRASH LOG #############
    Not that I should really have to say this, but the crashlog itself isn't exactly making it clear what EXACTLY I'm missing.

    Not sure if it matters, but... could there be an issue with my "display"? I'm using an old HP w2007 Display with an HDMI to DVI male end adapter. The display only uses DVI or VGA, so I bought an adapter that enables me to plug one male end of the HDMI cable into it, and then converted into a DVI male adapter it plugs into my HP Display. I'm wondering if for that very reason I don't have ANY display drivers, which if Kodi is requiring, may prevent me from being able to launch the application unless I can edit the coding of Kodi..??

    Just as an Example as to what I mean...

    Code:
    darthrevan@Korriban:~$ xrandr
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 1680 x 1050, current 1680 x 1050, maximum 1680 x 1050
    default connected 1680x1050+0+0 0mm x 0mm
       1680x1050      0.00* 
    darthrevan@Korriban:~$

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    19,854
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Kodi Crash -- Something different

    If you want to run Kodi on a Raspberry Pi, the easy, pre-built solution is osmc.
    https://osmc.tv/

    Get the img and use dd to shovel the bits onto an microSD. Of course, you could use the tool to "build" the SD stuff. Why are people afraid of dd?

  3. #3
    Join Date
    Nov 2016
    Beans
    6

    Re: Kodi Crash -- Something different

    Quote Originally Posted by TheFu View Post
    If you want to run Kodi on a Raspberry Pi, the easy, pre-built solution is osmc.
    https://osmc.tv/

    Get the img and use dd to shovel the bits onto an microSD. Of course, you could use the tool to "build" the SD stuff. Why are people afraid of dd?
    The advice is greatly appreciated, however that isn't a fix - that's (in my opinion) the same as giving up because something is "too difficult", and I'm just not that guy. I have ordered a couple more SD cards, and might end up doing that just for when I have a movie night or something, but my raspberry pi is supposed to be my cheap alternative to a desktop/laptop. It would defeat the entire purpose by installing an OS that (from the looks of their website) has literally only one purpose...

    So, IS there a way to fix Kodi, or re-install it an alternative way for Raspberry PI with Ubuntu Mate, or are you trying to tell me in a very nice way that's it's just not possible for some reason?

    It took me two days to get this far (since I screwed up the OS by accident, and had to fix it), and I'm not quite ready to give up yet.

  4. #4
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    19,854
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Kodi Crash -- Something different

    Impossible? Probably not. However, people have worked over 10 yrs to make a system that mostly works. Why not take advantage of that? There are multi-boot solutions for r-pi devices. You can have 5+ different OSes on a single microSD card.

    Sometimes doing it the hard way is the path to enlightenment.
    Sometimes doing it the hard way is the path to wasted time.
    Only you can decide when the line is crossed between those.

    You might use the OSMC distro as a way to get the list of packages that are needed for a working Kodi install. Perhaps?

    I would never consider using a r-pi as a desktop. A $50 Intel CPU is 50x (or more) faster and doesn't have the I/O limitations that all r-pi devices have.

    I wish you luck.

  5. #5
    Join Date
    Nov 2016
    Beans
    6

    Re: Kodi Crash -- Something different

    That's true...
    After giving it some thought this is what I came up with;
    Temporarily I'm going to install OSMC to my USB drive, and after enabling boot mode on the RBPI I'm going to run it from the USB. After that, I'm definitely going to use your suggestion of finding the list of packages needed to install, and probably end up packaging them into tarballs which will then be copied onto another USB, and switched into my Mate desktop.

    The main reason why I'm using the PI for a desktop, is because it was cheap, incredibly small (I'll eventually basically build a laptop out of it using an external usb DVD RW, among others things at which point it'll be about the size of a tablet, but able to do what I need it for which arguable can't be done on a tablet), and for the purposes of primarily web browsing, email, shell/bash coding, HTML coding, and maybe a few other things it's perfect. I bought it on Ebay for around 30$, then the keyboard and mouse were another 8 altogether.

    I already have a MicroSD with Kali on it for pentesting, I'll have this OS as my flagship, and then we'll see what happens to OSMC. Then again.... Once I hook up the external HDD I really should just dualboot all the OS's I'm using, as that would be substantially more practical.

    Anyways, thanks for the help - it's greatly appreciated!

  6. #6
    Join Date
    Nov 2012
    Location
    Halloween Town
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: Kodi Crash -- Something different

    Thread moved to Multimedia Software.

  7. #7
    Join Date
    Jun 2007
    Location
    Hikkaduwa
    Beans
    3,173
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Kodi Crash -- Something different

    I was using Kodi on a Win10 Intel compute stick, It was a little choppier than using VLC on that device.
    I have been testing OpenELEC on a Raspberry Pi and it is way better, even streaming off a slowish internet connection is smooth.
    It is what happens when you concentrate on doing just one thing really well.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •