Bug 12860 - bluetooth: transfer file from Phone to Laptop failed
Summary: bluetooth: transfer file from Phone to Laptop failed
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-02-23 12:34 CET by Marc Lattemann
Modified: 2015-10-27 06:59 CET (History)
2 users (show)

See Also:
Source RPM: obexd-0.48-2.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Marc Lattemann 2014-02-23 12:34:51 CET
The transfer of files from smartphone (Android 4.2.2) to Mageia 4 fails (see log file entries below). Pairing is working and also file transfer from Mageia to phone. File transfer at LinuxMint (LiveVersion) with same hardware is working as well.


output from journalctrl -fa:
Feb 23 12:11:43 Rechner systemd[1]: Reached target Bluetooth.
Feb 23 12:11:44 Rechner obexd[3053]: CONNECT(0x0), (null)(0xffffffff)
Feb 23 12:11:44 Rechner obexd[3053]: CONNECT(0x0), (null)(0x0)
Feb 23 12:11:44 Rechner obexd[3053]: PUT(0x2), (null)(0xffffffff)
Feb 23 12:11:48 Rechner obexd[3053]: open(/tmp/21168.strip.gif): Operation not permitted (1)
Feb 23 12:11:48 Rechner obexd[3053]: PUT(0x2), FORBIDDEN(0x43)
Feb 23 12:11:48 Rechner obexd[3053]: DISCONNECT(0x1), (null)(0xffffffff)
Feb 23 12:11:48 Rechner obexd[3053]: DISCONNECT(0x1), SUCCESS(0x20)
Feb 23 12:11:48 Rechner obexd[3053]: disconnected: Transport got disconnected


seems not related to permission of /tmp folder:
[root@Rechner marc]# ls -l / | grep tmp
drwxrwxrwt  19 root root    500 Feb 23 12:24 tmp/

[root@Rechner marc]# ls -l /tmp | grep gif
-rw------- 1 marc marc  0 Feb 23 12:11 21168.strip.gif


my device:
[root@Rechner marc]# lsusb | grep Blue
Bus 001 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card

Please let me know if you need more information.


Reproducible: 

Steps to Reproduce:
Marc Lattemann 2014-02-23 12:35:16 CET

CC: (none) => doktor5000, marc.lattemann

Manuel Hiebel 2014-03-03 18:33:30 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 Florian Hubold 2014-05-18 16:28:11 CEST
Is this related to or a duplicate of https://bugs.mageia.org/show_bug.cgi?id=10486 ?
Comment 2 Samuel Verschelde 2015-09-21 13:22:07 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Marja Van Waes 2015-10-27 06:59:01 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.