unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Meiyo Peng <meiyo@riseup.net>
Cc: 34971@debbugs.gnu.org
Subject: [bug#34971] [PATCH] gnu: Add mako.
Date: Wed, 10 Apr 2019 22:35:00 +0200	[thread overview]
Message-ID: <87sgupa9aj.fsf@gnu.org> (raw)
In-Reply-To: <87r2aauu56.fsf@riseup.net> (Meiyo Peng's message of "Wed, 10 Apr 2019 16:44:21 +0800")

Hi,

Meiyo Peng <meiyo@riseup.net> skribis:

> 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)

So I’m a bit at loss but what I can say is that /run/user/UID/bus
doesn’t seem to exist in practice.

For example, if I strace “dbus-monitor --session”, I see this:

  connect(3, {sa_family=AF_UNIX, sun_path=@"/tmp/dbus-ktJE8…"}, 23) = 0

I have no idea where this file name comes from but it seems to be
deterministic.

So… more investigation needed!

Ludo’.

  reply	other threads:[~2019-04-10 20:36 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 [this message]
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

  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=87sgupa9aj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34971@debbugs.gnu.org \
    --cc=meiyo@riseup.net \
    /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).