Bug 6803 - update openobex to fix bluetooth file copy to smartphone
Summary: update openobex to fix bluetooth file copy to smartphone
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: MGA2TOO MGA3TOO
Keywords: Junior_job, Triaged
: 8063 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-07-17 14:41 CEST by episteme promeneur
Modified: 2015-10-27 06:56 CET (History)
1 user (show)

See Also:
Source RPM: openobex
CVE:
Status comment:


Attachments

Description episteme promeneur 2012-07-17 14:41:51 CEST
Description of problem:
unable to copy files to smartphone

Version-Release number of selected component (if applicable):

mageia 2 x86_64
bluedevil-1.3-0.rc2.1.mga2.x86_64.rpm

How reproducible:


Steps to Reproduce:
with dolphin copy files to a smartphone using bluetooth
then
the windows displaying the smartphone destination folder becomes empty
and
we don't see anything at the kde notifier. the notifier does not display any transfert progressing

after that we can't communicate again with the smartphone. we must restart the system.

we can copy files from the smartphone.

worst : one time turning off bluedevil then system switches to tty 1
i had to use Ctrl_alt_F8 to go back to kde !


another experiment with mandriva 2010.2, kde 4.8.4 and bluedevil 1.2.3 :

kernel 3.1.6 -> no pb

kernel 3.2.18 -> unable to copy files to smartphone.

it seems there is pb around the kernel.
Comment 1 episteme promeneur 2012-08-22 11:24:37 CEST
with mandriva 2010.2 and kernel 3.2.27 no pb

this confirm there is pb around the kernel
Comment 2 episteme promeneur 2012-10-09 08:11:29 CEST
1. pb

appears for all kernels >= 3.2.x

you can browse, download file, delete file but you can't upload file to your smartphone

2 solution

update openobex to 1.6 and obexdataserver to 0.4.6

see http://mib.pianetalinux.org/forum/viewtopic.php?f=20&t=3512

please supply openobex 1.6 and obexdataserver 0.4.6

thanks
Comment 3 Samuel Verschelde 2013-08-28 10:29:53 CEST
Hi,

Is that a kernel problem, a bluedevil problem or a openobex problem? (obexdataserver already has version 0.4.6)

CC: (none) => stormi

Comment 4 episteme promeneur 2013-08-28 10:54:26 CEST
sorry i don't use mageia; i just tested mageia.

the solution is in the comment 2 and for the howto follow the link
Comment 5 Samuel Verschelde 2013-08-28 11:51:12 CEST
Ok so I gather the solution yields in fixing or updating openobex. Since we also have openobex 1.5 in Mageia 3 and Cauldron I guess the problem is valid there too... So setting version to cauldron + MGA2 + MGA3.

I don't understand why you say that we must update also obexdataserver to 0.4.6 since we already have 0.4.6 though.

Keywords: (none) => Junior_job, Triaged
Version: 2 => Cauldron
Summary: mageia2, bluedevil, copy to smartphone does not work => update openobex to fix bluetooth file copy to smartphone
Source RPM: (none) => openobex
Whiteboard: (none) => MGA2TOO MGA3TOO

Comment 6 episteme promeneur 2013-08-28 12:50:36 CEST
at the date of the description of the bug, mageia didn't get obex-data-server 0.4.6
but 0.4.5

today for all openobex components the version are :

- openobex 1.7.1
- obexftp 0.24
- obexfs 0.12

see
http://sourceforge.net/projects/openobex/files/

see all the dependencies of obex-data-server here

http://www.linuxfromscratch.org/blfs/view/svn/general/obex-data-server.html

you see that openobex 1.7.1 is one of the dependencies of obex-data-server
Comment 7 Rémi Verschelde 2013-09-26 13:56:03 CEST
*** Bug 8063 has been marked as a duplicate of this bug. ***
Comment 8 Samuel Verschelde 2015-05-17 01:29:58 CEST
Probably still valid in Mageia 4 which still has openobex 1.5. Mageia 5 has a more recent version.

Version: Cauldron => 4

Comment 9 Samuel Verschelde 2015-09-21 13:19:01 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 10 Marja Van Waes 2015-10-27 06:56:28 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.