Package: connman Version: 1.36-2.1~deb10u1 Severity: important Dear Maintainer,
Recently I've made minimal install of Debian. Due to limited resources, I decided to try connman + iwd, despite the fact, that I experienced the same problem earlier on. What is happening?- PC can't connect to any other network than the one used during install. At first I thought that it can be caused by early state of development of iwd package in Buster. But it turned out that the problem persists with wpasupplicant. I found that I'm obtaing ip, but not dns name. My /etc/resolv.conf wasn't changed by connman and sticked to ip of gateway used during install. After some more effort, as last resort I decided to delete file /etc/resolv.conf, hoping that network manager will create it anew with proper setup. This happened indeed and solved the issue, but it definitely isn't nice welcome to Debian with connman . -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages connman depends on: ii dbus 1.12.20-0+deb10u1 ii iptables 1.8.2-4 ii libc6 2.28-10 ii libdbus-1-3 1.12.20-0+deb10u1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgnutls30 3.6.7-4+deb10u6 ii libreadline7 7.0-5 ii libxtables12 1.8.2-4 ii lsb-base 10.2019051400 Versions of packages connman recommends: ii bluez 5.50-1.2~deb10u1 ii iwd 0.14-2 ii ofono 1.21-1 Versions of packages connman suggests: pn connman-vpn <none> -- no debconf information
