Description of problem:
Started /usr/bin/systemadm directly as root user. 
Attempted to stop cryptsetup.target which crashed systemadm

cryptsetup.target did appear as being inactive in subsequent runs of systemadm.
Stopping any other target/service is a pretty surefire way to trigger the same double free


Version-Release number of selected component:
systemd-ui-1-3.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/bin/systemadm
crash_function: job_unit_link_destroy
kernel:         3.6.7-5.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #6 job_unit_link_destroy at /home/kay/data/src/systemd-ui/src/systemd-interfaces.vala:151
: #7 main_window_update_job_iter at /home/kay/data/src/systemd-ui/src/systemadm.vala:760
: #8 main_window_on_job_new at /home/kay/data/src/systemd-ui/src/systemadm.vala:788
: #12 g_signal_emit_by_name at gsignal.c:3393
: #13 _dbus_handle_manager_job_new at systemd-interfaces.c:1506
: #14 manager_proxy_g_signal at systemd-interfaces.c:1541
: #15 ffi_call_unix64 at ../src/x86/unix64.S:75
: #16 ffi_call at ../src/x86/ffi64.c:486
: #17 g_cclosure_marshal_generic at gclosure.c:1454
: #22 on_signal_received at gdbusproxy.c:927