Posts by DaVu

  • Img ? sorry

    \\ip.to.libreelec.here\

    should work. As it works for me very fine while NOT being in the same workgroup!!!

    So maybe you entered a ":" before and that's the cause.

    Again...while you are using windows you have to use this to access the samba share:

    Code
    \\ip.to.libreelec.here\

    while you are using linux, this way:

    Code
    smb://ip.to.libreelec.here/

    Note the difference between "/" and "\". That's important!!

  • LibreELEC first install


    Just FYI...we don't care in any way about TVADDONS. As this is a banned repository. See:

    Official:Forum rules/Banned add-ons - Official Kodi Wiki

    So, tbh, if you have any problem with this repo, report to the person who maintains it. But be aware, that if you have problems with LibreELEC while this repo is installed, you won't get any support. As this repos (and the addons which the repo contains) are sometimes causing issues. So if you run into any problem, remove those first and try again.

    The forums works fine for my using Firefox 45.0.

    Greetings

  • Img ? sorry

    @Dreamcatcher:

    To reach the samba shares, you don't need to change the workgroup. Open up a file browser and enter:

    Code
    \\ip.from.libreelec.here\

    and you're done.

    If you have multiple clients and changed the "systemname" to something individual (like TV-room, bedroom, bathroom ... etc.) you can reach the shares with

    Code
    \\bedroom\
or


\\bathroom\\


    ^^ that's for windows....
    Linux based systems reach the samba shares with: smb://whatever.ip.here/
    same as for the hostname....: smb://bedroom/

  • Updating my NUC from 6.0.3 to LE

    @ Alternativende:

    The only thing, that confuses me in a bit is that "*" under the 'poweroff' section..

    Code
    ...
poweroff)
   *
    /storage/.config/fuckme.sh
    ;;


    I would remove that.
    and for the ultimative test, I would change the script to the following:


    and then check /storage/test.txt what's in there. So you will know the "case" will work.

    If you want, you could run that script via command line, as we already know that $1 should be 'poweroff' from your previous test.

    Now we need to know why the 'case' might not work. To get a more verbose output remove the "#" from the '#set -x" line and start the script from command line like:

    Code
    ./storage/shutdown.sh poweroff

    then, normally "poweroff" should be written to /storage/test.txt. You will see a lot of lines at the output of what the script exactly does. That's because of the "set -x" line you activated by removing the "#". And maybe you will see why the script fails. To change this massive output again, just add the "#" again in front of "set -x" or just remove that line completely.

    And just for the cosmetics....LibreELEC, as the same as for OpenELEC, doesn't have bash....it has sh. So the shebang at the fuckme.sh shouldn't be:

    #!/bin/bash

    it should be

    #!/bin/sh

    shouldn't be a big problem. But I would change it, too ;).

    For checking which shell is used, enter: echo $SHELL

    Greetings

  • HOW-TO: provide bug-reports

    For getting things better we need you to report to us.

    For getting the best support you have to explain your problem as best as you can. "Nothing works" is not very helpful ;).

    For every issue you are facing we need the following:

    • Full hardware specs (GPU is most important)
    • The LibreELEC version you are running ('latest' is not a version number)
    • In most cases a full debuglog
    • Tell us the complete steps how to face the issue, so we can try to reproduce

    Additionally to the above, if you are facing video playback issues:

    • A full debuglog while trying to play the video
    • Informations about the Kodi video and audio settings (maybe a screenshots from both)
    • If possible a mediainfo from that file/container

    Additionally for hardware related problems:

    • Name the specific hardware and maybe a link to the manufactor
    • Get us the output of 'dmesg' while the hardware is connected
    • Get us the output of 'lspci' if it's about PCI hardware
    • Get us the output of 'lsusb' if it's about some USB hardware

    Greetings

  • [BUG] Bootloop with Third Party Skin

    @J0hnny,

    The last thing I see at the logfile is airplay related....could you try to disable that? Just for a test.

    And I see you have connected some Bluetooth audio device. Is that the main audio device you are using? And if not, could you disable that, too please?

  • Merge setting screens Kodi & lebreElec

    No, as LibreELEC settings is it's own addon AFAIK. That's the reason why it might be located under different locations using different skins. Sometimes (for AeonMQ6 for example) it's located under "Programs". So including it, even it would be possible, would brake a lot of things for other skinners, I guess.

    And I suppose we like the idea have those things completely seperated to Kodi settings as they effect completely different things.

  • system restart black screen

    could you ssh in after a restart and try to grab a debuglog?

    enable debug logging in system settings before restarting, try to restart, ssh in, grab the log and paste it on a paste-servic you like (pastebin.com for example).

    you can use a command for this (for the case you don't know):

    Code
    pastebinit /storage/.kodi/temp/kodi.log

    you will get back an URL. Provide that please.

    Greetings

  • service.libreelec.settings should respect locksettings

    I guess that's the reason kodi provides the option to use different profiles for 'special' users ;)

    If you create a profile (lets name it 'Kids') and enabling the 'master lock' you are able to specify which menu point is reachable and which not...

    See here:

    Other benefit is, that you are able to specify which content is available for the kids. As different profiles can have different libraries.

    So I would give it a shot.

    Cheers