Now I got bitten by the same problem - and got solution (at least for devuan) - so this might be interesting for Bill :) It turned out that the compination of "apparmor" plus "pulseaudio" made networkmanager go kind of numb. It would not connect to my wifi for ever. Retrying did not change anything nor did turning the wifi device on/off change anything. Last entry in syslog was always "wlan0: associated", but it looked like ip address was received. Now removing "apparmor" increased the chace of getting ip adresses via dhcp to ~ 50%. After removing pulseaudio and pulseaudio-modules-bluetooth the rate is back to normal aka 100%. Note: I had pulseaudio to connect to bluetooth speakers and my problems begun after installing it. At last I got the speakers working with "bluealsa" --> kmix is not confused with the "pulseaudio" device sneeking in as first coundcard. Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
