Sad face loop after OSMC's August update

That’s a different topic, that was a short (onetime) sad face after the update that was caused by skinshortcuts:

  1. This thread is about “sad face loop”
  2. This should not happen anymore since August update

Ooohhh sorry :slight_smile:

How did the reinstallation go?

this helped for me. altough all the settings and addons i had are gone now… :confused:

EDIT:
When i activated the PVR IPTV Simple Client and added m3u and epg urls the sad face loop returned… and that was the only thing i changed after the settings had been reset…

EDIT 2:
The latest log https://paste.osmc.tv/ehapozogag

EDIT 3:
As the backup deleted all my info, i tried to reinstall the whole osmc and now the PVR IPTV Simple Client works as it should. Sad though that I have to configure everything again…

The command simply made a backup of your settings and add-ons. You can simply revert the command and all will be returned, but so will your sad face issue.

Started my Vero this morning. Kodi.log ends with this…

please help! first time my Vero is stuck in sad face loop!

10:35:12.583 T:4113842176 NOTICE: ADDONS: Using repository repository.xbmc.org
10:35:12.694 T:4083262448 NOTICE: No Devices found - retry: 4
10:35:14.223 T:4083262448 NOTICE: No Devices found - retry: 3
10:35:15.751 T:4083262448 NOTICE: No Devices found - retry: 2
10:35:17.277 T:4083262448 NOTICE: No Devices found - retry: 1
10:35:18.854 T:4083262448 NOTICE: Found 0 Lists of Devices
10:35:18.875 T:4083262448 WARNING: ActiveAE::Configure - sink returned large buffer of 249 ms, reducing to 100 ms
10:35:19.042 T:4113842176 ERROR: AML: no rw on /dev/amvideo
10:35:19.042 T:4113842176 ERROR: AML: no rw on /dev/amstream*
10:35:19.042 T:4113842176 ERROR: AML: no rw on /sys/class/video/axis
10:35:19.042 T:4113842176 ERROR: AML: no rw on /sys/class/video/screen_mode
10:35:19.042 T:4113842176 ERROR: AML: no rw on /sys/class/video/disable_video
10:35:19.042 T:4113842176 ERROR: AML: no rw on /sys/class/tsync/pts_pcrscr
10:35:19.042 T:4113842176 ERROR: AML: no rw on /dev/video10
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/module/amvideo/parameters/omx_pts
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/module/amlvideodri/parameters/freerun_mode
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/class/audiodsp/digital_raw
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/class/ppmgr/ppmgr_3d_mode
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/class/vfm/map
10:35:19.043 T:4113842176 ERROR: AML: no rw on /sys/class/tsync/enable
10:35:19.043 T:4113842176 NOTICE: InitWindowSystem: Using EGL Implementation: amlogic
10:35:19.044 T:4113842176 ERROR: EGL error in InitDisplay: 3003
10:35:19.044 T:4113842176 ERROR: InitWindowSystem: Could not create display
10:35:19.044 T:4113842176 FATAL: CApplication::Create: Unable to init windowing system

Sorry full log here. https://paste.osmc.tv/iforubefog

Hosed myself when trying adding the osmc to a different group inadvertently, removed osmc for all default groups including video! … dumbass!

Glad you found the solution :slight_smile:

what do you mean?
I still have the problem that the sad face loop return if I update without fresh install… so right now I just run until there is a permanent solution where I can update without a lot of extra work.

I made some manual modifications to the system that caused it to not be able to start. Undoing those and redoing it fixed my issue. Don’t think they are related to you problem.

So i took the risk and wanted to try update from 2017.07-1 to 2017.08-1 trough “My OMSC” only to find the same sad loop returning… This is getting pretty sad that I can’t enjoy the automatic updates the most of the users use.
The only addons i use when i tried to update is Confidence skin, Youtube and Simple IPTV PVR.

And so the sad face loop story starts.
After the above attempt, I did a clean install of 2017.08-1 which is the latest on the website, and later update to the 2017.09-2 trough “My OSMC” which is recommended. A sad face appeared after the update restart, but it was only once.
Then everything was fine until i setup the IPTV Simple Client and then BOOM the sad face loop is back.
Honestly I’m getting tired of this.

Just to confirm: every time you enable the IPTV client and configure it, your system becomes unstable?
With IPTV disabled, everything is OK?

Sam

It seems like that was the obvious problem when running 2017.09-2.
As i didn’t make any changes or install other add-ons at all when running it besides setting up IPTV client and exactly when I enabled the sad face appeared… I can’t disable it now either as the sad loop is too intensive.

And there seems to be a good change that IPTV clients make the sad face loop return when i try to update trough OSMC, as it like the only addon I have activated.

Is anyone else experiencing this problem with IPTV?

We haven’t had any reports of major problems with IPTV.

With that said, a couple of providers are definitely playing tricks (as you will find on this forum) and trying to block OSMC clients from accessing streams. I worked around this however, and crashes weren’t part of this behaviour.

Try enable debug logging, and when you get a crash send the log again.

Sam

Hi,

I would try this

mv ~/.kodi/userdata/addon_data/pvr.iptvsimple/settings.xml ~/.kodi/userdata/addon_data/pvr.iptvsimple/settings.bak

sudo systemctl restart mediacenter

If you no longer sad looping, try simple iptv without the epg configured. I suspect based on testing (admittedly I’ve only seen this on pi, with less memory), that loading the epg over a certain number
of channels, can cause the memory to run out.

This is just for testing, not suggesting you run permanently without an epg.

Thanks Tom.

I have sent you the log in pm!

thanks for your help!
I tried also without the epg (which was on 32mb…)

But the sad face loops starts after i put in the m3u, enabling the IPTV Simple Client works great.

And this is the first thing I do after a fresh install.

There’s a segfault in your log:

Oct 18 20:17:37 osmc-Wesley mediacenter[462]: Kodi exited with return code 139 after 0 hours, 2 minutes and 24 seconds

I’m not sure why, but I’d reduce the EPG or follow Tom’s advice and leave it off for now.