Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalI am able to install and use snx (800008061) in ubuntu:cosmic and bionic.
Install dependencies:
Problem with systemd-resolved can be solved by unlinking /etc/resolv.conf (possible rm -r /etc/resolv.conf && echo "nameserver 127.0.0.53" > /etc/resolv.conf ) and installing libnss-resolve:i386 and libnss-resolve, which will provide fallback resolving in case of missing resolv.conf, which is edited directly by snx.
I am able to install and use snx (800008061) in ubuntu:cosmic and bionic.
Install dependencies:
Problem with systemd-resolved can be solved by unlinking /etc/resolv.conf and installing libnss-resolve:i386 and libnss-resolve, which will provide fallback resolving in case of missing resolv.conf, which is edited directly by snx.
I am able to install and use snx (800008061) in ubuntu:cosmic and bionic.
Install dependencies:
Problem with systemd-resolved can be solved by unlinking /etc/resolv.conf (possible rm -r /etc/resolv.conf && echo "nameserver 127.0.0.53" > /etc/resolv.conf ) and installing libnss-resolve:i386 and libnss-resolve, which will provide fallback resolving in case of missing resolv.conf, which is edited directly by snx.
I am able to install and use snx (800008061) in ubuntu:cosmic and bionic.
Install dependencies:
Problem with systemd-resolved can be solved by unlinking /etc/resolv.conf and installing libnss-resolve:i386 and libnss-resolve, which will provide fallback resolving in case of missing resolv.conf, which is edited directly by snx.
