Bluetooth file transfer to phone fails (from both Nautilus and Bluetooth applet)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-sendto |
New
|
Undecided
|
Unassigned | ||
bluez (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
nautilus-sendto (Ubuntu) |
Incomplete
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: bluez
Ubuntu version: Intrepid
Package versions:
bluetooth: 4.12-0ubuntu2
bluez: 4.12-0ubuntu2
bluez-gnome: 1.8-0ubuntu1
obex-data-server: 0.3.4+svn1951-
Attempt to send file 1:
1. On desktop, right click on .txt file and select 'Sent To...'
2. In "Send To..." dialog, select "Bluetooth (OBEX Push)" and name of phone
3. Press "Send"
Expected:
4. File transfer dialog
Actual behaviour:
4. Error message "Obex Push file transfer unsupported"
Syslog contains:
Oct 18 14:24:00 gertrude bluetoothd[9012]: Discovery session 0xb95e50d8 with :1.597 deactivated
Oct 18 14:24:03 gertrude bluetoothd[9012]: Discovery session 0xb95e50d8 with :1.598 activated
Phone reports nothing.
Attempt to send file 2:
1. Right click on Bluetooth icon in notification area.
2. Select "Send files to device..."
3. Select .txt file in file dialog
4. Select phone in "Select Device" dialog
5. Click "Connect"
6. "File transfer" dialog opens
Expected:
7. File transfer completes, phone reports incoming file to store.
Actual behaviour:
7. File transfer remains with an empty progress bar for approximately 10 seconds. Then it reports "Error occurred" and red error text appears: "org.openobex.
Syslog contains:
Oct 18 14:27:22 gertrude bluetoothd[9012]: Discovery session 0xb95e58c8 with :1.600 activated
Oct 18 14:27:28 gertrude bluetoothd[9012]: Discovery session 0xb95e58c8 with :1.600 deactivated
Phone reports nothing.
These are regressions from Hardy, where both methods allowed successful file transfer with identical hardware on both ends.
Changed in bluez: | |
status: | Incomplete → New |
Changed in bluez: | |
assignee: | alex-mayorga → nobody |
It sounds like your device might simply not be working with any bluetooth period. Do you by chance have an input device (keyboard or mouse) that you can test with?