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 20:46:29 +0200 [thread overview]
Message-ID: <20221001184629.7PzXbzKo7VNYhObnIHhNxAHWfdwi6b1vIP0tkESuFg0@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: 908 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/39488#issuecomment-1264446947
Comment:
> If this is an error only with epiphany 43, then we don't have to fix it in this PR.
TL;DR: webkit2gtk fails to connect to dbus since it disables networking in containers and the default dbus configuration uses tmpdir which on Linux (but not BSD) defaults to abstract sockets (although there is a PR in dbus to change that). It doesn't affect distros using the systemd user init because that overrides the settings to use the filesystem instead of abstract sockets.
(This doesn't affect flatpak because flatpak creates its own socket path and uses it in the containerss which webkit2gtk is supposed to do but doesn't)
This doesn't just affect epiphany.
https://bugs.webkit.org/show_bug.cgi?id=245843
There still isn't a solution upstream unfortunately.
next prev parent reply other threads:[~2022-10-01 18:46 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 [this message]
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
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=20221001184629.7PzXbzKo7VNYhObnIHhNxAHWfdwi6b1vIP0tkESuFg0@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).