Dpkg: error processing jitsi-videobridge2 stable and unstable channel, ubuntu 18.04

Install & Config
#1

I am experiencing problems with ubuntu (deb) installation of the stable channel.
Here is the output of the apt install command that tried to fix a broken install:
sudo apt-get --fix-broken install
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… Done
The following package was automatically installed and is no longer required:
jitsi-meet-turnserver
Use ‘sudo apt autoremove’ to remove it.
The following additional packages will be installed:
jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config
Recommended packages:
jitsi-meet-turnserver | apache2
The following packages will be upgraded:
jicofo jitsi-meet jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config
5 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
5 not fully installed or removed.
Need to get 0 B/57.9 MB of archives.
After this operation, 3,714 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Preconfiguring packages …
Setting up jitsi-videobridge2 (2.1-202-g5f9377b9-1) …
sed: -e expression #1, char 14: unterminated `s’ command
dpkg: error processing package jitsi-videobridge2 (–configure):
installed jitsi-videobridge2 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
jitsi-videobridge2
E: Sub-process /usr/bin/dpkg returned an error code (1)

same issue with the unstable channel:

sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
jicofo jitsi-meet-prosody jitsi-meet-web jitsi-meet-web-config
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up jitsi-videobridge2 (2.1-207-ga4bfc7f2-1) …
sed: -e expression #1, char 14: unterminated `s’ command
dpkg: error processing package jitsi-videobridge2 (–configure):
installed jitsi-videobridge2 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
jitsi-videobridge2
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any hint to solve that ?

#2

For the record, I tried yesterday to install ‘unstable’ - actually 4653 - on an Ubuntu 20.04 container and was greeted by an ominous warning of missing dependencies, so of course I dropped the 20.04 container, setup a 18.04 instead and installed the 4653 release of Jitsi-meet without issue (not completely true since at the moment secure domain don’t work as it should but vanilla install worked completely).
So what did you do really ? did you by any chance force the initial installation ?

#3

Well, a simple combo sudo apt-get update; sudo apt-get upgrade that works usually.
No force of any kind produces this bug. Then all the “recovery” procedures from apt don’t work either.
The /etc/apt/sources.list.d/jitsi.list contains
deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] https://download.jitsi.org stable/
or unstable/ depending. So nothing unusual there.

The problem appears in the procedure of the post-installation package.

Setting up jitsi-videobridge2 (2.1-207-ga4bfc7f2-1) ...
sed: -e expression #1, char 14: unterminated "s" command
dpkg: error processing package jitsi-videobridge2 (--configure):
installed jitsi-videobridge2 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
jitsi-videobridge2
E: Sub-process /usr/bin/dpkg returned an error code (1)

#4

Maybe you have commented --apis param in /etc/jitsi/videobridge/config
There is ongoing work on fixing that https://github.com/jitsi/jitsi-videobridge/pull/1273

1 Like
#5

It appears btw to be related to commented lines indeed… Thanks for the hint.

#6

it was just a config mistake; there is no problem with current unstable (4663 now) that I am aware of.