v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: v17 LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) (/showthread.php?tid=269814) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|
RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - zaphod24 - 2016-08-26 Which pvr client are you using? I'm using mythtv. I have 2 rpi3 devices and both had the issue with nothing under default or livetv on 0825 but after reverting to 0824 recordings are accessible again. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - f1vefour - 2016-08-26 (2016-08-26, 04:14)zaphod24 Wrote: Which pvr client are you using? I'm using mythtv. I have 2 rpi3 devices and both had the issue with nothing under default or livetv on 0825 but after reverting to 0824 recordings are accessible again.If mythtv is on a different device try restarting it, I had this issue with tvheadend and it resolved it. According to reverting builds it may be unlikely. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - mark_dj - 2016-08-26 (2016-08-26, 00:33)Milhouse Wrote:(2016-08-25, 22:47)mark_dj Wrote: It's set to expert, but I can't change the size there, only the position? Thanks for that, the skin didn't show these settings so it's fixed now. Took me WAY longer than expected though Also, Dead Poets Society (the movie) doesn't seem to work on Kodi. I've tested it with multiple versions of both Kodi and the movie but nothing is shown when I start the movie. Has anyone ever heard of this problem? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-08-26 (2016-08-26, 09:06)mark_dj Wrote: Thanks for that, the skin didn't show these settings so it's fixed now. Took me WAY longer than expected though If you're using a third-party skin that's your choice, but you shouldn't be reporting issues with third party skins in this thread. Only report issues you can reproduce with stock Estuary. (2016-08-26, 09:06)mark_dj Wrote: Also, Dead Poets Society (the movie) doesn't seem to work on Kodi. I've tested it with multiple versions of both Kodi and the movie but nothing is shown when I start the movie. Has anyone ever heard of this problem?Nope. Post a debug log (wiki) of you trying to pay this movie. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Saner - 2016-08-26 It's worth trying to turn off h/w decoding and try it. I had a couple that refused to pay video, that kicked it RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - mark_dj - 2016-08-26 (2016-08-26, 09:49)Milhouse Wrote:(2016-08-26, 09:06)mark_dj Wrote: Thanks for that, the skin didn't show these settings so it's fixed now. Took me WAY longer than expected though I did actually try and look for it with the stock Estuary skin, but was unable to find it (hence my 6 hour search). I guess switching to the skins back and forth somehow reset (some of) my settings. (2016-08-26, 13:14)Saner Wrote: It's worth trying to turn off h/w decoding and try it. Thanks, gonna give that a spin RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - BigNoid - 2016-08-26 Here's my crashlog with the debug build. It started with #822 and the crashes only occur when the Xbox 360 controller is plugged in. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - zaphod24 - 2016-08-26 (2016-08-26, 05:17)f1vefour Wrote:(2016-08-26, 04:14)zaphod24 Wrote: Which pvr client are you using? I'm using mythtv. I have 2 rpi3 devices and both had the issue with nothing under default or livetv on 0825 but after reverting to 0824 recordings are accessible again.If mythtv is on a different device try restarting it, I had this issue with tvheadend and it resolved it. Looks like Milhouse was kind enough to report the issue with PR 10333 and it looks like that PR introduced a regression which someone has already corrected. Thanks to Milhouse for reporting! RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-08-26 (2016-08-26, 14:55)BigNoid Wrote: Here's my crashlog with the debug build. It started with #822 and the crashes only occur when the Xbox 360 controller is plugged in. This backtrace looks screwy to me: Code: Thread 1 (Thread 0x592ff3a0 (LWP 12790)): binutils? Anything else compiler / system libs / gdb related? RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-08-26 (2016-08-26, 15:50)popcornmix Wrote: Milhouse - might this backtrace have been broken by one of the bumps? No, #0824 and #0825x are both clean builds, with no package bumps other than those documented. I've been testing the binutils/gcc/etc. package bumps in a different repo that is completely separate from the repo I use for these builds (they don't even share ccache). BigNoid says this started with #0822, can it just be a coincidence that there is a controller related PR in #0822? I could try reverting it, and BigNoid can tell if it has any effect. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-08-26 @BigNoid can you try debug-enabled build #0826x: RPi2 It's basically #0825x with the following changes reverted: (2016-08-23, 03:40)Milhouse Wrote: While I don't understand the backtrace either, I also have no reason to suspect it is wrong (as in bad build) at this stage. The fact that the crash only happens when a controller is connected makes me suspect the controller-related changes, particularly as they were added in the first build that has this problem. Perhaps there is some threading/corruption issue occurring? There's a peripheral.joystick update that will be in tonight's build, but I wouldn't have thought it will have any effect on this issue (though looking at that backtrace, who knows anymore...) RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - BigNoid - 2016-08-26 Installing now, thx. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-08-26 (2016-08-26, 16:06)Milhouse Wrote: No, #0824 and #0825x are both clean builds, with no package bumps other than those documented. I've been testing the binutils/gcc/etc. package bumps in a different repo that is completely separate from the repo I use for these builds (they don't even share ccache). My belief is that the joystick bump has caused the SIGSEGV crash and that started in #0822. But I believe a separate regression has broken backtrace. That may have occurred in any build since backtraces were last seen working (possibly a couple of weeks or more back). The backtrace Bignoid reported is not plausible. The symbols are unrelated to the code that has been running as so backtrace is useless. RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - popcornmix - 2016-08-26 Just to clarify, a working backtrace for Application thread (thread 1) should always look like: Code: Thread 1 RE: LibreELEC Testbuilds for RaspberryPi (Kodi 17.0) - Milhouse - 2016-08-26 This is a crashlog from #0825x that I forced with "kill -SIGSEGV $(pidof kodi.bin)" - looks fairly normal to me... http://sprunge.us/TJYS Would it be possible for a process/thread to corrupt the call stack? @BigNoid can you try the "kill -SIGSEGV" command on #0825x with and without the controller connected to see if there's any difference in the resulting crashlogs? |