I've attached lshal output with the default, unchanged hal-info package and no tweaks in /etc/hal/fdi . The phone was not connected over USB. A bluetooth pairing exists which is trusted on both ends. An OBEX connection from phone to host over BT was active at the time lshal was run. The phone was set to visible in its bluetooth control panel.
Package versions:
ii bluez-gnome 0.25-0ubuntu2 Bluetooth utilities for GNOME
ii bluez-utils 3.36-1ubuntu1 Bluetooth tools and daemons
ii gnome-bluetooth 0.11.0-0ubuntu2 GNOME Bluetooth tools.
ii hal-info 20080508+git20080601-1ubuntu2~nm1 Hardware Abstraction Layer - fdi files
ii network-manager 0.7~~svn20080818t061112+eni1-0ubu network management framework daemon
ii network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1 network management framework (GNOME frontend)
(hal-info and NM are from the NM PPI)
The phone properly exposes a DUN interface over SDP, so with an existing pairing it should be discoverable even with visibility off.
I've attached lshal output with the default, unchanged hal-info package and no tweaks in /etc/hal/fdi . The phone was not connected over USB. A bluetooth pairing exists which is trusted on both ends. An OBEX connection from phone to host over BT was active at the time lshal was run. The phone was set to visible in its bluetooth control panel.
Package versions:
ii bluez-gnome 0.25-0ubuntu2 Bluetooth utilities for GNOME git20080601- 1ubuntu2~ nm1 Hardware Abstraction Layer - fdi files 8t061112+ eni1-0ubu network management framework daemon manager- gnome 0.7~~svn2008081 7t183748- 0ubuntu1 network management framework (GNOME frontend)
ii bluez-utils 3.36-1ubuntu1 Bluetooth tools and daemons
ii gnome-bluetooth 0.11.0-0ubuntu2 GNOME Bluetooth tools.
ii hal-info 20080508+
ii network-manager 0.7~~svn2008081
ii network-
(hal-info and NM are from the NM PPI)
The phone properly exposes a DUN interface over SDP, so with an existing pairing it should be discoverable even with visibility off.