[Bug 179399] crash bug fixed

[Robert Lange]

Attached is a patch that fixes the crash bug described here.  Using the
information from comments 25-27, I caught the timeout and notified the
user that the authentication had failed.

Also, I modified the dbus timeout to be longer than the bluetooth
authentication handshake timeout.  The result is that the error message
sent to users informs them that the authentication timed out.  If I had
not done this, users would simply get a generic, uninformative timeout
message.

What will it take to get this patch into hardy-updates? It fixes a
crash-bug that is confusing a lot of bluetooth users.

Also, any help pushing this patch upstream would be appreciated.

This is not a terribly elegant solution; there is some room for
improvement.  Specifically, I would like to know how to programmatically
obtain the exact timeout length for the bluetooth authentication
handshake, so that I can set the dbus timeout to be 1 millisecond
longer.  (This will allow us to catch dbus errors that do not involve
bluetooth timeouts in the minimum amount of time.)  Right now, I have
just hard-coded the dbus timeout to be 5 minutes, which seems to be well
longer than the bluetooth timeout.

** Attachment added: "patch to catch bluetooth input device auth failure in bluetooth-properties"
   http://launchpadlibrarian.net/14567352/bluez-gnome-0.25__properties__input.c.patch

-- 
bluetooth-properties crashed with signal 5 while adding HID device
https://bugs.launchpad.net/bugs/179399
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-gnome in ubuntu.