gss-client leaves zombie moonshot process running

[Kevin Wasserman]

This happens whether or not ui was brought up. While the zombie process runs, moonshot ui cannot be made visible.
In the example below, no ui was brought up since there was already an identity associated to the service.

kevin@moonshot1-13-2012:~$ ps -C moonshot
  PID TTY TIME CMD
kevin@moonshot1-13-2012:~$ gss-client -mech "{1 3 6 1 4 1 5322 22 1 18}" localhost host@locahost hello
Sending init_sec_context token (size=37)...continue needed...
CTRL-EVENT-EAP-STARTED EAP authentication started
Sending init_sec_context token (size=35)...continue needed...
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=21
CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
Sending init_sec_context token (size=86)...continue needed...
Sending init_sec_context token (size=358)...continue needed...
Sending init_sec_context token (size=83)...continue needed...
Sending init_sec_context token (size=148)...continue needed...
EAP-MSCHAPV2: Authentication succeeded
Sending init_sec_context token (size=83)...continue needed...
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Sending init_sec_context token (size=133)...continue needed...

context flag: GSS_C_MUTUAL_FLAG
context flag: GSS_C_REPLAY_FLAG
context flag: GSS_C_SEQUENCE_FLAG
context flag: GSS_C_CONF_FLAG
context flag: GSS_C_INTEG_FLAG
"steve@local" to "host/locahost", lifetime -1, flags 13e, locally initiated, open
Name type of source name is { 1 2 840 113554 1 2 1 1 }.
Mechanism { 1 3 6 1 4 1 5322 22 1 18 } supports 5 names
  0: { 1 2 840 113554 1 2 1 1 }
  1: { 1 2 840 113554 1 2 1 4 }
  2: { 1 3 6 1 5 6 4 }
  3: { 1 3 6 1 4 1 5322 22 2 1 }
  4: { 1 3 6 1 5 6 3 }
Signature verified.
Inconsistency detected by ld.so: dl-close.c: 743: _dl_close: Assertion `map->l_init_called' failed!
kevin@moonshot1-13-2012:~$ ps -C moonshot
  PID TTY TIME CMD
 3942 ? 00:00:00 moonshot

[Sam Hartman (hartmans)]

So, leaving the process around is in of itself a bug.
However, the big issues here are

1) Once you have sent send once, you cannot ever see the UI again even
if there is another authentication to take place

2) running moonshot by hand or from desktop menus will not allow you to
go in and manage identities.

Fixing 2 probably requires either a new dbus message or that when there
are no outstanding authentication requests and send is pressed the
process exit.

 assigneepete-fotheringham
 status confirmed
 milestone tech-pilot
 importance critical