Version-Release number of selected component: certmonger-0.70-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/sbin/certmonger -S -p /var/run/certmonger.pid -n crash_function: _dbus_abort executable: /usr/sbin/certmonger kernel: 3.12.6-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #2 _dbus_abort at dbus-sysdeps.c:94 #3 _dbus_warn_check_failed at dbus-internals.c:290 #4 dbus_connection_get_is_connected at dbus-connection.c:2932 #5 cm_tdbus_reconnect at tdbus.c:469 #6 tevent_common_loop_timer_delay at ../tevent_timed.c:341 #7 epoll_event_loop_once at ../tevent_epoll.c:912 #8 std_event_loop_once at ../tevent_standard.c:112 #9 _tevent_loop_once at ../tevent.c:530
Created attachment 852727 [details] File: backtrace
Created attachment 852728 [details] File: cgroup
Created attachment 852729 [details] File: core_backtrace
Created attachment 852730 [details] File: dso_list
Created attachment 852731 [details] File: environ
Created attachment 852732 [details] File: limits
Created attachment 852733 [details] File: maps
Created attachment 852734 [details] File: open_fds
Created attachment 852735 [details] File: proc_pid_status
Created attachment 852736 [details] File: var_log_messages
certmonger-0.71.2-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/certmonger-0.71.2-1.fc19
certmonger-0.71.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/certmonger-0.71.2-1.fc20
Package certmonger-0.71.2-1.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 certmonger-0.71.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-1695/certmonger-0.71.2-1.fc20 then log in and leave karma (feedback).
Would it make sense to push the build to stable updates so that it gets more exposure in Fedora 20?
I've had no issues with it, so I have no problem pushing it out. I'm a bit surprised that it hadn't already happened.
(In reply to Michael Hampton from comment #15) > I've had no issues with it, so I have no problem pushing it out. I'm a bit > surprised that it hadn't already happened. It did not reach the stable karma so the maintainer needs to push it manually.
certmonger-0.71.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
certmonger-0.71.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days