Description of problem: Logged in. Version-Release number of selected component: systemd-analyze-197-1.fc18.1 Additional info: cmdline: /usr/bin/python /usr/bin/systemd-analyze --user dso_list: pygobject3-base-3.4.2-6.fc18.x86_64 executable: /usr/bin/systemd-analyze kernel: 3.7.6-201.fc18.x86_64 uid: 1000 Truncated backtrace: types.py:76:constructor:GError: Error spawning command line `dbus-launch --autolaunch=2992adb976de4342a877dc1a1de498e9 --binary-syntax --close-stderr': Child process exited with code 1 Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 328, in <module> verb.get(args.action)() File "/usr/bin/systemd-analyze", line 110, in time firmware_time, loader_time, kernel_time, initrd_time, userspace_time, finish_time = acquire_start_time() File "/usr/bin/systemd-analyze", line 54, in acquire_start_time None, 'org.freedesktop.systemd1', '/org/freedesktop/systemd1', 'org.freedesktop.DBus.Properties', None) File "/usr/lib64/python2.7/site-packages/gi/types.py", line 76, in constructor return info.invoke(cls, *args, **kwargs) GError: Error spawning command line `dbus-launch --autolaunch=2992adb976de4342a877dc1a1de498e9 --binary-syntax --close-stderr': Child process exited with code 1 Local variables in innermost frame: info: <gi.FunctionInfo object (new_for_bus_sync) at 0x0x2269d88> cls: <class 'gi.overrides.Gio.DBusProxy'> args: (<enum G_BUS_TYPE_SESSION of type GBusType>, <flags 0 of type GDBusProxyFlags>, None, 'org.freedesktop.systemd1', '/org/freedesktop/systemd1', 'org.freedesktop.DBus.Properties', None) cls_name: 'DBusProxy' kwargs: {}
Created attachment 698704 [details] File: backtrace
Created attachment 698705 [details] File: core_backtrace
Created attachment 698706 [details] File: environ
Fixed in a way in git, since we now have a nice C implementation of the tool that prints nicer messages.
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1
Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback).
Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.3 then log in and leave karma (feedback).
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.