Bug#966138: Package: connman sysvint script disables DNS lookups when resolvconf package installed

[n Xecure]

As the reply above, the solution is to convert the string into a variable
call, so that the change to /etc/default/connman can be properly processed.

Please, someone with powers, add the fix to
debian/patches/01-init-script-lsb-headers.patch
.
I would also like to request to anyone with powers to package thee fix when
you have time after the bullseye release if not sooner.

These would be the changes to said file, in case the petition is not
understood:
https://gitlab.com/nXecure/connman/-/commit/d5d43713977a5317c84b620251f3cdf2848598f2#8ec1dbece58825f4fe44c11e357d1993f9e23d81

Thanks for your time.

Bug#966138: Package: connman sysvint script disables DNS lookups when resolvconf package installed

[Pelayo González Muñoz]

There is a typo in the init script, a "$" is missing to expand the variable:

if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then

Should be:

if [ "$CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then

Once fixed, create /etc/default/connman:

echo " CONNMAN_RUNSTATEDIR_RESOLVCONF=no" > /etc/default/connman

Regards
--
Pelayo González

On Thu, 23 Jul 2020 11:39:54 -0400 Vernon Van Steenkist 
wrote:
> Package: connman
> Version: 1.36-2
>
> Beowulf connman 1.36-2 i386 sysvinit script conflicts with resolvconf
1.79 package leaving the system in a state unable to do DNS lookups.
>
> Problem one:
>
> sed -n "22,25p" /etc/init.d/connman
>
> if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then
>  mkdir -p /run/connman
>  ln -sf /run/connman/resolv.conf /etc/
> fi
>
> Since string CONNMAN_RUNSTATEDIR_RESOLVCONF will never be equal to string
no, the following line will always be executed
> ln -sf /run/connman/resolv.conf /etc/
>
>
> So, I am not what conditional
>
> if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ]
>
> is supposed to accomplish.
>
> Problem Two:
>
> This creates a problem when using the resolvconf package. Package
resolvconf links /etc/resolv.conf to
> /run/resolvconf/resolv.conf However, after re-boot, /etc/init.d/connman
overwrites this link and links
> /etc/resolv.conf to /run/connman/resolv.conf
> once again leaving the system in a state unable to do DNS look-ups.
>
> I have brute forced a fix by commenting out the line
> ln -sf /run/connman/resolv.conf /etc/ in /etc/init.d/connman
>
> sed -n "22,25p" /etc/init.d/connman
>
> if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then
>  mkdir -p /run/connman
> #ln -sf /run/connman/resolv.conf /etc/
> fi
>
> and re-linking /etc/resolv.conf to /run/resolvconf/resolv.conf
>
> I am not sure what the correct fix should be.
>
> Please don't hesitate to contact me if you have any questions.
>
> Thanks,
> Vernon
>
>
>

Bug#966138: Package: connman sysvint script disables DNS lookups when resolvconf package installed

[Vernon Van Steenkist]

Package: connman
Version: 1.36-2

Beowulf connman 1.36-2 i386 sysvinit script conflicts with resolvconf 1.79 
package leaving the system in a state unable to do DNS lookups.

Problem one:

sed -n "22,25p" /etc/init.d/connman

if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then
mkdir -p /run/connman
ln -sf /run/connman/resolv.conf /etc/
fi

Since string CONNMAN_RUNSTATEDIR_RESOLVCONF will never be equal to string no, 
the following line will always be executed
ln -sf /run/connman/resolv.conf /etc/


So, I am not what conditional

if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ]

is supposed to accomplish.

Problem Two:

This creates a problem when using the resolvconf package. Package resolvconf 
links /etc/resolv.conf to
/run/resolvconf/resolv.conf However, after re-boot, /etc/init.d/connman 
overwrites this link and links
/etc/resolv.conf to /run/connman/resolv.conf
once again leaving the system in a state unable to do DNS look-ups.

I have brute forced a fix by commenting out the line
ln -sf /run/connman/resolv.conf /etc/ in /etc/init.d/connman

sed -n "22,25p" /etc/init.d/connman

if [ "CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then
mkdir -p /run/connman
#ln -sf /run/connman/resolv.conf /etc/
fi

and re-linking /etc/resolv.conf to /run/resolvconf/resolv.conf

I am not sure what the correct fix should be.

Please don't hesitate to contact me if you have any questions.

Thanks,
Vernon