Bug 712702

Summary:	systemd fails to respond properly to "is-active"
Product:	[Fedora] Fedora	Reporter:	redhatbug <mjmccaffrey>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	dcbw, harald, jklimes, johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-13 09:45:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description redhatbug 2011-06-12 15:00:04 UTC

Description of problem:


Version-Release number of selected component (if applicable):
systemd-26-2.fc15.x86_64
NetworkManager-0.8.9997-2.git20110531.fc15.x86_6
(already a third update!!)
How reproducible:
Every time the following command is issued

   systemctl is-active NetworkManager.service
   
when NetworkManager is disabled

Steps to Reproduce:
1. Type the command 
   systemctl is-active NetworkManager.service
   when NetworkManager is disabled
2.
3.
  
Actual results:
process 2272: arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1548.
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:
0 or other return value from the command

Additional info:

Comment 1 Jirka Klimes 2011-06-13 09:42:31 UTC

That's not related to NetworkManager. It is a sytemctl bug.
Already fixed upstream: 78e39b43b89c6bf9ce401d6030939a004a23c850

Step to reproduce:    
* systemctl stop gpm.service  
* systemctl disable gpm.service  
* systemctl is-active gpm.service

Comment 2 Michal Schmidt 2011-06-13 09:45:41 UTC

The crash is bug 709909. That it will still give wrong information after fixing the crash is bug 699027.

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