So I just dealt with this for a 2nd time ( E profile got corrupted
after a hard lockup ). I thought I document what was needed for me, at
least for myself the next time it happens, if not for others who have
the same issue ...

I need to run:


 ... on startup. nm-applet triggers a dialog asking for my password
for gnome keyring, and after it's entered, I can successfully connect
to saved networks.


On Wed, Nov 2, 2016 at 12:29 PM, Carsten Haitzler <> wrote:
> On Wed, 2 Nov 2016 11:52:28 +1100 Daniel Kasak <> said:
>> Hi all.
>> I just switched jobs ( yay ) and the new one has a wireless network
>> with WPA2 security, PEAP auth, and a CA certificate.
>> When I set this up in the gnome control panel, running under gnome, it
>> connects fine. But when I launch E after booting, I get a cryptic
>> error in systemd logs:
>> No agents were available for this request
>> I guess there are some gnome services that are required that aren't
>> running for me under E? Does anyone know what I'm missing?
> i don't know but i might guess that gnome talks to networkwrmanager over dbus
> and advertises/provides this "auth agent" which would require popping up a
> password or something dialog and passing it back to networkmanager. we hve no
> such code in e... :/ you could run nm-client or whatever it is? we removed
> xmbed systray support so as long as nm-client supports the app indicator dbus
> protocol it should be ok i think... if not there are 3rd party tray apps like
> trayer or others.
> --
> ------------- Codito, ergo sum - "I code, therefore I am" --------------
> The Rasterman (Carsten Haitzler)

Check out the vibrant tech community on one of the world's most 
engaging tech sites,!
enlightenment-users mailing list

Reply via email to