Bug 1163539

Summary: getcert status crash
Product: [Fedora] Fedora Reporter: Jamie Lennox <jlennox>
Component: certmongerAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mharmsen, nalin, nkinder
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-13 01:35:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jamie Lennox 2014-11-13 01:20:34 UTC
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:

Comment 1 Jamie Lennox 2014-11-13 01:35:57 UTC

*** This bug has been marked as a duplicate of bug 1163541 ***