All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erfaun Atabakhsh <eatabakhsh04@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Erfaun Atabakhsh <eatabakhsh04@gmail.com>
Subject: [PATCH] obexd: launch obexd directly from dbus service
Date: Tue, 28 Feb 2023 23:02:42 -0600	[thread overview]
Message-ID: <20230301050242.47225-1-eatabakhsh04@gmail.com> (raw)

Whenver obexd is summoned via dbus with the systemdservice file, the
daemon exits with the following error: Failed to start org.bluez.obex service: Process org.bluez.obex exite.
Irregardless of obex.service is enabled and running in the background,
whenver an app calls for obexd via dbus, it seems like it forces to use
the systemdservice, and that for whatever reason doesn't work.

Therefore, I propose instead of having systemd launch obexd, obexd
should be launched directly from the dbus service. Using this patch has
fixed all of my woes described in https://bugs.kde.org/show_bug.cgi?id=464929#c3
, and has worked both on KDE and GNOME. This is my first email patch, so
I look forward to you all's feedback and critical response!
---
 obexd/src/org.bluez.obex.service | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/obexd/src/org.bluez.obex.service b/obexd/src/org.bluez.obex.service
index a53808884..efbd8f1d9 100644
--- a/obexd/src/org.bluez.obex.service
+++ b/obexd/src/org.bluez.obex.service
@@ -1,4 +1,3 @@
 [D-BUS Service]
 Name=org.bluez.obex
-Exec=/bin/false
-SystemdService=dbus-org.bluez.obex.service
+Exec=/usr/lib/bluetooth/obexd
-- 
2.39.2


             reply	other threads:[~2023-03-01  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  5:02 Erfaun Atabakhsh [this message]
2023-03-01  6:13 ` obexd: launch obexd directly from dbus service bluez.test.bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230301050242.47225-1-eatabakhsh04@gmail.com \
    --to=eatabakhsh04@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.