[User 282437]

I moved my backend/ frontend combo to an SSD boot drive a couple of months back (Ubuntu 16.04 LTS). This caused all sorts of boot issues with networking etc.. Seems crazy, but a whole bunch of scripting changes (sleep etc) were needed to slow things down before I managed a clean and reliable boot.

However, an issue with Kodi and myth pvr add in remains. Kodi crashes on the first run in a session when the PVR loads.

It usually takes three or four attempts to get it load safely.

Oddly, when I turn FULL debugging on it doesn't happen, i.e. . Kodi and the PVR load and run in all their glory on first try. So now when I want to leave Kodi unattended for automatic shutdown and recording, I turn FULL DEBUG on and it works. Go figure.

I have tried delaying Kodi's startup by 20 seconds and more, but the first run with full debug OFF will always crash when the PVR attempts to start up.

If I boot off a mechanical drive, all is well also.

Is there a way or the inclination to address this problem?
This is the crash log

12:39:17.302 T:139797047617920 NOTICE: Running the application...
12:39:17.307 T:139797047617920 NOTICE: starting zeroconf publishing
12:39:17.307 T:139797047617920 NOTICE: CWebServer[8080]: Started
12:39:17.307 T:139797047617920 NOTICE: starting upnp client
12:39:17.312 T:139797047617920 NOTICE: starting upnp server
12:39:17.317 T:139797047617920 NOTICE: starting upnp controller
12:39:17.318 T:139797047617920 NOTICE: starting upnp renderer
12:39:17.322 T:139797047617920 ERROR: JSONRPC Server: Failed to connect to sdpd
12:39:17.324 T:139794734638848 NOTICE: ES: Starting UDP Event server on port 9777
12:39:17.325 T:139794734638848 NOTICE: UDP: Listening on port 9777 (ipv6 : true)
12:39:17.529 T:139795162437376 NOTICE: AddOnLog: MythTV PVR Client: Launcher stopped
12:39:17.533 T:139796420732672 NOTICE: PVRManager - stopping

PS: Before someone tells me they want the full debug log, please read the above. The crash does not happen when full debug is ON.

Cheers

[disaacso]

I have a similar problem I'm tracking down right now, out of curiosity do you have trim enabled for your ssd?

[User 282437]

I have a similar problem I'm tracking down right now, out of curiosity do you have trim enabled for your ssd?

I have no idea what that is or how I would enable/ disable it.

[disaacso]

I have a similar problem I'm tracking down right now, out of curiosity do you have trim enabled for your ssd?

I have no idea what that is or how I would enable/ disable it.

Well trim isn't the issue, I've tested that now. I had the delete my channels database, I think it was db29 but can't remember for sure, and the problem has been reduced if not eliminated.

Trim is handy for ssd's, here is some info on that

[nickr]

Does this happen if mythtv.pvr is disabled, but then enabled after boot?

The fact that it works OK on a mechanical drive, or if debugging is enabled, points (IMHO) to some sort of race condition. Debugging will slow Kodi, not much, but perhaps enough to prevent the race condition?

Try setting log level to 1 in advancedsettings.xml, then you will get debugging, but not the annoying on screen display that usually goes with it.

[disaacso]

Try turning off settings>livetv>recordings> display a notification on timer update. It seems to have eliminated my problem (for the last couple of days at least)

[nickr]

Good to see it is working for you now.

[User 282437]

Try turning off settings>livetv>recordings> display a notification on timer update. It seems to have eliminated my problem (for the last couple of days at least)

Hasn't worked for me. It probably me, not you.

[nickr]

Well answer he questions I posed in post 5 then.