Error adding TVE source with new Synology DSM 7 Channels package

apolson · July 10, 2021, 7:48pm

I tried to use the new DSM 7 compatible package (thanks for putting that together), but every time I try and setup TV Everywhere, it fails with the error below. In case it makes a difference, I'm signing into FuboTV. Also, I was able to get Locast setup without issue.

chrome failed to start: ./chromedp-shell: line 15: 28760 Segmentation fault (core dumped) "$loader" "$root/bin/true" 2> /dev/null ln: /var/packages/ChannelsDVR/target/channels-dvr/data/chromedp-chroot/headless-shell/swiftshader/.: cannot overwrite directory [0710/123455.768628:WARNING:resource_bundle.cc(419)] locale_file_path.empty() for locale [0710/123455.768892:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox. #0 0x55c3181dd6e9 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2dba6e8) #1 0x55c3181604a3 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d3d4a2) #2 0x55c31816d296 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d4a295) #3 0x55c31713820e (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x1d1520d) #4 0x55c31810a0df (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce70de) #5 0x55c31810852c (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce552b) #6 0x55c31810866c (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce566b) #7 0x55c318158b24 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d35b23) #8 0x55c318158838 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d35837) #9 0x7fad24961fca __libc_start_main #10 0x55c315d14bfa _start Received signal 6 #0 0x55c3181dd6e9 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2dba6e8) #1 0x55c3181604a3 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d3d4a2) #2 0x55c3181dd291 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2dba290) #3 0x7fad25698c20 (/usr/lib/libpthread-2.26.so+0x11c1f) #4 0x7fad24974fbf gsignal #5 0x7fad24976327 abort #6 0x55c3181dc225 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2db9224) #7 0x55c31816d6fd (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d4a6fc) #8 0x55c31713820e (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x1d1520d) #9 0x55c31810a0df (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce70de) #10 0x55c31810852c (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce552b) #11 0x55c31810866c (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2ce566b) #12 0x55c318158b24 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d35b23) #13 0x55c318158838 (/volume1/@appstore/ChannelsDVR/channels-dvr/data/chromedp-chroot/headless-shell/headless-shell+0x2d35837) #14 0x7fad24961fca __libc_start_main #15 0x55c315d14bfa _start r8: 0000000000000000 r9: 00007ffdbf9e2430 r10: 0000000000000008 r11: 0000000000000246 r12: 00007ffdbf9e3758 r13: 00007ffdbf9e3750 r14: 00007ffdbf9e3740 r15: 00007ffdbf9e2ef0 di: 0000000000000002 si: 00007ffdbf9e2430 bp: 00007ffdbf9e2670 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fad24974fbf sp: 00007ffdbf9e24a8 ip: 00007fad24974fbf efl: 0000000000000246 cgf: 0000000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.

chDVRuser · July 11, 2021, 2:09am

I moved your post to its own topic.

Not sure, but it may help if you state how you upgraded.

If you had the old Channels DVR Synology package installed before upgrading to DSM 7.
Did you stop or uninstall it prior to upgrading to DSM 7.
Was it still installed when you installed the new version.
etc...

apolson · July 11, 2021, 2:26am

Thanks for that. Definitely makes more sense to have it separate.

It’s actually on a first-time install on a new NAS (the DS920+ specifically). My previous install is on a Windows desktop and I’m trying to gradually move over to the NAS though I started fresh.

chDVRuser · July 11, 2021, 2:33am

First I've heard of this issue and I'm sure others are using TVE on a Synoloy with DSM 7.
I'm on DSM 7, but running Channels in docker containers.

You'll have to wait until one of the developers responds to you. I'm sure they saw your post.

tmm1 · July 11, 2021, 4:41am

We are taking a look.

If you can SSH in please run these commands and paste the output shown here:

ls -alh /usr/lib/libsqlite*
ls -alh /lib/ld*.so

apolson · July 11, 2021, 3:41pm

Thank you for looking into this. I can't speak for others, and I'll let you be the judge, but this isn't something that I personally need a solution to quickly. Please enjoy your weekend if you can.

I should also note that I'm happy to do troubleshooting, run diagnostics, whatever you need, if it'll help track down the issue. As I said, I'm running a fresh install so have little to lose.

apolson@Synology:~$ ls -alh /usr/lib/libsqlite*
lrwxrwxrwx 1 root root   19 Jul 10 09:54 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6
lrwxrwxrwx 1 root root   19 Jul 10 09:54 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6
-rwxr-xr-x 1 root root 937K Jan 27 00:54 /usr/lib/libsqlite3.so.0.8.6
apolson@Synology:~$ ls -alh /lib/ld*.so
-r-xr-xr-x 1 root root 154K Apr 11 23:44 /lib/ld-2.26.so
apolson@Synology:~$

Aspesi4 · July 11, 2021, 3:46pm

I'm having the same issue adding TVE using the DSM 7.0 package on a Synology 218+. My whole house and remote users are down. Is there an update on this? I'd love to get it back up and running. Thanks!

tmm1 · July 11, 2021, 4:47pm

Try upgrading to prerelease and then click-and-hold the TVE Sign In button

Aspesi4 · July 11, 2021, 4:56pm

That seems to have worked! The TVE channels are loading now.

Another side question, if you delete a DVR backup, is there anyway to reimport your previous shows and movies by leaving them in the Channels DVR folder? I know I can import from other locations, but if I try that there's an error obviously. I've lost the backup at this point.

tmm1 · July 11, 2021, 5:01pm

No it's only possible with the backup.

Aspesi4 · July 11, 2021, 5:07pm

I have a recorder.db file from the previous install, but it won't import when I do a restore during setup.

Still no way?

tmm1 · July 11, 2021, 5:11pm

What does that mean it won't import?

The recorder.db and settings.db are the backup. So if you have those you can put them in a backup folder and restore it, or you can put them in the dvr data folder directly.

Aspesi4 · July 11, 2021, 5:42pm

I don't have the settings file. Just the recorder.db file unfortunately. Can I still restore just the DVR information, but reset up all the settings?

tmm1 · July 11, 2021, 7:54pm

Yes, you can use a new settings.db with your old recorder.db

Just put the two files you want to use in a backup folder and restore them.

apolson · July 12, 2021, 1:12am

That did it! Thanks so much for your quick help with this. Transitioning over from my Windows host to my Synology was painless after that. Keep up the great work!