Sound not working after using YouTube for a while

I have been using OSMC for a while and I loved it. However, after latest upgrade, I found that the sound will stop working after I watch YouTube for a while. I can “solve” the problem by restart my raspberry pi 2. Does anyone has the same problem and knows a solution? Below is the version info. Thanks,

osmc@osmc:~$ uname -a
Linux osmc 4.2.1-1-osmc #1 SMP PREEMPT Wed Sep 23 17:57:49 UTC 2015 armv7l GNU/Linux

osmc@osmc:~$ cat /etc/os-release
PRETTY_NAME=“Open Source Media Center”
VERSION=“September 2015”


1 Like

Same problem rp2
I2.restart and it goes back to normal. The same video has sound after reboot

Avg. length of time before the audio stops?

Same problem here,

Sound stop working after a random time.

I can restart it, but sometimes it’s cut just 1min after video playing, sometimes after 30min…

also if you wait a while ~5min the sound come back itself !

Really embarrassing, my wife is foreigner, watch TV show by youtube…

I didn’t know if this problem is from Kodi/Sound or Rpi2 or Youtube plugin or Youtube restriction itself.

We need logs here…

Kernel logs :

System logs :

Kodi logs : MEGA
130mb file !? I guess from i test it, installed one week ago

For information, i have add apache/php server on it with ssh2_mod.

The kodi logs are most important but no one is going to download 130mb of them. Please reboot twice to cycle out any large logs, create the problem while debugging is enabled, then use the paste site for the reasonably sized log please.


If your Kodi debug log is 130MB, check for updates to make sure you aren’t on the initial September update that had lots of extra debugging enabled by accident.

After you have done this, go into Settings->System->Debugging, and disable component specific-logging - there is a bug in the default settings that causes “verbose logging for the video component” in component specific logging to be enabled by default - this will cause large debug logs if you play videos with debugging enabled. This will be fixed in next months update.

Once you have checked for updates and disabled component specific debugging reboot twice to clear the Kodi logs then try to reproduce the problem again and post your logs again and you should find your Kodi log is not 130MB…(which nobody is going to read)