[Logcheck-devel] Bug#284825: logcheck-database: connecting a bluetooth adaptor

Lee Maguire lee-debian at hexkey.co.uk
Thu Dec 9 01:15:07 UTC 2004


Package: logcheck-database
Version: 1.2.32
Severity: wishlist

The following was generated as a result of plugging in a bluetooth USB
device (while running a phone manager program) making a connection,
disabling the connection and then unplugging the USB device.

(hcid is part of "bluez-utils", the hex codes have been changed to all F)

Dec  9 00:47:54 localhost usb.agent[4631]:      hci_usb: loaded successfully
Dec  9 00:47:54 localhost kernel: Bluetooth: HCI USB driver ver 2.7

Dec  9 00:57:34 localhost hcid[3300]: HCI dev 0 registered
Dec  9 00:57:34 localhost hcid[3300]: HCI dev 0 up
Dec  9 00:57:34 localhost hcid[3300]: Starting security manager 0
Dec  9 00:57:43 localhost usb.agent[5586]:      hci_usb: already loaded
Dec  9 00:58:08 localhost hcid[3300]: link_key_request (sba=FF:FF:FF:FF:FF:FF, dba=FF:FF:FF:FF:FF:FF)
Dec  9 00:58:08 localhost udev[5702]: creating device node '/dev/rfcomm0'
Dec  9 00:58:50 localhost udev[5709]: removing device node'/dev/rfcomm0'
Dec  9 00:59:01 localhost kernel: usb 1-1: USB disconnect, address 3
Dec  9 00:59:01 localhost hcid[3300]: HCI dev 0 down
Dec  9 00:59:01 localhost hcid[3300]: Stoping security manager 0
Dec  9 00:59:02 localhost hcid[3300]: HCI dev 0 unregistered







More information about the Logcheck-devel mailing list