Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: webkit2gtk: update to 2.38.0.
Date: Sat, 01 Oct 2022 21:02:26 +0200	[thread overview]
Message-ID: <20221001190226.h9jW19HRQIt2dErbPMsWpn6IiGJEKdXs4FvKpWFWlEU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39488@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/pull/39488#issuecomment-1264452354

Comment:
> Can't the socket issue be fixed with a configuration change in dbus?

Yes.
The file is `/usr/share/dbus-1/session.conf`
You can change `tmpdir=` to `dir=` and that would also workaround the issue.

  parent reply	other threads:[~2022-10-01 19:02 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  6:04 [PR PATCH] " oreo639
2022-09-27  6:19 ` [PR PATCH] [Updated] " oreo639
2022-09-27 12:18 ` [PR REVIEW] " ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 12:18 ` ahesford
2022-09-27 16:38 ` oreo639
2022-09-27 16:38 ` oreo639
2022-09-27 16:39 ` oreo639
2022-09-27 16:39 ` oreo639
2022-09-27 16:39 ` oreo639
2022-09-27 16:45 ` [PR REVIEW] " ahesford
2022-09-27 16:45 ` oreo639
2022-09-27 16:46 ` oreo639
2022-09-27 16:46 ` ahesford
2022-09-27 16:47 ` [PR REVIEW] " oreo639
2022-09-27 16:47 ` oreo639
2022-09-27 16:48 ` oreo639
2022-09-27 16:52 ` oreo639
2022-09-27 16:52 ` [PR REVIEW] " ahesford
2022-09-27 16:54 ` oreo639
2022-09-27 16:54 ` oreo639
2022-09-27 17:15 ` ahesford
2022-09-27 21:24 ` [PR PATCH] [Updated] " oreo639
2022-09-27 21:31 ` oreo639
2022-09-27 22:10 ` oreo639
2022-09-28  6:52 ` oreo639
2022-09-28  6:52 ` oreo639
2022-09-28  6:52 ` oreo639
2022-09-28  6:53 ` oreo639
2022-09-28 20:45 ` oreo639
2022-10-01 16:59 ` paper42
2022-10-01 18:29 ` oreo639
2022-10-01 18:30 ` oreo639
2022-10-01 18:30 ` oreo639
2022-10-01 18:35 ` oreo639
2022-10-01 18:40 ` oreo639
2022-10-01 18:46 ` oreo639
2022-10-01 18:47 ` oreo639
2022-10-01 18:57 ` ahesford
2022-10-01 18:59 ` oreo639
2022-10-01 19:00 ` oreo639
2022-10-01 19:00 ` oreo639
2022-10-01 19:01 ` oreo639
2022-10-01 19:02 ` oreo639 [this message]
2022-10-01 19:02 ` oreo639
2022-10-01 19:08 ` ahesford
2022-10-01 19:19 ` oreo639
2022-10-01 19:35 ` oreo639
2022-10-02  1:16 ` oreo639
2022-10-02  1:22 ` oreo639
2022-10-02 10:54 ` [PR PATCH] [Updated] " oreo639
2022-10-02 10:55 ` oreo639
2022-10-05 21:20 ` [PR REVIEW] " paper42
2022-10-05 21:20 ` paper42
2022-10-05 21:20 ` paper42
2022-10-05 21:20 ` paper42
2022-10-05 21:20 ` paper42
2022-10-05 22:23 ` ahesford
2022-10-05 22:27 ` paper42
2022-10-08  2:38 ` oreo639
2022-10-08  2:38 ` oreo639
2022-10-08  2:49 ` [PR PATCH] [Updated] " oreo639
2022-10-21  0:29 ` paper42
2022-10-21  4:55 ` [PR PATCH] [Updated] " oreo639
2022-10-21  4:56 ` oreo639
2022-10-21  4:57 ` [PR PATCH] [Updated] " oreo639
2022-10-21  5:08 ` webkit2gtk: update to 2.38.1 oreo639
2022-10-21  9:48 ` [PR PATCH] [Merged]: " paper42

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=20221001190226.h9jW19HRQIt2dErbPMsWpn6IiGJEKdXs4FvKpWFWlEU@z \
    --to=oreo639@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 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 NNTP newsgroup(s).