Re: Could not connect to wicd's D-Bus interface
I can confirm that this worked for me as well, but after I ran this command and rebooted during bootup, just before the system would ask me to log in, I get the following, visible error messages:
Originally Posted by sickness
Intel AES: Intel AES-NI instructions are not detected.
padlock: VIA PadLock not detected.
Funny thing is that I can just type in my username, hit enter, then I'm asked for my password like normal. Not sure if this was caused by fixing the WICD stuff, but it seems highly likely. Pretty weird, but yeah, all is working well now. Thanks Sickness!