From: Meiyo Peng <meiyo@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34971@debbugs.gnu.org
Subject: [bug#34971] [PATCH] gnu: Add mako.
Date: Wed, 10 Apr 2019 16:44:21 +0800 [thread overview]
Message-ID: <87r2aauu56.fsf@riseup.net> (raw)
In-Reply-To: <87k1gbrs9u.fsf@gnu.org>
Hi Ludovic,
Ludovic Courtès writes:
> Meiyo Peng <meiyo@riseup.net> skribis:
>
>> Ludovic Courtès writes:
>>
>>> Meiyo Peng <meiyo@riseup.net> skribis:
>>>
>>>> If you have trouble running mako and mako gives you an error message
>>>> like:
>>>>
>>>> #+begin_example
>>>> Failed to connect to user bus: No such file or directory
>>>> #+end_example
>>>
>>> I would expect Mako to automatically spawn the D-Bus user bus if it’s
>>> not already needed, no? We don’t need to do anything special with other
>>> D-Bus applications AFAIK.
>>
>> Yeah. I expect that too. I am not sure why mako is so special. mako
>> uses the sd-bus library of systemd/elogind instead of libdbus. Do you
>> think that could be the cause?
>
> Could you check with ‘strace’ whether it tries to connect to
> /run/dbus/system_bus_socket instead of /var/run/dbus/system_bus_socket?
I get this output from `strace mako`:
#+begin_example
...
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
getsockopt(3, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
setsockopt(3, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0
getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
setsockopt(3, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0
connect(3, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 21) = -1 ENOENT (No such file or directory)
close(3) = 0
write(2, "Failed to connect to user bus: N"..., 57Failed to connect to user bus: No such file or directory
) = 57
exit_group(1) = ?
+++ exited with 1 +++
#+end_example
It tries to connect to /run/user/1000/bus.
And that error message is from
https://github.com/emersion/mako/blob/master/dbus/dbus.c:
#+begin_src c
ret = sd_bus_open_user(&state->bus);
if (ret < 0) {
fprintf(stderr, "Failed to connect to user bus: %s\n", strerror(-ret));
goto error;
}
#+end_src
--
Meiyo Peng
https://www.pengmeiyu.com/
next prev parent reply other threads:[~2019-04-10 8:45 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 [this message]
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ć
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2aauu56.fsf@riseup.net \
--to=meiyo@riseup.net \
--cc=34971@debbugs.gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.