Issue with chromium Ubuntu package which uses snap
I fixed it by uninstalling chromium and install..... Got all my TVE channels back.
sudo apt install chromium-bsu
Package chromium is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
chromium-bsu
E: Package 'chromium' has no installation candidate
nyplayer@janeddvr:~$ sudo apt install chromium-bsu
The package is called chromium-browser
Did a full rescan everything authorized with chromium-browser ... will add that to my notes thank you.
Sample
022/10/26 02:36:38.276782 [TVE] Channel scan 1/217 NBC successful
2022/10/26 02:36:38.667293 [TVE] Channel scan 2/217 ABC successful
2022/10/26 02:36:39.328171 [TVE] Channel scan 3/217 FOX successful
2022/10/26 02:36:39.829308 [TVE] Channel scan 4/217 CBS successful
Curious, what is the output of terminal command
chromium —version
I ran into this exact issue Sunday night. I also reinstalled the package and restarted the server and it fixed it. So far I haven't had the issue crop up again.
I wonder if installed Chrome instead of Chromium would prevent the issue in the future? I ask because I am receiving my new Beelink mini PC tomorrow and I plan to throw Ubuntu server on that to use for my Channels DVR.
Every single channel authorized so I am not messing with it anymore ...
Package Details
Description Transitional package - chromium-browser -> chromium snap
This is a transitional dummy package. It can safely be removed.
.
chromium-browser is now replaced by the chromium snap.
Package chromium-browser Class A-E
Version 1:85.0.4183.83-0ubuntu2 Vendor Ubuntu Developers <[email protected]>
Architecture amd64 Installed Unknown
This is back today .... I have 2 Primes so not vital for tonight just hope others that rely on TVE do not experience this.
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
022/10/27 01:28:12.059055 [TVE] Channel scan 29/217 TBS failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:12.146219 [TVE] action=auth mvpd=Comcast_SSO requestor=TBS
2022/10/27 01:28:12.147406 [TVE] action=xvfb display=:686
2022/10/27 01:28:12.197591 [TVE] Channel scan 30/217 TBSP failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:12.285916 [TVE] action=auth mvpd=Comcast_SSO requestor=TNT
2022/10/27 01:28:12.287061 [TVE] action=xvfb display=:987
2022/10/27 01:28:12.340076 [TVE] Channel scan 31/217 TNT failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:12.488764 [TVE] action=auth mvpd=Comcast_SSO requestor=TNT
2022/10/27 01:28:12.489973 [TVE] action=xvfb display=:940
2022/10/27 01:28:12.538860 [TVE] Channel scan 32/217 TNTP failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:12.727005 [TVE] Channel scan 33/217 TRU successful
2022/10/27 01:28:13.060412 [TVE] Channel scan 34/217 TRUP successful
2022/10/27 01:28:13.175619 [TVE] action=auth mvpd=Comcast_SSO requestor=TCM
2022/10/27 01:28:13.176771 [TVE] action=xvfb display=:726
2022/10/27 01:28:13.225829 [TVE] Channel scan 35/217 TCM failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:13.329515 [TVE] Channel scan 36/217 TOON successful
2022/10/27 01:28:13.502691 [TVE] Channel scan 37/217 TOONP successful
2022/10/27 01:28:13.617562 [TVE] action=auth mvpd=Comcast_SSO requestor=AETV
2022/10/27 01:28:13.618666 [TVE] action=xvfb display=:793
2022/10/27 01:28:13.666712 [TVE] Channel scan 38/217 AETV failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:13.763786 [TVE] action=auth mvpd=Comcast_SSO requestor=HISTORY
2022/10/27 01:28:13.765077 [TVE] action=xvfb display=:734
2022/10/27 01:28:13.822142 [TVE] Channel scan 39/217 HISTORY failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:13.907710 [TVE] action=auth mvpd=Comcast_SSO requestor=FYI
2022/10/27 01:28:13.908801 [TVE] action=xvfb display=:843
2022/10/27 01:28:13.954621 [TVE] Channel scan 40/217 FYI failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.058471 [TVE] action=auth mvpd=Comcast_SSO requestor=LIFETIME
2022/10/27 01:28:14.059508 [TVE] action=xvfb display=:909
2022/10/27 01:28:14.117343 [TVE] Channel scan 41/217 LIFETIME failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.214655 [TVE] action=auth mvpd=Comcast_SSO requestor=msnbc
2022/10/27 01:28:14.216285 [TVE] action=xvfb display=:905
2022/10/27 01:28:14.274884 [TVE] Channel scan 42/217 MSNBC failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.366898 [TVE] action=auth mvpd=Comcast_SSO requestor=cnbc
2022/10/27 01:28:14.368039 [TVE] action=xvfb display=:639
2022/10/27 01:28:14.425319 [TVE] Channel scan 43/217 CNBC failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.524551 [TVE] action=auth mvpd=Comcast_SSO requestor=usa
2022/10/27 01:28:14.525743 [TVE] action=xvfb display=:630
2022/10/27 01:28:14.577288 [TVE] Channel scan 44/217 USA failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.670632 [TVE] action=auth mvpd=Comcast_SSO requestor=usa
2022/10/27 01:28:14.671884 [TVE] action=xvfb display=:742
2022/10/27 01:28:14.723882 [TVE] Channel scan 45/217 USAP failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.815176 [TVE] action=auth mvpd=Comcast_SSO requestor=syfy
2022/10/27 01:28:14.816314 [TVE] action=xvfb display=:927
2022/10/27 01:28:14.865183 [TVE] Channel scan 46/217 SYFY failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:14.956695 [TVE] action=auth mvpd=Comcast_SSO requestor=syfy
2022/10/27 01:28:14.957838 [TVE] action=xvfb display=:730
2022/10/27 01:28:15.009527 [TVE] Channel scan 47/217 SYFYP failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:15.126107 [TVE] action=auth mvpd=Comcast_SSO requestor=e
2022/10/27 01:28:15.127544 [TVE] action=xvfb display=:858
2022/10/27 01:28:15.193309 [TVE] Channel scan 48/217 E failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:15.282605 [TVE] action=auth mvpd=Comcast_SSO requestor=e
2022/10/27 01:28:15.283766 [TVE] action=xvfb display=:566
2022/10/27 01:28:15.336685 [TVE] Channel scan 49/217 EP failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/10/27 01:28:15.438018 [TVE] action=auth mvpd=Comcast_SSO requestor=bravo
2022/10/27 01:28:15.439097 [TVE] action=xvfb display=:881
2022/10/27 01:28:15.489715 [TVE] Channel scan 50/217 BRAVO failed: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
Is this going to be an ongoing problem when installing in latest UBUNTU do I have to convert to a docker ? Can somebody explain to me what exactly is this error ?
6159 GOLF
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6160 OLYMPICS
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6162 SNY
Xfinity does not provide TVE access to SNY
6163 NESN
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6164 NBCSN-CHICAGO
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6165 NBCSN-WASHINGTON
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6166 NBCSN-BOSTON
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
6167 NBCSN-BAYAREA
chrome failed to start: /system.slice/channels-dvr.service is not a snap cgroup
Have you seen this
I guess i have to replace firefox with chrome ... but something needs to be done on the channelsdvr side. I moved to Docker. Only response I got was from you on a possible fix much appreciated.
snap remove --purge firefox
apt purge firefox
apt install firefox
Reading all the way through that very long thread seems to narrow down where the problem originates, but other than a few reported workarounds (that didn't work for everyone) there was no clear conslusion as of the last post 5 days ago.
I haven't had this issue happen since I installed Ubuntu on the Beelink I am now using.
I read through that thread as well and so far there are a few workarounds, but I hate having to do workarounds.
Can Chromium, or even Chrome be installed without using snapd? I don't personally care if it's in snapd or not.
But, like I said, so far I've not run into it again. If it does happen again it will most likely wait until it's trying to record something I really want to watch.
I moved over to docker ... I have other APPS that use XMLTV from Channels DVR and cannot afford this error it keeps popping up every other day.
Yes.
sudo apt install chromium-browser
I have done that and after a reboot or after a day or 2 I get the snap error. I always use the command supplied in the linux Channels DVR doc.
apt-get install chromium-browser xvfb