From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 48538@debbugs.gnu.org
Subject: bug#48538: D-Bus services do not work on foreign distributions/non-user profiles
Date: Thu, 20 May 2021 13:18:32 -0400 [thread overview]
Message-ID: <87wnrtxr13.fsf@gmail.com> (raw)
In-Reply-To: <8735uhzb2a.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 20 May 2021 11:20:29 -0400")
This can be verified on a system where the jami-daemon (libring) has not
yet been installed (commonly via propagation from one of the jami
clients):
$ guix environment --ad-hoc jami-gnome -- jami-gnome
Attempt to run it:
$ jami-gnome
It should fail with the following message: "Could not rec-connect to the
Jami daemon (dring). Jami will now quit."
as the currently running dbus session doesn't know about
the newly installed D-Bus service, as it only look under a few
hard-coded places.
For this particular instance, a workaround is to run jami via the
dbus-run-session utility, which launches the client in an ad-hoc d-bus
session which knows about the dring D-Bus service (through the
XDG_DATA_DIRS variable set by glib's search path).
$ guix environment --pure --ad-hoc jami-gnome dbus glib \
-- dbus-run-session jami-gnome
The glib package is added for its XDG_DATA_DIRS search path. It works
because the client doesn't really care about being able to talk to
anything else but its daemon over D-Bus.
next prev parent reply other threads:[~2021-05-20 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 15:20 bug#48538: D-Bus services not working on foreign distributions/non-user profiles Maxim Cournoyer
2021-05-20 17:18 ` Maxim Cournoyer [this message]
2021-05-27 18:54 ` bug#48538: D-Bus services do not work " zimoun
2021-05-27 19:20 ` Leo Famulari
2021-05-27 19:59 ` zimoun
2021-05-27 20:14 ` Leo Famulari
2021-05-27 23:17 ` Leo Prikler
2021-05-28 2:17 ` Maxim Cournoyer
2021-05-28 6:35 ` Leo Prikler
2021-05-28 5:10 ` Maxim Cournoyer
2021-08-17 2:57 ` bug#48538: D-Bus services not working " John Kehayias via Bug reports for GNU Guix
2021-08-17 4:32 ` John Kehayias via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnrtxr13.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=48538@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).