On Sat, 25 Apr 2020, Jack Hill wrote:
in Source/WebKit/UIProcess/Launcher/glib/BubblewrapLauncher.cpp of WebKitGTK,
I set the PULSE_CLIENTCONFIG environemnt variable to the store path rather
than /etc/pulse/client.conf, which is what it was set to before.
That allowed epiphany to get past the
I now think what is being shared with bubblewrap is on the write track.
After seeing
"""
const char* pulseConfig = g_getenv("PULSE_CLIENTCONFIG");
if (pulseConfig)
bindIfExists(args, pulseConfig);
"""
in Source/WebKit/UIProcess/Launcher/glib/BubblewrapLauncher.cpp of
WebKitGTK, I set the P
On Sat, 25 Apr 2020, sirgazil via Bug reports for GNU Guix wrote:
I can reproduce this bug. I can't load any page and see the same messages in
the terminal.
Thanks, as a fist step it is helpful to know that the problem can be
reproduced.
The second step is to figure out why this is happeni
I can reproduce this bug. I can't load any page and see the same messages in
the terminal.
I expericne the problem with epiphany installed both in the system profile
and in an ad-hoc environment.
Best,
Jack
Hi Guix,
On Guix System with the current core-updates branch, epiphany/GNOME-Web
starts, but doesn't work because the web process crash in a loop.
When I run epiphany from the terminal I see
"""
$ epiphany
** (epiphany:29457): CRITICAL **: 22:37:21.415: void
webkit_web_context_register_uri_
