Ticket #15 (new defect)

Opened 7 months ago

Last modified 6 months ago

Problems to register network servers when the adapter is replaced

Reported by: cktakahasi Assigned to: vcgomes
Priority: major Milestone: Undefined
Component: networking Version: 3.30
Keywords: Cc:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: 0 Total Hours:

Description

When the networking service starts it register "default" servers(NAP, GN and PANU). When a dongle is replaced and the hcid daemon starts, the networking service reads all /var/lib/bluetooth/ subdirectories(dongle addresses) looking for "nap", "gn", "panu" files and register the "objects".

How reproduce:

  1. Kill/stop hcid
  2. Remove the dongle and attach a new one
  3. Run the hcid => network server objects are not registered for this new adapter

Problem: Server for the new adapter can fail depending on the directory reading order. The D-Bus path is unique: "/org/bluez/network/{nap, gn, panu}"

Change History

04/17/08 20:27:55 changed by vcgomes

  • hours changed.
  • estimatedhours changed.
  • billable changed.

I think this problem could be solved definitively when we define how to expose the services with the new API. So, this ticket depends on ticket:25.

05/19/08 14:48:32 changed by cktakahasi

  • milestone changed from Sprint 3 to Undefined.

it is going to be automatically fixed in the BlueZ 4.X architecture. Move it to "undefined" milestone.