Posts by Morphy

    emby4.start

    Code
    1. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
    2. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
    3. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
    4. ERROR: ld.so: object '/storage/.kodi/addons/service.emby4/lib/libMagickCore-7.Q16HDRI.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
    5. cat: error while loading shared libraries: libMagickCore-7.Q16HDRI.so.7: cannot open shared object file: No such file or directory
    6. /storage/.kodi/addons/tools.dotnet-runtime/bin/le_dotnet: line 8: dotnet: not found

    Hi awiouy thanks for getting back to me. I have updated all addons so I'm assuming dotnet is up to date. Output of journalctl -u service.emby4 is blank. I'll try refreshing the repo's see if it's missing an update.


    systemctl status service.emby4.service reports:

    Just seen an old thread re emby and this command might help? ldd $(which dotnet):


    Code
    1. linux-vdso.so.1 (0x00007ffe41508000)
    2. libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007febe8c4c000)
    3. libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007febe8c32000)
    4. libc.musl-x86_64.so.1 => not found
    5. libm.so.6 => /usr/lib/libm.so.6 (0x00007febe8af2000)
    6. libc.so.6 => /usr/lib/libc.so.6 (0x00007febe893c000)
    7. /lib/ld-musl-x86_64.so.1 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007febe8fe6000)

    Thanks for looking. I'm on the addon default 4.2 so I guess I can update to 4.3 at least for now. Where do we go to get this fixed? I'm guessing the maintainer for the addon is inactive due to it not being updated for a while. I was thinking of switching to Docker but I'm not sure how straight forward this would be.

    I've just tried this on my LE generic system and it seems to update ok according to the script output but the service won't start:


    Code
    1. # /storage/.kodi/addons/service.emby4/bin/emby-update 4.5.0.6
    2. 1. stopping Emby service
    3. 2. download Emby version 4.5.0.6
    4. ######################################################################### 100.0%######################################################################### 100.0%
    5. 3. removing old install
    6. 4. extracting Emby
    7. 5. restarting Emby service
    8. ... done


    systemctl status service.emby4.service :


    Journal-cur.log shows:


    Has anyone tried updating with this script to 4.5.0.6 or 4.4.2 (tried both)?

    Sorry to resurrect an old thread but this is the first result that comes up. I've got a m2 SSD connected via usb3 adapter (don't ask) and I've just written the latest image to it only to be confronted with the boot menu which requires a keyboard. Surely there should be an option in this to make it live for every boot? I've got to find a Usb stick and write the image again off an Ubuntu live boot usb now...

    It depends on profile settings but afaik addons get installed for all users but they're disabled in other profiles. It's just the userdata folder which is unique.


    I think what's happening is on logoff the VPN isn't being disconnected and when the other user logs on the check detects it as still connected so it doesn't reconnect. I'm not sure if it is still connected to the VPN or not but emby doesn't connect to my server. It's Https and over WAN so maybe it's something to do with that.


    I've got around it for now so it's not too much of a problem for me. I just set a different default VPN location on each user so it will force reconnect on logon with each Kodi user.

    Has this been tested with multiple Kodi user profiles? The reason I ask is I'm having a problem with this and with Emby for kodi client. When I flip from the master profile which has been connected to a VPN to another user, trying to play any emby library files result in Kodi freezing for a few minutes and not playing the file. There are a lot of "CCurlFile::Stat - Failed: Timeout was reached" in the logs. I've noticed if I disconnect the VPN in the other user and then try Emby this works again. Also using another connection makes it work again too. It's not losing connectivity as other addons like YouTube stream fine.

    I've got an annoying bug with the RPi4 where when turning my TV to standby it powers off then a few seconds later it powers back on again. It's basically saying you can't leave me :D

    I've got a debug log with verbose CEC logging on a fresh install. Dmesg here. I've also tried with the firmware mentioned here. I've tried disabling all power options in the CEC options in peripherals.


    This only seems to happen when connected to my Onkyo AV amp, if I connect directly to my TV this behaviour doesn't occur. RPi3 behaves as expected.


    Obviously early days in RPi4 development but thought I'd put the bug out there. Is there anywhere else I can post this, maybe RPi forum? Github?

    Morphy

    Currently I don't own a RPi4 and I'm not sure if I get one at this point because I already have way more SBCs than TVs. But it's still somewhat wip at the moment and the RPi4 firmware gets updates as the project as well. Once it's more tested I can add probably update my build files but I can't really test the images at the moment. ;)

    Yea I can imagine! The performance gains really are great though so I'm hoping emulation will be a much better experience. If you need me to do any testing I'd be happy to help.

    Anyone else having weird HDMI CEC issues with the RPi 4? I couldn't control anything earlier until I rebooted it and now every time I switch the TV off it comes back on again a few seconds later 🙃

    I've got a mini HDMI adapter ATM but getting a cable tomorrow so if that doesn't solve it I'll grab some logs.

    Hi zomboided I'm getting these lines spamming my debug log, any idea off the top of your head what could be causing it? It's otherwise working as expected..