Bug 1401094

Summary:	Receiving files through bluetooth doesn't work
Product:	[Fedora] Fedora	Reporter:	pawel.wollny
Component:	bluez	Assignee:	Don Zickus <dzickus>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	dwmw2, dzickus, marcel, piotrdrag
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:57:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description pawel.wollny 2016-12-02 19:51:02 UTC

Description of problem:

It is possible to pair a notebook Dell Latitude 5430 with an android phone Huawei Y300, however it isn't possible to send a file from phone to the notebook using bluetooth.

How reproducible:

Try to send files via bluetooth from the phone to the notebook.

Steps to Reproduce:
1. Pair devices.
2. Try to send files from the phone to the notebook.

Actual results:

An error that the file can't be send was returned on the phone.

Expected results:

On a desktop, a window with destination location of the file should be opened.

Comment 1 pawel.wollny 2016-12-05 12:29:28 UTC

The problem is solved by using the following command:

[code]systemctl --user start obex[/code]

but I guess it isn't the way it should work. Shouldn't obex service start after bluetooth adapter is turned on? Maybe just enabling this service by default should be considered.

Comment 2 Don Zickus 2016-12-05 15:13:09 UTC

Hi,

Yes, agreed.  It would be more helpful to have that work out of the box.
I need to dive into bluez history to figure out why that isn't the case
before blindly enabling it.

Cheers,
Don

Comment 3 Fedora End Of Life 2017-11-16 19:13:35 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-12-12 10:57:35 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.