2016-01-05, 23:46
Ahhh, wasn't there earlier.Or I didn't see it. No way to change the page to view by date.
(2016-01-05, 21:51)Milhouse Wrote: It's an upstream issue, so continuing the discussion on github would be appropriate. Unfortunately there's not much useful information in that github issue though - it might be worth posting "journalctl" and "dmesg" from a working system and again from a non-working system.
The first report is against 5.95.5, so it would be useful to know if 5.95.4 has the same WiFi issue - if not, that would narrow it down to changes between 5.95.4 and 5.95.5. Getting hold of 5.95.4 and 5.95.5 builds is likely to be tricky, though.
If any of the OE developers have ideas I'd be happy to include them in a test build - perhaps additional logging would help collect more information on what is no longer working. It's odd that it seems to be mainly an issue with Chromebox, or is that an inaccurate statement?
Edit: Hopefully http://archive.openelec.tv/ will be updated with the 5.95.4 and 5.95.5 builds shortly.
# uname -a
Linux OpenELEC 4.4.0-rc8 #1 SMP Fri Jan 8 20:03:10 GMT 2016 x86_64 GNU/Linux
# lsb_release
OpenELEC (Milhouse) - Version: devel-20160108200216-#0108-gbcd8e12 [Build #0108]
(2016-01-09, 20:39)Hitcher Wrote: Since #0101 empty TV shows aren't hidden even if the setting is enabled.
(2016-01-09, 20:39)Hitcher Wrote: EDIT: And skip seeking is acting weird as well. The indicator doesn't start from where you currently are but from the previous point.
# uname -a
Linux OpenELEC 4.4.0-rc8 #1 SMP Sun Jan 10 01:07:37 GMT 2016 x86_64 GNU/Linux
# lsb_release
OpenELEC (Milhouse) - Version: devel-20160110010535-#0110-gcbf8287 [Build #0110]
(2016-01-09, 20:39)Hitcher Wrote: Since #0101 empty TV shows aren't hidden even if the setting is enabled.
EDIT: And skip seeking is acting weird as well. The indicator doesn't start from where you currently are but from the previous point.
(2016-01-06, 00:05)Matt Devo Wrote: I'll test and determine where the issue began. It's certainly not a ChromeBox issue, since the majority of posters on the github tracker have Intel 7260 wifi cards; the ChromeBox uses an Atheros 9xxx. I'm happy to provide whatever logs etc are needed, can compile my own builds and bisect the issue, just need a little guidance to troubleshoot
edit: this bug is present in 5.95.1, so will have to start bisecting commits