unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Stefanović" <stefanx2ovic@gmail.com>
To: 34971@debbugs.gnu.org
Subject: [bug#34971] [PATCH] gnu: Add mako.
Date: Tue, 23 Apr 2019 12:14:48 +0000	[thread overview]
Message-ID: <CAFBTj=jT3+T86rRuD2qQ2=qSiR8YN-K7scLq6Fno9Eb8QD2X=w@mail.gmail.com> (raw)
In-Reply-To: <20190324060845.7921-1-meiyo@riseup.net>

Hello.

AFAIK mako relies on elogind to access user DBus session daemon.

elogind relies on environment variable DBUS_SESSION_BUS_ADDRESS.
In my case DBUS_SESSION_BUS_ADDRESS is set to
"unix:path=/run/user/1000/dbus-1/session_bus_socket".

DBUS_SESSION_BUS_ADDRESS is created by user session manager.
In my case it is set in a shell script by executing:
echo "Starting user DBus session daemon."
dbus-daemon \
  --syslog --fork \
  --address="${DBUS_SESSION_BUS_ADDRESS}" \
  --print-pid --session

This is not perfect solution but it works, for now.

Please take a look at relevant elogind issue:
https://github.com/elogind/elogind/issues/87

Stefan.

  parent reply	other threads:[~2019-04-23 12:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24  6:08 [bug#34971] [PATCH] gnu: Add mako Meiyo Peng
2019-03-24  6:39 ` Meiyo Peng
2019-03-25 10:39   ` Ludovic Courtès
2019-03-25 14:35     ` Ricardo Wurmus
2019-03-25 21:24       ` Ludovic Courtès
2019-03-25 16:31     ` Meiyo Peng
2019-04-03 16:02       ` Ludovic Courtès
2019-04-10  8:44         ` Meiyo Peng
2019-04-10 20:35           ` Ludovic Courtès
2019-05-21 14:50             ` Ludovic Courtès
2019-05-23 11:24               ` Meiyo Peng
2019-05-24 15:26                 ` Ludovic Courtès
2019-04-23 12:14 ` Stefan Stefanović [this message]
2019-05-29  3:09 ` [bug#34971] [PATCH v2] " Meiyo Peng
2020-01-30 11:41   ` bug#34971: " Marius Bakke

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='CAFBTj=jT3+T86rRuD2qQ2=qSiR8YN-K7scLq6Fno9Eb8QD2X=w@mail.gmail.com' \
    --to=stefanx2ovic@gmail.com \
    --cc=34971@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).