After updating to 5.7 the kodi stopped working

werneck · 2017-06-11T22:12:10+00:00

Good evening, after the upgrade to 5.7 I can no longer open the kodi, just go back to the batocer menu when I try to get in, can you help me?

PauloCamper

Can we rollback the upgrade?

PauloCamper

I found this on my kodi.log. These are the last lines before crash.

06:52:43 T:139799289648896 DEBUG: Thread LanguageInvoker 139799289648896 terminating
06:52:43 T:139799281256192 INFO: Python script interrupted by user
06:52:43 T:139799281256192 DEBUG: Thread LanguageInvoker 139799281256192 terminating
06:52:43 T:139800128436160 INFO: XRANDR: /usr/lib/kodi/kodi-xrandr --screen 0 --output HDMI-1 --mode 0x67
06:52:43 T:139799679571712 DEBUG: Thread ActiveAE 139799679571712 terminating
06:52:43 T:139799671179008 DEBUG: Thread AESink 139799671179008 terminating
06:52:43 T:139800128436160 NOTICE: stopped
06:52:43 T:139800128436160 NOTICE: destroy
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2af6ea0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2adb730 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2b82f30 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2afc2b0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2ae1c40 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2d405c0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2b5dc50 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2b33260 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2afeef0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2afa1f0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:52:43 T:139800128436160 NOTICE: closing down remote control service
06:52:43 T:139800128436160 INFO: LIRC SetEnabled: disabled
06:52:43 T:139800128436160 NOTICE: unload sections
06:52:43 T:139800128436160 DEBUG: CAnnouncementManager - Announcement: OnClear from xbmc
06:52:43 T:139800128436160 NOTICE: special://profile/ is mapped to: special://masterprofile/
06:52:43 T:139800128436160 DEBUG: object 0 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 1 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 2 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 3 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 4 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 5 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 6 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 7 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 8 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 9 --> 0 instances
06:52:43 T:139800128436160 DEBUG: CAnnouncementManager - Announcement: OnClear from xbmc
06:52:43 T:139800128436160 NOTICE: destroy
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10021 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist
06:52:43 T:139800128436160 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist
06:52:43 T:139800128436160 NOTICE: closing down remote control service
06:52:43 T:139800128436160 INFO: LIRC SetEnabled: disabled
06:52:43 T:139800128436160 NOTICE: unload sections
06:52:43 T:139800128436160 DEBUG: object 0 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 1 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 2 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 3 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 4 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 5 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 6 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 7 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 8 --> 0 instances
06:52:43 T:139800128436160 DEBUG: object 9 --> 0 instances
06:52:43 T:139800128436160 NOTICE: application stopped...
06:52:43 T:139800128436160 DEBUG: ActiveAE DSP - destroyed
06:52:43 T:139800128436160 DEBUG: PVRManager - destroyed
06:52:43 T:139800128436160 DEBUG: LinuxRendererGL: Cleaning up GL resources

FireRat666

I am on a Clean Install of 5.7 and Kodi is working for me on RaspBerryPi 3

nadenislamarre

it looks like kodi is not crashing, but closing for an unknown reason.
but i've really really not enough feedback to help. i got only 1 file report ; i cannot find a solution without more information from people having troubles.

nadenislamarre

can somebody have the trouble do the following :

1) unplug all the pads
2) plug a keyboard
3) start kodi

According to the report i have, it looks like a bug/issue with joysticks :

At the end of the kodi start, kodi find 1 button pressed (but was it really pressed) and launch the shutdown procedure as if the user requested to quit.
It's something to confirm with this test and with some other report files.

22:05:38 T:1925812224 DEBUG: Joystick 0 button 1 Down
22:05:38 T:1925812224 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc

Cankemi

Hello, how are you?
I unplugged my wireless xbox 360 joystick and started the batocera only with the keyboard. By doing this I was able to open Kodi.

I generated the report:
https://drive.google.com/open?id=0Bze3RNdZFgnsdF9iTnN3VkF6TXM

NickDG

Hi,
Update from Udoo x86 running Batocera 5.7 from 2,5" HDD

I too deleted all paired controllers and only left the keyboard plugged, now im able to run Kodi 17

PauloCamper

The problem is joystick.
When Kodi starts with just a keyboard, there's no problem.
When trying to start with joystick, Kodi does not work.
After starts Kodi with keyboard, you can plug joystick and it works. But, if you restart Kodi with joystick plugged in, he won't starts again.

Kodi 17 is not recognizing joystick at boot.

Scofield

i tryed launcher kodi with a .sh script and works fine, a member on facebook group shared this script, temporary solution
script

#!/bin/bash

Horrible script

will kill kodi when it's thread are < 8

because it the number of threads hanging

when you try to quit after seeing a movie

and letting the process hang

LD_LIBRARY_PATH="/usr/lib/mysql" /usr/lib/kodi/kodi.bin --standalone -fs -n &
pid=$!

sleep 5

running=1
while [[ "$running" == "1" ]]; do
sleep 3
nbThread=cat /proc/$pid/status | grep Threads: | cut -d":" -f2 | tr -d '[[:space:]]'
if [[ "$nbThread" -lt "8" ]];then
kill $pid
running=0
fi
done
echo "exiting"

es_systems file

<system>
<fullname>Kodi</fullname>
<name>kodi</name>
<path>recalbox/share/roms/kodi</path>
<extension>.sh .SH</extension>
<command>/recalbox/scripts/kodilauncher.sh %ROM% "kodi"</command>
<platform>kodi</platform>
<theme>kodi</theme>
</system>

nadenislamarre

i guess there is a conflict with the internal kodi joystick database.
i'll get a "classical pad" and make new test.
people having trouble can indicate their joystick please here ?

Scofield

nadenislamarre i use snesc30 8bitdo and xbox 360

nadenislamarre

@Scofield you have the problem with 2 differents pad ?
does it work if you unplug both pads and use a keyboard ?
i still can't reproduce which make it hard to analyse for the moment.

Scofield

nadenislamarre dosen't work any joystick or keyboard, i tried wiht Dragon Rise zero delay too, with fresh install and upgrade my system i have the same problem

nadenislamarre

@Scofield i got only 1 report file to analyse the issue. Can you send me yours please ?

Scofield

nadenislamarre Yes, i send to you, do need generate diferent files by pad?

Scofield

nadenislamarre https://1fichier.com/?pd4eq7e09v

nadenislamarre

@Scofield same issue but with an xbox 360 controller.
can you unplug the xbox controller, rerun kodi and remake a new report ?

18:40:57 T:1926176768 DEBUG: Joystick 0 button 15 Up
18:40:57 T:1926176768 DEBUG: Joystick 0 button 1 Down
18:40:57 T:1926176768 DEBUG: Activating window ID: 10111
18:40:57 T:1926176768 DEBUG: ------ Window Init (DialogButtonMenu.xml) ------
18:40:57 T:1926176768 INFO: Loading skin file: DialogButtonMenu.xml, load type: KEEP_IN_MEMORY
18:40:57 T:1926176768 DEBUG: Load DialogButtonMenu.xml: 13.04ms
18:40:57 T:1926176768 DEBUG: Alloc resources: 14.05ms (13.27 ms skin load)
18:40:57 T:1926176768 DEBUG: Joystick 0 button 1 Up
18:40:58 T:1926176768 DEBUG: Joystick 0 button 1 Down
18:40:58 T:1926176768 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc

Scofield

nadenislamarre I reinstalled an old backup (5.6) and upgraded to 5.7, now keyboard works.

keyboard
https://1fichier.com/?3n2jozoos6
snes30
https://1fichier.com/?8g39m93i9l

Razorgate

Well. ..i go wait for 5.8 version 😕

nadenislamarre

i've got an xbox one controller. it works (via usb), and kodi works.
for the moment, i've only 2 reports. I just think that it's related to some controllers, like the xbox 360 one.
@Scofield no other pad to test ?

« Previous Page Next Page »