Hi Patrick, Luiz On Tue, Aug 26, 2014 at 2:39 PM, Patrick Ohly <patrick.ohly@xxxxxxxxx> wrote: > I noticed a problem in obexd and/or Bluez 5.21 (Debian Testing): > > - PullAll from Samsung Galaxy S3 > - Suspend > - kill the process who called obexd > - try to pull again from a different process > => GDBus.Error:org.bluez.obex.Error.Failed: Unable to find service > record I also was able to reproduce the issue with Bluez 5.21 and Motorola RAZRi/HTC Desire Z using steps described by Patrick. > obexd notices that its client died (there is a InterfacesRemoved signal > for the transfer and session path), but the cleanup seems to leave the > device or the local side in an unusable state. What I noticed is that after killing client process, phone still seems to see active session - Bluetooth icon on the phone is still blue (it turns blue when there is an active session), so that may indicate that phone is left in unusable state. > Killing obexd and restarting it makes it possible to access the phone > again. For me also switching phone Bluetooth off and on makes it possible to create new session form different process, without need to restart obexd. Regards, Mateusz Półrola -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
