After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 577744 - should check supported profiles before offering devices
should check supported profiles before offering devices
Status: RESOLVED OBSOLETE
Product: gnome-bluetooth
Classification: Core
Component: sendto
2.27.x
Other All
: Normal minor
: ---
Assigned To: gnome-bluetooth-general-maint@gnome.bugs
gnome-bluetooth-general-maint@gnome.bugs
: 701278 (view as bug list)
Depends on: 578485
Blocks:
 
 
Reported: 2009-04-02 16:29 UTC by Bill Nottingham
Modified: 2019-03-20 10:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bill Nottingham 2009-04-02 16:29:13 UTC
When I choose to send files, it offers me all devices as send destination, including my phone which only supports the headset (or whatever it's called) profile.

The tool should filter the devices by what profiles they support, and only show ones where obex will work.

Other information:
gnome-bluetooth-2.27.1-4.fc11.x86_64
Comment 1 Baptiste Mille-Mathias 2009-04-02 16:42:23 UTC
confirmed
Comment 2 Bastien Nocera 2009-06-13 23:00:45 UTC
We'd need to filter devices for ObexPush based on file transfer service class. We don't export service classes right now.
Comment 3 Bastien Nocera 2013-11-13 16:13:46 UTC
*** Bug 701278 has been marked as a duplicate of this bug. ***
Comment 4 Bastien Nocera 2013-11-13 16:14:20 UTC
From the duplicate:
On bug 685717 we added a patch to only show devices that support OPP.

There are two issues at this moment:
- BlueZ isn't sending information about Services for non-paired devices
- We don't refresh the list
Comment 5 GNOME Infrastructure Team 2019-03-20 10:36:58 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-bluetooth/issues/14.