Bug 10486 - obexd: dbus service domain changed; fix needed for obexd to work
Summary: obexd: dbus service domain changed; fix needed for obexd to work
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords: PATCH, Triaged, UPSTREAM
Depends on:
Blocks:
 
Reported: 2013-06-11 09:05 CEST by Pablo Saratxaga
Modified: 2015-03-31 16:04 CEST (History)
5 users (show)

See Also:
Source RPM: obexd-0.47-2.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Pablo Saratxaga 2013-06-11 09:05:25 CEST
Description of problem:
Gnome is unable to see obexd clients, because the dbus domain changed but service file wasn't updated

Version-Release number of selected component (if applicable):
0.47-2.mga3.

How reproducible:
always

Steps to Reproduce:
1. try to send a file to a bluetooth device in Gnome
2. error message about no service providing org.openobex.client dbus 

fix:
edit 
/usr/share/dbus-1/services/obex-client.service to have Name=org.openobex.client

see also upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=682106

Reproducible: 

Steps to Reproduce:
Comment 1 Pablo Saratxaga 2013-06-11 09:06:24 CEST
add "patch" keyword: s/bluez/openobex/ :)

Keywords: (none) => PATCH
CC: (none) => pablo

Manuel Hiebel 2013-06-11 20:12:44 CEST

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

Christian Lohmaier 2013-06-30 13:25:04 CEST

CC: (none) => lohmaier+mageia

Comment 2 Colin Guthrie 2013-10-14 12:32:41 CEST
I'm quite certain that the Name=org.openobex.client is incorrect by itself. The code inside obexd itself does not mention this name at all and binds to org.bluez.obex.client as the file states.

I guess we need to revert back to obexd 46 for MGA3 Can you confirm that this works OK? I can build a test package if you like?
Comment 3 Christian Lohmaier 2013-10-14 12:43:07 CEST
willing to test - if you could provide a package, that would be appreciated.
Comment 4 Olav Vitters 2013-10-14 13:17:39 CEST
Upstream says that it needs to be downgraded.

CC: (none) => olav

Comment 5 Colin Guthrie 2013-10-14 13:51:47 CEST
OK, I've pushed a slightly hacky package to updates_testing. The version is still officially 0.47 in the package but it is 0.46 internally (I wanted to avoid epoch for now)

My main concern here is that other desktops have moved to the newer API and this update will introduce a regression for them...

Do we know if anyone else (e.g. KDE) is using the org.bluez.obex.client API?
Comment 6 Christian Lohmaier 2013-10-21 11:50:22 CEST
With the package from testing, sending files works fine (note: you need to reboot (or logout, didn't check that as I had to reboot anyway) for the changes to kick in).

I have problems receiving files though, but that might be a problem with the other device, need to double-check with more devices to be sure.
Florian Hubold 2014-02-16 19:36:04 CET

CC: (none) => doktor5000

Comment 7 Florian Hubold 2014-05-18 16:30:52 CEST
Ping? From various reports, this is still present in Mageia 4, right? Could we get the testing packages built for Mageia 4 and passed over to QA team please?
Comment 8 Julien Gouesse 2014-05-30 13:06:47 CEST
(In reply to Christian Lohmaier from comment #6)
> I have problems receiving files though, but that might be a problem with the
> other device, need to double-check with more devices to be sure.

I have problems to receive files too: https://bugs.mageia.org/show_bug.cgi?id=13447

CC: (none) => gouessej

Comment 9 Marja Van Waes 2015-03-31 16:04:09 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

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


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