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.
Posts by Morphy
-
-
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# /storage/.kodi/addons/service.emby4/bin/emby-update 4.5.0.6 1. stopping Emby service 2. download Emby version 4.5.0.6 ######################################################################### 100.0%######################################################################### 100.0% 3. removing old install 4. extracting Emby 5. restarting Emby service ... done
systemctl status service.emby4.service :
Code
Display Moreservice.emby4.service - Emby 4 - streaming server Loaded: loaded (/storage/.kodi/addons/service.emby4/system.d/service.emby4.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2020-04-18 10:37:11 UTC; 7min ago Docs: http://emby.media Process: 13123 ExecStart=/bin/sh /storage/.kodi/addons/service.emby4/bin/emby4.start (code=exited, status=134) Main PID: 13123 (code=exited, status=134) Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5. Apr 18 10:37:11 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly. Apr 18 10:37:11 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:37:11 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
Journal-cur.log shows:
Code
Display MoreApr 18 10:20:08 HEC-TOR systemd[1]: Started Emby 4 - streaming server. Apr 18 10:20:08 HEC-TOR sh[5629]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Apr 18 10:20:08 HEC-TOR sh[5629]: Aborted Apr 18 10:20:08 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a Apr 18 10:20:08 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 1. Apr 18 10:20:09 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:20:09 HEC-TOR systemd[1]: Started Emby 4 - streaming server. Apr 18 10:20:09 HEC-TOR sh[5647]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Apr 18 10:20:09 HEC-TOR sh[5647]: Aborted Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 2. Apr 18 10:20:09 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:20:09 HEC-TOR systemd[1]: Started Emby 4 - streaming server. Apr 18 10:20:09 HEC-TOR sh[5665]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Apr 18 10:20:09 HEC-TOR sh[5665]: Aborted Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a Apr 18 10:20:09 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 3. Apr 18 10:20:10 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:20:10 HEC-TOR systemd[1]: Started Emby 4 - streaming server. Apr 18 10:20:10 HEC-TOR sh[5683]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Apr 18 10:20:10 HEC-TOR sh[5683]: Aborted Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 4. Apr 18 10:20:10 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:20:10 HEC-TOR systemd[1]: Started Emby 4 - streaming server. Apr 18 10:20:10 HEC-TOR sh[5702]: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxxx'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Apr 18 10:20:10 HEC-TOR sh[5702]: Aborted Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Main process exited, code=exited, status=134/n/a Apr 18 10:20:10 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Service RestartSec=100ms expired, scheduling restart. Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Scheduled restart job, restart counter is at 5. Apr 18 10:20:11 HEC-TOR systemd[1]: Stopped Emby 4 - streaming server. Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Start request repeated too quickly. Apr 18 10:20:11 HEC-TOR systemd[1]: service.emby4.service: Failed with result 'exit-code'. Apr 18 10:20:11 HEC-TOR systemd[1]: Failed to start Emby 4 - streaming server.
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...
-
My nzb indexer is showing unavailable in Sonarr. Apparently this is due to Mono not using TLS 1.2. Can this be updated please?
-
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
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?
-
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.
-
Hey 5schatten I'm a lucky new owner of a RPi 4
, any idea when we can expect a build for this?
-
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..
Code
Display More2019-05-04 15:00:09.507 T:1527960432 DEBUG: CSettingsManager: requested setting (label869) was not found. 2019-05-04 15:00:09.507 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label869. Creating a setting on-the-fly... 2019-05-04 15:00:09.507 T:1527960432 DEBUG: CSettingsManager: requested setting (label901) was not found. 2019-05-04 15:00:09.507 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label901. Creating a setting on-the-fly... 2019-05-04 15:00:09.507 T:1527960432 DEBUG: CSettingsManager: requested setting (label912) was not found. 2019-05-04 15:00:09.507 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label912. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label917) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label917. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label94) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label94. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label949) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label949. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label96) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label96. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label960) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label960. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label965) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label965. Creating a setting on-the-fly... 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CSettingsManager: requested setting (label98) was not found. 2019-05-04 15:00:09.508 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label98. Creating a setting on-the-fly... 2019-05-04 15:00:09.509 T:1527960432 DEBUG: CSettingsManager: requested setting (label997) was not found. 2019-05-04 15:00:09.509 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting label997. Creating a setting on-the-fly... 2019-05-04 15:00:09.509 T:1527960432 DEBUG: CSettingsManager: requested setting (vpn_password_display) was not found. 2019-05-04 15:00:09.509 T:1527960432 DEBUG: CAddonSettings[service.vpn.manager]: failed to find definition for setting vpn_password_display. Creating a setting on-the-fly...
-
Is this something that could be implemented for RPi builds to increase SD card life expectancy?
Give Your Raspberry Pi SD Card a Break: Log to RAM | Hackaday
-
From my past experience I can only say that I had mediocre ones with genuie PS3 ones. The SHANWAN stuff should work if you follow these steps but I can't say if they will be able to connect to bt as a group.
I'm confused is bluez-tools included in this build? I have a shanwan P3 gamepad to try out and I can't get it to pair via LE settings. Not sure if this helps?
Code
Display Morehciconfig hci1: Type: Primary Bus: UART BD Address: B8:27:EB:97:B9:A3 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:8766 acl:0 sco:0 events:487 errors:0 TX bytes:4296 acl:0 sco:0 commands:234 errors:0 hciconfig hci1: Type: Primary Bus: UART BD Address: B8:27:EB:97:B9:A3 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:8766 acl:0 sco:0 events:487 errors:0 TX bytes:4296 acl:0 sco:0 commands:234 errors:0
-
-
Running on LibreELEC (5schatten)
about addons pls have a look at the 5schatten build thread
Thanks but it's not specific to his build. I've just tried on a millhouse nightly fresh install and it still occurs. debug log
I'll try on the LE stable shortly but I'm guessing it's still going to happen...
-
I've been trying to test which addons it might be but now I can't recreate this issue.
I have been seeing another issue related to LE settings and being unable to connect to a wifi network due to "invalid parameter" error appearing after pressing connect. More here. This was due to the service.bluetooth-audio addon conflicting so I'm wondering if this is behind all of the issues with LE settings addon and RPi networking components. CvH
-
UPDATE:
So I've discovered there is an addon causing this behaviour for me:
service.bluetooth-audio
disabling this works. Re-enabling also works until I reboot then the issue is present again.
I've tried enabling debug logging but I can only see this of any relevance:
-
Im getting this error too with a RPi B+ looking at other threads it seems this bug has been around for a while and it's quite a major one. I'm discovering so many bugs in the LE settings add-on 😑