The Responsive JEM

I tried the default protostar template and the result is still the same - after I copy the Responsive JEM into the template, the table is gone.
My setup - Joomla! 3.8.2 Stable, protostar template on the JEM menu item - simple list.
Everytime I put Responsive JEM files into the template (or any other) - the table in this view is gone... see screens. So I do not think, it is a template problem... It must be something else. It even works, if I set a Responsive JEM suffix for the menu item (hiding the filter for example).

Me, I can't reproduce

@Egnarts

Hey,
for me it looks like your JEM-Responsive does not find the override of the jem.css.
Please make shure that you your jem.css is in the correct folder as described in the installation manual of JEM-Responsive.

To better examine the problem it would be good if you give me a link to your problematic web page. Then I will take a look at your site.

I will install {Less} Allrounder on my page to test it.

Edit:
I installed Less Allrounder and the traditional Allrounder on my test page. All worked correctly, it should be a problem of your page/your way to "install" JEM-Responsive. But I will try to help you.

The path of the jem.css file of my override should be: <JoomlaRoot>/templates/lessallrounder/css/com_jem/jem.css

Hi,
the problematic page is here:
kctjicin.cz/index.php/jem

I set the template to allrounder, the files are there, where they should be - see screen. There are even the awesomeicons working correctly...

They are correct, but the user does not have access to those files.
Try to access that URL with your browser:
kctjicin.cz/templates/allrounder-j1.6/css/com_jem/jem.css

If it works correctly it should look like the default template.css:
kctjicin.cz/templates/allrounder-j1.6/css/template.css

Did you restrict path access via the .htaccess file?

Another way to try is to change the file access on ftp, the access rights should be -rw-r--r- or something like that - readable for all people on the world.

You see the font-awesome icons because FontAwesome is included per default by your template.

I am such a noob... It was so trivial, thank you for your quick repsonse!