"browse files" on device does nothing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-bluetooth (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
I click on the Bluetooth icon on the top-right corner of the screen next to the battery icon
My mobile phone is listed in the drop down. I select it and I click on "Browse files"
Expected: a Nautilus window should appear showing the browsable contents of the device. Maybe the device should prompt me whether to allow browsing before
Observed: ABSOLUTELY NOTHING happens. The computer doesn't even try to connect to the phone. Nothing happens on the phone, nothing happens on the computer; no error message is shown anywhere, it's just as if I had done nothing.
I've done an hcidump while trying this, and it's empty.
This HAD WORKED BEFORE on the same machine and with the same device.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: bluetooth (not installed)
ProcVersionSign
Uname: Linux 3.8.0-33-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
Date: Fri Nov 22 17:53:08 2013
InstallationDate: Installed on 2013-10-11 (41 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: Acer Aspire V3-571G
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire V3-571G
dmi.product.
dmi.sys.vendor: Acer
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING PSCAN ISCAN
RX bytes:549 acl:0 sco:0 events:31 errors:0
TX bytes:1168 acl:0 sco:0 commands:31 errors:0
Changed in indicator-bluetooth (Ubuntu): | |
status: | In Progress → Confirmed |
If the bluetooth is working and recognizes your phone, then probably this bug should be reported against nautilus (browsing files via bluetooth.)