Comment # 5 on bug 1079320 from Nick Singer

(In reply to Oliver Kurz from comment #4)
> Hi nicksinger, you as the test writer, any ideas? Can you take a look into
> the logs?

This one looks really weird. Obviously the gnome-applet itself can communicate
with the NM backend (it can scan networks, It sees the adapters, etc.).

However, after issuing the nmcli commands all of a sudden the
GNOME-NetworkManager-UI pops up
(https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/19).
The empty "Visible Networks" section and the two empty buttons on top
(https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/19) give me
the suspicion that the dbus communication between the gnome-network-settings
and NM are somehow misbehaving.

Unfortunately there are no logs available (no network on upload).

(In reply to Dominique Leuenberger from comment #0)
> This seems to be an interaction issue between GNOME Control Center and
> NetworkManager 1.10 (?)
> 
> As can be seen in the screenshots, the connection has been established, just
> g-c-c seems not able to show the status (something which somehow I could not
> yet reprodcue on my own machine)

No offense, but are you sure you tested the GNOME (control center) interface of
NM or did you actually check the "native" NM-GUI on your local machine? In
which screenshot did you see that the connection is established?
https://openqa.opensuse.org/tests/601692#step/NM_wpa2_enterprise/24
unfortunately only shows that it clicks "connect". Afterwards I was unable to
see any indication if the connection is actually established (I'm not a gnome
user after all - sry).


However. Since we still see the same error in the most recent snapshot
(https://openqa.opensuse.org/tests/647737#step/NM_wpa2_enterprise/26) I'll try
to extract more logs on a local machine and maybe even improve debugging here.