Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 64520 - hal-device-manager can't excute.
Summary: hal-device-manager can't excute.
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: foser (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-18 07:19 UTC by Young-Ho Cha
Modified: 2004-09-19 04:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Young-Ho Cha 2004-09-18 07:19:48 UTC
install hal-0.2.97 and run hal-device-manager, can't excute.

Reproducible: Always
Steps to Reproduce:
1. install hal-0.2.97
2. run hal-device-manager


Actual Results:  
hal-device-manager prints this error.

Traceback (most recent call last):
  File "/usr/bin/hal-device-manager", line 15, in ?
    DeviceManager()
  File "/usr/share/hal/device-manager/DeviceManager.py", line 78, in __init__
    self.add_device_signal_recv (name);
  File "/usr/share/hal/device-manager/DeviceManager.py", line 94, in
add_device_signal_recv
    udi)
  File "/usr/lib/python2.3/site-packages/dbus.py", line 89, in add_signal_receiver
    dbus_bindings.bus_add_match(self._connection, match_rule)
  File "dbus_bindings.pyx", line 1417, in dbus_bindings.bus_add_match
dbus_bindings.DBusException: Connection ":1.10" is not allowed to add more match
rules (increase limits in configuration file if required)

Expected Results:  
hal-device-manager runs!

apply this patch. 

--- tools/device-manager/DeviceManager.py~   2004-09-18 23:19:51.166371152 +0900
+++ tools/device-manager/DeviceManager.py    2004-09-18 22:50:40.324539568 +0900
@@ -87,6 +87,7 @@
                                     "org.freedesktop.Hal.Device",
                                     "org.freedesktop.Hal",
                                     udi)
+       return
        self.bus.add_signal_receiver(self.device_changed,
                                     "Condition",
                                     "org.freedesktop.Hal.Device",
@@ -99,6 +100,7 @@
                                     "org.freedesktop.Hal.Device",
                                     "org.freedesktop.Hal",
                                     udi)
+       return
        self.bus.remove_signal_receiver(self.device_changed,
                                     "Condition",
                                     "org.freedesktop.Hal.Device",
Comment 1 Stefan Schweizer (RETIRED) gentoo-dev 2004-09-18 07:45:03 UTC
~ $ hal-device-manager
Traceback (most recent call last):
  File "/usr/bin/hal-device-manager", line 12, in ?
    from DeviceManager import DeviceManager
  File "/usr/share/hal/device-manager/DeviceManager.py", line 6, in ?
    import dbus
ImportError: No module named dbus


obviously /usr/lib/python2.3/site-packages/dbus.py is missing, how did you get it?
Comment 2 Seemant Kulleen (RETIRED) gentoo-dev 2004-09-18 10:30:51 UTC
do you have dbus emerged?
Comment 3 foser (RETIRED) gentoo-dev 2004-09-18 12:52:03 UTC
@stefan : you have to build dbus with python support.. hal-device-manager is not meant as a user tool, at this point i see no reason to force deps for it. Anyway it's not the same problem as the one reported, please try to keep different problems in different bugs.

@initial reporter : im not sure what the patch is supposed to fix ? Does it run with that patch applied ?

Comment 4 Young-Ho Cha 2004-09-18 23:42:44 UTC
i copied that patch from current hal cvs. after apply that patch,  it can run.

http://freedesktop.org/cgi-bin/viewcvs.cgi/hal/tools/device-manager/DeviceManager.py?r1=1.13&r2=1.14&root=hal

2004-08-31  David Zeuthen  <david@fubar.dk>
	* tools/device-manager/DeviceManager.py: Don't print out Conditions;
	should give us more headroom until D-BUS is fixed wrt. rules maximum
	and subscription of signals in the python bindings
Comment 5 foser (RETIRED) gentoo-dev 2004-09-19 04:14:14 UTC
right, i read about that. Well, i'm not gonna fix that in the ebuild... we're waiting for a new snapshot anyway.