Version-Release number of selected component: systemd-208-9.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-hostnamed crash_function: _dbus_abort executable: /usr/lib/systemd/systemd-hostnamed kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (3 frames) #2 _dbus_abort at dbus-sysdeps.c:94 #3 _dbus_warn_check_failed at dbus-internals.c:290 #4 connect_bus at ../src/hostname/hostnamed.c:670
Created attachment 843393 [details] File: backtrace
Created attachment 843394 [details] File: cgroup
Created attachment 843395 [details] File: core_backtrace
Created attachment 843396 [details] File: dso_list
Created attachment 843397 [details] File: environ
Created attachment 843398 [details] File: limits
Created attachment 843399 [details] File: maps
Created attachment 843400 [details] File: open_fds
Created attachment 843401 [details] File: proc_pid_status
Created attachment 843402 [details] File: var_log_messages
Yeah, we use NULL in cleanup. Easy enough to fix.
systemd-208-11.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-11.fc20
Package systemd-208-11.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-11.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0902/systemd-208-11.fc20 then log in and leave karma (feedback).
systemd-208-13.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-13.fc20
systemd-208-14.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-14.fc20
systemd-208-14.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.