Description of problem:
Use systemd-run to launch a process in a new systemd scope, then run "systemctl show" on that scope. For example:

  $ sudo systemd-run --scope bash
  Running as unit run-5179.scope.
  # systemctl show run-5179.scope
  Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Version-Release number of selected component:
systemd-208-16.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd --switched-root --system --deserialize 23
crash_function: _dbus_abort
environ:        
executable:     /usr/lib/systemd/systemd
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 _dbus_abort at dbus-sysdeps.c:94
 #6 _dbus_warn_check_failed at dbus-internals.c:290
 #7 dbus_message_iter_append_basic at dbus-message.c:2586
 #8 bus_property_append_string at ../src/shared/dbus-common.c:526
 #9 bus_default_message_handler at ../src/shared/dbus-common.c:390
 #10 bus_scope_message_handler at ../src/core/dbus-scope.c:94
 #11 bus_unit_message_dispatch at ../src/core/dbus-unit.c:479
 #12 bus_unit_message_handler at ../src/core/dbus-unit.c:610
 #13 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #15 bus_dispatch at ../src/core/dbus.c:525

Potential duplicate: bug 902026