2017-02-19, 15:38
Kodi has been running on this hardware for years without issue, but recently, it is unable to start. I created a clean ~/.kodi to minimize variables. Debug is here. Any thoughts are welcomed.
2017-02-19, 15:38
2017-02-19, 15:43
wrong gpu drivers or no xserver available. It's not a Debug Log - so I cannot see.
As it worked for years -> check what you "ARCHgraded" ...
As it worked for years -> check what you "ARCHgraded" ...
2017-02-19, 15:50
@fritsch - Now using the advancedsettings.xml shown for Advanced#advancedsettings.xml_for_everything... but it is the same number of lines... what am I missing?
original log posted above
new log with everything debugging
I see segfaults in dmesg that correspond to when I try launching kodi.
EDIT: The corresponding nvidia modules are loaded (340.xx series) and the lxdm greeter can run with this setup :/
original log posted above
new log with everything debugging
I see segfaults in dmesg that correspond to when I try launching kodi.
Code:
kodi.bin[482]: segfault at 8 ip 00000000009ae7e1 sp 00007ffc1ce20020 error 4 in kodi.bin[400000+24ef000]EDIT: The corresponding nvidia modules are loaded (340.xx series) and the lxdm greeter can run with this setup :/
2017-02-19, 16:10
glxinfo is needed - your log does not startup with debugging therefore I cannot even say which GPU driver / userspace side you are using.
Your issue has nothing to do with kodi. But driver / userspace f*ckup :-)
Your issue has nothing to do with kodi. But driver / userspace f*ckup :-)
2017-02-19, 16:11
@fritsch - Is there anything else I can place in advancedsettings.xml to help? Currently, starting it with:
Code:
# cat /var/lib/kodi/.kodi/userdata/advancedsettings.xml
<advancedsettings>
<loglevel>1</loglevel>
<debug>
<extralogging>true</extralogging>
<setextraloglevel>32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536</setextraloglevel>
<showloginfo>true</showloginfo>
</debug>
</advancedsettings>2017-02-19, 16:31
More info:
The segfault and errors only happen when I try launch using the kodi user/systemd service.
If I log in to lxdm as another user, and launch kodi from a shell, it runs as expected.
Debug log after manually logging into lxdm and launching from another user: here.
EDIT: I think the problem is with xorg-server... downgrading it (and others) returns functionality.
I don't have time to debug further now, but the problem is likely due to one of the above + the systemd standalone-service on this particular hardware. Note for others following this thread that the packages listed above are from 14-Feb-2017 snapshot.
The segfault and errors only happen when I try launch using the kodi user/systemd service.
If I log in to lxdm as another user, and launch kodi from a shell, it runs as expected.
Debug log after manually logging into lxdm and launching from another user: here.
EDIT: I think the problem is with xorg-server... downgrading it (and others) returns functionality.
Code:
Packages (22) alsa-utils-1.1.3-2 bash-4.4.012-1 bzip2-1.0.6-6 dbus-1.10.16-1 fixesproto-5.0+9+g4292ec1-1 glib2-2.50.3-1
gnutls-3.5.9-1 guile-2.0.14-1 libkscreen-5.9.2-1 libnl-3.2.29-2 linux-4.9.9-1 mesa-17.0.0-1
ncurses-6.0+20170128-1 nvidia-340xx-340.102-1 nvidia-340xx-libgl-340.102-1 nvidia-340xx-utils-340.102-1
readline-7.0.003-1 sqlite-3.17.0-1 vim-8.0.0329-1 vim-runtime-8.0.0329-1 xorg-server-1.19.1-5
xorg-server-common-1.19.1-5I don't have time to debug further now, but the problem is likely due to one of the above + the systemd standalone-service on this particular hardware. Note for others following this thread that the packages listed above are from 14-Feb-2017 snapshot.
2017-09-19, 13:37
not in the x-server business. updated to the latest kodi version from git, the same error
2017-09-19, 14:33
Guys - if no Xserver is available kodi cannot start. This has nothing to do with kodi ... if you start xterm you will get the very same error.
2017-09-20, 08:45
the Xserver starts up normally. Kodi does not work.
kodi from last version git falls with error.
rolled back to the old version Kodi (18-Alpha1, git:20170819-0f9abae) and it all worked again.
kodi from last version git falls with error.
rolled back to the old version Kodi (18-Alpha1, git:20170819-0f9abae) and it all worked again.
2017-09-20, 09:40
See this exactly happens when people shout "me too". without a Debug Log. I fixed a problem for GLX (run on nvidia gpus) yesterday, which might have fixed your personal issue which has absolutely nothing to do with the OP's issue.
2017-09-22, 06:44
Since your fix, I'm having the "Failed to find matching visual" errror. This is the log of Milhouse Generic LibreELEC.tv Leia build #0921: https://pastebin.com/hLLYB0u2
2017-09-22, 07:10
Same problem here NVidia card and after kodi updates same segfault, got a new update 5 minutes ago and same:
22:08:55.199 T:140291348166976 INFO: Pixel Ratio: 1.333618
22:08:55.199 T:140291348166976 NOTICE: Checking resolution 15
22:08:55.199 T:140291348166976 ERROR: Failed to find matching visual
22:08:55.199 T:140291348166976 INFO: GL: Maximum texture width: 32768
22:08:55.199 T:140291348166976 INFO: Pixel Ratio: 1.333618
22:08:55.199 T:140291348166976 NOTICE: Checking resolution 15
22:08:55.199 T:140291348166976 ERROR: Failed to find matching visual
22:08:55.199 T:140291348166976 INFO: GL: Maximum texture width: 32768
2017-09-22, 09:15
(2017-09-22, 06:44)MaxMustermann Wrote: [ -> ]Since your fix, I'm having the "Failed to find matching visual" errror. This is the log of Milhouse Generic LibreELEC.tv Leia build #0921: https://pastebin.com/hLLYB0u2
So then, please use the build before that which does not have this PR: http://milhouse.libreelec.tv/builds/mast...98a31e.tar (#0918) - working?
Edit: Yeah, it will work, cause the root cause is: [X11] factor out glx support (PR:12219, 4 commits, 11 files changed) which I tried to fix - so no chance for you to test that. So then, stay on 0918 for now
2017-09-22, 09:18
For the selfbuilders:
Revert my fix, revert: [X11] factor out glx support (PR:12219, 4 commits, 11 files changed) and it should be back to normal.
Revert my fix, revert: [X11] factor out glx support (PR:12219, 4 commits, 11 files changed) and it should be back to normal.
2017-09-22, 09:32
If my build is crashing, can someone post a crashlog?