Hi. I am using the FEL testing software.
https://paste.osmc.tv/qicajelozu
When I try to start the movie, “A beautiful planet” ( that I’m sure worked before ), my vero V simply reboots. It is not a DV movie, it’s HDR10+.
Do you guys spot anything on the log?
Thank you.
Adolfo
Suggestion :
If playing from Jellyfin Vero Reboots then try Disabling jellyfin and playing directly to see if there’s a difference.
Your log is not debug enabled, the real support people here can advise further.
Yeah, it also happens when I play directly. I did not mention that because it makes no sense. Jellyfin just points to the file.
Jellyfin is an addon which is directly manipulating the database to make Kodi load a URL.
Since it’s directly modifying the database it could be loading malformed URLs which cause cURL to crash which in turn restarts Kodi and reboots the device.
It’s just as susceptible to creating issues as any other addon.
Always best not to assume something isn’t an issue when you’re dealing with anything “added” to a standard installation.
In any case, since you already tried my suggestion I’ll bugger off now and leave you to the real support team.
Take care.
Yeah, thank you.
The same happens when played directly.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
http://paste.osmc.tv/qomosedixo
Here you go ! Thank you
You would need to let us know what you did and what happend? E.g. did you play and OSMC rebooted? Also how do you define a “reboot”? Did you see frowning face and the GUI restarted?
Last entry in log doesn’t show any attempt to play anything
`2026-04-28 16:37:28.018 T:2871 info : Loading skin file: Settings.xml, load type: KEEP_IN_MEMORY`
Also looks like you might be using different Kodi versions or have a stuck database
`JELLYFIN.jellyfin_kodi.objects.kodi.movies → INFO::jellyfin_kodi/objects/kodi/movies.py:171 Starting migration for Omega database changes`
I did install the testing FEL version. Nothing more. I go to file manager, find the file, press to play and a few seconds later it just reboots as in screen turns black, osmc led lights up and I see the startup logo. It hard reboots, I don’t see the frowning face.
Then we need to see a log for that. As your last log did not show any “go to file manager”
Here you go. If it’s not there I dunno. I filmed it.
It’s really odd there is nothing in the logs after your succesfully play the previous movie.
As you you are on staging maybe we wait for the stable release to see if it fix your issue. Otherwise might need persistent logging enabled to dig deeper. Or if you can take a snippet of the file with which the you can replicate the issue you could also share that.
2026-04-29 10:03:39.596 T:4134 info <general>: Deleting settings information for files nfs://192.168.168.10/mnt/user/ColdStorage/Filmes/1917 (2019)/1917 (2019) - 7.1 TrueHD Atmos - Remux-2160p - HEVC - DV HDR10Plus.mkv
2026-04-29 10:03:39.604 T:2878 info <general>: VideoPlayer: finished waiting
2026-04-29 10:03:39.604 T:2878 info <general>: CVideoPlayer::CloseFile()
2026-04-29 10:03:39.604 T:2878 info <general>: VideoPlayer: waiting for threads to exit
2026-04-29 10:03:39.604 T:2878 info <general>: VideoPlayer: finished waiting
2026-04-29 10:03:39.622 T:2947 info <general>: CAESinkALSA::Initialize - Requested layout FL, FR
2026-04-29 10:03:39.622 T:2947 info <general>: CAESinkALSA::Initialize - set digital codec 0
2026-04-29 10:03:39.623 T:2947 info <general>: CAESinkALSA::Initialize - Attempting to open device "default"
2026-04-29 10:03:39.636 T:2947 info <general>: CAESinkALSA::Initialize - Opened device "default"
2026-04-29 10:03:39.636 T:2947 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2026-04-29 10:03:39.636 T:2947 info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2026-04-29 10:03:39.671 T:2947 info <general>: CAESinkALSA::Initialize - speaker layout 0
2026-04-29 10:03:40.208 T:2878 info <general>: GLES: Maximum texture width: 8192
2026-04-29 10:03:41.208 T:3019 info <general>: Skipped 1 duplicate messages..
2026-04-29 10:03:41.208 T:3019 info <general>: JELLYFIN.jellyfin_kodi.player -> INFO::jellyfin_kodi/player.py:420 --<[ playback ]
2026-04-29 10:03:43.900 T:3019 info <general>: JELLYFIN.jellyfin_kodi.monitor -> INFO::jellyfin_kodi/monitor.py:105 [ playlist ] cleared
Sure. Here you have it. I confirmed it reboots with the trimmed file.
Well here it also crashes the Vero.
Could be a corrupt file. Maybe someone else of the team can test or find something. Below the kernel log.
```
Apr 29 22:03:48 osmc-verov kernel: dim:ch[0]:di_receiver_event_fun,3:_START
Apr 29 22:03:48 osmc-verov kernel: vdec_init, vf_provider_name = vdec.h265.00, b 0
Apr 29 22:03:48 osmc-verov kernel: vdec->port_flag=0x102, port_flag=0x10b
Apr 29 22:03:48 osmc-verov kernel: [0]vh265 cached=16384 need_size=16384 speed= 10 ms
Apr 29 22:03:48 osmc-verov kernel: [0]Bit depth luma = 10
Apr 29 22:03:48 osmc-verov kernel: [0]Bit depth chroma = 10
Apr 29 22:03:48 osmc-verov kernel: [0]hevc->performance_profile 0
Apr 29 22:03:48 osmc-verov kernel: [0]set pic_list_init_flag 1
Apr 29 22:03:48 osmc-verov mediacenter[2897]: [codec_pause]p->has_audio=0
Apr 29 22:03:48 osmc-verov mediacenter[2897]: video_pause!
Apr 29 22:03:48 osmc-verov kernel: [0]init_buf_spec2 3840 2160
Apr 29 22:03:48 osmc-verov kernel: [0]set pic_list_init_flag to 2
Apr 29 22:03:48 osmc-verov kernel: [0]set pic_list_init_flag to 3
Apr 29 22:03:48 osmc-verov kernel: [vdec_kpi][vh265_isr_thread_fn] First I frame coming.
Apr 29 22:03:48 osmc-verov kernel: hdmitx: sysfs set hdmi_ch to 0
Apr 29 22:03:48 osmc-verov kernel: iec_info: rate: 192000, codec_type:0x8, channel status L:0x9001902, R:0x9001902
Apr 29 22:03:48 osmc-verov kernel: hdmitx: audio: aout notify rate 192000
Apr 29 22:03:48 osmc-verov kernel: hdmitx: audio: aout notify size 16
Apr 29 22:03:48 osmc-verov kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Apr 29 22:03:48 osmc-verov kernel: aml_spdif_fifo_ctrl, bit depth:16, frddr type:1, toddr:type:1
Apr 29 22:03:49 osmc-verov kernel: asoc-aml-card auge_sound: S/PDIF[0] Playback enable
Apr 29 22:03:49 osmc-verov kernel: [0]VH265: output first frame
Apr 29 22:03:49 osmc-verov kernel: [vdec_kpi][post_video_frame] First I frame decoded.
Apr 29 22:03:49 osmc-verov kernel: dim:value reg:ch[0]:fix_buf:0;ponly <0,0>
Apr 29 22:03:49 osmc-verov kernel: dim:3840x2160-0x501000.
Apr 29 22:03:49 osmc-verov kernel: dim:dim_nr_ds_init alloc nrds canvas 84.
Apr 29 22:03:49 osmc-verov kernel: dim:di_vf_get:to pass
Apr 29 22:03:49 osmc-verov kernel: cal_dur_from_pts vstatus 4004 dur3690 → 3936, revised 3936
Apr 29 22:03:49 osmc-verov kernel: wr=2,slot=2 pts 7470, 3780, 0
Apr 29 22:03:49 osmc-verov kernel: cal_dur_from_pts vstatus 4004 dur3780 → 4032, revised 4032
Apr 29 22:03:49 osmc-verov kernel: wr=3,slot=3 pts 11250, 7470, 3780
Apr 29 22:03:49 osmc-verov kernel: vframe_rate_uevent: sent uevent FRAME_RATE_HINT=3984
```
I’m assuming it is not corrupt since It plays fine on the computer but I will test.
It’s not the file as far I can tell. New file, continues to reboot.
Here, this mp4 video sample lets crash a VeroV with current OSMC release, so it is NOT related to the current FEL version in staging.
More interesting: If I remux the clip from an mp4 to an mkv container using mkvtoolnix, it play fine on the official OSMC release as well as on the FEL testing version.
So, the issue is isolated to this specific mp4 file means, it is somehow corrupt or using something very special which the Kodi code or the hardware acceleration stack currently cannot handle.
Where did this file come from/how was it created?
Meanwhile I used VLC to remux the sample mp4 to a new mp4 container keeping the original video and audio tracks.
This file plays fine as HDR10+.
The big difference I see is/are special ‘menu’ items in the crashing mp4 which are detected by mediainfo.
Don’t know for sure that this is the root cause but I’ve never seen such items in mp4 samples I used for tests.
I created it using
ffmpeg -i movie.mkv -t 39 -c copy output.mp4
If mkvtoolnix fixes it, I might as well do the same but my memory tells me that I have watched this movie on osmc at the very least on the raspberry pi 4 before I got my very V. I’m positive I watched it either on the pi4 or the vero V.
But this is an interesting case because It plays on windows, linux, on the browser and my phone! The vero V is the only that fails.