RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1370420 - sending files to a Lenovo notebook via bluetooth does not work
Summary: sending files to a Lenovo notebook via bluetooth does not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-bluetooth
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 09:37 UTC by Oliver Ilian
Modified: 2017-08-01 22:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:38:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
bluetooth_debug (39.30 KB, text/plain)
2016-08-29 10:08 UTC, Oliver Ilian 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2096 0 normal SHIPPED_LIVE control-center, accountsservice, gnome-settings-daemon, libgnomekbd update 2017-08-01 19:36:13 UTC

Description Oliver Ilian 2016-08-26 09:37:59 UTC 
Description of problem:
I have tried to send a file from my Phone (Samsung Galaxy S6) to 2 different Lenovo notebooks (T430s and T460s). The phone tries to send the file but directly gets to "File not send" and the notebook does not react at all

Version-Release number of selected component (if applicable):
bluez-5.41-1.el7.x86_64
gnome-bluetooth-3.14.1-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. pair your phone with a notebook
2. send a file from your phone to the notebook


Actual results:
File is not send to notebook

Expected results:
Notebook should open a dialog to accept the file transfer and ask where to store it.
Comment 2 Don Zickus 2016-08-26 15:13:20 UTC 
Hi,

Can you adding some debug info for me.

In the file, /usr/lib/systemd/system/bluetooth.service, can you add a '-d' like below

ExecStart=/usr/libexec/bluetooth/bluetoothd -d

and the 'systemctl restart bluetooth'

and then in a shell run 'journalctl -f' (which shows the output of the bluetoothd).

Once that is setup, can you re-run your send file test?

I tried a similar test on my machine and it fails because of a timeout I believe, but on the shell I see the bluetoothd hang on a 'PUT' command.  But I connected through a 'network profile' as opposed to an 'audio profile'.  I assume you did the same?

Now, I do _not_ expect the laptop to ask for a directory or permission.  Once you have paired, it is good to go.  I believe the file gets put into '/home/<user>/.cache/obexd/' directory.

If all my instructions above work, then can you attach part of the journalctl file with the bluetoothd output?

Cheers,
Don
Comment 3 Oliver Ilian 2016-08-29 10:08:35 UTC 
Created attachment 1195303 [details]
bluetooth_debug
Comment 4 Oliver Ilian 2016-08-29 10:10:26 UTC 
I have added the debug message.

Would it be possible instead of putting the transferred file into a hidden folder (.cache) to put the files in: ~/Downloads/Bluetooth ? This would be a better place so that users can actually find the files also.
Comment 5 Don Zickus 2016-08-29 12:47:37 UTC 
Hi Oliver,

The request is being reject with 'FORBIDDEN'.  Probably a permission problem.  I need to dig around to figure out exactly what paths can cause that.

As for configuring to use something not ~/.cache, it will be a challenge as that path is hardcoded into the obexd itself.  There is no spec file magic I can apply to change that (aside from the obvious patch :-) ).

I need to keep poking at the tool.

Cheers,
Don
Comment 6 Bastien Nocera 2016-08-29 15:16:37 UTC 
(In reply to Oliver Haessler from comment #0)
> Description of problem:
> I have tried to send a file from my Phone (Samsung Galaxy S6) to 2 different
> Lenovo notebooks (T430s and T460s). The phone tries to send the file but
> directly gets to "File not send" and the notebook does not react at all

Did you set anything up on the laptop side to actually receive those? In older versions of GNOME, that should be toggling "Bluetooth file reception" in the Sharing panel. In newer versions, you'll need to keep the Bluetooth panel opened.
Comment 7 Oliver Ilian 2016-08-29 15:29:35 UTC 
I o not set up anything on the notebook side as there was no option to enable bluetooth receiving.

I tried again with the Bluetooth setting open, an get the same error.
Comment 8 Bastien Nocera 2016-08-30 08:46:22 UTC 
(In reply to Oliver Haessler from comment #7)
> I o not set up anything on the notebook side as there was no option to
> enable bluetooth receiving.

Then it's really not going to work. Is gnome-user-share installed?

> I tried again with the Bluetooth setting open, an get the same error.

Did you see a label saying that transferred files would be saved in the downloads folder, in the Bluetooth panel? If not, again, it won't do anything.
Comment 9 Oliver Ilian 2016-08-30 09:55:58 UTC 
based on here: http://koji.fedoraproject.org/koji/packageinfo?packageID=168 gnome-user-share seems to not be available for RHEL 7. I will try to install a 3.14.x version and see if this helps.

Update: installed http://koji.fedoraproject.org/koji/buildinfo?buildID=621628 and http://koji.fedoraproject.org/koji/buildinfo?buildID=562125 and that works.

So do I need to open a bug report to add gnome-user-share to RHEL 7 CSB.. or maybe we an build it in EPEL. Let me try that.
Comment 10 Bastien Nocera 2017-03-02 17:24:02 UTC 
gnome-bluetooth and control-center 3.22 in RHEL 7.4 will use bluez' obexd directly, avoiding the gnome-user-share dependency.
Comment 11 Bastien Nocera 2017-03-08 15:08:28 UTC 
Fixed in gnome-bluetooth-3.20.1-1.el7 (and the corresponding control-center-3.22.1-2.el7)
Comment 13 Pavlin Georgiev 2017-04-03 11:53:21 UTC 
TEST SETUP 1
On notebook Lenovo W541 under RHEL 7.3 Workstation x86_64,
with GNOME desktop environment.
Testing with mobile phone Xiaomi Redmi Note, OS: Android 4.4.4.
Component version:
gnome-bluetooth-3.14.1-1.el7

TEST PROCEDURE 1
1. Pair the phone with the notebook.
2. Send a photo from the phone to the notebook.
The file transfer fails.


TEST SETUP 2
On notebook HP EliteBook 8470p running under RHEL 7.4 Workstation x86_64,
with GNOME desktop environment.
Component version:
gnome-bluetooth-3.20.1-1.el7

TEST PROCEDURE 2
1. Pair the phone with the notebook.
2. Send a photo from the phone to the notebook.
The file transfer is successful.

RESULTS
Upgrading: gnome-bluetooth
from: 3.14.1-1.el7
to:   3.20.1-1.el7
has fixed the bug.
Comment 14 errata-xmlrpc 2017-08-01 22:38:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2096
Note You need to log in before you can comment on or make changes to this bug.