Bug 436279

Summary:	Unable to connect to HAL to list CDROM volumes
Product:	Red Hat Enterprise Linux 5	Reporter:	Alexander Todorov <atodorov>
Component:	virt-manager	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.2	CC:	crobinso, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-03-11 15:40:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexander Todorov 2008-03-06 10:53:24 UTC

Description of problem:
runnin gvirt-manager and trying to create a pv guest I see this in virt-manager.log

[Thu, 06 Mar 2008 05:49:53 virt-manager 5708] ERROR (opticalhelper:39) Unable to
connect to HAL to list cdrom volumes: 'A security policy in place prevents this
sender from sending this message to this recipient, see message bus
configuration file (rejected message had interface "(unset)" member
"GetPropertyBoolean" error name "(unset)" destination "org.freedesktop.Hal")'
[Thu, 06 Mar 2008 05:49:53 virt-manager 5708] ERROR (create:145) Unable to
create optical-helper widget: 'A security policy in place prevents this sender
from sending this message to this recipient, see message bus configuration file
(rejected message had interface "(unset)" member "GetPropertyBoolean" error name
"(unset)" destination "org.freedesktop.Hal")'



Version-Release number of selected component (if applicable):
virt-manager-0.5.3-2.el5

How reproducible:
100%

Steps to Reproduce:
1. Start virt-manager
2. Click "New" to create a new guest
3. The error appears in virt-manager.log after clicking New.
  
Actual results:
Error in log file

Expected results:
No errors

Additional info:
SELinux is in Permissive mode.

Comment 1 Cole Robinson 2008-03-10 18:36:27 UTC

I think this may be fixed by the dbus patch that Dan took care of for bug
436276. Can you see if this is still an issue with virt-manager-0.5.3-3.el5 or
later?

Comment 2 Alexander Todorov 2008-03-11 09:56:21 UTC

Not seeing this error with:
virt-manager-0.5.3-4.el5

Comment 3 Cole Robinson 2008-03-11 15:40:12 UTC

I'll just close this as a DUP then. Thanks!

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