Bug 436279 - Unable to connect to HAL to list CDROM volumes
Summary: Unable to connect to HAL to list CDROM volumes
Keywords:
Status: CLOSED DUPLICATE of bug 436276
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-06 10:53 UTC by Alexander Todorov
Modified: 2009-12-14 21:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-11 15:40:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.