Description of problem: Running getcert status after installing. Version-Release number of selected component: certmonger-0.75.14-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: getcert status crash_function: _dbus_abort executable: /usr/bin/getcert kernel: 3.16.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #2 _dbus_abort at dbus-sysdeps.c:94 #3 _dbus_warn_check_failed at dbus-internals.c:290 #4 dbus_message_new_method_call at dbus-message.c:1263 #5 prep_req at getcert.c:279 #6 query_rep at getcert.c:358 #7 status at getcert.c:3058 #9 _start
Created attachment 956894 [details] File: backtrace
Created attachment 956895 [details] File: cgroup
Created attachment 956896 [details] File: core_backtrace
Created attachment 956897 [details] File: dso_list
Created attachment 956898 [details] File: environ
Created attachment 956899 [details] File: limits
Created attachment 956900 [details] File: maps
Created attachment 956901 [details] File: open_fds
Created attachment 956902 [details] File: proc_pid_status
Created attachment 956903 [details] File: var_log_messages
Description of problem: On a new Fedora 20 (cloud) virtual machine, with a fresh install of certmaster and certmonger calling getcert status and certmaster-getcert status results in a failures with message: process 25227: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1262. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Version-Release number of selected component (if applicable): certmonger-0.75.14-1.fc20.x86_64 certmaster-0.28-7.fc20.noarch dbus-libs-1.6.12-9.fc20.x86_64 dbus-1.6.12-9.fc20.x86_64 How reproducible: It failed on my personal machine and so i tried it from scratch on an up to date vm image and got the same problem. Steps to Reproduce: 1. sudo yum install certmonger certmaster 2. sudo systemctl start certmaster 3. sudo systemctl start certmonger 4. sudo getcert status Actual results: process 25227: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1262. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Expected results: A status output, in this case it's probably empty. Additional info:
*** Bug 1163539 has been marked as a duplicate of this bug. ***
The command was incorrectly assuming that information for locating the particular request would be specified, and what you're seeing is what would happen when that assumption was proved wrong. It should be fixed in 0.76 and later. If you can verify that the current test update (https://admin.fedoraproject.org/updates/certmonger-0.76.7-1.fc20) fixes it, I'd appreciate it. Thanks!
Ok, that fixes the crash. Ideally it would produce a usage message, like for example if you do getcert request with no arguments it prints the arguments it expects. I was obviously using the command incorrectly (and it's not what i wanted anyway) but the message doesn't give me any further details on what i should do.
(In reply to Jamie Lennox from comment #14) > Ok, that fixes the crash. > > Ideally it would produce a usage message, like for example if you do getcert > request with no arguments it prints the arguments it expects. Agreed, and that'd be consistent with other commands like "list", too. This'll be fixed in 0.76.8 and later.
certmonger-0.76.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2014-14948/certmonger-0.76.8-1.fc20
certmonger-0.76.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.