Description of problem: lshal emits error message: lshal >/dev/null process 29945: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Version-Release number of selected component (if applicable): hal-0.5.8.1-5.fc6 How reproducible: Steps to Reproduce: 1. lshal >/dev/null 2. 3. Actual results: process 18206: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Expected results: Additional info:
I am getting the same error. I believe this message started showing up recently with the release of new dbus RPMs # rpm -qa | grep dbus dbus-x11-1.0.1-8.fc6 dbus-python-0.70-6 dbus-1.0.1-8.fc6 dbus-devel-1.0.1-8.fc6 dbus-glib-devel-0.70-6.fc6 dbus-glib-0.70-6.fc6 # rpm -qa | grep hal hal-gnome-0.5.8.1-5.fc6 hal-0.5.8.1-5.fc6 hal-devel-0.5.8.1-5.fc6 hal-cups-utils-0.6.2-4.2
Yep, and it's not just lshal, either: leto:~% hal-device >/dev/null process 8567: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. leto:~% rpm -q hal dbus hal-0.5.8.1-5.fc6 dbus-1.0.1-8.fc6
Same here. x86_64 platform.
It is certainly because lshal tries to close a shared dbus connection, like a connection to the SYSTEM bus. It is clearly forbidden here: http://dbus.freedesktop.org/doc/api/html/group__DBusConnection.html#ge130c33da29477897d362ab89f068191 I hadn't a look at the hal code, though.
Same issue for me: hal-0.5.8.1-6.fc6 dbus-1.0.1-9.fc6 on different hw.
This seems to be fixed now in devel hal-0.5.9-0.git20070218.fc7
I had the same problem with hal-0.5.8.1-6.fc6 and dbus-1.0.1-9.fc6. This was fixed in hal upstream 2006-10-23. dbus_connection_close(conn) was removed in one place in both lshal.c and hal-device.c. Afaik this still is not patched in FC6, although there have been 2 updates to hal in FC6 since upstream fixed this.
Closing since this seems to be fixed in f7 and fc6 isn't supported anymore.