Scrap that – I didn’t get the PM notification until now. Seems to be a Discourse bug after updating.
Unfortunately no debugging enabled. Have you also downgraded or can you repro?
Sam
Ah poop. Maybe I missed the step for debugging. Probably in the settings. When I get a minute I’ll re-update (yeah I downgraded) and enable debugging, wherever that is. Bleh.
Hopefully these are the logs you need for the crash, @sam_nazarko:
https://paste.osmc.tv/urasezuhot
If not, tell me what else you need; unlike these other wimps, I haven’t rolled back to the unbuggy version. 
I just keep wondering, were other people still on stretch-devel main source when experiencing the issue? I did add the source when the RC was open for testing and I admit, I did not remove the source for multiple days afterwards… and got 2 or 3 updates in that time. Maybe one of these updates on stretch-devel main after the official RC caused the issue?
Issue is there on the main release.
Thx, just wanted to make sure. The preview of a solution here reminded me that I did install the rc april update before the official release and that it took me a couple of weeks to remove the source… funny enough I deactivated stretch-devel main just two days ago, otherwise I would have downloaded the broken version from tonight as well.
Lol well not being able to watch ANYTHING was a bit of an issue for me, lol. Thanks for uploading the logs. Hopefully this can get resolved ASAP.
I am investigating, thanks for logs.
How to get your kids out into the town to do stuff on weekends?
Install faulty update and blame it on Sam
change Adjust Refresh Rate from Always to Start / Stop works for me !!!
No Problems after changing this Setting !
Yep, as suggested before:
It’s not really appropriate to set it to Always any more.
That doesn’t work, as has already been established earlier in the thread.
1 Like
Found the problem – working on a fix.
2 Likes
Wooooooo!!!
Sorry for hijacking the thread with a question that has nothing to do with this… but I’m still on 17.6 because I am too lazy to find the manual of my projector to figure out the supported resolutions it offers to than setup whitelisting properly. I wonder couldn’t the device use what it finds over EDID and than auto fill the whitelist when you enable it ? Or is that how it already works
We only display supported resolutions advertised by the display.
If it’s working on v17, don’t bother with the whitelist - ie just don’t select any resolutions in it.
1 Like
When when when when?
No pressure.
When when when when when when?
The crashes (problem) are fixed and in staging.
You can upgrade again.
Sam
Doing it now. Will report back!