New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Black screen if you start video after picture #14643

boot2k3 opened this Issue Oct 18, 2018 · 3 comments


None yet
5 participants
Copy link

boot2k3 commented Oct 18, 2018

Bug report

Describe the bug

Here is a clear and concise description of what the problem is:

Black screen instead of video if video is loaded right after picture in the same directory.
I hear sound stream of video, but no video

Expected Behavior

Here is a clear and concise description of what was expected to happen:

Video have to be on screen, not a black screen

To Reproduce

Steps to reproduce the behavior:

  1. Go to pictures and open directory where you have image and video files
  2. Open image
  3. Go to next picture. If next file is not picture but video than you see black screen


The debuglog can be found here:

Your Environment

Used Operating system:

  • Android

  • Linux with AMLogic

  • iOS

  • Linux

  • OSX

  • Raspberri-Pi

  • Windows

  • Windows UWP

  • Operating system version/name: Android, Libreelec

  • Kodi version: Leia last nightly

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

@Razzeee Razzeee added the v18 Leia label Oct 18, 2018


This comment has been minimized.

Copy link

FernetMenta commented Oct 18, 2018

please post log for Linux too


This comment has been minimized.

Copy link

boot2k3 commented Oct 19, 2018

Looks like it repeated only on amlogic box on both Android Kodi and and LE/CE
CE log if required:

on x86 all works correctly


This comment has been minimized.

Copy link

fritsch commented Oct 19, 2018

I fixed it in the bug description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment